lucky_cli
lucky_cli copied to clipboard
A Crystal command-line tool for generating new Lucky Web Applications.
Ref: https://github.com/luckyframework/lucky_flow/pull/152
Fixes #724 The one part this is still missing is when you're in an application and run `lucky -h`, it still won't show the `lucky dev` command because this isn't...
It should be silent. ``` To: [#] From: [email protected] Subject: Reset your password CC: [] BCC: [] Headers: {} ======= TEXT ======= Please reset your password: http://localhost:5001/password_resets/1?token=fake ======= HTML =======...
``` Failures: 1) Authentication flow allows sign in through backdoor when testing Failure/Error: flow.el("@sign-out-button").should be_on_page Expected to find element on page, but it was not found. ▸ looking for: [flow-id='sign-out-button']...
I'm pretty sure this must relate to exit codes and how yarn wraps different types of ongoing watch processes + how Nox traps exit codes, but haven't dug in deeply...
One of the woes of installing lucky_cli from source is that, in order for `lucky init` to work properly, you must be on a tag. I would be nice if...
Right now when you run `lucky init`, we run `crystal init app NAME` under the hood. It's nice because it gives us a default structure, and a ton of things...
Sister PR of https://github.com/luckyframework/lucky/pull/1648
This is the error message when a user boots a new lucky app with a correctly configured database url which points to an empty database (no migrations table): ``` 2022-03-04...
There are a bunch of situations which a developer might not otherwise need or want postgres cli tools to be installed -- can this check be removed?