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
Initially, we considered separating each module type from the beginning, but after some discussions, we decided to put everything inside the same section, called “Modules”. Now, Modules will be an official concept for users as well.
Changes:
New group called Modules (as we have Pages in applications). Clicking there, we open a menu with three options (Query Modules, JS Modules, and UI Modules soon)
When users add a Query Module, we add it to the Modules section with the Datasource icon (not the purple module icon as we have now). If users add a JS Module, we add it to the Modules section with the JS icon. Later, when users add a UI Module, we add it to the Modules section with the UI Module icon (since we don't have an icon for UI).
JS Modules will work like Pages: when users create a reusable JSObject, we automatically create the main.js file (its name cannot be changed) which is the exposed object of that JSObject. Although main.js file is visible to users, in the consumer file of that JS Module, they will use JSModuleName.function(x,y).
Initially, we considered separating each module type from the beginning, but after some discussions, we decided to put everything inside the same section, called “Modules”. Now, Modules will be an official concept for users as well.
Changes:
info described here.
Design:
Zeplin: https://zpl.io/llz7QxD
Figma
The text was updated successfully, but these errors were encountered: