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

fixed some inherit bugs for statusbar visibility #3579

Merged
merged 2 commits into from Feb 9, 2024

Conversation

snehara99
Copy link
Contributor

I updated the default settings to actually get the inheritDefault values. Defaults in nested settings like these need to be put at the top level to be recognized. Also removed the config.ts option for project status visibility for the new presets since only the top level node on the sidebar tree should be configurable.

@@ -70,13 +70,11 @@ export interface AdvancedOptionConfig {
statusBarLength?: number;
};
packagePreset?: {
projectStatusVisibility?: ProjectStatusOptionVisibility;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why is this removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the presets are the children of the main dropdown node on the sidebar. Only the parent node should be able to be set visible or not (cpack and workflow)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

also there wasn't an equivalent setting in package.json

Copy link
Contributor

@sinemakinci1 sinemakinci1 left a comment

Choose a reason for hiding this comment

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

Issue not reproing for me now!

@snehara99 snehara99 merged commit 969ad34 into main Feb 9, 2024
4 checks passed
@snehara99 snehara99 deleted the dev/snehara/fix-inherit-setting branch February 9, 2024 19:28
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.

None yet

3 participants