We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It should be interesting to persist the user object differently. Now it is persisted like this (with a property named with the userID):
The text was updated successfully, but these errors were encountered:
How would you suggest? Collections are keyed by _id for performance.
Sorry, something went wrong.
In fact this is linked with #14.
If the user object should be accessed through props in component (and is not null), then this issue #13 is deprecated.
OK, I'll take care of #14 and close this.
No branches or pull requests
It should be interesting to persist the user object differently.
Now it is persisted like this (with a property named with the userID):
The text was updated successfully, but these errors were encountered: