hark130 / daunting-aggregate Goto Github PK

Change the appearance of a node if it is unblocked and not yet complete.
This particular feature would be very useful to visually "call out" blocking nodes.
However, it also makes some assumptions as to what the "status" field means.
Maybe, the user inputs "status flow", in order, to help inform this algorithm.
If that's the case, it should be blocked by #8 because the current format doesn't easily/cleanly support another one-off like "Color Scheme".

Check for existing edges before adding any. (No need for two arrows on the DAG!)

• Directed graphs nodes are given a pattern (e.g., component, type, status)

TO DO: DON'T DO NOW... Decide what to base the pattern off of. Probably "type".

A database entry that isn't long enough produces: VALUE ERROR: not enough values to unpack (expected 2, got 1)

Instead, it should produce: VALUE ERROR: Line number {} is too short/long or something similar.
Something that is specific, detailed, and (most importantly) actionable.

Additionally, a database entry that's too long doesn't produce any error at all. Fix it.

• Directed graph nodes are color coded (e.g., component, type)

TO DO: DON'T DO NOW... Decide what to base the color off of. Probably "status".

• Python package
• Takes a database file as CLI input
• Reads database file
• Creates a directed graph based on the database file

• Setup script releases DAAG as a wheel
• Wheel installs
• DAAG available from the CLI

Choose an actual format: INI, YAML, etc.

This will likely result in a major release (if #2 has been completed).