Skip to content
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

Improve the documentation of chi.Router #714

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

curio77
Copy link

@curio77 curio77 commented Mar 18, 2022

Make it clear(er) what the "fresh middleware stack" means and document some intrinsics/caveats.

Resolves #712

Make it clear(er) what the "fresh middleware stack" means and document
some intrinsics/caveats.
@tyliggity
Copy link

Just ran into this on the go doc today when implementing a router group.

@TheRandomCharacter
Copy link
Contributor

I was also misled by fresh middleware stack. I find phrasing proposed in this PR too long and excessive, simple change of fresh to copy seems more appropriate

Found this PR doing due diligence for opening my own. Sadly 1.5 years of ghosting this PR doesn't reinforce confidence in the project.

@VojtechVitek
Copy link
Contributor

@TheRandomCharacter I hesitated to review this PR as the new GoDoc comment felt very long to me. I agree that changing fresh to copy might just do the job? Mind submitting a PR, please?

@TheRandomCharacter
Copy link
Contributor

@VojtechVitek
Submitted a new PR #862.
Also conversion to *Mux in Group() looks superfluous to me. Made PR for that also (#863)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ambiguities re middlewares after routes
4 participants