You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Change the default in the template for normalizeHttpPath #197
I thinks changing the template is not a breaking change, since it affects only newly scaffolded projects. It is a big change though, we should post an update to the mailing list and also notify @dashby3000 et all.
Now that 3.0 is coming soon, I'd like to get this into our roadmap and implement it as a breaking change in strong-remoting, with an easy way how to opt into the old 2.x mode.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.
Activity
bajtos commentedon May 7, 2015
I thinks changing the template is not a breaking change, since it affects only newly scaffolded projects. It is a big change though, we should post an update to the mailing list and also notify @dashby3000 et all.
kevinji commentedon Jul 15, 2015
I don't think we should change the template until
normalizeHttpPathis fixed. Currently, it does nothing.bajtos commentedon May 9, 2016
Now that 3.0 is coming soon, I'd like to get this into our roadmap and implement it as a breaking change in strong-remoting, with an easy way how to opt into the old 2.x mode.
Possibly related discussion: strongloop/loopback#608, especially strongloop/loopback#608 (comment)
EDIT: and of course strongloop/loopback#433 which implemented
normalizeHttpPathoption7 remaining items
stale commentedon Aug 23, 2017
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale commentedon Sep 6, 2017
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the
CODEOWNERSfile at the top-level of this repository.