spiff-element-units/TODO.md

# TODOs

## v0.3.1

1. document the supported element units
1. document the expected call pattern
   1. full workflow with main process id x2
   1. lazy load with subprocess id x2
   1. restore main process id/something related to call activity
1. in the integration tests, do some save/restore (maybe on human task?)
   1. or after each task and requery for that element id? perf?

## mostly unordered queue

1. write log under each cache key
1. new api to get element units without using the cache
1. new api to write existing element units to the cache
1. split cache into spiff-element-units-disk-cache
1. split spiffworkflow-specs to own lib
1. add support for the `all_specs` structure
1. cleanup the auto generated descriptions (pypi page is blank)
1. are there too many to_strings?
   1. yes tied into domain objects vs serde objects
1. there is some issue in the tests when after an rmtree the cache dir can't be created again
   1. create a test for it?
   1. not sure if it affects callers that own the cache dir
   1. ^ wtf was i thinking about here?
1. there is some issue where it takes two integration test runs for multiple-call-activities to catch up
   1. no its on run of the integration tests hashes for the ResumableSubprocess and index order change
   1. stable order in the manifest problem?
1. can dmn `decision_table`s be lazy loaded for `BusinessRuleTasks`?
   1. for "free" if we make a subprocess out of them and swap the node for a `CallActivity`?
   1. or (in some situations?) "compiled"?
1. using the serde objects as domain objects is too expensive/restrictive
   1. have intermediate objects that are ref/slice based?
   1. most likely just do for element units before returning them out
   1. could help with spec mixin interactions?
   1. specific task types?
1. need to have test versions of element units
   1. build.rs? read from disk? just hardcode?
   1. how much do we leverage the integration tests vs rust tests?
   1. when we don't use the serde objects, unit tests become easier?
1. port/use/something the env macros from typeahead
1. more macro leverage?
1. push to crates.io

## good first issues

1. when pushing for keys, if the last index is what is about to be pushed, can skip duplicating the index
   1. see simple call activity main manifest
1. "mutliple-call-activities/multiple_call_activities.json" naming has tripped me up 2x now
1. look at more (self) -> X to transition objects instead of clone
   1. must reduce the number of clones or somehow else be cleaner
   1. manifest from_element_units?
1. move more things to Iterator (element_ids, processes, etc)
1. maybe not run full build matrix on pr?
   1. nothing real arch/os specific happening so just linux/x86_64 and sdist?
1. fill out the rest of the specs.rs is_empty function
1. run integration tests as part of CI
1. run cargo tests as part of CI
   1. https://github.com/actions-rs/cargo
   1. also maybe just build the dev image and use make to also get integration tests?