I've seen projects where even the dockerfiles, docker-compose, etc., are in an entirely different repo, and you could run the project in dev with anything (your own docker images, symfony cli, frankenphp, etc.).
However, there is still something about the tests that is very specific:
Do you have a CI? Do you deploy your project to production if the test suite fails, locally or in the CI?
If you do, tests are just information, metadata about the "current estimated safety" of the project.
If you need tests/CI to be green before deploying, this means that your tests ARE a necessary part of your project, same for the testing framework the tests use.
Once again, a unit test and a hell lot of debugging time helped me realise that I long ago had a function that should have been broken but wasn't for strange reasons.
Still, in a Promise, I used "return resolveFunc" instead of calling "resolveFunc()".
return new Promise((resolve) => {
this._callback(data, operation, requestParameters);
return resolve;
resolve();
});
That's stupid, I know.
I even don't have any idea why I couldn't see that before. Everything worked super well, but it's only when unit-testing this particular piece of code that I realized the promise actually takes super long time, therefore is never resolved ("never resolved" should have given me a hint, by the way)
It was first made to ease local development and integration with SymfonyCloud, but now that SymfonyCloud has abandoned its white mark and moved back to Platform.sh, the Platform.sh integration in Symfony CLI is just a wrapper around the Platform.sh CLI tool (which is also open source: https://github.com/platformsh/cli)
The "installer" part is still a wrapper around "composer create" though.
@dantleech To be clear: I was at first pretty fine with the Symfony installer because back then it gave some "hope" to see different Symfony "distributions" (like the "demo", "skeleton", and "full" we first have), but no work has ever been done to promote other distributions.
Before the CLI tool, promoting a distribution was just about promoting another repo for "composer create", but now it's more about Github templates (like for API Platform's distribution, or Monofony, for instance).
@dantleech I had so many fights when I was working at SL with the maintainers of Symfony CLI, I really insisted to open-source the CLI tool and they didn't want it.
They only did it once SymfonyCloud "moved" (or more specifically "came back") to Platform.sh 🤷♂️
@herndlm What saddens me the most is that it's the same with the React hype. I hate that, but somehow I will end up being forced to join the hype train if I want to keep a job.
And I really hate that monopolizing-hype every framework has.