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

config intellisense #128

Merged
merged 12 commits into from
Sep 19, 2023
Merged

config intellisense #128

merged 12 commits into from
Sep 19, 2023

Conversation

claytercek
Copy link
Member

@claytercek claytercek commented Sep 18, 2023

Took a pass at adding intellisense to config files via the defineConfig method mentioned in #125. This is downstream of #118 and #124.

  • narrowed most of the vague types (any, *, {}, and object)
  • converted classes to JSDoc type definitions
  • added functions to apply defaults to high level configs
  • added defineConfig function exported from the core package, as well as a defineContentConfig exported from the content package, and a defineMonitorConfig exported from the monitor package

resolves #125

Intellisense in action here:

Screenshot 2023-09-18 at 2 20 52 PM

@claytercek claytercek changed the base branch from main to develop September 19, 2023 00:07
@claytercek claytercek merged commit 0284121 into develop Sep 19, 2023
@claytercek claytercek deleted the feat/config-intellisense branch September 19, 2023 21:38
@github-actions github-actions bot mentioned this pull request Sep 19, 2023
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.

Intellisense for configs
2 participants