fix: Extend blueprint to include RequestBody properties

[kainpets]

• The seam-blueprint.test.ts.md snapshot now includes request parameters with appropriate values.
• @seamapi/types were bumped to latest version which is the cause of other changes to snapshot

Closes #25

[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	Aug 1, 2024 5:18pm

[razor-x]

We need to define these in the blueprint spec. I'm not sure if we need type and format. I guess the main use case for type would be "json type" and format is "semantic meaning". But if we know something is a date or a uuid, then we also know it is a string.

I think at the blueprint level, it's more important to build on the semantics. So we IMO we want

export type Property =
  | StringProperty
  | EnumProperty
  | RecordProperty
  | ListProperty
  | ObjectProperty
  | BooleanProperty
  | DatetimeProperty
  | IdProperty

but we can still include the low level type info. How about we remove type and do

interface StringProperty extends BaseProperty {
  format: 'string'
  jsonType: 'string'
}

interface DatetimeProperty extends BaseProperty {
  format: 'datetime'
  jsonType: 'string'
}

// ...