-
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
Make it possible to define order of plugins in configuration #1201
Conversation
…he concept page deleted
…es on the concept page if it is set up to be shown. A default value for showing the notation is 'true'
…ster the master branch
…t only helps keep the code safe.
… the concept page
…oved to the more reasonable location in the class
Codecov Report
@@ Coverage Diff @@
## master #1201 +/- ##
============================================
- Coverage 68.71% 68.58% -0.14%
- Complexity 1598 1630 +32
============================================
Files 32 32
Lines 3929 3995 +66
============================================
+ Hits 2700 2740 +40
- Misses 1229 1255 +26
Continue to review full report at Codecov.
|
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.
Some minor comments on files, looks otherwise very good!
Ps. the starting post could be updated to link to the issue this is fixing.
…ab-id-not-found Avoid uncaught fatal errors in REST API if vocabulary ID not found
…bFi/Skosmos into issue1148-order-of-plugins
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
This fixes only a part of the issue #1148. Vocabulary-specific plugins can be configured and listed with skosmos:vocabulyPlugins, but the order listed in that property is changed when plugins are loaded. Therefore the issue is reopened. |
Changes into function and variable names ii VocabularyConfig.php :
Fixes #1148