Skip to content

Commit b8353d8

Browse files
authored
Merge branch 'main' into rewrite/media-management
2 parents 5a6d29e + 1ac0836 commit b8353d8

File tree

3 files changed

+67
-11
lines changed

3 files changed

+67
-11
lines changed

docs/ff-integrations/firebase/connect-to-firebase-setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -168,9 +168,9 @@ com/embed/1abddd1120db477da2c085dbc6b7a742?sid=5b161c8b-3957-4ac9-b27f-dc5ebc03f
168168

169169

170170

171-
## Enable Billing for Cloud Functions Access
171+
## Enable Billing
172172

173-
If you want to deploy functions (e.g., Braintree payments, Push Notifications), you will need to enable billing for your Firebase project. Please follow these steps to enable billing:
173+
If you want to deploy [Cloud Functions](https://firebase.google.com/products/functions) (e.g., Braintree payments, Push Notifications) or use [Firebase Cloud Storage](https://firebase.google.com/products/storage), you will need to enable billing for your Firebase project. Please follow these steps to enable billing:
174174

175175
1. From the Firebase dashboard of your project, navigate to the far left menu. Under Build, select **Functions** and then select **Upgrade project**.
176176

docs/resources/data-representation/global-properties.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ A list of all the available global properties is as follows:
3333

3434
- **Current Device Location:** Obtains he user's current location, ideal for updating their position on Google Maps or storing it in a backend database. [Check out examples](#current-device-location) on how to retrieve and save the current device location.
3535

36-
- **Link To Current Page:** Provides the deep link of the current page. Learn more about [adding deep links here](../../ff-concepts/navigation-routing/deep-dynamic-linking.md#adding-deep-link).
36+
- **Current Route Path**: Provides the route name of the currently active or visible page in your app. This property is especially helpful in scenarios where you want to adjust or block specific actions if the active page isn't the one you expect. For example, if you launch the app through a push notification, the home page might still run in the background, even if the notification directs you to a different page. Using this property, you can prevent unnecessary action triggers, such as On Page Load from the home page. See details on avoiding [this issue](https://github.com/FlutterFlow/flutterflow-issues/issues/2765#issuecomment-2598915946).
3737
- **Fraction of Screen Width:** Determines the proportional width of the device's screen.
3838
- **Fraction of Screen Height:** Determines the proportional height of the device's screen.
3939
- **Screen Width:** Provides the total width of the current device's screen in pixels.
@@ -45,7 +45,7 @@ A list of all the available global properties is as follows:
4545
- **Is Dark Mode:** Checks if the app's current theme mode is set to dark.
4646
- **Is Light Mode:** Checks if the app's current theme mode is set to light.
4747
- **Is On-Screen Keyboard Visible:** Checks if the on-screen or soft keyboard is visible. This is helpful in making UI adjustments if keyboard is visible on screen. See a [quick example](#is-on-screen-keyboard-visible).
48-
48+
- **Current Environment**: Gives you the current [development environment](../../testing-deployment-publishing/development-environments/development-environments.md) value.
4949

5050
:::tip[Generated Code]
5151
Learn more about the [**Generated Code**](../../ff-concepts/state-management/generated-code.md#global-state) behind Global Properties.

docs/testing-deployment-publishing/branching-collaboration/branching.md

Lines changed: 63 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -384,6 +384,34 @@ You can modify files or edit the project directly from the lower panel at any ti
384384

385385
After editing, click **Save Changes** to confirm your changes. A red reset button appears if you want to undo your changes and restore the file to its initial state before you began editing.
386386

387+
For more information, check out the video below.
388+
389+
<div style={{
390+
position: 'relative',
391+
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
392+
height: 0,
393+
width: '100%'}}>
394+
<iframe
395+
src="https://www.youtube.com/embed/r8BR248HR0U"
396+
title=""
397+
style={{
398+
position: 'absolute',
399+
top: 0,
400+
left: 0,
401+
width: '100%',
402+
height: '100%',
403+
colorScheme: 'light'
404+
}}
405+
frameborder="0"
406+
loading="lazy"
407+
webkitAllowFullScreen
408+
mozAllowFullScreen
409+
allowFullScreen
410+
allow="clipboard-write">
411+
</iframe>
412+
</div>
413+
<p></p>
414+
387415
### Resolve Merge Conflicts
388416
A merge conflict occurs when multiple team members make changes to the same part of the project.
389417

@@ -526,15 +554,9 @@ To configure these permissions, navigate to **Settings & Integrations > Project
526554

527555
Closing a branch is a common practice after the branch has served its purpose, typically once its changes have been merged into another branch (like the `main` or `development` branch). By regularly closing inactive or merged branches, you help maintain a clean, efficient, and well-organized project.
528556

529-
### When to Close a Branch
530-
557+
:::info[When to Close a Branch]
531558
- **After a Merge:** Once the branch’s changes have been merged into the `main` branch (or another target branch), it’s safe to close the branch. This often happens after a feature is complete or a bug is fixed.
532559
- **Unused Branch:** If a branch is no longer needed (e.g., a feature was abandoned or changes were made in another branch), it’s a good idea to close it.
533-
534-
:::warning
535-
536-
Once a branch is closed, it will no longer appear in the list of active **Branches**, meaning no further changes can be made. **This action is permanent and cannot be undone**, so ensure that all necessary work is completed or merged before closing the branch.
537-
538560
:::
539561

540562
Here’s how you can close a branch:
@@ -571,6 +593,40 @@ Here’s how you can close a branch:
571593
- **Coordinate with your team:** If you’re working in a team, ensure that no one is actively using the branch before you close it, to avoid disrupting ongoing work.
572594
:::
573595

596+
Once a branch is closed, it will no longer appear in the list of active branches. However, you can restore a closed branch within **30 days** of its closure.
597+
598+
### Restore Branch
599+
To restore a branch, open the **Branch Filter** menu and enable **Show Closed Branches**. Search for or select the branch you want to restore, and it will open in a new browser tab. Then, within the closed branch, open the **Branching Options** menu and select **Restore Branch** to reactivate it.
600+
601+
602+
<div style={{
603+
position: 'relative',
604+
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
605+
height: 0,
606+
width: '100%'}}>
607+
<iframe
608+
src="https://demo.arcade.software/RQ8lrFH85EZr71sQ7VKN?embed&show_copy_link=true"
609+
title=""
610+
style={{
611+
position: 'absolute',
612+
top: 0,
613+
left: 0,
614+
width: '100%',
615+
height: '100%',
616+
colorScheme: 'light'
617+
}}
618+
frameborder="0"
619+
loading="lazy"
620+
webkitAllowFullScreen
621+
mozAllowFullScreen
622+
allowFullScreen
623+
allow="clipboard-write">
624+
</iframe>
625+
</div>
626+
<p></p>
627+
628+
629+
574630
## FAQs
575631
<details>
576632
<summary>

0 commit comments

Comments
 (0)