My opinion right now is that we shouldnât add any extra configuration files by default without clearly asking the users if they want them or not. I can imagine a lot of use cases where CodeSandbox wonât be needed (if you are working on a private project for example) and it would feel weird to have that file there.
In terms of user experience, if Frontity users want to convert their project into a CodeSandbox they just have to add the sandbox.config.js
file, which I feel is not a big deal. In the future we could even make it easier with a command.
In terms of Community Support, I agree it would help. If I understood it correctly, right now you have to fork the repo and add the sandbox.config.js
file yourselves. That way you are able to run the CodeSandbox right?
Iâve seen that, according to this issue, it isnât currently possible to add the sandbox.config.js
file directly in the CodeSandbox after importing the GitHub repo, and that is the reason you have to fork it beforehand. It seems it will be possible in the future and, if users donât add it in their GitHub repo, we will be able to add it afterwards in CodeSandbox.
To sum up:
- If the repo has the proper
sandbox.config.js
file you can directly import the GitHub repo to CodeSandbox it will work by default.
- If the repo doesnât have it, right now you have to fork the repo, add the
sandbox.config.js
file yourselves, and you are able to import the GitHub repo to CodeSandbox.
- If this issue is solved, if the repo doesnât have the
sandbox.config.js
file, you can import it directly to CodeSandbox and add the file there.
Could you confirm if this is right or there is something that Iâm missing?
Regarding this, I feel the same way. Itâs true we recommend Vercel but I wouldnât add the file without asking because a lot of users will want to deploy Frontity in other services.