Support dart_dependency_validator.yaml at the root of a pub workspace

[MobiliteDev]

Is there a way to use dependency_validator in pub worspace, with a dart_dependency_validator.yaml file at the root of the workspace ?

For example, I need to add camera_android on all my apps pubspec.yaml in my workspace (to override camera plugin behavior)

So I would like to add a dart_dependency_validator.yaml file at the root of the workspace with this.

ignore:
  - camera_android

And run dart pub global run dependency_validator' which use it. And If dependency_validator' finds other dart_dependency_validator.yaml file in workspace packages/apps, it should combines dart_dependency_validator.yaml options. If the same property is found in sub package, I think the sub dart_dependency_validator.yaml file should overrides the 'default' same option found in the worskpace root dart_dependency_validator.yaml.

[matthewnitschke-wk]

Hi @MobiliteDev!

If we apply the root dart_dependency_validator.yaml to all sub-packages, we will loose the ability to specifically ignore just the root package dependencies

We could potentially add a new field to the dart_dependency_validator config, something like global:

global:
  ignore:
    - camera_android

But I'm not convinced that this additional layer of configuration is fully necessary. You could either just create an individual file in each package and duplicate the config, or syslink them

Is there a reason why those two options don't work for you?

[MobiliteDev]

Thank you for your quick answer.
the goal was precisely to not duplicate files in each project to avoid erros, ensure integrity and facilitates the maintain in the workspace.
I haven't studied syslink yet.

Adding a 'global' option seems to be a good option, but in a worspace root dart_dependency_validator.yaml file.

I think this 'global' option could be complementary with 'specific' sub-package config, what do you think ?
sub-package config should be always the finest configuration.