Skip to content
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

Refactor: Use 'login' for authentication instead of 'email' in registration process #1465

Conversation

luanrafaelpinheiro
Copy link
Contributor

Refactor: Use 'login' for authentication instead of 'email' in registration process

Issue #1464

Description

Types of Changes

  • [ x] Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Documentation update
  • Breaking change (could cause existing functionality to not work as expected)
  • Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

  • Removing a public function or component or prop
  • Adding a required argument to a function
  • Changing the data type of a function parameter or return value
  • Adding a new peer dependency to package.json

Changes

  • Refactoring: Use 'login' for authentication instead of 'email' in registration process

How to Test-Drive This PR

  • Register a customer using a login different of the customer email.

Checklists

General

  • [ x ] Changes are covered by test cases
  • CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

  • There are no changes to UI

or...

Localization

  • Changes include a UI text update in the Retail React App (which requires translation)

@luanrafaelpinheiro luanrafaelpinheiro requested a review from a team as a code owner October 5, 2023 17:10
@wjhsf
Copy link
Contributor

wjhsf commented Oct 6, 2023

Currently, PWA Kit uses the same value for login and email. If the two values differ, then the value for login must be used for logging in. Therefore, I don't think that this change will break any existing code.

Thanks for the contribution @luanrafaelpinheiro! Would you mind adding this bug fix to the changelog under the 1.1.0-dev heading so that it is documented for the next release?

@wjhsf wjhsf added the Acknowledged Team has responded to issue label Oct 6, 2023
@luanrafaelpinheiro
Copy link
Contributor Author

Certainly, I updated the changelog.

kevinxh
kevinxh previously approved these changes Oct 6, 2023
Copy link
Collaborator

@kevinxh kevinxh left a comment

Choose a reason for hiding this comment

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

thank you

wjhsf
wjhsf previously approved these changes Oct 6, 2023
@wjhsf
Copy link
Contributor

wjhsf commented Oct 6, 2023

Uh oh, @luanrafaelpinheiro! Looks like you don't have signed commits. Could you set that up and redo the changes? Thanks!

@luanrafaelpinheiro
Copy link
Contributor Author

Uh oh, @luanrafaelpinheiro! Looks like you don't have signed commits. Could you set that up and redo the changes? Thanks!

I need to open a new PR or just send a new signed commit?

@luanrafael luanrafael force-pushed the bugfix-error-401-after-register branch from aa21999 to da9e079 Compare October 6, 2023 20:09
@wjhsf
Copy link
Contributor

wjhsf commented Oct 6, 2023

Uh oh, @luanrafaelpinheiro! Looks like you don't have signed commits. Could you set that up and redo the changes? Thanks!

I need to open a new PR or just send a new signed commit?

All of the commits on the branch must be signed, so you could either force push to this branch or create a new one (and a new PR). Whichever way is most convenient.

@luanrafael luanrafael dismissed stale reviews from wjhsf and kevinxh via 16e559f October 6, 2023 20:23
@luanrafael luanrafael force-pushed the bugfix-error-401-after-register branch 2 times, most recently from ee46109 to 69b4e62 Compare October 6, 2023 20:30
…ration process

Issue SalesforceCommerceCloud#1464

Signed-off-by: Luan Rafael Pinheiro <luanrafael.pinheiro@salesforce.com>
Signed-off-by: Luan Rafael Pinheiro <luanrafael.pinheiro@salesforce.com>
Signed-off-by: Luan Rafael Pinheiro <luanrafael.pinheiro@salesforce.com>
Signed-off-by: Luan Rafael Pinheiro <luanrafael.pinheiro@salesforce.com>
@luanrafael luanrafael force-pushed the bugfix-error-401-after-register branch from 69b4e62 to 265afe5 Compare October 6, 2023 20:40
@luanrafaelpinheiro
Copy link
Contributor Author

Uh oh, @luanrafaelpinheiro! Looks like you don't have signed commits. Could you set that up and redo the changes? Thanks!

I need to open a new PR or just send a new signed commit?

All of the commits on the branch must be signed, so you could either force push to this branch or create a new one (and a new PR). Whichever way is most convenient.

done!

@wjhsf wjhsf enabled auto-merge (squash) October 6, 2023 20:44
@wjhsf wjhsf merged commit c902d91 into SalesforceCommerceCloud:develop Oct 6, 2023
18 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Acknowledged Team has responded to issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants