-
Notifications
You must be signed in to change notification settings - Fork 2.1k
IUrlHelper and support for RouteOptions.LowercaseUrls #7720
Comments
Thanks for contacting us, @enemyofthedawn. |
@enemyofthedawn, if you'd like to submit a PR in the |
IUrlHelper and support for RouteOptions.LowercaseUrls #issue : aspnet/Mvc#7720
Also it would be nice if
It could be a separate option to use hyphens (boolean) or enum option to choose the convention (something like Json.NET does) Or maybe some action so you can write your function that controls the naming. What do you think? |
checked appliesd to the query string. @rynowak aspnet#518 #Issue: aspnet/Mvc#7720
changes are made as suggestions. @rynowak aspnet#518 #Issue: aspnet/Mvc#7720
IUrlHelper and support for RouteOptions.LowercaseUrls #issue : aspnet/Mvc#7720
checked appliesd to the query string. @rynowak #518 #Issue: aspnet/Mvc#7720
changes are made as suggestions. @rynowak #518 #Issue: aspnet/Mvc#7720
Fixed by acea87a |
@LeCoque - if you'd be willing to send a PR, I think we'd be willing to take something like this
I don't want to add too many options to the framework by default - as you point out there are a lot of different schemes for generating query strings. I'd rather add a hook that lets application developers customize it. |
Uh oh!
There was an error while loading. Please reload this page.
I have the following setting:
When I generate URL from my controller, query parameters are named like in C#, for example
query?Property=x
I expected it to be
query?property=x
, ideally in camel case. Soquery?propertySomething=x
It would be nice if IUrlHelper implementation or
RouteValueDictionary
or something else respected this setting.Example invocation:
The text was updated successfully, but these errors were encountered: