-
Notifications
You must be signed in to change notification settings - Fork 95
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
Issue #737 sorting concept property values correctly #741
Conversation
…ation is true, fixes #737
…ed PHP 7.2+ build test
…vis-new-php-versions
…ures on 7.2 & fuseki SNAPSHOT
If additional fields are requested using the 'fields' parameter, add them to the JSON-LD context. Note: This will break any implementation that relies on the 'skos:' prefix being part of the keys.
…osmos into danmichaelo-test-relatedmatch
…ail optional. Fixes #761
…ific recipient has been set. Fixes #761
The cache that was created in the Model instance, now was moved to the GlobalConfig, but is still accessed from Model to add entries looked up. There is no more need of a separate .ttl file for vocabularies, as it is now part of the configuration file. Old files were removed. In order to maintain backward compatibility, most methods of GlobalConfig and of VocabularyConfig were maintained as-is. With internal changes to re-route requests to the right RDF objects. Tests were minor updates in tests, but only to replace .inc by .ttl or fix coverage annotations.
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.
I don't like the variable name $notsort
- it could perhaps be renamed to the more verbose $sort_by_notation
- but other than that, looks good!
…i/Skosmos into henriyli-henriyli-notsort-fix-737
There's a lot of clutter in the commit history. I will do a manual rebase before merging to verify that only the intended changes are included. |
Merged after manual rebase. Thanks! |
Using natural case sort for sorting concept property values when sortByNotation is true, fixes issue #737.
This PR should undo the damage done in the previous bug fix. I had to add an extra parameter for the ConceptProperty constructor. Is this ok or should the vocabulary configuration value be passed some other way?