Add Detail View for Login #212
No reviewers
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#212
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "6543/tea:refactor_login-and-conf"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add Detail View for Login
... refactor AddLogin
... make complient with #37
... rm unused code'
Add Detail View for Login ... refactor AddLogin ... make complient with #37 ... rm unused codeto Add Detail View for LoginYeah, the refactoring starts to show off! the code has actually become a joy to read ?
Added kind/breaking, as
tea login
without further args behaves very differently now@ -6,4 +0,0 @@
// App related variables
var (
AppVer string
We might need a package like this to implement the debug mode via build tags (i.e. makefile injects
-X settings.Tags="debug"
)?make already inject to
-X "main.Version=$(TEA_VERSION)" -X "main.Tags=$(TAGS)"
I also think it make more sence to have a flag and set verbose levels
what I mean is: we need the debug tag as some global state, and a
settings
package would be a good fit. but yeah, maybe a flag is better than a tag anyway.