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

LHC-189 #72

Merged
merged 1 commit into from
Apr 10, 2019
Merged

LHC-189 #72

merged 1 commit into from
Apr 10, 2019

Conversation

rdai10
Copy link
Owner

@rdai10 rdai10 commented Apr 10, 2019

Description

https://issues.liferay.com/browse/LHC-189

Due to the way the Zendesk Customization is set, customers for a long project name are not able to view the full project name. To get around that, the team decided to grab the value from the dropdown and hide it. Then display that value separately as text. That way the text will naturally wrap and allow the customer to see the entire organization name.

@rdai10 rdai10 requested a review from jonmak08 April 10, 2019 19:36
@rdai10 rdai10 merged commit 7af640d into dev Apr 10, 2019
@rdai10 rdai10 deleted the LHC-189 branch April 10, 2019 19:42
Copy link
Collaborator

@jonmak08 jonmak08 left a comment

Choose a reason for hiding this comment

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

Hey @rdai10,

Can you make the change?

Please let me know if you have any questions. Thanks!


const orgNamePlaceholder = document.getElementById('orgNamePlaceholder');

orgNamePlaceholder.innerHTML = orgName;
Copy link
Collaborator

Choose a reason for hiding this comment

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

We should check to make sure orgNamePlaceholder is not null or undefined.

Copy link
Owner Author

Choose a reason for hiding this comment

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

orgNamePlaceholder is a div in the template. Even if a Zendesk Curlybar helper were to fail, that div would still get rendered. Do we still need to null check?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I would do it as a fail safe for the JS side just in case someone removed it accidentally or something happened further down the line which they were unaware of the ramifications. Always better to be safe than sorry with a simple check.

Copy link
Owner Author

Choose a reason for hiding this comment

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

#73

Copy link
Collaborator

Choose a reason for hiding this comment

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

Thanks @rdai10!

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.

2 participants