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
Copy file name to clipboardExpand all lines: docs/intro/ff-ui/resource-hierarchy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ You can add a description for each of the following resources in FlutterFlow:
59
59
-**Data Type**: Summarizes the purpose of a custom data model. Example: "Represents a user’s order including items, total cost, and status."
60
60
-**Parameters**: Provide context for how a parameter is used, including expected data types or value ranges. Example: "String to store the user’s phone number—must include country code."
61
61
-**Page/Component State Variables**: Clarify what state data is being stored and why. For instance, "Tracks the currently selected tab in this component."
62
-
-**App State Variables**: Describe the global data shared across pages. Example: “Stores the user’s authentication token for all network requests”.
62
+
-**App State Variables**: Describe the global data shared across pages. Example: "Stores the user’s authentication token for all network requests".
63
63
-**Constant**: Add the intended purpose of any fixed value used throughout the app. Example: "Base API URL for all network calls".
64
64
-**Enum**: Provide a rationale for the enumerated values. Example: "Defines possible user roles—admin, editor, viewer".
65
65
-**Firestore Collection**: Explain what data the collection holds and how it relates to your app’s functionality. Example: "Stores all user profiles with fields for name, email, and profile photo URL".
0 commit comments