feat/AB#80252_Allow-frontend-to-reload-when-admin-updates/create-a-form

[GuilhermeGabriel]

Description

One issue we usually face while configuring forms/resources is that the system will stop working as expected after saving forms/resources. Indeed, the back-end needs to reload, and the front does not get the changes. We should, if possible, either reload the entire front, either reload the graphql.

Useful links

• Please insert link to ticket: (I don't have access)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• Improvement (refactor or addition to existing functionality)

How Has This Been Tested?

Create a new form, add a field to it, and test if the field appears in the layout editor without reloading the page.

Screenshots

output.mp4

Checklist:

( * == Mandatory )

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-frontend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

More explanation

https://www.loom.com/share/05a716d61b9744faaf51fb304c21d1e5?sid=f87cf896-582a-4f76-93ae-8ceed801b145

[AntoineRelief]

@GuilhermeGabriel
that won't work
you need to wait for the server to be ready again to do that

[GuilhermeGabriel]

Ok, I tried a new approach!

[AntoineRelief]

@GuilhermeGabriel
I don't like this approach
you're duplicating a query we already see in another service, for a call that will be done only once, so for me it doesn't make sense

you should prefer, for example, build a subject in the query-builder, and, when you detect a change in the subject, you refetch the data

so you can, in the form builder service, just emit an event to the query builder service

[matheus-relief]

@AntoineRelief do you think a websocket solution would be overkill?