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
In my testing, if two projects are both loaded and use the authorized module, the state is shared between the two projects.
authorized
So if one project defines an edit user action and a second project defines an edit user action, the second would overwrite the first.
edit user
At a minimum, the documentation should disclaim the singleton behavior and note that it's only intended to be used by project at a time.
The text was updated successfully, but these errors were encountered:
document singleton behavior, how to create new instances
e788510
and how to share state between multiple instances. Fixes tschaub#10
d1a33fb
Successfully merging a pull request may close this issue.
In my testing, if two projects are both loaded and use the
authorized
module, the state is shared between the two projects.So if one project defines an
edit user
action and a second project defines anedit user
action, the second would overwrite the first.At a minimum, the documentation should disclaim the singleton behavior and note that it's only intended to be used by project at a time.
The text was updated successfully, but these errors were encountered: