-
Notifications
You must be signed in to change notification settings - Fork 9
Description
Currently Metacard actions are coupled to the query response results. Metacard actions are obtained by using a different api (from platform) and should not be represented in the data the catalog methods return. This should be separated to its own RPC method and a mechanism devised to get the metacards actions.
Since the interface for ActionProvider is public <T> Action getAction(T subject);
There will need to be a way devised to supply the paramter subject to the action provider. This is often times a metacard (and could be represented by a reference to a metacard and then fetched by the jsonrpc) but may not always be a metacard. the fact that an abitrary subject can be passed into this interface will need to be accounted for in the parameters of this rpc endpoint.