Closed drgif closed 3 years ago
Handle spec defaults differently: Simplify map->entity to use deep-merge with subsequent (valid?) call.
Consider making a central registry in entity to store defaults for each spec. Could use a macro that calls (s/fdef) and registers the default.
The map with default values for the merger would still be generated by calling (explain-data) on an empty map. EDIT: There is (spec/get-spec) which should make this a lot easier
Fixed in https://github.com/mwiederhold/limpa/commit/9cfe5260753d15ad20260ad2a4443ff3c9d41848 but does not work with nested entities
How to reproduce: