Skip to content

Commit 2883aac

Browse files
authored
Merge branch 'main' into fix/faq-merge-info
2 parents ef6085f + 16ff158 commit 2883aac

File tree

11 files changed

+283
-189
lines changed

11 files changed

+283
-189
lines changed

docs/ff-concepts/adding-customization/custom-code.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ While FlutterFlow provides a wide range of pre-built components and functionalit
1414
times when you need to extend your app with custom logic or UI components that are not available out of the box.
1515
This is where writing custom code comes into play.
1616

17-
There are a few different ways to make custom code accessible in FlutterFLow:
17+
There are a few different ways to make custom code accessible in FlutterFlow:
1818

1919
* **[Custom Functions](custom-functions.md):** Custom Dart functions that can be used to set Widget or Action properties.
2020
* **[Custom Actions](custom-actions.md):** Custom Dart functions that can be triggered by [Action Triggers](https://docs.flutterflow.io/resources/functions/action-triggers/) or used as nodes in an [Action Flow](https://docs.flutterflow.io/resources/functions/action-flow-editor#action-flow-editor). These are usually `async` functions and are able to import [custom package dependencies](#adding-a-pubspec-dependency).
@@ -522,4 +522,4 @@ If any project errors related to packages arise, they will be displayed in both
522522
allow="clipboard-write">
523523
</iframe>
524524
</div>
525-
<p></p>
525+
<p></p>

docs/ff-concepts/design-system/design-system.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -836,7 +836,7 @@ If you prefer watching a video tutorial, here is the guide for you:
836836

837837
Creating a theme for widgets ensures that your app looks consistent and has a cohesive design. The Theme widgets can be reused, making it easy to update the styles of your app. If you decide to change any property of the widget, such as color scheme or fonts, you can update the theme widget instead of going through every widget individually. This can save a lot of time and effort, especially in larger projects.
838838

839-
For example, creating theme widgets for different types of buttons such as 'primary_button', 'secondary_button', and 'tertairy_button' with specific attributes like width, color, icon, border radius, and padding. Then, these widgets can be directly added to a page or applied to an existing widget.
839+
For example, creating theme widgets for different types of buttons such as 'primary_button', 'secondary_button', and 'tertiary_button' with specific attributes like width, color, icon, border radius, and padding. Then, these widgets can be directly added to a page or applied to an existing widget.
840840

841841
### Adding theme widgets
842842

docs/generated-code/ff-app-state.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,15 +34,14 @@ class FFAppState extends ChangeNotifier {
3434
notifyListeners();
3535
}
3636

37-
// App State variable of primitive type with a getter and setter
38-
bool _enableDarkMode = false;
37+
// App State variable of primitive type with a getter and setter
38+
bool _enableDarkMode = false;
3939

40-
bool get enableDarkMode => _enableDarkMode;
40+
bool get enableDarkMode => _enableDarkMode;
4141

42-
set enableDarkMode(bool value) {
42+
set enableDarkMode(bool value) {
4343
_enableDarkMode = value;
44-
}
45-
44+
}
4645
}
4746
```
4847

@@ -52,7 +51,7 @@ The `_enableDarkMode` is an App State variable created by developer that creates
5251
When updating an `AppState` variable from the Action Flow Editor, you will be presented with several **[update type](../resources/data-representation/app-state.md#update-type)** options such as **Rebuild All Pages**, **Rebuild Current Page**, and **No Rebuild** in the Action Settings. Let's see how the generated code changes when these options are selected.
5352

5453
### Rebuild Current Page
55-
When a developer chooses to update App State with the update type set to **Rebuild Current Page**, the corresponding `setter` is called. Immediately after, `setState((){});` is invoked, which updates only the current page.
54+
When a developer chooses to update App State with the update type set to **Rebuild Current Page**, the corresponding `setter` is called. Immediately after, `setState(() {});` is invoked, which updates only the current page.
5655

5756
Here's an example of the generated code when we update the App State `enableDarkMode` in the `onInitialization` action trigger of the `ProductListPage`.
5857

@@ -90,7 +89,7 @@ Only the setter is called with no setState or update method invoked afterward. T
9089
When you add an [**Update App State**](../resources/data-representation/app-state.md#update-app-state-action) action via the Action Flow Editor, the corresponding pages will include this line within the build method:
9190
9291
```js
93-
@override
92+
@override
9493
Widget build(BuildContext context) {
9594
context.watch<FFAppState>();
9695
...
@@ -155,4 +154,4 @@ These functions are automatically generated to provide a convenient and consiste
155154
156155
:::info[How to create App State variables]
157156
To learn more about creating and using App State variables in FlutterFlow's UI, check out the[ **App State**](../resources/data-representation/app-state.md) guide.
158-
:::
157+
:::
135 KB
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.

0 commit comments

Comments
 (0)