Repository navigation
Wingify Adapter for Vercel Flags - #580
Kaustubh22327 wants to merge 1 commit into
Conversation
|
@Kaustubh22327 is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
|
We're currently working on the next major version of the flags sdk, so I wanted to give a heads up that we're not currently accepting new adapters. Once the new version is out adding adapters will be much simpler |
|
Hey @dferber90. Any tentative timeline for this upgrade? |
This adds a Wingify Feature Management adapter for use with the
flag()function.It evaluates Wingify flags through
wingify-fme-node-sdk.shouldWaitForTrackingCallsdefaults totrueso impression calls finish before a serverless or edge instance freezes. PassshouldWaitForTrackingCalls: falseto opt out.The adapter has the following functions:
variation()returns the Flags SDK adapter. With no options it resolves toflag.isEnabled(). WithvariableNameit resolves toflag.getVariable(name, defaultValue).wingifyAdapteris the default singleton. It readsWINGIFY_ACCOUNT_IDandWINGIFY_SDK_KEYon first use.createWingifyAdapter({ accountId, sdkKey, ... })is for explicit credentials, more than one Wingify account, or extra SDK options such aspollInterval.getProviderData(client)loads Wingify feature definitions for Flags Explorer.identifymust returnentities.id. The adapter throws if it is missing.Also adds the provider docs page and a Flags SDK skill entry.