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

Plugin schema too restrictive #2822

ldesplat opened this issue Oct 4, 2015 · 0 comments

Plugin schema too restrictive #2822

ldesplat opened this issue Oct 4, 2015 · 0 comments


Copy link

@ldesplat ldesplat commented Oct 4, 2015


Since Hapi 10.2 or earlier, Hapi decided to check the schema of everything that a plugin exports. Most likely due to the new features.

This breaks the Bell plugin since hapijs/bell#48 . Now, I don't mind too much just having those Utilties being provided from server.expose since Bell is meant to be used with Hapi. But, before I make any of those breaking changes I was wondering if this is intentional and if there is a plan to allow plugins to just expose plain utilities that way.

Thank you!

// this now breaks in Hapi 10
exports.providers = Providers;
exports.oauth = OAuth;

exports.register = ...

exports.register.attributes = ...
@hueniverse hueniverse changed the title Hapi 10 and checking plugin's exports schema Plugin schema too restrictive Oct 4, 2015
@hueniverse hueniverse added the bug label Oct 4, 2015
@hueniverse hueniverse added this to the 10.4.0 milestone Oct 4, 2015
@hueniverse hueniverse self-assigned this Oct 4, 2015
@hueniverse hueniverse closed this in e5d9cda Oct 4, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Jan 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants