Skip to content

Commit 2edb3c0

Browse files
authored
Merge branch 'main' into fix/notification-info
2 parents d5886bf + c7a4980 commit 2edb3c0

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

docs/resources/control-flow/user-interactivity/forms/form-widgets/text-field.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -538,7 +538,7 @@ Enabling this feature will refresh the page whenever a user types into TextField
538538
Here's an example of displaying the TextField value in a Text widget in realtime:
539539

540540
1. Select the TextField widget, move to the **Properties Panel** **> Additional Properties >** enable the **Update Page On Change** property.
541-
2. Also, set the **Update Delay (ms)** after which the page will refresh its UI when the user has stopped typing. For example, If the *Update Delay (ms)* value is set to 2000 ms (2 seconds), The page will update 2 seconds after use is done typing. For this example, let's keep it to 0.
541+
2. Also, set the **Update Delay (ms)**, which specifies the time interval after the user stops typing before the page refreshes its UI. For example, if the *Update Delay (ms)* value is set to 2000 ms (2 seconds), the page will update 2 seconds after the user stops typing. For this example, let's set it to 0 ms.
542542
3. Now select the **Text** widget, move to the **Properties Panel > Set from Variable > Widget State > [TextFieldName]**. Tip: You can also set the default value to be displayed until the user has entered any text.
543543

544544
:::tip
@@ -1037,4 +1037,4 @@ If you prefer watching a video tutorial, here's the one for you:
10371037
allow="clipboard-write">
10381038
</iframe>
10391039
</div>
1040-
<p></p>
1040+
<p></p>

docs/resources/style-guide.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ Best practices for naming conventions in app development (especially for project
1414

1515
Various naming styles (as suggested by [Dart Effective Style Guide](https://dart.dev/effective-dart/style#identifiers)):
1616

17-
- **UpperCamelCase** names capitalize the first letter of each word, including the first.
17+
- **UpperCamelCase** (also known as PascalCase) names capitalize the first letter of each word, including the first.
1818

19-
- **lowerCamelCase** names capitalize the first letter of each word, except the first which is always lowercase, even if it's an acronym.
19+
- **lowerCamelCase** (also known as camelCase) names capitalize the first letter of each word, except the first which is always lowercase, even if it's an acronym.
2020

21-
- **lowercase_with_underscores** names use only lowercase letters, even for acronyms, and separate words with _.
21+
- **lowercase_with_underscores** (also known as snake_case) names use only lowercase letters, even for acronyms, and separate words with _.
2222

2323
![various-naming-styles.png](imgs/various-naming-styles.png)
2424

@@ -140,4 +140,4 @@ Custom functions and custom actions created in the Custom Code tab of FlutterFlo
140140
- **Don’t use overly generic names:** Avoid vague terms like `doSomething` or `functionOne`, which don’t provide context.
141141
:::
142142

143-
Note that **[Action Blocks](../resources/control-flow/functions/action-blocks.md)** should follow the same naming convention as custom actions, as they are both technically Dart functions internally in the generated code.
143+
Note that **[Action Blocks](../resources/control-flow/functions/action-blocks.md)** should follow the same naming convention as custom actions, as they are both technically Dart functions internally in the generated code.

0 commit comments

Comments
 (0)