Skip to content

feat: Add covered and optimal query examples CLOUDP-311782 #6883

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

Merged
merged 3 commits into from
Apr 29, 2025

Conversation

rubydong
Copy link
Collaborator

@rubydong rubydong commented Apr 28, 2025

Description

https://jira.mongodb.org/browse/CLOUDP-311782

Best viewed with 'hide whitespace'

Added a tooltip for when the type is not supported:
image

Default state:
image

One field:
image

Two fields:
image

Three fields:
image

Checklist

  • New tests and/or benchmarks are included
  • Documentation is changed or added
  • If this change updates the UI, screenshots/videos are added and a design review is requested
  • I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

  • Bugfix
  • New feature
  • Dependency update
  • Misc

Types of changes

  • Backport Needed
  • Patch (non-breaking change which fixes an issue)
  • Minor (non-breaking change which adds functionality)
  • Major (fix or feature that would cause existing functionality to change)

@github-actions github-actions bot added the feat label Apr 28, 2025
@rubydong rubydong added the no release notes Fix or feature not for release notes label Apr 28, 2025
@rubydong rubydong marked this pull request as ready for review April 28, 2025 20:07
Copy link
Member

@Anemy Anemy left a comment

Choose a reason for hiding this comment

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

Looking good, left a couple questions/comments

@@ -173,25 +173,30 @@ const IndexFlowSection = ({
{}
);

const coveredQueriesArr = fields.map((field, index) => {
return { [field.name]: index + 1 };
const [coveredQueriesObj, setCoveredQueriesObj] = useState<{
Copy link
Member

@Anemy Anemy Apr 29, 2025

Choose a reason for hiding this comment

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

When the user changes the fields should we reset this so that they have to re-click the show covered queries button? That way we don't show them something out of date. Fine as is also, I'm mostly thinking if it's a nicer experience for the user one way.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

https://jira.mongodb.org/browse/CLOUDP-311787 i have this ticket for polishing up all the UX for further disabled states, error states etc for everything across the modal

@rubydong rubydong merged commit ec89d93 into main Apr 29, 2025
52 of 54 checks passed
@rubydong rubydong deleted the cloudp-311782 branch April 29, 2025 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat no release notes Fix or feature not for release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants