-
Notifications
You must be signed in to change notification settings - Fork 367
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
Advanced flag #149
Advanced flag #149
Conversation
This is only for httprouter. Still need to add for other frameworks
GitHubAction Templates for generated projects
# Conflicts: # cmd/create.go # cmd/program/program.go # cmd/steps/steps.go
…into advanced-flag
This is PROD-ready, there is no need to merge into the staging branch. |
cmd/program/program.go
Outdated
if err != nil { | ||
log.Fatal(err) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if placehodler does not get re-written, is it going to log fatal?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When running through it with the flag being false, it doesn't not log fatal. The Parse is just taking in a string so I think it'll be fine no matter what the string is, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Current process cannot be killed
} | ||
err = spinner.ReleaseTerminal() | ||
if err != nil { | ||
log.Printf("Could not release terminal: %v", err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
if we get here, cant we make sure to release the terminal for them? Maybe explicitly setting a kill for the terminal? Otherwise it will be hanging and the user needs to close the terminal.
Not blocking, just some food for thought
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What would that look like? Would we want to do an os.Exit
or something like that?
Won't the CheckErr
handle exiting with a non-zero exit code?
Sorry if these are simple questions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, revoking my approval.
Can we change this from staging-2 to main branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides the conflict, LGTM.
# Conflicts: # cmd/program/program.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.
Problem/Feature
This introduces the
--advanced
flag discussed in #147.Description of Changes:
As of right now when creating the draft PR, the HTMX/Templ support is incomplete. Below is a list of places it needs to be added. I wanted to get the draft PR open in case others wanted to start adding to it. I'll keep adding to it the rest of the week/weekend and hopefully we can get something ready to merge by next week.
routes
dbRoutes
Checklist