Page
https://dataprovider.tech/docs/migrations/ (Website/src/docs/migrations.md)
A. The column-type list is incomplete
The docs say:
Supported column types include Text, Integer, Real, Blob, Boolean, DateTime, Guid, and vector types on PostgreSQL.
But SchemaYamlSerializer.ParseType accepts many more — including the ones almost every real schema needs and that the canonical NAP migrations/schema.yaml uses: Uuid, Int, BigInt, SmallInt, TinyInt, Json/Jsonb, Date, DateTimeOffset, Decimal(p,s), VarChar(n), NVarChar(n|max), Char(n), Float, Double, Money, Time, Xml, RowVersion, Geometry/Geography, Vector(n).
A reader following the docs literally would not know that DateTimeOffset, Json, Uuid, or Decimal even exist. Please publish the full accepted-token list (it can be generated straight from ParseType).
B. The "PKs must be Text" rule contradicts the first-class Uuid type
The Rules section says:
Primary keys must be UUIDs (Text at the column level, generated by your application).
But there is a first-class Uuid type, and the canonical NAP migrations/schema.yaml uses type: Uuid for every primary key. "Text at the column level" directly contradicts real, recommended usage. Please clarify that Uuid is the intended PK column type.
C. (Minor) onDelete tokens
The example only shows onDelete: NoAction. Worth listing all accepted values (NoAction/No_Action, Cascade, SetNull/Set_Null, SetDefault/Set_Default, Restrict).
These cost real investigation time (reading the serializer source) to resolve while authoring a production schema.
Page
https://dataprovider.tech/docs/migrations/ (
Website/src/docs/migrations.md)A. The column-type list is incomplete
The docs say:
But
SchemaYamlSerializer.ParseTypeaccepts many more — including the ones almost every real schema needs and that the canonical NAPmigrations/schema.yamluses:Uuid,Int,BigInt,SmallInt,TinyInt,Json/Jsonb,Date,DateTimeOffset,Decimal(p,s),VarChar(n),NVarChar(n|max),Char(n),Float,Double,Money,Time,Xml,RowVersion,Geometry/Geography,Vector(n).A reader following the docs literally would not know that
DateTimeOffset,Json,Uuid, orDecimaleven exist. Please publish the full accepted-token list (it can be generated straight fromParseType).B. The "PKs must be Text" rule contradicts the first-class
UuidtypeThe Rules section says:
But there is a first-class
Uuidtype, and the canonical NAPmigrations/schema.yamlusestype: Uuidfor every primary key. "Textat the column level" directly contradicts real, recommended usage. Please clarify thatUuidis the intended PK column type.C. (Minor) onDelete tokens
The example only shows
onDelete: NoAction. Worth listing all accepted values (NoAction/No_Action,Cascade,SetNull/Set_Null,SetDefault/Set_Default,Restrict).These cost real investigation time (reading the serializer source) to resolve while authoring a production schema.