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

Validate configured options using pluginOptionsSchema #39

Closed
raae opened this issue Sep 21, 2022 · 2 comments · Fixed by #45 or #46
Closed

Validate configured options using pluginOptionsSchema #39

raae opened this issue Sep 21, 2022 · 2 comments · Fixed by #45 or #46
Assignees
Labels

Comments

@raae
Copy link
Collaborator

raae commented Sep 21, 2022

Relevant Gatsby Docs

@olavea
Copy link
Collaborator

olavea commented Sep 26, 2022

cloudinary-raae pushed a commit that referenced this issue Sep 27, 2022
Validation of plugin options through the use of Gatsby Node API's `pluginOptionsSchema`.

closes #39
cloudinary-raae pushed a commit that referenced this issue Sep 27, 2022
`type` was documented with "all" as the default value. This is the
correct mental model as an empty `type` will result in fetching all
types, but setting it to the string "all" will result it an error.

fixes #39
github-actions bot pushed a commit that referenced this issue Sep 27, 2022
# [0.3.0](v0.2.0...v0.3.0) (2022-09-27)

### Bug Fixes

* incorrect plugin option (type) validation ([#46](#46)) ([47d113a](47d113a)), closes [#39](#39)

### Features

* validation of plugin options ([#45](#45)) ([5ca373b](5ca373b)), closes [#39](#39)
@github-actions
Copy link

🎉 This issue has been resolved in version 0.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 participants