Remove stale warning in node flags docs#47
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Confidence Score: 5/5This looks mergeable after clarifying the supported SDK version.
docs/tracking-methods/sdks/nodejs/nodejs-flags.mdx
|
| Filename | Overview |
|---|---|
| docs/tracking-methods/sdks/nodejs/nodejs-flags.mdx | Removes the runtime-targeting limitation without stating which Node SDK versions support it. |
Reviews (1): Last reviewed commit: "Merge branch 'main' into fix_callout" | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| Support for runtime targeting has not yet been released. Thus runtime rules other than a single-condition, exact match key-value pair, will ALWAYS be evaluated to true. | ||
| </Warning> | ||
|
|
||
| <Warning> |
There was a problem hiding this comment.
If full runtime targeting was released after the documented minimum Node SDK version, removing this warning also tells users of older supported versions that non-exact or multi-condition rules work. Those rules can instead evaluate as true and expose the wrong flag variant; qualify support with the SDK version that introduced it.
Context Used: Our developers like concise reviews. Avoid verbose... (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
2 participants
No description provided.