Changelog

[Unreleased]

Added

• sweet-tooth.endpoint.test.harness/assert-response-contains-one-entity-like a macro for nicer assertions against an API endpoint response. Should only be used with endpoints that return a single entity. Advantage is that it uses (is (= ...)) so you can see the diff between expected and actual.
• sweet-tooth.endpoint.test.harness/assert-response-contains-entity-like similar to above. assert that one entity among all returned contains specified k/v pairs

Chaanged

• sweet-tooth.endpoint.routes.reitit/expand-routes added a third argument, keywordize-ig-refs-cljs, a boolean defaulting to true that controls whether integrant.core.Ref types are replaced with the keyword they refer to in cljs compilation. Integrant refs almost always refer to backend components, and replacing them with keywords makes it easier to use the value returned by expaned-routes directly in frontend code.
• Spec'd and documented sweet-tooth.endpoint.routes.reitit
• sweet-tooth.endpoint.system/system not uses a custom init function that differs from ig/init in that, when a component's config has Replacement record, that record's :component key is used and the actual init-key method is not called for that component

Deprecated

• sweet-tooth.endpoint.test.harness/contains-entity? - use sweet-tooth.endpoint.test.harness/assert-response-contains-* macros instead