Expose allowed values for app settings exposed as enum types #160
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.
See datalust/seq-tickets#1029
Allow Seq apps to use enum types for settings, which the Seq UI can expose as a select list.
The two components of the change are:
inputType: Select
andallowedValues
in the definition format:and 2., support for conversion from string values such as
"Tcp"
back to enum members when initializing the app object.The change is implemented in such a way that the Seq.Apps package doesn't immediately need an update: app authors opt in by using enum types for app settings. Seq versions prior to 2020.5 won't be able to load these, however, so widely-used public apps will only be realistically able to depend on this after a transition period (perhaps, 6-12 months).