(feature) Allow custom hide columns action #833
Merged
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.
Dear Team,
First and foremost, I want to express my heartfelt gratitude for the incredible work each of you has contributed. Over the past year, I've had the pleasure of utilizing this package, and I must say, I've thoroughly enjoyed it.
Description
Upon delving into how custom actions are rendered and handled, I've observed that they lack access to crucial data such as
columns
and event callbacks likeonColumnsChanged
oronSearchChanged
. Providing access to this data would empower users to customize the behavior of default actions.Impacted Areas in Application
List general components of the application that this PR will affect:
MTableToolbar
MTableActions
MTableAction
Additional Notes
There are multiple approaches to implementing the overwrite of default actions' behavior, and I am open to hearing your insights on the matter.
I am eager to tackle this task with your expert guidance and oversight, ensuring that we maintain the highest quality standards that you consistently uphold.