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

Update configs #8

Merged
merged 2 commits into from
Jan 5, 2023
Merged

Update configs #8

merged 2 commits into from
Jan 5, 2023

Conversation

kevinwcyu
Copy link
Collaborator

Updates configuration for

  • Prettier
  • Eslint
  • Jest

Removes

  • @grafana/tookit

The configuration updates made match what is used scaffolded by the create-plugin tool. The only difference is I added the configuration files to the root directory instead of a separate .config dir (for an example of this see how the configuration is setup in redshift-datasource.

Dependencies were also updated in order to support the updated configurations.

@kevinwcyu kevinwcyu force-pushed the kevinwcyu/update-configs branch 2 times, most recently from 083c4d7 to f98cc6d Compare January 3, 2023 14:50
@kevinwcyu kevinwcyu requested review from a team, iwysiu and idastambuk and removed request for a team January 3, 2023 14:50
@kevinwcyu kevinwcyu marked this pull request as draft January 3, 2023 15:06
@kevinwcyu kevinwcyu marked this pull request as ready for review January 3, 2023 19:40
Copy link
Member

@sarahzinger sarahzinger left a comment

Choose a reason for hiding this comment

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

Seems reasonable! Had another idea but I defer to your thoughts on it!

@@ -1,3 +1,10 @@
module.exports = {
...require('@grafana/toolkit/src/config/prettier.plugin.config.json'),
Copy link
Member

Choose a reason for hiding this comment

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

what do you think of having a .config folder and extending that rather than copying over the contents of the config folder into our config pages. That way its a bit more obvious what pieces we are directly extending in this repo and what pieces are coming from some sort of default configuration setting? Also if there ever is a way to like migrate to new configuration settings maybe it'll be easier?

@kevinwcyu kevinwcyu requested a review from a team as a code owner January 5, 2023 21:09
@kevinwcyu kevinwcyu merged commit 0cdd781 into main Jan 5, 2023
@kevinwcyu kevinwcyu deleted the kevinwcyu/update-configs branch January 5, 2023 21:16
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