Fluffy
WWasp-lang
•Created by Fluffy on 5/25/2024 in #🙋questions
Direction of wasp-lang
- more comprehensive docs
I do get that it's suppose to be beginner-friendly and allow people to quickly create their app, but I've encountered quite a few lack of documentation while working on it. Like using
signin function over signInForm if we want to really customize the appearance and the interactions of those workflows while using still using the auth. --skip-build if we want to deploy without rebuilding again (maybe making changes to server files ,etc that get overridden when building) to fly in this case.
Where I'm working at, we have a culture of documenting every "surface area" that we expose to prevent misuse and blaming when we do modify it down the road (even more so at enterprise level 😓 )
- Optimization strategies and best practices
Since it's been abstracted, are there strategies related to wasp implementation that optimize performance, caching, etc...
Lastly maybe making it more professional looking?
- People might wonder why server and client url are different when logging in/signing up from e.g google
- Hiding away "hello world" when visiting the server url in production, by returning a 301 redirect to the client url (or something similar would be good)
- Support different status code pages, 301, 302, 404 ( I saw that not found pages would work properly in the near future, but would be good if we can set the status code for those pages properly as well)
Sorry if I post in the wrong place (as it's a combination of questions(mainly), reviews, suggestions and rants 😅)
But liking what I see thus far (the studio visualization is a really nice touch!), hope to see more when it gets out from beta 🙏10 replies