What's difference between DocumentRootName and DatabaseRootName?
See original GitHub issueIt seem both class has nearly the same code and property. And DocumentRootName
was not used anywhere. Something seem wrong here
Also I was suspect that DocumentRootName
and DocumentPathName
and AnyPathName
should contains “CollectionID” because the nature of FireStore system need CollectionID to be the parent of all documents. Hence the root of document should have collection name specified
Issue Analytics
- State:
- Created 6 years ago
- Comments:14
Top Results From Across the Web
Enum DocumentChange.Type (3.9.2) | Java client library
Indicates a new document was added to the set of documents matching the query. MODIFIED. Indicates a document within the query was modified....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The new packages are now pushed to nuget.org, so you should be able to pick them up.
Yes, I raised the high level API in this issue - because if we can fix everything that’s preventing you from using the high level API, you won’t need to worry about things like this issue. I will always prioritize issues with the high level API over questions around the low level API because they will be useful to more customers.
It sounds like a single new issue is all that’s required, explaining what you want your code to look like. Note that we wouldn’t take a direct dependency on Json.NET - there’s already an indirect one, but we’re hoping to get rid of that over time. So while I wouldn’t expect serializing a
JObject
to work necessarily, it seems reasonable to want to serialize anIDictionary<string, Foo>
whereFoo
is any type that can normally be serialized as a value. I’ll start working on the code for that - if you could file the issue so I can make sure that the change satisfies it, that would be appreciated.Basically I’m very keen on getting you to the stage where you can use the high level API. You gave a “thumbs up” to my previous pull request, so I assumed that was the only change required. Please feel free to file issues about anything that’s blocking you from using the high level API, as it may well affect others too. I can’t guarantee that we can satisfy everything directly, but we’ll see what we can do.