Skip to content
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

[firebase] force thread and module namespacing #58

Open
sloane-shark opened this issue Jul 23, 2016 · 2 comments
Open

[firebase] force thread and module namespacing #58

sloane-shark opened this issue Jul 23, 2016 · 2 comments

Comments

@sloane-shark
Copy link
Collaborator

We should enforce that any modules that try to access firebase only have access to the calling threadID and module document. For example, if someone in threadID=1 access the preferences module, that instance should only have access to /1/preferences in the firebase DB. We will probably want some whitelisted exceptions explicitly provided in firebase.js, like giving all modules access to a threads general preferences.

@kedarv
Copy link
Collaborator

kedarv commented Nov 4, 2016

I think this is already being done to some extent

@sloane-shark
Copy link
Collaborator Author

well its done by convention, but my intention here was to actually force modules to do it somehow. idk if thats feasible.

@kedarv kedarv added the wontfix label Nov 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants