-
Notifications
You must be signed in to change notification settings - Fork 48
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
Consider dropping crystal init during setup #741
Comments
One of the patterns I've come across that I like here is that I treat https://github.com/grepsedawk/sharded.cr/blob/main/.github/workflows/init#L18-L19 I take all the "my files" and copy |
… to generate on Windows. Fixes #741
Right now when you run
lucky init
, we runcrystal init app NAME
under the hood. It's nice because it gives us a default structure, and a ton of things like setting up the src, and spec folders and such.The issue is right after we do that, we basically remove almost all of it.
lucky_cli/src/generators/web.cr
Lines 107 to 138 in 0b5b8fb
We used to even have this 45f3529 because Crystal would default generate a travis CI, but then we started using Github, and then later versions of Crystal stopped generating that.
We're also at the mercy of whatever naming conventions, or bugs may appear in the crystal init.( ref )
Related: #735
In regards to that issue, if we just generated our own structure out of the box, we'd keep control and flexibility to what goes in to an app.
The main downside would be that this also opens us to bugs with all the different permutations of app type (i.e. browser, api, auth, etc...), it's possible we miss something, or similar to the Crystal naming bug, we end up creating our own bugs with naming....
The text was updated successfully, but these errors were encountered: