-
-
Notifications
You must be signed in to change notification settings - Fork 45
Springcleaning 2020 #432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Springcleaning 2020 #432
Conversation
…umentation into springcleaning-2020
close #32
they are fully working
@wolfgangmm please review close eXist-db#241
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor stylistic comments, otherwise good to go.
One side note for the future, it would simplify review greatly to keep the prettyfing changes (like whitespace) in a separate PR to make review easier. Many thanks though for the springcleaning effort!
…umentation into springcleaning-2020
ea06b1a
to
290af25
Compare
Thank you for the speedy reviews, while i was still working on this. I have incorporated your comments. @joewiz schematron is not available for now, if we need to extend the new schema rules beyond the abilities of relaxng we should do so via the test-suite.xql. @tuurma yes while you can choose not to display whitespace changes in the review options on Github, this is what it is. We are now linting all listings during build, we could extend that to articles, which would make review easier, but last time i suggested that there was some pushback. So maybe something for the community call. mic drop |
add test close eXist-db#308 close eXist-db#437
8624887
to
63b2a4b
Compare
smokey says: "only you can prevent the docs from getting out of date"