Overview of open issues for contributors to pick up and work on

[Martinsos]

This is a quick overview of some of the most interesting / well defined issues that you might find interesting as a contributor looking for your next issue to work on. Keep in mind this is not an exhaustive list and there are more issues to be found if you look for them directly in the issues.

Simple tasks for beginners:

• [Haskell] Implement wasp info command #277
• [Javascript] Add more restrictions for user's password (Auth) #88

Relativey well defined tasks of moderate difficulty and limited scope:

• [Haskell] When dependency is added, warn user to restart wasp start or have wasp start run npm install automatically #269
• [Haskell] Move all bash-completion logic to Haskell (from bash script) #258, and possible later Make bash completion easier to discover and install #256 as a follow up.
• [Javascript] Fix linter errors in code that Wasp generates #251
• [Haskell] Convert functions in Util.IO to use StrongPath instead of Path #278

Tricky bug we haven't managed to solve yet, even just ideas could help:

• On sigkill (Ctrl+C) for wasp CLI, sometimes child processes remain running / occupying ports #198

This issue would benefit the most from web dev who understand the problem well and can help us define what needs to be done and what we need to think about in order to solve this. Once we define that well, solving it will not be hard and can be nice way to get accustomed with the codebase:

• [Web, Javascript, some Haskell] Add support in Wasp for hosting the frontend in non-root directory #8

Somewhat bigger features, that require proper design and research up-front, but the goal is relatively clear and implementing them should be challenging and fun (at least I find them really fun, I will be jealous of you while you implement them!). I recommend taking one of these one after you are somewhat accustomed with the codebase already and are interested in working on one bigger issue for some period of time. Should be a rewarding experience if you want to make a bigger impact and "own" a feature:

• [Haskell] Better show Wasp development information: CLI Powerline or browser dev tooling or Wasp Studio #250
• [Haskell] Make Wasp smarter when writing over existing generated files (e.g. delete redundant(old) files) #209
• [Advanced Haskell] Figure out a better way to work with templates #124

[Martinsos]

Clsoing this one as we solved most of the issues from it!