[BUG] Incorrect type definition for useFeatureEntitlements

[hognevevle]

const foo = useFeatureEntitlements("bar");

foo is now, according to Typescript, of type Entitlement.
During runtime, however, it is in fact a Ref<Entitlement>.

This causes problems when you're not directly using foo in the component html, but instead using it elsewhere in the script part.

You are then forced to do something like this:

(foo as unknown as Ref<typeof foo>).value.isEntitled
(alternatively unref(foo).isEntitled)

Proof:

  console.log("checking entitlement");
  console.log(foo.isEntitled);
  console.log((foo as unknown as Ref<typeof foo>).value.isEntitled);

Outputs:

In this case, the user is indeed entitled, so true is the correct output.

Similar to #349

[doregg]

@hognevevle Thanks for reporting the issue. We will take a look and update.

[doregg]

Fixed in 3.0.14

[hognevevle]

Thanks @doregg , but it seems the typings disappeared after this change (now returning any instead). 🤔

npmjs.com confirms the same:

[hognevevle]

@doregg Can you please reopen this? The types are still gone as of 3.0.19.