Fix for list pages not reading rdfs:member & /object page links not rendering properly #130
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
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.
Some intermediate code was left behind while transitioning to using a new helper function
getObjects()which accepts a list of multiple predicates for ease of use. Currently, feature collections & features are not rendered on list pages. This is now fixed by using the newgetObjects()function.Also, objects on the
/objectpage were not rendering links correctly if they had multiple links. The current logic was that links for parent objects may have included theprez:linkfor the focus object. This is now fixed with an extra filter condition.