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

Rename tooling config repos to use frontend-* convention #160

Open
kdmccormick opened this issue Feb 3, 2023 · 2 comments
Open

Rename tooling config repos to use frontend-* convention #160

kdmccormick opened this issue Feb 3, 2023 · 2 comments
Labels
maintenance Routine upkeep necessary for the health of the platform

Comments

@kdmccormick
Copy link
Member

Background

MFEs use frontend-app-*, MFE components use frontend-component-*, and the main frameworks just use frontend-*. As someone who doesn't usually work on the frontend, this has been pretty useful in helping me understanding what is what 💯

Suggestion

Rename the tooling config repos the same way:

  • stylelint-config-edx -> frontend-config-stylelint
  • typescript-config -> frontend-config-typescript
  • browserslist-config -> frontend-config-browserslist
  • eslint-config -> frontend-config-eslint
@kdmccormick
Copy link
Member Author

@adamstankiewicz @arbrandes Just an idea for you folks. No sweat if it doesn't seem worth the trouble.

@arbrandes
Copy link

I think a reasonable idea, but we would have to gauge the effort. It's not just renaming the repo, though we could do just that: it's also about (potentially) renaming the NPM package, which would then make it a multi-repository, backward compatibility, minor nightmare.

@arbrandes arbrandes moved this to Backlog in Frontend Working Group Feb 6, 2023
@arbrandes arbrandes added the maintenance Routine upkeep necessary for the health of the platform label Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Routine upkeep necessary for the health of the platform
Projects
Status: Backlog
Development

No branches or pull requests

2 participants