-
Notifications
You must be signed in to change notification settings - Fork 160
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
enable tag vocabularies #116
Conversation
@@ -449,5 +500,6 @@ def _expand_schemas(schemas): | |||
if fname not in s: | |||
continue | |||
s[fname] = [_expand_preset(f) for f in s[fname]] | |||
s[fname] = [_expand_vocabulary(f) for f in s[fname]] |
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.
This means vocabulary choices are expanded into the schema once on startup, so the server needs to be restarted if the vocabulary tags are modified?
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.
That is correct. I figure its better than talking to the database in each request.
This is problematic on a more fundamental level because initialization of a fresh db fails upon trying to |
provides the property
"vocabulary"
, the value of which is the name of the vocabulary.Example:
provides the property
"free_tags_only"
in the top level of the schema definition."free_tags_only": true
will prevent vocabulary tags from being listed in the free tags' display.Currently tested with presets
select
andmultiple_select
.