-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Support "." char as user name for User/Orgs in RSS/ATOM/GPG/KEYS path ... #23874
Conversation
ah damed that milestone never got cleaned up :/ *done now |
wouldn't |
well that's also affected by the chi issue :/ so NO sadly |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
}, func(ctx *context.Context) { | ||
ctx.Data["EnableFeed"] = setting.EnableFeed | ||
}, context_service.UserAssignmentWeb()) | ||
m.Get("/{username}", func(ctx *context.Context) { |
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.
OK, I think this function should get moved out of web.go and into a named function within routers/web/user - and we should probably also update the routing.UpdateFuncInfo(req.Context(), ...)
(Although we should do that without causing the funcInfo to be generated at run time.)
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.
In the best case the upstream issue get solved ...
the question is if we wana have that workaround now in or engineer around it properly ... or wait for upstream
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.
I have personally given up on waiting for chi
to fix any issues 😉
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.
well that would mean we must fix and submit a patch upstream 😆
Backport #23882 by @wxiaoguang Found an UI problem when testing #23874 The `ul li` styles were polluted. Before: ![image](https://user-images.githubusercontent.com/2114189/229409756-22438268-ee36-4e4a-a20b-04ee8ee4a79d.png) After: ![image](https://user-images.githubusercontent.com/2114189/229409809-25cea715-b6f1-4346-9bb4-3fbb58fcca65.png) Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
moved breaking part into #23908 |
workaround for go-chi/chi#781