Awesome! I’ll get that together.
I’d also like to propose an option to relax attr key restrictions… Currently only attrs with keys defined in the spec will assigned at node creation due to computeAttrs; extra keys are silently ignored.
If there were a spec option to allow undefined keys, or perhaps keys matching some pattern, then arbitrary metadata could be stored in attrs with key-level conflicts without having to use the metadata node pattern…
I could open an RFC for this… Doesn’t look like that repo sees much action.
Edit: To expand on “key-level conflicts” I mean that because we have key-level update granularity we can update dynamic keyed metadata with last-writer-wins(or a custom conflict resolution strategy via transaction interceptors) semantics per-key. Vs at the object level, or having to resort to a metadata node.