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

feat(search): Add Search Functionality to Resource List in Insights Page #788

Merged
merged 5 commits into from
Feb 10, 2025

Conversation

Cookiery
Copy link
Contributor

@Cookiery Cookiery commented Feb 9, 2025

What type of PR is this?

/kind feature
/kind chore

What this PR does / why we need it:

  • Add Search Functionality to Resource List in Insights Page
  • Update Makefile to use full path for swag and swagger commands

Which issue(s) this PR fixes:

#679

- Update Makefile to use full path for swag and swagger commands
- Add 'keyword' query parameter to OpenAPI specification files
- Modify search handler to support keyword filtering in SQL queries
- Enable keyword search in UI search input component
@Cookiery Cookiery changed the title feat(search): add optional keyword search parameter feat(search): Add Search Functionality to Resource List in Insights Page Feb 9, 2025
@elliotxx
Copy link
Collaborator

elliotxx commented Feb 9, 2025

Your movement is fast, let me take a look at these modifications.

Copy link

@MDA1422 MDA1422 left a comment

Choose a reason for hiding this comment

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

Are there any specific scenarios or edge cases that we should test for the keyword search functionality?

Copy link

@MDA1422 MDA1422 left a comment

Choose a reason for hiding this comment

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

Is the updated documentation compliant with any particular markdown rendering requirements or guidelines?

@Cookiery
Copy link
Contributor Author

Is the updated documentation compliant with any particular markdown rendering requirements or guidelines?

Yes, the doc is generated by make gen-api-doc, but when i submitted it, I found that there were several places that needed manual line breaks, or needed to add <br> in the comments.

@Cookiery
Copy link
Contributor Author

Are there any specific scenarios or edge cases that we should test for the keyword search functionality?

The only other character that could affect it is spaces, so I can add a line to remove spaces. I don't have any other ideas. Initially, I thought about preventing SQL injection, but the input query is already an SQL statement.

Copy link
Collaborator

@elliotxx elliotxx left a comment

Choose a reason for hiding this comment

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

lgtm

@elliotxx elliotxx merged commit 67c1c5d into KusionStack:main Feb 10, 2025
9 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants