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

Format resource name in FindResourceDialog to include type and audience #37636

Merged
merged 4 commits into from Nov 3, 2020

Conversation

bethanyaconnor
Copy link
Contributor

@bethanyaconnor bethanyaconnor commented Nov 3, 2020

This came out of the bug bash, as often times multiple resources have the same name.

Screenshot 2020-11-03 at 8 03 53 AM

Links

Testing story

Reviewer Checklist:

  • Tests provide adequate coverage
  • Privacy and Security impacts have been assessed
  • Code is well-commented
  • New features are translatable or updates will not break translations
  • Relevant documentation has been added or updated
  • User impact is well-understood and desirable
  • Pull Request is labeled appropriately
  • Follow-up work items (including potential tech debt) are tracked and linked

if (resource.properties.type) {
formattedName += ` - ${resource.properties.type}`;
}
if (resource.properties.audience) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Did they request to have it include audience too? I think it was just type

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, just type was brought up I think. Do you think I should remove audience? I don't have an opinion either way really -- just thought it might be easier to see audience too

Copy link
Contributor

Choose a reason for hiding this comment

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

I think audience makes it long and I don't think its that helpful in this context so I would leave it off until we get asks for it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

okay -- will change. Thanks!

@bethanyaconnor bethanyaconnor merged commit 32604a0 into staging Nov 3, 2020
@bethanyaconnor bethanyaconnor deleted the better-resource-dropdown-names branch November 3, 2020 22:21
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.

None yet

2 participants