Libraries #141

pinkeshmars · 2024-09-19T10:44:02Z

Libraries

Linear ticket and magic word Fixes DEVR-600

Type of change

bolt-new-by-stackblitz · 2024-09-19T10:44:06Z

Run & review this pull request in StackBlitz Codeflow.

PoojaB26

Need some shuffling around of the topics

docs/resources/libraries.md

PoojaB26 · 2024-09-23T09:57:01Z

docs/resources/libraries.md

+
+- You can only publish libraries if you have access to branching, which is available to Pro+ users.
+- Libraries can only be published from the main branch, and each published version is linked to a specific commit, ensuring robust version control.
+- You can add new features and publish updated versions of the library. Each time a new version is published, the version number will automatically increment.


I feel this should be its own topic. "Library Versioning" can be a new topic. That can have sub topics around publishing a new version, importing to a version of choice or upgrading to latest. also mention the importance of library versioning.

No worries. Updated as per your suggestion.

PoojaB26 · 2024-09-23T10:08:01Z

docs/resources/libraries.md

+
+Follow these steps to ensure both libraries rely on the same version of Components Library:
+
+1. **Upgrade both libraries**: Start by upgrading libraries to their latest versions. Often, newer versions are built to rely on a common or more flexible version of Components Library, which can resolve conflicts.


Little confusing here. Do you mean upgrading the dependencies used in these libraries? If yes, its not very clear here because of the heavy use of "libraries" and not mentioning which ones we are talking abiut here. Can we rephrase?

Ya, It's updated now to make it more clear.

docs/resources/libraries.md

PoojaB26 · 2024-09-23T10:10:55Z

docs/resources/libraries.md

+2. **Modify libraries**: If you have access to the library projects, adjust the dependencies of either User Auth Library or Payment Gateway Library (or both) to use the same version of Components Library.
+3. **Contact library maintainers**: If you cannot resolve the conflict yourself, reach out to the maintainers of User Auth Library and Payment Gateway Library. They may provide guidance, suggest workarounds, or release a version that addresses the conflict.
+
+## Access Library Resources


This topic doesnt need a topic of its own, I mean we already have "Library Resources" section above and this should be included as a paragraph there (without any heading)

Good catch. I have merged 'Library Resources' into 'Access Library Resources'. Kept it at the bottom so that it looks step by step.

PoojaB26 · 2024-09-23T10:11:23Z

docs/resources/libraries.md

+![access-library-resources.avif](imgs/access-library-resources.avif)
+
+## FAQs
+Here are the FAQs in the requested format:


What does that mean? "requested format?"

Oh, It's a text from ChatGPT that came along with the formatted FAQs that Docusaurus uses (i.e., < details >
< summary >...). Removed it.🙂

Co-authored-by: Pooja Bhaumik <pbhaumik26@gmail.com>

pinkeshmars · 2024-09-24T07:22:47Z

@PoojaB26 all comments till now are addressed. You can review them again.

PoojaB26 · 2024-09-24T08:13:36Z

I just noticed Libraries is part of Resources, should this be not part of Resources > Projects instead? @pinkeshmars

PoojaB26

Moved Libs to Projects since its a component/setting of a project

PoojaB26 · 2024-09-24T08:15:01Z

docs/resources/imgs/libraries.avif

Great diagram!

Thanks Pooja!🙂

PoojaB26 · 2024-09-24T08:16:07Z

docs/resources/libraries.md

+
+Previously, FlutterFlow offered several methods to share resources between projects, such as team code libraries, design systems, API libraries, and by leveraging marketplace items. However, these methods had limitations, including the inability to share custom data types or custom functions alongside components or API calls and the absence of version control.
+
+With the Libraries, you can publish the complete FlutterFlow project as a library and import it as a dependency into other projects.


Suggested change

With the Libraries, you can publish the complete FlutterFlow project as a library and import it as a dependency into other projects.

With Libraries, you can publish the complete FlutterFlow project as a library and import it as a dependency into other projects.

* Keyboard Shortcut (#144) * added on shortcut press action trigger * 'demo arcade' removed * Added important points related to keyboard shortcuts * Added branch permission and commits section * Making a few modifications * Fixing some outdated information and rewording * Added dev environments * added note * Content correction * Updated as per review comments * Added environment variables * Making some changes * One more change based on pooja feedback * Libraries (#141) * Added libraries content * add note * added dependency conflicts section * minor fix * Update docs/resources/libraries.md Co-authored-by: Pooja Bhaumik <pbhaumik26@gmail.com> * Apply suggestions from Pooja's review Co-authored-by: Pooja Bhaumik <pbhaumik26@gmail.com> * Address review comments * Move libraries to projects --------- Co-authored-by: Pooja Bhaumik <pbhaumik26@gmail.com> * Widget builder as parameter (#142) * Added widget builder as parameter * Address review comments * Added libraries content * add note * added dependency conflicts section * minor fix * Update docs/resources/libraries.md Co-authored-by: Pooja Bhaumik <pbhaumik26@gmail.com> * Apply suggestions from Pooja's review Co-authored-by: Pooja Bhaumik <pbhaumik26@gmail.com> * Address review comments * Move libraries to projects * making some modifications * Moving built in widgets to widget section * Making adjustments to widget builder as parameter * Mentioning commits in versions page * Adding shotcut info * Fix name * update action flow editor visuals * added action triggers * added arcade for example 3rd step * added lifecycle stages * Fixed review comments * Formatting fix * Formatting fixes * added lifecycle for tap gesture * Making adjustements to gesture detector stuff * Specify Firestore collections * fix slug for widget builder * fix admonition * minor corrections * fix slug for dev envs * fix slug for dev envs * fix slug for dev envs * Spellings --------- Co-authored-by: null <null> Co-authored-by: Leigha Reid <leigha.jarett@gmail.com> Co-authored-by: PoojaB26 <pbhaumik26@gmail.com>

pinkeshmars added 3 commits September 13, 2024 14:19

Added libraries content

6cc6cd7

add note

e47b6f6

added dependency conflicts section

e915ab5

github-actions bot requested a review from PoojaB26 September 19, 2024 10:44

minor fix

812f171

pinkeshmars requested a review from leighajarett September 23, 2024 04:16

PoojaB26 requested changes Sep 23, 2024

View reviewed changes

PoojaB26 changed the base branch from main to ffdc-features September 23, 2024 10:20

pinkeshmars and others added 3 commits September 24, 2024 10:21

Update docs/resources/libraries.md

df4af8b

Co-authored-by: Pooja Bhaumik <pbhaumik26@gmail.com>

Apply suggestions from Pooja's review

8e96e78

Co-authored-by: Pooja Bhaumik <pbhaumik26@gmail.com>

Address review comments

f47d10a

Move libraries to projects

1299522

PoojaB26 approved these changes Sep 24, 2024

View reviewed changes

PoojaB26 merged commit f10eb29 into ffdc-features Sep 24, 2024


		Follow these steps to ensure both libraries rely on the same version of Components Library:

		1. Upgrade both libraries: Start by upgrading libraries to their latest versions. Often, newer versions are built to rely on a common or more flexible version of Components Library, which can resolve conflicts.


		Previously, FlutterFlow offered several methods to share resources between projects, such as team code libraries, design systems, API libraries, and by leveraging marketplace items. However, these methods had limitations, including the inability to share custom data types or custom functions alongside components or API calls and the absence of version control.

		With the Libraries, you can publish the complete FlutterFlow project as a library and import it as a dependency into other projects.

	With the Libraries, you can publish the complete FlutterFlow project as a library and import it as a dependency into other projects.
	With Libraries, you can publish the complete FlutterFlow project as a library and import it as a dependency into other projects.

Libraries #141

Libraries #141

Uh oh!

Conversation

pinkeshmars commented Sep 19, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Libraries

Type of change

Uh oh!

bolt-new-by-stackblitz bot commented Sep 19, 2024

Uh oh!

PoojaB26 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pinkeshmars Sep 24, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pinkeshmars commented Sep 24, 2024

Uh oh!

PoojaB26 commented Sep 24, 2024

Uh oh!

PoojaB26 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pinkeshmars Sep 24, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

pinkeshmars commented Sep 19, 2024 •

edited

Loading

pinkeshmars Sep 24, 2024 •

edited

Loading

pinkeshmars Sep 24, 2024 •

edited

Loading