Filip Sodić

Hey @EmmanuelTheCoder. The task (although seemingly simple) might be a challenging for someone not familiar with our codebase (there are a lot of Wasp intricacies) , that's why we haven't...

Sure! Give me some time (a day max) and I'll get back to you.

How about this one: https://github.com/wasp-lang/wasp/issues/756

@pt2121 Sorry for the late response, the answer is "yes" :). I know see that you've already made a PR. Great! Will check it out ASAP.

> Regarding the documentaion -> you are leaving that for the end? Yes, I'll take care of it once the API becomes "stable".

We could consider splitting Wasp into two folders: - `.wasp/` - This one remains hidden and contains the build artifacts. Users to not include it in version control. - `wasp-info`...

I was playing around with [@shayneczyzewski's idea](https://github.com/wasp-lang/wasp/pull/638#pullrequestreview-1012552960) and took it a step further. I got the thing working so I can even send you the code or update it myself...

@Martinsos I probably wouldn't touch anything for now since our code is still changing rapidly. We can make the changes and update the docs as we encounter them.

Yes, this is a tricky one. I think it makes sense to determine what we do with versions on a case-by-case basis, depending on how reliable/up-to-date they are. Of course,...

Just a couple of things to add here. ### Syntax considerations I think I'd prefer the following ways of defining the version: ```css app Something { version: "^1.2.3" ... }...