Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

Improve usability of the request localization middleware #164 #170

Merged
merged 1 commit into from
Dec 11, 2015

Conversation

DamianEdwards
Copy link
Member

#164

Fixed up some out of date doc comments too.

@rynowak @ryanbrandenburg @Eilon

@hishamco
Copy link
Contributor

I'm not sure if the issue #127 should take place here or will be ignored

{
if (value == null)
{
throw new ArgumentNullException();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should have the name of the property in the exception yeah?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I actually wasn't sure what name to use here, but property name makes sense.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be nameof(value). That is the name of the parameter.

@DamianEdwards
Copy link
Member Author

@hishamco that will be separate

@ryanbrandenburg
Copy link
Contributor

:shipit:

- Remove the defaultRequestCulture parameter from IApplicationBuilder.UseRequestLocalization and make it a property on RequestLocalizationOptions instead
- Have just a single overload for IApplicationBuilder.UseRequestLocalization that takes the options
- #164
@DamianEdwards DamianEdwards merged commit 0b013ae into dev Dec 11, 2015
@DamianEdwards DamianEdwards deleted the damianedwards/bug-164 branch December 11, 2015 23:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants