Kai
Kai
Currently the docs for distage and logstage are too dry. They list features, a couple of examples, but overall they do not provide a unified view on how an idiomatic...
Currently `LocatorRef` is implemented as a magic `Import` instruction, that's handled differently from other imports. This forces unnecessary workarounds e.g. in `OrderedPlan#unresolvedImports` where this magic import must be filtered out:...
`distage-extension-logstage` is pretty useless right now. Moving configuration reader there would make it more useful. Also, configuration reader / pureconfig instance should be in `logstage-core`, without distage dependency
Some logstage features exist but are undocumented. You can notice them in example code, but they're not explained in detail or named directly, time to fix that! - [ ]...
Related to https://github.com/7mind/izumi/issues/653, make exposed distage API's more opinionated, e.g. make `produceF` the only clearly visible default and stuff impure APIs into a separate namespace.
BIO hierarchy is missing a `Resource` type, but there's already one in `distage`! There's currently no effect-type generic fully covariant resource type in ecosystem - except Lifecycle! Since it's not...
We currently use `DIEffect` typeclass in distage for interoperability with monofunctor effect types that define a `Sync` instance, even though the bifunctor case is handled by `BIO`. There's a way...
After version `distage` `0.10`, `SymbolInfo` no longer contains trees for all the annotations on the symbol (because we can't depend on `scala-reflect`, so we can't represent trees) That means user-defined...
`ModuleDefDSL#include`, `ModuleBase#++` & `(Seq[ModuleBase])#merge`, `ModuleBase#morph` methods are not mentioned on the microsite.