Use barrel files for features

[marfavi]

A barrel file is a file in a folder that exports all dart files within it.

It greatly reduces the amount of imports in files that need to refer to a feature, improving code legibility.

There's an extension that can generate these files for us.

https://marketplace.visualstudio.com/items?itemName=miquelddg.dart-barrel-file-generator

[jonasanker]

I think we should be very mindful about the trade-off. It might be that it makes imports looks smaller but it also hides usages of files, can affect refactorings and lead to importing more than what is needed.

I would question if this would solve a real problem for us compared to possible side effects.
It's probably more a code design smell that our features are not cleanly designed if we have a need for Barrel files.

See this opinionated blog on Barrel files https://steven-lemon182.medium.com/are-typescript-barrel-files-an-anti-pattern-72a713004250

[marfavi]

I agree with you @jonasanker. Closing this issue

[marfavi]

Re-opening with POC pull request at #570.

The interest for barrel files now stems from the desire to keep feature changes encapsulated, meaning that if I change one feature, we want to minimise the amount of file changes from outside that feature. Let's talk

[marfavi]

Maybe we can use this package to generate barrel files?

https://pub.dev/packages/barrel_files/example