Shared interface between CapsuleContainer and CapsuleReader

[busslina]

Do you think would be possible (and a good idea) to have a common interface between CapsuleContainer and CapsuleReader?

My use case is very simple. I have to duplicate every entry on my extensions on both types:

extension CapsuleContainerExt on CapsuleContainer {
  Language get language => read(languageCapsule);
}

extension CapsuleReaderExt on CapsuleReader {
  Language get language => call(languageCapsule);
}

[GregoryConrad]

You shouldn't really be reading stuff directly from the CapsuleContainer unless you're writing a Dart-only app and/or are doing some weird edge case stuff where you can't use a regular capsule (routing in Flutter comes to mind with some imperative APIs).

And seeing as CapsuleReader interface is set in stone from v1 release, and only exposes the call() function, it wouldn't make sense to write something like:

final container = CapsuleContainer();
final something = container(someCapsule);

Besides, not sure I'd really recommend adding extensions onto CapsuleReader anyways--too easy to get them confused with side effects since that will be the same syntax. I.e.,

final lang = use.language;

Looks like it is a side effect, possibly a WidgetSideEffect that uses BuildContext to access a localization preference. You shouldn't mix capsule reads in there

[busslina]

I understand.

You shouldn't really be reading stuff directly from the CapsuleContainer unless you're writing a Dart-only app...

My use-case is backend side, but also flutter side when using external libraries which are not prepared to be integrated into ReArch declarative flow. E.G. Beamer Router.

easy to get them confused with side effects since that will be the same syntax

This could be solved by using some identifying syntax like putting and end character (use.language_).
Also, I only use this technique with a few capsules that are used a lot, making them easier to type.

I fully understand you point, but I don't get to the point of 100% declarative, even if there is no external library forcing me in the opposite direction. There is always cases where I have to use the container... But of course I will continue to improve my coding willing to be the closest to that 100%.

:)