Replies: 1 comment 1 reply
-
Hey @icopp, Thanks for taking the time to create this discussion! This is a valid use case and I think this feature would help simplify the config when you have a lot of files as you mentioned. The Do you feel comfortable creating a PR for this or should I implement it? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For an example of what I mean, let's say I have these:
...except, I don't actually want to copy the
.eslintrc
orjest.config.js
files to theeslint-config-org-name
orjest-preset-org-name
repo respectively, because neither tool can handle a recursive reference in a config file ("extends": "@org-name/eslint-config-org-name"
inside that package itself will just result in anot found
).The syntax could potentially look like:
This would simplify the logic around working with any really long lists of files and repos.
Beta Was this translation helpful? Give feedback.
All reactions