This repository was archived by the owner on Jun 28, 2026. It is now read-only.
Expose processedData in DataTable#8181
Merged
Merged
Conversation
|
Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>. |
1 similar comment
|
Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>. |
melloware
approved these changes
Aug 2, 2025
Member
|
I am not sure this is the best name for the exposed method? I am trying to think of a better one but can't! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR exposes the
processedData()method in theDataTablecomponent.The purpose of this change is to enable the implementation of custom export functionality that respects the currently applied filters. Currently, the built-in
exportCSV()method usesprocessedData()internally to retrieve filtered and sorted data. By making this method accessible, custom exporters can achieve the same behavior and maintain consistency with the built-in export logic.Old but still relevant discussion here: https://github.com/orgs/primefaces/discussions/23