Skip to content

Add FAQ section on using custom classes in Library Projects #413

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 9, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion docs/ff-concepts/adding-customization/code-file.md
Original file line number Diff line number Diff line change
Expand Up @@ -459,4 +459,15 @@ You can access the custom enums from **Set from Variable** menu > **Custom Enum*
- Keep your custom class files modular and focused; ideally one class per file for better organization and reusability.
- Avoid advanced Dart features that are not supported by FlutterFlow’s parser, such as generics or function-typed fields.
- Re-parse your code after making changes to ensure FlutterFlow updates the parsed structure correctly.
- Document your code with comments to make your custom classes easier to understand and maintain over time.
- Document your code with comments to make your custom classes easier to understand and maintain over time.

## FAQs

<details>
<summary>
Can I add Custom Classes (Code Files) in a Library Project?
</summary>
<p>
Yes, you can. When a Library Project is imported, any custom code files you’ve defined will be parsed, and the resulting classes will be available for use in the consuming project.
</p>
</details>