Daniel
Daniel
@sadortun thanks for the PR! Looks good, just some minor comments.
I think this might close #7527
This PR also resolves the issue of the server being exposed before schemas are loaded. Before, migrations happen once express routes are exposed: ![Screen Shot 2022-04-28 at 8 32 08...
It’s a bit of everything really. And yep, I believe the race condition is fixed by this PR. @Moumouls might have more to say though
The old code works fine because the core tests don’t care for race conditions / deploying schema before exposure and checking cloud code, and use the current function ParseServer.start. This...
> Does this mean you want to be able to call the Parse Server API before the server has finished its start-up procedure? I'm not quite sure how this is...
Not quite sure why this runs fine locally but github actions responds with `[Error: ENOENT: no such file or directory, open './src/options/Definitions.js'] {`
Ok, thanks for the pointers CI expert! If you could have a quick look at the approach and let me know your general thoughts some time that would be great.
What do you think of adding a parameter such as `({raw: true})` to the aggregate? We could also make sure the existing aggregate fails safely.
Possibly related to #7082