-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tree: Add schema symbol to TreeNodes to allow NodeKind based narrowing. #22222
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
45d863c
Add schema symbol to TreeNodes to allow NodeKind based narrowing.
CraigMacomber 629bb2a
Update packages/dds/tree/src/simple-tree/core/withType.ts
CraigMacomber 1ba7c27
Better docs
CraigMacomber abd7f50
Update example
CraigMacomber 112af61
Fix index export commented sections
CraigMacomber File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
--- | ||
"fluid-framework": minor | ||
"@fluidframework/tree": minor | ||
--- | ||
--- | ||
"section": "tree" | ||
--- | ||
Enable compile time type narrowing based on a TreeNode's NodeKind. | ||
|
||
TreeNode's schema aware APIs implement WithType, which now has a NodeKind parameter that can be used to narrow TreeNodes based on NodeKind. | ||
|
||
Example: | ||
|
||
```typescript | ||
function getKeys(node: TreeNode & WithType<string, NodeKind.Array>): number[]; | ||
function getKeys(node: TreeNode & WithType<string, NodeKind.Map | NodeKind.Object>): string[]; | ||
function getKeys(node: TreeNode): string[] | number[]; | ||
function getKeys(node: TreeNode): string[] | number[] { | ||
const schema = Tree.schema(node); | ||
if (schema.kind === NodeKind.Array) { | ||
const arrayNode = node as TreeArrayNode; | ||
const keys: number[] = []; | ||
for (let index = 0; index < arrayNode.length; index++) { | ||
keys.push(index); | ||
} | ||
return keys; | ||
} | ||
if (schema.kind === NodeKind.Map) { | ||
return [...(node as TreeMapNode).keys()]; | ||
} | ||
|
||
return Object.keys(node); | ||
} | ||
``` |
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Best practices question, since this example is end-user-facing: should we use a
switch
here with a default handler that errors on unrecognized node kind? I don't know how likely it is that we will add a fundamentally new node type any time soon, but if we were to do so, the default behavior here may not be what the user wants.Seems like the switch pattern highlights this potential better. Curious what others think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.