Disable or choose the order of notes for each field

[leandroluk]

Problem

I like being able to declare the name of reflected fields from the Prisma schema in the database, even for fields where the name is the same, to standardize the way my team builds Prisma schemas. The problem is that when using the prism extension for VSCode I can't order the annotations that define the field in the database and I wanted to somehow always leave "@map()" as the first property.

Suggested solution

Create a configuration in the extension that allows the ordering of possible annotations or that disables the reordering of annotations

[suiyun39]

I totally agree with this idea.

Maintaining readability is our first priority when choosing to format the code.