The contact email, repository, social media links, etc.
The ordering and grouping of parameters
parameter tooltip descriptions
parameter display names
Parameter Display
The UI only displays parameters specified in theLatchMetadata object:
metadata.parameters must be the name of one of the parameters of the workflow function. Other keys will be ignored. Parameters without a corresponding key in metadata.parameters will not be displayed.
{class}~latch.types.metadata.LatchParameterspecifies the metadata associated with each workflow parameter.{class}~latch.types.metadata.LatchAuthordescribes information about the workflow author.{class}~latch.types.metadata.LatchRuledescribes the rule that the parameter input must follow.
Custom Parameter Layout (Flow)
By default, parameters are displayed in a flat list, in the order in which they are declared in the metadata. For more complex workflows it is often better to specify a custom layout, known as a “flow”. The custom layout is defined using theflow parameter of the {class} ~latch.types.metadata.Metadata specification, which is a list of flow elements. Some flow elements can have child flows. All flow elements can be arbitrarily nested.
Flow Elements
{class}~latch.types.metadata.Paramsis the most basic flow element which displays the specified parameter widgets one after another. A parameter can be part of any number of{class}~latch.types.metadata.Paramselements. The default workflow layout is equivalent toflow=[Params("first_param", "second_param", ...)]{class}~latch.types.metadata.Titleand{class}~latch.types.metadata.Textare decorative flow elements that display a string of title and body text respectively. These elements have full markdown support. They are most often used to explain a parameter or group parameters without cluttering the UI as much as a{class}~latch.types.metadata.Section{class}~latch.types.metadata.Sectiondisplays a child flow in a card with a given title. This is the basic building block of most UIs{class}~latch.types.metadata.Spoilerdisplays a child flow in a collapsible card with a given title. The spoiler is collapsed by default. This is often used for hiding away parts of the UI that will not be useful to the majority of users{class}~latch.types.metadata.Forkshows a set of mutually-exclusive alternatives. The alternatives are specified as a list of{class}~latch.types.metadata.ForkBranch, each of which displays a child flow when active and nothing otherwise. Each branch is identified by a unique key. This key is passed to the workflow is astr-typed parameter so the user selection can be used to change runtime behavior