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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ideally we should use the Enum for provisionStatus and not an hardcoded string.
Update server to return the correct enum in ProvisionSubscriptionResult as follow:
ProvisionSubscriptionResult
import { Field, ObjectType, registerEnumType } from "@nestjs/graphql"; import { ProvisionSubscriptionStatus } from "@stigg/node-server-sdk"; @ObjectType({ isAbstract: true, }) export class ProvisionSubscriptionResult { @Field(() => ProvisionSubscriptionStatus, { nullable: false, }) provisionStatus!: ProvisionSubscriptionStatus; @Field(() => String, { nullable: true, }) checkoutUrl?: string; } registerEnumType(ProvisionSubscriptionStatus, { name: "ProvisionSubscriptionStatus", });
export the enum from the server, or use the types from stigg on the client
see [amplication-client/src/Purchase/PurchasePage.tsx
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened?
Ideally we should use the Enum for provisionStatus and not an hardcoded string.
Update server to return the correct enum in
ProvisionSubscriptionResult
as follow:What you expected to happen
export the enum from the server, or use the types from stigg on the client
How to reproduce
see [amplication-client/src/Purchase/PurchasePage.tsx
Amplication version
No response
Environment
No response
Are you willing to submit PR?
No response
The text was updated successfully, but these errors were encountered: