Format Solr schema.xml using update-fields.sh on Linux #11135
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pdurbin
added
Size: 0.5
sekmiller
approved these changes
Jan 22, 2025
ofahimIQSS
reviewed
Jan 22, 2025
Co-authored-by: Omer Fahim <[email protected]>
|
Proofread, no issues to report. Merging PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
We need a consistent way to format our Solr schema.xml file. If we have some people using Mac and others using Linux, the
git diffoutput will be harder to read due to sorting differences.Which issue(s) this PR closes:
Special notes for your reviewer:
I used this procedure to update schema.xml in the following PR (which has already been merged):
Suggestions on how to test this:
Try the steps documented in this PR.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No.
Is there a release notes update needed for this change?:
No, this is dev territory.
Additional documentation:
None.