Bloc: [VSCode Extension] Infer Equatable usage

[Jomik]

Is your feature request related to a problem? Please describe.
It is quite frustrating to miss question to use Equatable and hit "no" by mistake..

Describe the solution you'd like
If equatable is in my pubspec, we could assume that I want to use it.
Probably an option to enable/override it.

Describe alternatives you've considered
A configuration option.

Additional context
Would we ever _not_ want to use Equatable, if it is in our pubspec? I suppose if you use freezed, etc. you may not want to. So we should probably give an option to disable this "smart" behavior.

[felangel]

Hi @Jomik 👋
Thanks for opening an issue!

I think this is an interesting feature request and I have always had the idea of a bloc.yaml configuration file that could be checked into source control and be used for global configuration settings like the one you described. What do you think?

[Jomik]

Hmm, I think it fits better to use VSCode's configuration system.
You can create workspace specific configuration, that can be checked into version control.

We can then go all in and actually create an option to use freezed as well.

[felangel]

@Jomik ideally I’d want to share the configuration across multiple IDEs though.

[Jomik]

Hmm, I can understand that. But the extension is IDE specific?
Solution could be to allow both options?
So that if a bloc.yaml exists, that will be used.

[felangel]

There's an equivalent plugin for intelliJ haha and yup that could work as well.

[tenhobi]

Rather than bloc.yaml, we could use settings in pubspec.yaml. Other packages (flutter, flutter_icons, flutter_native_splash etc.) use it as well. Then you could set up what you wanna use for a generation: nothing, equatable, freezed etc.