Open rbtcollins opened 2 years ago
resolve stickiness is correct but not the work to resolve the stickiness field. In the spec tests, that always seems to be
customField
but that's a coincidence - that field can
so thats a super interesting choice. If I was designing the API I would absolutely not have put this in the same value location in the API as the enumeration values: because there is now a free-form string field where some values behave differently. e.g. 'default' or 'random' do not refer to context.properties['random']. Whats the right way to get review of such things into the unleash roadmap?
No unit tests yet; not sure if we need them or not, but the client spec is super thin on this.