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

Making HRD work in signup page and showing an error when HRD is detected in the forgot password page #1278

Merged
merged 2 commits into from
Mar 8, 2018

Conversation

luisrudge
Copy link
Contributor

@luisrudge luisrudge commented Feb 28, 2018

fix #1250

image

@luisrudge luisrudge added this to the v11.4.0 milestone Mar 1, 2018
Copy link
Contributor

@lbalmaceda lbalmaceda left a comment

Choose a reason for hiding this comment

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

If the error copy wasn't reviewed by design it should. It's the first 3 lines error message I see and I personally don't like it (visually).

What I also find confusing of the PR is that there are many i18n values updates but the key changes on some of them are not changes on others, what's the reason behind this? i.e. hr.js adds a lots of new keys while fi.js doesn't.

@joshcanhelp
Copy link
Contributor

@lbalmaceda - I wrote that and agree that it doesn't look great as all-caps. We could remove that first sentence, TBH, and I think the message would be understandable. It's really just there to provide a path forward for folks. I don't think the end user is going to care about Enterprise or not.

@luisrudge
Copy link
Contributor Author

as for the translation: they probably weren't translated before.
as for the text, I don't think it's too big, in any case the customer can change that so, is that a big deal?

@vctrfrnndz
Copy link
Contributor

vctrfrnndz commented Mar 8, 2018

I don't think it this is a big deal, but it is a design issue in lock. Error messages were intended for shorter all caps errors. I think we can live with it for the moment, I don't want to introduce design changes for this specific issue.

@lbalmaceda lbalmaceda changed the title Making HRD work in signup page and showing an error when HRD is decteded in the forgot password page Making HRD work in signup page and showing an error when HRD is detected in the forgot password page Mar 8, 2018
@@ -36,6 +40,21 @@ export default class ResetPassword extends Screen {
getScreenTitle(m) {
return i18n.str(m, 'forgotPasswordTitle');
}
isSubmitDisabled(m) {
Copy link
Contributor

@lbalmaceda lbalmaceda Mar 8, 2018

Choose a reason for hiding this comment

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

Where is this used? Tests?

Copy link
Contributor

@lbalmaceda lbalmaceda left a comment

Choose a reason for hiding this comment

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

I'd like some tests over the Screen#isSubmitDisabled methods (5 occurrences once this PR added), since each one has it's own particular logic to make the decision. I'll approve it anyway, just keep that in mind 💃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider HRD configuration of enterprise connections in forgot password
4 participants