It would be slick to be able to provide configuration via bsconfig.json. Real world use cases I had in mind after running reanalyze on a fairly large and diverse project:
Having a bindings folder with ad hoc bindings, where you really want to consider all of the code in there live (like it's an actual lib).
Using things like Storybook that expects you to have a bunch of files/components that are exported to Storybook, but that reanalyze will think are dead since they're never used in the app itself.
I believe this is possible to suppress via CLI args right now. But, it'd be slick to be able to configure it via bsconfig.json too, so that general tooling (like a dead code mode in the editor extension) can take advantage of the config too. Maybe letting the CLI args override the eventual values in bsconfig.json?
It would be slick to be able to provide configuration via
bsconfig.json. Real world use cases I had in mind after runningreanalyzeon a fairly large and diverse project:bindingsfolder with ad hoc bindings, where you really want to consider all of the code in there live (like it's an actual lib).reanalyzewill think are dead since they're never used in the app itself.I believe this is possible to suppress via CLI args right now. But, it'd be slick to be able to configure it via bsconfig.json too, so that general tooling (like a dead code mode in the editor extension) can take advantage of the config too. Maybe letting the CLI args override the eventual values in bsconfig.json?