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.

Sign up for GitHub

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

Jump to bottom

Make Config completely optional for plugins #9502

Merged
merged 2 commits into from Oct 7, 2022
Merged

Make Config completely optional for plugins #9502

merged 2 commits into from Oct 7, 2022

Commits on Oct 7, 2022

  1. Make Config completely optional for plugins 

    Right now the `Config` type requires a `content` key. However, for plugins, this should be completely optional. There’s little reason for a plugin to override content. All other keys are already optional by virtue of using `Partial<…>` so we’ll do the same for the `Config` type used by plugins.
    @thecrypticace
    thecrypticace committed Oct 7, 2022
    Copy the full SHA
    14a571a View commit details
    Browse the repository at this point in the history

  2. Update changelog

    @thecrypticace
    thecrypticace committed Oct 7, 2022
    Copy the full SHA
    2915060 View commit details
    Browse the repository at this point in the history