chore(flags): docs on the new sendFeatureFlags (or send_feature_flags) behavior#12187
chore(flags): docs on the new sendFeatureFlags (or send_feature_flags) behavior#12187
sendFeatureFlags (or send_feature_flags) behavior#12187Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ivanagas
left a comment
ivanagas
left a comment
There was a problem hiding this comment.
I think there is some tweaks here we can do to make this a lot clearer.
|
|
||
| ## Performance considerations | ||
|
|
||
| - **With local evaluation**: When [local evaluation](/docs/feature-flags/local-evaluation) is configured, setting `sendFeatureFlags: true` will **not** make additional server requests. Instead, it uses the locally cached feature flags, and it provides an interface for including person and/or group properties needed to evaluate the flags in the context of the event, if required. |
There was a problem hiding this comment.
I'm a bit confused here.
If you are using local evaluation, you also need to set onlyEvaluateLocally: true when calling capture with sendFeatureFlags? Person and group properties for sendFeatureFlags are only relevant if locally evaluating?
There was a problem hiding this comment.
Ahh, I guess if you want sendFeatureFlags to evaluate locally too you use it, otherwise it will make a server-call?
There was a problem hiding this comment.
Person and group properties for sendFeatureFlags are only relevant if locally evaluating?
Not true, we still support property overrides even when we use the server call (e.g. they want to pass a person property that hasn't been ingested yet)
If you are using local evaluation, you also need to set onlyEvaluateLocally: true when calling capture with sendFeatureFlags?
yeah, the idea is you have to specify that you're sending feature flags locally, otherwise we will hit the servers for the most up-to-date evaluation.
…lags-code-python-set-send-feature-flags-to-true.mdx Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
…lags-code-python-set-send-feature-flags-to-true.mdx Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
…lags-code-python-set-send-feature-flags-to-true.mdx Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
…lags-code-node-set-send-feature-flags-to-true.mdx Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
…lags-code-node-set-send-feature-flags-to-true.mdx Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
…lags-code-node-set-send-feature-flags-to-true.mdx Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
…lags-code-node-set-send-feature-flags-to-true.mdx Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
…lags-code-python-set-send-feature-flags-to-true.mdx Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
…lags-code-node-set-send-feature-flags-to-true.mdx Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
…/posthog.com into chore/docs-on-send-feature-flags
2 participants
Changes
Docs for these changes:
sendFeatureFlagsparameter more declarative and ergonomic posthog-js-lite#566Checklist
vercel.json