Closed oklas closed 2 years ago
I think a better solution to prevent name-specific
issues would be to match [jt]sconfig\..*\.json
. Is this something you would consider? If so, I can open a PR
Hi Urmzd, this pr mostly workaround than final. Actually it must not to guess the name of config file. If you have some case that may not be solved, then explain it.
Hi @oklas, use any path that deviates from the pattern ^[jt]sconfig(\.paths)?.json
, and the plugin cannot resolve the aliases correctly. This is problematic for two reasons
For these reasons, I think we should allow users to use different names. We don't have "guess" the name, but rather grab the file path from "extends". What do you think?3
Closes #41