Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Support "." char as user name for User/Orgs in RSS/ATOM/GPG/KEYS path ... #23874
Changes from 2 commits
74fedb2
6a9e90c
df424ee
a85694f
a486a46
4ae6695
0129cb1
f515159
4cc8623
9d8cd97
96b1b30
1a78424
69cb014
6b5f2dc
808bacb
89ce389
8418d40
94c3ee3
2e974f1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 😆