You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to support / differentiate text variables between simple one-line inputs and multi-line textareas in the schema. (See original request for support in Seqera Platform launch page).
Need to figure out what the best JSON schema syntax is first. Suggestions from Slack discussion:
minLength
New format type textarea
Using a pattern that includes zero or more \n newlines
Once we agree on such a flag we can detect it in the launch form and have an option / docs for it in the schema builder.
The text was updated successfully, but these errors were encountered:
It would be great if the schema included an optional configuration to specify the desired height of the box (like rows) when defining multi-line text areas.
I can see a number of use cases where the text area can be small and others where it should be bigger for it to be useful.
It would be nice to support / differentiate text variables between simple one-line inputs and multi-line textareas in the schema. (See original request for support in Seqera Platform launch page).
Need to figure out what the best JSON schema syntax is first. Suggestions from Slack discussion:
minLength
format
typetextarea
pattern
that includes zero or more\n
newlinesOnce we agree on such a flag we can detect it in the launch form and have an option / docs for it in the schema builder.
The text was updated successfully, but these errors were encountered: