You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/resources/projects/libraries.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -228,13 +228,13 @@ You can easily upgrade to newer versions of the libraries as they become availab
228
228
229
229
## Library Values
230
230
231
-
**Library Values** are essentially variables created by a library publisher and intended to be set by the library consumer. These values allow library publishers to create configurable variables that are useful in different contexts, such as API keys, global settings, or other project-specific configurations. These values allow consumers to input specific data required for the library to function properly in their project.
231
+
**Library values** are essentially variables created and used by a library publisher and intended to have their values set by the library consumer. These values allow library publishers to create configurable variables that are useful in different contexts, such as API keys, global settings, or other project-specific configurations. These values allow consumers to input specific data required for the library to function properly in their project.
232
232
233
233
For example, If someone has built a library that uses OpenAI API, they would define a Library Value for the OpenAI API key. As the consumer of the library, when you import, you must provide your own API key to ensure the library functions properly.
234
234
235
235
By using Library Values, the publisher allows consumers to adapt the library to their own configurations without hardcoding sensitive or project-specific data, like API keys, into the library itself.
236
236
237
-
### Create Library Values
237
+
### Create Library Values as Publisher
238
238
239
239
The publisher defines the variable name, data type (e.g., string, enum), whether the variable is nullable, and an optional default value.
240
240
@@ -266,7 +266,16 @@ To create library values, navigate to **Settings and Integrations > App Settings
266
266
</div>
267
267
<p></p>
268
268
269
-
### Set Library Values
269
+
#### Use Library Values
270
+
After setting Library Values, they function just like any other variable in FlutterFlow. You can bind them to components, actions, API calls, or any property that allows you to configure dynamic values across your library project. You can access Library Values via the ****Set from Variable**** menu.
271
+
272
+
:::tip
273
+
Library values are used only within the library project and are not available for use in the consumer project. The library consumer can only set their values.
To set library values, navigate to **Settings and Integrations > Project Setup > Project Dependencies** page. When you import a library, you'll be prompted to set values for required Library Values. If the library has already been added, click on **View Details**, which will open a dialog and then you can enter a value.
272
281
@@ -296,8 +305,6 @@ To set library values, navigate to **Settings and Integrations > Project Setup >
296
305
</div>
297
306
<p></p>
298
307
299
-
After setting Library Values, they function just like any other variable in FlutterFlow. You can bind them to components, actions, or API calls, allowing you to easily configure dynamic settings across your project.
300
-
301
308
:::tip
302
309
For different [**development environments**](../../testing-deployment-publishing/development-environments/development-environments.md) (e.g., development vs. production), you can bind Library Values to [**environment values**](../../testing-deployment-publishing/development-environments/development-environments.md#use-environment-values). For instance, you could have two different Library Values for an API key, such as `DEV_OPENAI_API_KEY` and `PROD_OPENAI_API_KEY`, and bind them to the development and production environments to track API usage separately.
0 commit comments