Skip to content
This repository was archived by the owner on Dec 13, 2018. It is now read-only.

State and tests - #301

Closed
brentschmaltz wants to merge 7 commits into
devfrom
StateAndTests
Closed

brentschmaltz wants to merge 7 commits into
devfrom
StateAndTests

Conversation

@brentschmaltz

Copy link
Copy Markdown
Contributor

Replacement #233
Changed logic for user-state
Added additional testing

Removed AuthenticationProperties as a Property on notification.
Added tests for sending and receiving 'user' state.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fix this comment.

@Tratcher

Copy link
Copy Markdown
Member

Close your old PR if you're done with it.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

You could put it in OpenIdConnectAuthenticationDefaults.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think that would work, will make that change.

Logging level, IsNullOrEmpty for string, comment tests, const for userstate property.
SetUserState method has single focus.
@brentschmaltz

Copy link
Copy Markdown
Contributor Author

@Tratcher @Eilon can you guys have a look at the latest.
I think we should make the change for leaving the notifications null and only engaging if !null.

@kevinchalet

Copy link
Copy Markdown
Contributor

@brentschmaltz I'm not sure it's really worth it. Anyway, we'll probably switch to good old methods in a future PR to match the pattern used by the OAuth2 middleware, so you won't have to care about null values in the handler itself: #257 (comment)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This method seems rather trivial and is used only once in the handler. Maybe you can remove it?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@PinpointTownes can you help me understand about leaving the notifications NON null (setting default no-ops in OpenIdConnectAuthenticationNotifications). I thinks there is a gain here, if the user hasn't set a notification, then no need to new up the Notification and call a no-op.

I opened
#307

+1 on removing the mini-method: SetUserStateOnMessage

@brentschmaltz

Copy link
Copy Markdown
Contributor Author

@Eilon this PR has been marked cla-required. What do I need to do?

@Eilon

Eilon commented Jun 29, 2015

Copy link
Copy Markdown
Contributor

@brentschmaltz I sent you mail about the CLA.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can use Assert.Equal.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yes but there is no overload that has a message.

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