What is the difference in calling exampleFlag() and exampleFlag.decide() in flags/next?
#124
Comments
|
Hi @kcrwfrd, it's a good callout that they may seem identical at first glance and we lack docs here. You have probably noticed that the documentation always calls flags and does not propose calling the decide function yourself. In the simplest case, Why you should always call exampleFlag(): Function parametersThe call signature of a flag is either no arguments, or precompute arguments. Decide functions can accept cookies and headers among other things, and the Flags SDK does the work to retrieve them based on the framework you're using, making functions that use these more portable across frameworks (more relevant to adapters, below) Adapter supportThe declaration of a flag either has decide, or adapter (and optionally identify). The flags SDK knows how to handle these more complex declarations and handles it automatically. OverridesFlags SDK will check for overrides from the Vercel Toolbar when calling the flag. Calling decide will mean that overrides aren't respected. I wonder if that satisfies your curiosity and is worth explaining on https://flags-sdk.dev? |
|
@AAorris thank you very much, this is exactly the context I was looking for. I think it would be very helpful to include this information in the docs, and to document the |
The docs don't offer any explanation here.
The quickstart guides and examples use
exampleFlag()but this isn't documented in the API reference, and neither are the flag instance methods likeexampleFlag.decide()The text was updated successfully, but these errors were encountered: