Uh oh!
There was an error while loading. Please reload this page.
Fix(Config): prevent undefined array key from first configuration - #61
Merged
Conversation
stonebuzz
commented
Sep 4, 2025
ContributorAuthor
need #60 to get |
2 tasks
stonebuzzforce-pushed
the
fix_warning_from_fist_config
branch
from
September 4, 2025 12:48
b0d4c4d to
079fc47CompareMary-Clb
approved these changes
Sep 4, 2025
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist before requesting a review
Please delete options that are not relevant.
Description
When configuring the plugin for the first time, three warnings were displayed because no values existed yet for non-initialized fields:
This PR prevents these warnings from being triggered during the initial setup.
Screenshots (if appropriate):