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

NIFI-13853: Added the ability to filter by all to the Advanced Rules page #9371

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

HunterG6700
Copy link
Contributor

@HunterG6700 HunterG6700 commented Oct 9, 2024

Summary

NIFI-13853
Added the ability to filter on text anywhere in the UpdateAttribute advanced rules. Currently you can filter by matching text in Rule name, the Conditions, Comments, and the Actions. So I added an option to filter "Anywhere", if the search string matches anywhere in a rule, that rule will be displayed.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • Build completed using mvn clean install -P contrib-check
    • JDK 21

Licensing

  • New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • Documentation formatting appears as expected in rendered files

@HunterG6700 HunterG6700 changed the title NIFI-13853: Added the ability to filter by all to the Advanced Rules pag NIFI-13853: Added the ability to filter by all to the Advanced Rules page Oct 9, 2024
Copy link
Contributor

@exceptionfactory exceptionfactory left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution @HunterG6700. I noted some code formatting issues, and a labeling recommendation, but I will defer to @mcgilman or @scottyaslan for additional input from a frontend implementation perspective.

return actions;
}
} else if (filterType.value === 'action') {
var actions = [];
Copy link
Contributor

Choose a reason for hiding this comment

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

The indentation appears to be off in this new block, in comparison with the other blocks.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you I didn't notice that I thought my IDE auto formatted it.

@@ -201,6 +201,9 @@ var ua = {
}, {
text: 'by action',
value: 'action'
}, {
text: 'filter everything',
Copy link
Contributor

Choose a reason for hiding this comment

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

Following the existing pattern, it seems like it would be better to call this by any field or by any property.

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