Skip to content

[Playground Task]: Sort out code generation for constants in frontend #21925

@alexeyinkin

Description

@alexeyinkin

What needs to happen?

When building, the frontend uses constants with backend URLs from /playground/frontend/lib/config.g.dart.

Looks like this file is generated from /playground/frontend/gradle.properties in /playground/frontend/build.gradle. But gradle.properties is behind config.g.dart which has been edited manually. It means that if code generation is re-ran, the changes that are now in production will be lost.

Moreover, it looks like gradle.properties is in turn generated in /playground/terraform/build.gradle.kts. And build.gradle.kts is in turn behind gradle.properties which has been edited manually to change at least one constant: analyticsUA. It means that if this code generation is re-ran, these changes will be lost too.

This should be sorted out, the differences should be fixed, and some docs on the generation pipeline should be provided.

Issue Priority

Priority: 3

Issue Component

Component: beam-playground

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions