Feature: Allow functions for node Fields#945
Open
IBlackI wants to merge 3 commits intoCirclonGroup:masterfrom
Open
Feature: Allow functions for node Fields#945IBlackI wants to merge 3 commits intoCirclonGroup:masterfrom
IBlackI wants to merge 3 commits intoCirclonGroup:masterfrom
Conversation
Add eslint Add core-js Enable Ivy Enable Aot Fix polyfills Fix lint errors Fix template compilation errors Fix example-app build Fix docs-app build Fix cyclical component references (angular/angular#43227 (comment)) BREAKING CHANGE: Library is now build with 'partial' Ivy
Functions can be used to retrieve the value of Fields for nodes. resolve CirclonGroup#793
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
3 participants
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.
Pull request depends on #942
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently it is impossible to use the data of the node to programmatically determine the display. You can only use fixed values of the top level of the node data.
Resolves #793
What is the new behavior?
A function can be passed through the tree options which will evaluate the values for each node in the tree.
Does this PR introduce a breaking change?
Other information