fix(elements): skip event detail generation for filtering expression tree - master#17371
Open
IMinchev64 wants to merge 1 commit into
Open
fix(elements): skip event detail generation for filtering expression tree - master#17371IMinchev64 wants to merge 1 commit into
IMinchev64 wants to merge 1 commit into
Conversation
IMinchev64
added
❌ status: awaiting-test
Contributor
There was a problem hiding this comment.
Pull request overview
Adds metadata annotations to the filtering expression tree types so the Angular Elements event pipeline can skip generating event.detail payloads for this structure (aligning with the reported issue context).
Changes:
- Marked
IFilteringExpressionsTreewith/* skipEventDetails */. - Marked
FilteringExpressionsTreewith/* skipEventDetails */.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to #IgniteUI/igniteui-blazor#230
Description
Motivation / Context
Type of Change (check all that apply):
Component(s) / Area(s) Affected:
How Has This Been Tested?
Test Configuration:
Screenshots / Recordings
Checklist:
feature/README.MDupdates for the feature docsREADME.MDCHANGELOG.MDupdates for newly added functionalityng updatemigrations for the breaking changes (migrations guidelines)