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
Motivation: Why do you think this is important?
Related to - #654
Now that Generic Structs can have Schema associated with them optionally, it would be useful for the users of FlyteConsole - LaunchForm to launch an execution where for structure types, the UX is auto-generated
An ideal example for the UX could be to follow the VS code style - type-ahead JSON editor as shown here
OR
an auto-generating form like here
This makes the users like extremely easy to structured data. This is extremely useful for Hyper parameter tuning, node-code tasks, configuration etc
Goal: What should the final outcome look like, ideally?
Users should be able to enter valid json instead of arbitrary json
[Optional] Propose: Link/Inline OR Additional context AND/OR Mock ideas
[WIP]
The text was updated successfully, but these errors were encountered:
kumare3
added
enhancement
New feature or request
ui
Admin console user interface
untriaged
This issues has not yet been looked at by the Maintainers
and removed
untriaged
This issues has not yet been looked at by the Maintainers
labels
Jul 7, 2021
@jsonporter the doc for the json-schema update can be found here.
In short the schema for a json value is optional. But, when it is available it will be in a standardized jsonschema format (a closure with all entities described in the same schema). The schema is available in the LiteralType.metadata field.
Motivation: Why do you think this is important?
Related to - #654
Now that Generic Structs can have Schema associated with them optionally, it would be useful for the users of FlyteConsole - LaunchForm to launch an execution where for structure types, the UX is auto-generated
An ideal example for the UX could be to follow the VS code style - type-ahead JSON editor as shown here
OR
an auto-generating form like here
This makes the users like extremely easy to structured data. This is extremely useful for Hyper parameter tuning, node-code tasks, configuration etc
Example for workflow in flytesnacks https://github.com/flyteorg/flytesnacks/blob/master/cookbook/core/type_system/custom_objects.py
Goal: What should the final outcome look like, ideally?
Users should be able to enter valid json instead of arbitrary json
[Optional] Propose: Link/Inline OR Additional context AND/OR Mock ideas
[WIP]
The text was updated successfully, but these errors were encountered: