[ENHANCEMENT] Query String: Improve Filter Control and add prefix (for usage w/ multiple tables) #1566
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
⚡ PowerGrid - Pull Request
Welcome and thank you for your interest in contributing to our project!. You must use this template to submit a Pull Request or it will not be accepted.
Motivation
Description
This Pull Request aims to improve the filter control while using Query String and adds the possibility to prefix fields, to use query string with more than one component in the same page.
Filter control
❌ BEFORE
🚀 AFTER
Prefix Query String (Multiple Components)
When using multiple components, the user must pass the parameter
$prefix
to thepowerGridQueryString()
. As a result, each URL parameter will be prefixed with the provided prefix:While we could use the
$tableName
as a prefix, I think it's best to give the user control so they can decide what is in the URL. Some people my prefer "table_name" instead of "dish_table_name".I could not find a way to write proper tests for query-string.
Related Issue(s): #1563
Documentation
This PR requires Documentation update?