Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

feature: support frameworks with identical configuration file names and no dependencies #329

Open
erezrokah opened this issue Jun 30, 2021 · 0 comments
Labels
type: feature code contributing to the implementation of a feature and/or user facing functionality

Comments

@erezrokah
Copy link
Contributor

Which problem is this feature request solving?

Some frameworks don't have any local dependencies and might have the same configuration file.
See #326 (review)

We should find a way to support such use cases.

Describe the solution you'd like

A possible solution would be to allow pattern matching in files' content.

Describe alternatives you've considered

Keep things as is, which will result in reporting multiple frameworks in some cases.

Can you submit a pull request?

Yes

We should consider that this should be supported for both Node.js and the browser

@erezrokah erezrokah added the type: feature code contributing to the implementation of a feature and/or user facing functionality label Jun 30, 2021
@erezrokah erezrokah changed the title Please replace with a clear and descriptive title feature: support frameworks with identical configuration file names and not dependencies Jun 30, 2021
@erezrokah erezrokah changed the title feature: support frameworks with identical configuration file names and not dependencies feature: support frameworks with identical configuration file names and no dependencies Jun 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Development

No branches or pull requests

1 participant