Skip to content

Commit 0506a12

Browse files
committed
Merge branch 'refs/heads/main' into pooja/authentication-gen-code-v1
# Conflicts: # docs/generated-code/component-gen-code.md # docs/generated-code/flutterflow-model.md # docs/generated-code/imgs/page-component-generated.png # docs/generated-code/imgs/page-generated.png # docs/generated-code/imgs/page-generation-initial.png # docs/generated-code/pages-generated-code.md
2 parents a126265 + f37aeb0 commit 0506a12

22 files changed

+263
-16
lines changed

docs/generated-code/component-gen-code.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ sidebar_position: 6
66

77
# Generated Code: Components
88

9-
Similar to a [**Page**](pages-generated-code.md), when creating a component in FlutterFlow, it automatically generates two files: a `Widget` class and a `Model` class.
9+
Similar to a [**Page**](pages-generated-code.md), when creating a **[component](../resources/ui/components/intro-components.md)** in FlutterFlow, it automatically generates two files: a `Widget` class and a `Model` class.
1010

1111
:::info[Prerequisites]
12-
This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
12+
This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
1313
:::
1414

1515
## ComponentModel class

docs/generated-code/flutterflow-model.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Provides references to the associated widget and its `BuildContext`.
5757
BuildContext? get context => _context;
5858
```
5959
60-
`_widget` and `_context` (private fields) stores the widget and context references. `widget` and `context` (getters) are the public accessors for `_widget` and `_context`.
60+
`_widget` and `_context` (private fields) store the widget and context references. `widget` and `context` (getters) are the public accessors for `_widget` and `_context`.
6161
6262
## Disposal
6363
-5.21 KB
Loading
-5.34 KB
Loading
664 Bytes
Loading

docs/generated-code/pages-generated-code.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ sidebar_position: 5
99
When you create a new Page in FlutterFlow, it automatically generates two files: a `Widget` class and a `Model` class. So if the name of the page you created is called **ProductListPage**, FlutterFlow generation backend will automatically create **ProductListPageWidget** class and **ProductListPageModel** class.
1010

1111
:::info[Prerequisites]
12-
This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
12+
This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
1313
:::
1414

1515
## PageModel class
@@ -77,7 +77,6 @@ When dealing with dynamic lists of components, such as those in a `ListView`, Ro
7777
```js
7878
// Models for CategoryAvatar dynamic component.
7979
Map<String, FlutterFlowModel> categoryAvatarModels = {};
80-
8180
```
8281
8382
#### dispose()
@@ -106,7 +105,6 @@ class ProductListPageWidget extends StatefulWidget {
106105
@override
107106
State<ProductListPageWidget> createState() => _ProductListPageWidgetState();
108107
}
109-
110108
```
111109
112110
#### PageModel Initialization
@@ -140,7 +138,7 @@ Similarly, the [`dispose` method](#dispose) of the `PageModel` class is invoked
140138
Each page includes a `GlobalKey` for the `Scaffold`, which can be used to manage the scaffold's state, such as opening or closing drawers or snackbars programmatically.
141139
142140
```js
143-
final scaffoldKey = GlobalKey<ScaffoldState>();
141+
final scaffoldKey = GlobalKey<ScaffoldState>();
144142

145143
return Scaffold(
146144
key: scaffoldKey,

docs/intro/ff-ui/dashboard.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,10 @@ You can also find links to various resources to assist in building apps with Flu
7474
- Additionally, ensure that you have added a name to your FlutterFlow profile. The same name will be used for the community forum profile.
7575
:::
7676

77+
- **URL Access (Only Available for Enterprise Users)**: You can view and copy URLs that need to be whitelisted for FlutterFlow to function correctly in enterprise environments with restricted internet access. Check out docs on **[Whitelisting URLS](../../misc/enterprise-page.md#whitelist-urls)**.
78+
79+
![url-access](imgs/url-access-dashboard.avif)
80+
7781
- **Account**: This is helpful if you want to look at your account information, upload a profile picture, reset your password, see your referrals, or delete account.
7882

7983
- **Plan info**: See information about the current plan and eventually upgrade to access additional features.
Binary file not shown.

docs/misc/enterprise-support-policy.md renamed to docs/misc/enterprise-page.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,23 @@
1+
---
2+
slug: /misc/enterprise
3+
title: Enterprise
4+
description: Learn how to use FlutterFlow for Enterprise.
5+
tags: [Enterprise]
6+
sidebar_position: 1
7+
keywords: [Enterprise Support Policy, Whitelist URLs]
8+
---
19

2-
# Enterprise Support Policy
10+
# Enterprise
11+
12+
## Whitelist URLs
13+
14+
Enterprise environments often restrict internet access to enhance security and compliance. For example, they may allow access only to approved URLs that are essential for work-related tasks. FlutterFlow won't properly work in such restrictions because it accesses multiple services—Firestore, Cloud Functions, and various APIs—these URLs must be allowed in your corporate firewall for everything to function correctly.
15+
16+
To find out which URLs need to be whitelisted, navigate to the URL Access page from the FlutterFlow [dashboard](../intro/ff-ui/dashboard.md). Any URLs marked as **Inaccessible** are currently blocked by your network, which may prevent certain features from functioning properly. You can copy these URLs individually or use the Copy All Inaccessible URLs button in the top-right corner to collect them all at once. Then, share the list with your IT team for whitelisting.
17+
18+
![url-access](imgs/url-access.avif)
19+
20+
## Enterprise Support Policy
321

422
We understand our Enterprise customers often rely on FlutterFlow for mission critical applications. To that end, we have created a dedicated Enterprise support team to provide the highest level of service and support. This document outlines our support channels and scope for Enterprise customers.
523

docs/misc/imgs/url-access.avif

53.6 KB
Binary file not shown.

0 commit comments

Comments
 (0)