-
-
Notifications
You must be signed in to change notification settings - Fork 1
Generated CatalogsCatalogNameItemsPostRequestItemsInner class has hardcoded restaurant-specific fields #201
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Expected Behavior
I'm trying to upload/set items for a catalog using the "Catalogs > Catalog Items > Asynchronous" endpoint, but the generated client code has hardcoded restaurant-specific fields that don't match my actual catalog structure.
The generated CatalogsCatalogNameItemsPostRequestItemsInner class should allow dynamic field definitions based on the actual catalog structure, enabling users to set custom fields appropriate for their specific catalog type (e.g., products, events, etc.).
Actual Behavior
The generated class contains hardcoded fields specific to a restaurant catalog example:
- cuisine
- city
- rating
- loyalty_program
- top_dishes
- location (with latitude/longitude)
This prevents the class from being used with other catalog types that have different field structures.
Steps to Reproduce
- Generate client code from the OpenAPI spec for "Catalogs > Catalog Items > Asynchronous"
- Look at the generated CatalogsCatalogNameItemsPostRequestItemsInner class
- Observe that the class has hardcoded restaurant-specific properties instead of dynamic field support
https://github.com/braze-community/braze-specification/blob/master/openapi/spec.json#L459C10-L459C21
Keywords
catalog-items
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working