fts feature modeling with custom scopes requires a user callback with corresponding cdsrc configuration

[rlindner81]

If someone wants to use the /fts/* feature toggles with a non-implicit modeling, e.g., with some custom scopes. For example: a companyId that is derived from the req going into the middleware.

Then

• the user would need to configure their callback in the cds configuration for the plugin

  {
  "cds": {
    "featureToggles": {
      "configFile": "./srv/feature/toggles.yaml",
      "ftsScopeCallback": "./srv/feature/ftsScope.js"
    }
  }

• and need to implement the callback

// context is the cds context
// req is the middleware request, which is also on the cds context, so maybe take it from there for consistency?
// key you get the fts key, in case you want to model and use different scopes for different fts toggles
module.exports = (context, key) => {
  const companyId = ...; // your code here
  return {
    user: context?.user?.id,
    tenant: context?.tenant,
    companyId,
  }
};

[rlindner81]

Use context.http.req to access the initial http request from CAP's context.