-
-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
main.wasp polish #134
main.wasp polish #134
Conversation
* https://wasp-lang.dev/docs/data-model/entities | ||
*/ | ||
|
||
entity User {=psl | ||
id Int @id @default(autoincrement()) | ||
createdAt DateTime @default(now()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In all entities, I grouped fields and ordered them so that most generic ones go first (id, createdAt), then go important relations like user
+ userId
and similar, and then go business logic fields.
@@ -179,6 +207,7 @@ page LandingPage { | |||
component: import LandingPage from "@src/client/landing-page/LandingPage" | |||
} | |||
|
|||
//#region Auth Pages |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be coming out in the new version of Wasp's vscode plugin, allowing you to collapse the region of the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like!
* Polished small things in main.wasp. * Polished many small things in main.wasp file.
I did a bunch of small improvements to main.wasp and grouped them all in this one PR!