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.
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
(DOCSP-20071) Update TS Limitations #275
(DOCSP-20071) Update TS Limitations #275
Changes from 31 commits
70649c4
fd76f80
438156c
42cae8c
fc3537b
1853bf5
ea95abc
b35c0d9
a758cdd
4ba4c20
47ec306
079cd5e
1be07ca
f61c9f1
7e36683
f2ec69e
eb77c53
2d3cc37
b48748e
e1648d0
ad6c58d
f45b0a8
fe64c9f
353416a
4bfa35e
f7967df
e3f65ec
8bd69e4
06de329
8fb218b
6276c5d
36730a5
67dc810
cc4fdb1
ad3b47e
59ed5e0
7a1748f
8c97f31
11ba220
5a41582
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Just a note that this will probably need to change soon to something like$-prefixed but allow all $ -prefixed keys for forward compatibility with new server operators. Right now the corresponding note is correct, but once we release a fix, it will need to be updated.
{ $unknownOperator: "Accepts any type!" }
because we actually have a user submitted fix to make sure that we validate unknown keys that aren't(see mongodb/node-mongodb-native#3115)
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.
Hi Daria! There is a ticket to add the "query nested fields without dot notation" example back to a different section of the documentation (DevED-DBX agreed that TS page seemed only tangentially related to dot notation and was not the correct place for this content).
The page that should explain to readers how to use Dot Notation is the Update Arrays in a Document Page (linking to Java), however it seems like the corresponding Node page does not explicitly discuss dot notation. I've created a ticket to add this content .
As this PR has already been through a few internal reviews and has grown to be fairly large, I think it is best to close out this pull request and handle the upcoming changes as part of a new task (any substantial additions will require an additional copy review which will take a decent amount of time as the diff for this PR has become pretty big).
Sorry for the long response! Let me know if I have failed to address any of your concerns.
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.
I'm fine with doing the $-prefix updates later, but I really feel like the current page could benefit from a working example of dot notation type hinting use (i.e., show how having the wrong type in a non-recursive collection definition raises a typescript error)
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.
Good point, I agree an example of working dot notation type checking would benefit readers. I've added a "dot notation" subsection to the Features section Let me know if this addresses your concerns!
This file was deleted.