It should be less intrusive to specify which action types are sent over the wire to the aquedux-server and back to aquedux-client.
We currently prefix action types with AQUA: but it would be best to not modify the action types and expose an aquedux-client API like .moisten([]) or in the optional object parameter of the client instantiation, as follow:
// On the client side.
import { createAqueduxClient } from 'aquedux-client'
const client = createAqueduxClient(store, ..., { actionTypes: [ /* Here */ ]});
or
client.moisten([ /* Here */ ]);
It should be less intrusive to specify which action types are sent over the wire to the
aquedux-server
and back toaquedux-client
.We currently prefix action types with
AQUA:
but it would be best to not modify the action types and expose anaquedux-client
API like.moisten([])
or in the optional object parameter of the client instantiation, as follow: