We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is caused by the code defaulting to the BillingConfigLegacyItem if the flag isn't present, but it isn't an option in v3 and is a requirement.
BillingConfigLegacyItem
This is causing my jest testing to go haywire because the types don't match. Is it worth removing the Future for BillingConfigItem in v3?
BillingConfigItem
The text was updated successfully, but these errors were encountered:
Hi 👋
Thanks for the flag. I will bring this to the team to review.
Sorry, something went wrong.
No branches or pull requests
This is caused by the code defaulting to the
BillingConfigLegacyItem
if the flag isn't present, but it isn't an option in v3 and is a requirement.This is causing my jest testing to go haywire because the types don't match. Is it worth removing the Future for
BillingConfigItem
in v3?The text was updated successfully, but these errors were encountered: