-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
SECURITY: package settings (including secrets) accessible via client #308
Milestone
Comments
I had it in my mind to refactor the package / registry mechanism (and possibly |
|
aaronjudd
added a commit
that referenced
this issue
Dec 3, 2015
Changes that refactor the `ReactionCore.registerPackage` implementation to a more flexible, and structured template registry. `ReactionCore.registerPackage` moves to server. package.registry is published to client. These are not backwards compatible changes. Updated documentation at docs/packages.md Initial commit for issue #314 Strategic updates for Issue #273 Strategic updates for Issue #306 Strategic updates for Issue #305 Strategic updates for Issue #246 Strategic updates for Issue #183 Strategic updates for Issue #155 Strategic updates for Issue #16 Strategic updates for Issue #148 Resolves #53 Resolves #308 Resolves #178 *Remaining tasks* solve undefined error convert the rest of the payment packages context sensitive widgets (context?) update with detailed docs (document all the existing "provides")
aaronjudd
added a commit
that referenced
this issue
Dec 3, 2015
##package-registry-refactor Changes that refactor the `ReactionCore.registerPackage` implementation to a more flexible, and structured template registry. `ReactionCore.registerPackage` moves to server. package.registry is published to client. cycle = Core, Stable, Testing (todo: => correlates package semver) container = combine multiple registry entries These are not backwards compatible changes. Updated documentation at docs/packages.md Initial commit for issue #314 Strategic updates for Issue #273 Strategic updates for Issue #306 Strategic updates for Issue #305 Strategic updates for Issue #246 Strategic updates for Issue #183 Strategic updates for Issue #155 Strategic updates for Issue #16 Strategic updates for Issue #148 Strategic updates for Issue #146 Resolves #53 Resolves #308 Resolves #178
cmbirk
pushed a commit
to cmbirk/reaction
that referenced
this issue
Aug 18, 2019
…l-plugin chore(email-templates): update reaction-plugin-email-templates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
ReactionCore.Collections.Packages.findOne({"name":"reaction-paypal"})
Expected result:
Actual result:
This can apply to any package
The text was updated successfully, but these errors were encountered: