Rich talks extensively about making the distinction about a schema and about the required data within a schema when being used. A person can have many things and only some (different) parts of its data will be required in different functions. That's what the new select is about. Is there similar functionality in malli? I see {:optional true} in an

Checklist

• Did you write out a description of the feature you want to see?
• Did you look around for any related features?
• Did you specify relevant external information?

Feature Description

Add more debug logging information in the dependency API to help describe how it arrived at the order it did. Questions users might want answered:

• Why did Foo run before B

PyAF has a API call lEngine.standardPlots(). It gives some classical plots (signal against forecast, residues, trends, cycles, AR)

All the plots are generated with matplotlib

Document the plots generated.

The REST service (issue #20 ) also gives the same plots in a png/base64 encoding, to be documented.

Make it obvious that the user needs to use Multiple metaaction or just
do it silently in the background

When using a Merge function on FeatureType level and using an Aggregate function for the geometries of the source objects that are merged, this warning is displayed for the Instance transformation:
"Multiple values for source node w/o tnrasformation context"

This is expected as the mechanism which creates the warning is not aware of the fact that the Aggregate function is a greedy function usi

Currently, whenever a TU or TO fails, its error message is only showed if Butterfly is run in debug mode. The error message should be printed even in INFO level, but the error stack trace should remain only printed in debug mode.

use as monad Try[List[_]] (or just List) and implement some exploring space algorithms, such as 8 eight queens puzzle, or knight tour in the monad, to have an example, which will not compile, but will eventually be compiled after we will add more construct. This will make the game of enumerating all possible scala syntax trees not such boring ;)