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

✨ Highlight hidden config keys that have unsafe default values #11

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

hofp37
Copy link

@hofp37 hofp37 commented Jan 27, 2025

  • README update

Resolves #6

@hofp37 hofp37 requested a review from pavelsvagr January 27, 2025 16:36
@hofp37 hofp37 self-assigned this Jan 27, 2025
@hofp37 hofp37 force-pushed the feat/hidden-keys-default-values branch from a6a09ca to a38d204 Compare January 28, 2025 08:02

// ============== Underline keys with unsafe default values in config.ts file ==============
for (const hiddenKey of hiddenTsKeys) {
const safeDefaultValue =
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if the hidden value is of different type than string?

bool - We don't want to check I guess
json - {}?
number - 0? 😅
custom - Not our business I guess

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

✨ Check hidden values in default config to have no value set
2 participants