Skip to content

[Maintenance]: Change productType in graphql to one Type #335

@tjeerddie

Description

@tjeerddie
Contributor

there is a different product graphql type, one for products that uses ProductSchema and one that is used by SubscriptionInterface that uses ProductModel (does not have relations). This should become the same Type.

Activity

self-assigned this
on Aug 17, 2023
changed the title [-]Change productType in graphql to be based of ProductTable instead of ProductSchema[/-] [+]Change productType in graphql to one Type[/+] on Aug 17, 2023
tjeerddie

tjeerddie commented on Aug 18, 2023

@tjeerddie
ContributorAuthor

We do need the ProductModel graphql type because it is necessary for the auto registration of products to resolve correctly.

I believe the best approach is to update ProductModel to also have fixed_inputs, product_blocks and workflows, so we can add the GraphqlType ProductType to the ProductModel with ProductModel._strawberry_type = ProductType and will be resolved the same as root Products resource.

removed their assignment
on Aug 31, 2023
added
maintenanceKeeping the framework up to date
and removed
enhancementEnhancement or extension of existing feature
on Jul 1, 2025
changed the title [-]Change productType in graphql to one Type[/-] [+][Maintenance]: Change productType in graphql to one Type[/+] on Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    maintenanceKeeping the framework up to date

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @Mark90@tjeerddie

        Issue actions

          [Maintenance]: Change productType in graphql to one Type · Issue #335 · workfloworchestrator/orchestrator-core