The Tangerine Form Developers' Cookbook¶

Examples of various recipes for Tangerine Forms collected throughout the years. To create your own example, remix the example on glitch.com.

Skip a question based on input in another question¶

In the following example we ask an additional question about tangerines if the user indicates that they do like tangerines.

Run example

Skip sections based on input¶

In the following example, wether or not you answer yes or no to the question, you will end up on a different item.

Run example

Valid by number of decimal points¶

In the following example, we validate user input by number of decimal points.

Run example

Valid if greater or less than other input¶

Run example

Allowed date range based on today¶

Run example

Flag choice as discrepancy and/or warning and show or hide content depending¶

Run example

Indicate a mutually exclusive option in a checkboxes group such as "None of the above"¶

In the following example when you make a selection of a fruit and then choose one of the mutually exclusive options, your prior selections will be deselected.

Run example

Capture and show local date and time¶

Sometimes we want to show the user the local date and time to ensure their time settings are correct.

Run example

Show a timer in an item¶

Let's say you want to show a timer of how long someone has been on a single item. This calculates the time since item open and displays number of seconds since then in a tangy-box.

Run example

Capture the time between two items¶

Sometimes we want to know how much time passed between two points in a form. This example captures, the start_time variable on the first item, then end_time on the last item. Lastly it calculates the length of time.

Run example

Hard checks vs. soft checks¶

A "hard check" using "valid if" will not allow you to proceed. However a "soft check" using "warn if" will allow you to proceed after confirming.

Run example

Set selected value in radio buttons¶

In the following example we set the value of a <tangy-radio-buttons>.

Run example

Dynamically prevent proceeding to next section¶

In the following example hide the next button given the value of some user input.

Run example

Proactive input validation¶

In the following example we validate an input after focusing on the next input. This approach is more proactive than running the validation logic when clicking next or submit.

Run example

Content Box with Tabs¶

In the following example we display content in a set of tabs.

Run example

Dynamic Changing of Text Color¶

In the following example we change the color of text depending on a user's selection.

Run example

Use skip-if to reference variable inside tangy-inputs-group¶

In the following example a skip-if refers to an other variable local to the group itself is in. The trick is using backticks around the variable name (not quotes) you are referencing and prepending the variable name you are referencing with ${context.split('.')[0]}.${context.split('.')[1]}..

Run example

Use valid-if to reference variable inside tangy-inputs-group¶

In the following example a valid-if refers to an other variable local to the group itself is in. The trick is using backticks around the variable name (not quotes) you are referencing and prepending the variable name you are referencing with ${input.name.split('.')[0]}.${input.name.split('.')[1]}.. Watch out for the gotcha of not using input.name instead of context like we do in a skip-if.

Run example

Dynamic Location Level¶

In the following example we empower the Data Collector to select which Location Level at which they will provide their answer. This example can also be used in a more advanced way to base the level of location required for entry given some other set of inputs.

Run example

Prevent user from proceeding during asynchronous logic¶

Sometimes in a form the logic calls for running some code that is asynchronous such as database saves and HTTP calls. As this logic runs, we would like to prevent the user from proceeding in the form. This is a job for a <tangy-gate>. Tangy Gate is an input that by default will not allow a user to proceed in a form. The gate can only be "opened" by some form logic that set's that Tangy Gate's variable name's value to true. This gives your logic in your forms an opportunity to run asynchronously, blocking the user from proceeding, then when async code is done your code sets the the gate to open.

Run example