Conversation
…ramPlugin and standalone usePlugin config settings
…onfig.ttl and jenatestconfig.ttl
…st in config.ttl.dist
…Ls in config.ttl.dist
|
joelit
left a comment
There was a problem hiding this comment.
Looks good so far! This would also be a golden opportunity to streamline the new and deprecated configuration parameters into one - now it's two separate boolean properties skosmos:showChangeList & skosmos:showDeprecatedChanges where the former has to be set to true if the latter is to be used.
Would it be more concise if it was skosmos:showChangeList "new|new and deprecated|false"? Then again, the clear naming convention is not straight forwad and it's possible the current way is better.
This is no longer the case with Skosmos 3.
|



Reasons for creating this PR
Some Skosmos configuration parameters are redundant or badly named. With the upcoming release of Skosmos 3, we can clean up some of this legacy. See #1793
Link to relevant issue(s), if any
Description of the changes in this PR
skosmos:uiHoneypotEnabledtoskosmos:feedbackHoneypotEnabled(the ui is misleading)skosmos:uiHoneypotTimetoskosmos:feedbackHoneypotTime(the ui is misleading)skosmos:useParamPluginand standaloneskosmos:usePlugin; all configuration is now done usingskosmos:globalPluginsandskosmos:vocabularyPluginsskosmos:showChangeListandskosmos:fullAlphabeticalIndexfrom the config files used in unit testsconfig.ttl.dist; also change HTTP URLs to HTTPS for public SPARQL endpoints and vocabulary downloads in the fileNote: I've created a new wiki page Configuration for Skosmos 3 (+ added it to the wiki sidebar) and rewritten the section on Enabling Plugins in the wiki page Plugins for Skosmos 3 to match this PR.
Known problems or uncertainties in this PR
Not sure about
skosmos:logCaughtExceptions. Is it still useful? Should it be dropped?I have a feeling that there could be other configuration options that are no longer relevant for Skosmos 3, but it's hard to tell...
Checklist
.sr-onlyclass, color contrast)