You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The newest plan hook, usePlanData, has a resolver exposed as planName. We traditionally have treated plan names with the key value instead, and we haven't fully offloaded of it. We're sort of introducing two values, planName and value that represent the same thing, which is hard to keep track of on the frontend. This also stems from most of the backend (excluding gql) only using value instead of planName.
This ticket is to replace every planName with value and adjust the usePlanData hook only to use value (supported on GQL in prod as of now) and get rid of planName until we revise the naming conventions again.
The text was updated successfully, but these errors were encountered:
The newest plan hook,
usePlanData
, has a resolver exposed asplanName
. We traditionally have treated plan names with the keyvalue
instead, and we haven't fully offloaded of it. We're sort of introducing two values,planName
andvalue
that represent the same thing, which is hard to keep track of on the frontend. This also stems from most of the backend (excluding gql) only usingvalue
instead ofplanName
.This ticket is to replace every
planName
withvalue
and adjust theusePlanData
hook only to usevalue
(supported on GQL in prod as of now) and get rid of planName until we revise the naming conventions again.The text was updated successfully, but these errors were encountered: