Do all the things required to release the first version of the rewrite, which will be 0.7.0 (instead of 2.0.0 which I planned previously)
What is required?
things that already exist as issues
things that pop up during integration of entity-space into a work-related app (which I already started)
Ideally I should not come up with new things that are not required to integrate this library into an actual app.
Why
Because It is about time to get something released!
Items
feat
[x] ability to set composite primary keys via blueprints
[x] ability to set composite indexes via blueprints
[x] improve DX when declaring entity metadata
[x] use "optional" instead of "required"
[x] support string[] as from/to argument
[x] support hydrating properties of complex types
[x] NotInArrayCriterion.merge(), as it currently throws an Error which easily breaks app code unnecessarily.
[x] #216
[x] #213
[x] #214
[x] support primitive unions (i.e. a status property on an entity that is an enum, for a ticket it could be "open" | "rejected" | "closed")
0.7.0-alpha.0 is released, next version will be 0.7.0-alpha.1 until I am satisfied to drop the alpha suffix (no idea what the criteria for that is gonna be)
What
Do all the things required to release the first version of the rewrite, which will be 0.7.0 (instead of 2.0.0 which I planned previously) What is required?
Ideally I should not come up with new things that are not required to integrate this library into an actual app.
Why
Because It is about time to get something released!
Items
feat
fix
refactor
health