Can we access your project?
Current Behavior
When generating dependencies for inter-dependent projects, common dependency projects that are co-dependent are not generating code correctly. Also, files like backend/backend.dart and other utility functions that are generated when the project is run on it's own are not generated. Custom functions that are dependent no longer have access to the other projects custom functions.
Some of this can be worked around by using different dependencies instead of the generated index dependencies, some can not.
Expected Behavior
Would expect that the dependencies would be recognized and code generated correctly.
Steps to Reproduce
I have multiple common libraries. A core common, a project specific common and then multiple main project.
Example dependency tree:
core-common
project1-common -> depends on core-common
project1-main1 -> depends on project1-common and core-common
project1-main2 -> depends on project1-common and core-common
project2-main1 -> depends on core-common.
When running project1-main1 or project1-main2, data structures that exist in core-common that are utilized in project1-common are not being utilized during code generation and the dependency of project1-common is lost.
Example:
core-common has SimpleStruct
project1-common has a CommonStuct with a property of List
when code generation for project1-main runs, the property of CommonStruct is generated as List.
There is no pubspec.yaml entry for core-common in project1-common that is generated in dependencies.
Reproducible from Blank
Bug Report Code (Required)
IT48jOflzIt1j7xH15CBKcEwgiYXOUc7RIE30sFDQks8J5zKB+wAYvf7P1FWTL3mYAlAe2eGinI0/PfqhdmXVsA6Pkicc7pgzLhUahbweEOnacW0Es+7fW1QQMpRCUPG4aSZpRFdBNJqc04872Gqe/K8QnTsGZz0DWo3QvK1KdeK2SrDX1iXc2URm05KZDPz
Visual documentation
Environment
- FlutterFlow version: 7.0.79
- Platform: Web/Android/iOS/MacOS
- Browser name and version: Chrome 152.0.7977.76
- Operating system and version affected: MacOS 26.2
Additional Information
This is a high priority that holding up a customer delivery.
Can we access your project?
Current Behavior
When generating dependencies for inter-dependent projects, common dependency projects that are co-dependent are not generating code correctly. Also, files like backend/backend.dart and other utility functions that are generated when the project is run on it's own are not generated. Custom functions that are dependent no longer have access to the other projects custom functions.
Some of this can be worked around by using different dependencies instead of the generated index dependencies, some can not.
Expected Behavior
Would expect that the dependencies would be recognized and code generated correctly.
Steps to Reproduce
I have multiple common libraries. A core common, a project specific common and then multiple main project.
Example dependency tree:
core-common
project1-common -> depends on core-common
project1-main1 -> depends on project1-common and core-common
project1-main2 -> depends on project1-common and core-common
project2-main1 -> depends on core-common.
When running project1-main1 or project1-main2, data structures that exist in core-common that are utilized in project1-common are not being utilized during code generation and the dependency of project1-common is lost.
Example:
core-common has SimpleStruct
project1-common has a CommonStuct with a property of List
when code generation for project1-main runs, the property of CommonStruct is generated as List.
There is no pubspec.yaml entry for core-common in project1-common that is generated in dependencies.
Reproducible from Blank
Bug Report Code (Required)
IT48jOflzIt1j7xH15CBKcEwgiYXOUc7RIE30sFDQks8J5zKB+wAYvf7P1FWTL3mYAlAe2eGinI0/PfqhdmXVsA6Pkicc7pgzLhUahbweEOnacW0Es+7fW1QQMpRCUPG4aSZpRFdBNJqc04872Gqe/K8QnTsGZz0DWo3QvK1KdeK2SrDX1iXc2URm05KZDPz
Visual documentation
Environment
Additional Information
This is a high priority that holding up a customer delivery.