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

Bugfix: Unable to Continue as Guest after Close Bolt OTP Modal #178

Merged
merged 44 commits into from
Aug 11, 2023

Conversation

dumega
Copy link
Contributor

@dumega dumega commented Aug 5, 2023

https://app.asana.com/0/1200879031426307/1205119516372383/f

The solution is to remove disabled attribute when the authorize_modal_closed event is triggered

serenayanbolt and others added 18 commits June 27, 2023 17:04
* Add SSO login button.

* fix lint.
* Add SSO login endpoint.

* Fix lint.
* Store accessToken/refreshToken/refreshTokenScope/ExpireIn in SFCC

* fix lint

* updates

* update
* Store accessToken/refreshToken/refreshTokenScope/ExpireIn in SFCC

* fix lint

* Load Bolt account details for SSO login

* updates

* fix lint

* update
* Store accessToken/refreshToken/refreshTokenScope/ExpireIn in SFCC

* fix lint

* Load Bolt account details for SSO login

* updates

* fix lint

* Login SFCC Platform Account after Bolt Login- Checkout Page

* updates

* fix test
Remove get openid config call.
* Creat SFCC account for guest.

* Add empty check

* Fix lint.

* Add unit test and cleanup code.

* lint fix
Add get platform account endpoint.
* Clean custom fields code

* fix lints
* Skip customer check.

* fix lint
Remove unused OCPAI codes.
Check if SSO is enabled before login platform account.
// eslint-disable-next-line no-undef
Bolt.getInstance().on('authorize_modal_closed', () => {
var disabledAttr = $('.submit-customer').attr('disabled');
if (typeof disabledAttr !== 'undefined' && disabledAttr !== false) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Based on this article explaining Falsy values in JS. I think it's good to use if(!disabledAttr) as condition

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Make sense, just updated

serenayanbolt and others added 6 commits August 7, 2023 15:34
* Add SSO login button.

* fix lint.
* Add SSO login endpoint.

* Fix lint.
* Store accessToken/refreshToken/refreshTokenScope/ExpireIn in SFCC

* fix lint

* updates

* update
* Store accessToken/refreshToken/refreshTokenScope/ExpireIn in SFCC

* fix lint

* Load Bolt account details for SSO login

* updates

* fix lint

* update
* Store accessToken/refreshToken/refreshTokenScope/ExpireIn in SFCC

* fix lint

* Load Bolt account details for SSO login

* updates

* fix lint

* Login SFCC Platform Account after Bolt Login- Checkout Page

* updates

* fix test
@@ -141,6 +141,13 @@
<externally-managed-flag>false</externally-managed-flag>
<min-length>0</min-length>
</attribute-definition>
<attribute-definition attribute-id="boltEmbeddedAccountsTokens">
Copy link
Contributor

Choose a reason for hiding this comment

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

I believe this is not for this PR, right?

Base automatically changed from feature/embedded-sso to master August 10, 2023 21:55
@dumega dumega merged commit baae20e into master Aug 11, 2023
2 checks passed
@dumega dumega deleted the ning/close-otp-modal branch August 11, 2023 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants