Skip to content

Commit 43b3f80

Browse files
authored
Merge branch 'main' into feature/dynamic-content-tooltip
2 parents 2d00d2a + 95a2e54 commit 43b3f80

File tree

4 files changed

+84
-2
lines changed

4 files changed

+84
-2
lines changed

docs/ff-concepts/adding-customization/vscode-extension.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -231,6 +231,72 @@ To delete a Custom Action or Widget, delete the associated file.
231231
### Adding New Dependencies
232232
You can add custom [pub.dev](https://pub.dev/) package dependencies with the `Dart: Add Dependency` command from the Visual Studio Code command palette. This will update the `pubspec.yaml` file.
233233

234+
## Using Flutter Version Management (FVM)
235+
If you want to manage Flutter versions with [**Flutter Version Management (FVM)**](https://fvm.app/), you need to install it and add it to your system’s PATH. Follow these steps to get started:
236+
237+
### Install FVM
238+
239+
To install **FVM**, run the following command in your terminal. This installs FVM globally using Dart’s package manager.
240+
241+
```
242+
dart pub global activate fvm
243+
```
244+
245+
### Add FVM to Your System’s PATH
246+
247+
After installation, you need to add the directory containing FVM’s executables to your **PATH variable** so that it can be accessed globally.
248+
249+
#### For macOS & Linux
250+
251+
1. Open the Terminal and run the following command. It adds the `~/.pub-cache/bin` directory to your system's `PATH` permanently by updating your `~/.zshrc` file. This ensures that the FVM installed in `~/.pub-cache/bin` is accessible from anywhere in the terminal.
252+
253+
```bash
254+
echo 'export PATH="$PATH":"$HOME/.pub-cache/bin"' >> ~/.zshrc # For Zsh
255+
echo 'export PATH="$PATH":"$HOME/.pub-cache/bin"' >> ~/.bashrc # For Bash
256+
```
257+
258+
2. Restart your terminal or run `source ~/.zshrc` (or `source ~/.bashrc`) to apply the changes.
259+
260+
#### For Windows
261+
262+
1. Locate the **FVM executable path**, typically:
263+
264+
```
265+
C:\Users\YourUsername\AppData\Local\Pub\Cache\bin
266+
```
267+
268+
2. Add this path to your **System’s PATH variable**:
269+
1. Open **System Properties****Advanced system settings**.
270+
2. Click **Environment Variables**.
271+
3. Under **System variables**, select **Path****Edit**.
272+
4. Click **New** and add the above path.
273+
5. Click **OK** and restart your terminal.
274+
275+
276+
### Verify the Installation
277+
278+
To check if FVM is correctly installed and accessible, run:
279+
280+
```bash
281+
fvm --version
282+
```
283+
284+
If this command prints the installed version of FVM, it means FVM is successfully installed and added to PATH.
285+
286+
287+
### Configure FVM in Your Flutter Project
288+
289+
Once FVM is installed, navigate to your Flutter project folder and set up FVM:
290+
291+
```bash
292+
cd your-flutterflow-project
293+
fvm init
294+
fvm install <flutter_version>
295+
fvm use <flutter_version>
296+
```
297+
298+
*(Replace `<flutter_version>` with the required Flutter version.)*
299+
234300

235301
## FAQs
236302
<details>

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/resources/projects/libraries.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,17 @@ To publish a FlutterFlow project as a library, start by creating a FlutterFlow p
8080
- It's recommended to include a message that tells users what has changed in the version your are publishing.
8181
:::
8282

83+
:::warning
84+
To publish a project as a library, it must meet the following requirements:
85+
86+
- **No Prior Store Deployment**: The project must not have been deployed to the Google Play Store or Apple App Store.
87+
- **No Failed Deployments**: The Publish button remains disabled if a deployment process was started and failed.
88+
- **No Errors or Warnings**: All project errors or warnings must be addressed beforehand.
89+
- **Main Branch Only**: You can only publish from the main branch.
90+
- **Pro Plan Subscription**: A Pro Plan is required to publish a project as a Library.
91+
- **Not Cloned from Marketplace**: The project cannot be a clone of a Marketplace item.
92+
:::
93+
8394
### Disabled Features in a Library
8495

8596
When a project is converted into a library, the following features are disabled to ensure compatibility and functionality limitations:

firebase.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2317,6 +2317,11 @@
23172317
"source": "/misc/flutterflow-experts",
23182318
"destination": "/misc/hire-flutterflow-developer",
23192319
"type": 301
2320+
},
2321+
{
2322+
"source": "/firebase-content-manager",
2323+
"destination": "/integrations/database/cloud-firestore/firestore-content-manager/",
2324+
"type": 301
23202325
}
23212326
]
23222327
}

0 commit comments

Comments
 (0)