UP-5008: Convert FragmentDefinition.index (which no longer exists, r… #1155
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.
…eally) to FragmentDefinition.id
https://issues.jasig.org/browse/UP-5008
Checklist
Description of change
Pre-JPA DLM used to track the 'index' of a FragmentDefinition – meaning the position of the fragment within the XML config file. In modern DLM the file is gone, but the field is still there (and it always has a value of 0).
This discrepancy doesn't seem to have a significant negative impact on the portal, but should be cleaned up.