Skip to content
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

Retrieve schema (Back-end service) #111

Open
stefjoosten opened this issue May 1, 2023 · 2 comments
Open

Retrieve schema (Back-end service) #111

stefjoosten opened this issue May 1, 2023 · 2 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@stefjoosten
Copy link
Contributor

stefjoosten commented May 1, 2023

At runtime, we want every generated application to know its own schema, so the migration algorithm can retrieve the correct schema by simply asking the system. A schema is the Ampersand-script without the INTERFACEs and without the population. For this purpose, the Ampersand compiler must place a copy of the schema in the generated back-end application.

This issue is part of the Migration epic, which facilitates incremental development of the Ampersand application in production.

Task

Make een back-end service ``retrieve schema’’, which yields the original Ampersand schema of the deployed web application without the interfaces and without the population.

@stefjoosten stefjoosten changed the title Retrieve schema Retrieve schema (Back-end service) May 1, 2023
@hanjoosten
Copy link
Member

hanjoosten commented May 1, 2023 via email

@stefjoosten stefjoosten added enhancement New feature or request good first issue Good for newcomers labels May 1, 2023
@stefjoosten
Copy link
Contributor Author

stefjoosten commented May 26, 2023

Choice

With every migration, we store the schema in Ampersand source format in the back end. The compiler can question the back end to retrieve the actual schema of the running application.

We can realize a first implementation by enhancing the ampersand export command.

Complication

An Ampersand application consisting of multiple namespaces may cause complications. We need to investigate that. For now, we'll implement the export while expanding the aliases in namespaces, so that a combination of files can be exported in one file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants