-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Add RFCs re Test Directory Naming Unification and Router Service Refresh Method #665
Add RFCs re Test Directory Naming Unification and Router Service Refresh Method #665
Conversation
|
||
<add your name to author list, top and bottom> | ||
<add blurb and emoji to "SOME-INTRO-HERE"> | ||
Note this `refresh` method would be different than the currently available `Route.prototype.refresh` method that refreshes only the refreshes whatever route you call it on and all routes “below” it in the route hierarchy. This newly proposesd method would refresh all routes. |
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'm not familiar with the RFC so I wasn't sure what you meant by "only the refreshes whatever route ... in the route hierarchy." Is it possible to rephrase this part of the sentence? (If not, no worries.)
Can we fix the spelling from proposesd
to proposed
?
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.
thanks, taking a looksie at the RFC re: your comment 👀
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.
👍 really appreciate the writeups, thank you!
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 overall! Thanks for covering both RFCs!
No description provided.