feat: Add routePath to Resource and blueprint.events

[andrii-balitskyi]

Closes #74

• Add events
• Add test fixture event schema

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
blueprint	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 20, 2024 5:16pm

[andrii-balitskyi]

@razor-x The resources.event isn't being generated because createResources only supports regular schemas, not oneOf schemas. I think oneOf schemas are currently event and action_attempt. Should we come up with some sort of union resource definition for such schemas?

[razor-x]

@razor-x The resources.event isn't being generated because createResources only supports regular schemas, not oneOf schemas. I think oneOf schemas are currently event and action_attempt. Should we come up with some sort of union resource definition for such schemas?

Yes, but events and action attempts are different: events have one level of union and action attempts have two. Because blueprint defines the EventResouce, it can make some assumptions about the event resource type union. Let's only solve the event case now and leave action attempts for later.

For events, we can just find all properties that are common to all events and drop the rest. I realize this might create some false positives, e.g., we may see connected_account_id as a common property when it's really not, but let's give it a try and see what happens. Alternatively we can annotate the common properties in the yaml, e.g., is_common_property.

[razor-x]

Generally, mixing imperative mutation patterns with functional reduce patterns is confusing and unexpected. Prefer either a for loop with assignment, or

Suggested change

	result[propKey] = propValue
	return { ...result, [propKey]: propValue }

This is why result is not generally used as the arg name in reduce, because it's actually the intermediate accumulator at each step for the final result

[andrii-balitskyi]

97b8de8

[andrii-balitskyi]

I realized that enum values should be merged because with current implementation event_type would have only first single enum value. Implementation: dffc672