IQuery or not (#25).merge function should queue :compassus.core/route-data
for re-read if any route keys are present in the remote result (#16).:params and :tx) to set-route! (#8)will-mount, did-mount and will-unmount, which
hook into the respective lifecycle methods of the generated root component.:wrapper option from the compassus.core/application
configuration map. Use the compassus.core/wrap-render mixin instead.:history option from the compassus.core/application
configuration map. Use the new component lifecycle mixins instead.compassus.core/index-route function. Use the :index-route
key in the configuration map passed to compassus.core/application instead. Example
here.:reconciler-opts key in the compassus.core/application
configuration map with a :reconciler key that takes an Om Next reconciler. Note
that the parser in this reconciler must be constructed with compassus.core/parser,
not om.next/parser. (#7)queue? in compassus.core/set-route! should default to true in all function arities (#15).:values in local mutations, instead of nested results that are a consequence of calling the user parser inside Compassus's parser.om.next/transact! calls work properly (was missing a multimethod implementation).::compassus/route remains in the app state after a tempid migration.cljc so that it's usable from Cellophane.env, under the key :route.trueset-route! mutate function.compassus-merge.compassus-merge to extract the current route from the query passed to om.next/default-merge.target and not a hardcoded :remote for remote integration.Can you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |