Open rjrodger opened 7 years ago
It can be turned on again with the feature flag legacy.meta = true - which is the "fix" in seneca 3.4.0: https://github.com/senecajs/seneca/commit/61113889df0470d4b684c8701b587b67b2c550b7
The action meta properties are now available as a third argument to the action function: msg, reply, meta. See the new transport code for an example: https://github.com/senecajs/seneca/blob/master/lib/transport.js#L276 https://github.com/senecajs/seneca/blob/master/lib/transport.js#L342
msg, reply, meta
meta$ will be removed completely in 4.x
@rjrodger Understood. Thanks for letting me know about this.
How should I go about supporting different Seneca versions? Should I use meta$ if present? What's the general directive here?
meta$
It can be turned on again with the feature flag legacy.meta = true - which is the "fix" in seneca 3.4.0: https://github.com/senecajs/seneca/commit/61113889df0470d4b684c8701b587b67b2c550b7
The action meta properties are now available as a third argument to the action function:
msg, reply, meta
. See the new transport code for an example: https://github.com/senecajs/seneca/blob/master/lib/transport.js#L276 https://github.com/senecajs/seneca/blob/master/lib/transport.js#L342meta$ will be removed completely in 4.x