-
Notifications
You must be signed in to change notification settings - Fork 58
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
Support for nested properties setting customKey in collection.add() method? #88
Comments
@MichaelSolati any update on this? |
I have a plan in mind but I just haven't had time to get to this. I should have something by the end of the month though |
@MichaelSolati I need this feature as soon as possible, when do you think it will be available? |
@paolospag So I think this will work, it required more work then I thought and as I have been traveling I haven't had the time to fix it.
If it works I'll deploy it to NPM. |
@MichaelSolati Sorry for my late response. Thank you for the stuff, I'll take a look tomorrow and I'll let you know. |
@MichaelSolati I confirm that it now works exactly as I expected, thanks a lot! Please notify me on this issue when you deploy it to npm, then you can close this issue. |
Hi,
I'm using this awesome library to perform nearby query, but I noticed a limit when call
add()
method providingcustomKey
param: I'm not able to set nested properties of data object, i.e.place.coordinates
, and looking at the code I found this limit inutils.ts
: https://github.com/geofirestore/geofirestore-js/blob/master/src/utils.ts#L295My question: is it possible to add support for nested properties? I would like to do something like that:
Probably this isn't a bug issue or something like that, but it could be an enhancement.
The text was updated successfully, but these errors were encountered: