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

Improve Default Workspace Settings #270

Closed
scott-joe opened this issue Sep 23, 2020 · 1 comment
Closed

Improve Default Workspace Settings #270

scott-joe opened this issue Sep 23, 2020 · 1 comment

Comments

@scott-joe
Copy link
Contributor

Pulled from Roadmap item: Improve Default Workspace Settings (stub)

Required

  • Are there goals that these settings should meet?

Conversation Starters

  • Is the assumed workspace configuration the most basic one? Notes in the top level?
  • How opinionated are these?
  • Do they include configs for the required plugins?
  • Do we have multiple sets/levels that can be chosen from with a simple filename change?
    • E.g.: basic.settings.json, blogger.settings.json, aggressive.settings.json etc. renamed to .settings.json would "choose" that set.
  • Are these a part of Recipes?
  • Can this be part of an initialization script?
@riccardoferretti
Copy link
Collaborator

I didn't create that page so don't have much context on it, but let me share my thoughts.

  • Is the assumed workspace configuration the most basic one? Notes in the top level?

My guess is to be unopinionated where possible, and make it easy (docs, cli commands, ...) to change

  • How opinionated are these?

Little where possible :)

  • Do they include configs for the required plugins?

Yes

  • Do we have multiple sets/levels that can be chosen from with a simple filename change?

That could be an interesting approach

  • Are these a part of Recipes?

Definitely settings should be documented, yes

  • Can this be part of an initialization script?

Yes

@riccardoferretti riccardoferretti closed this as not planned Won't fix, can't repro, duplicate, stale Nov 13, 2022
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

No branches or pull requests

2 participants