-
Notifications
You must be signed in to change notification settings - Fork 19
Example Walkthrough
Let's say you want to add a feature or fix a bug in the codebase. Here is a short walk-through for how you would go about doing this.
Firstly, make sure you have setup the repository on your local computer. This means following the steps in the Wiki: installing git and node, cloning, getting the .env
, setting up VSCode, etc. This will only have to be done once.
When ready, you can determine what you want to work on by checking through the Issues list on the repo. You are looking for open issues that have no assignees yet. Make sure the issue you find is not too difficult or broad in scope. You can filter issues to find open ones that you are interested in, e.g. all open issues with the Frontend
and Enhancement
labels.
If you have something you want to work on that isn't found in any issues yet, open a new issue for it and be as specific as possible about what the bug is or what the feature request is. There should always be an issue open for what you are working on, unless its very simple fixes.
- Create a new branch off the dev branch named specifically
- Run LATE in dev mode with the backend and frontend servers
- Make changes to the code
- Test the code locally
- Add and commit the changed files
- Push to origin after you are done with the item or are stopping
Remember, team, the scope of what we are working on. Our goal is to make our own lives and that of our peers easier.
LATE Stack Documentation | Learning Resources | Flowchart | LATE Discord Server Invite
Backend | Frontend | Terminology
Learn LATE
- FreeCodeCamp
- Git
- Web Basics
- HTML
- CSS [coming soon]
- JS [coming soon]
- VueJS [coming soon]
- Node [coming soon]
- MongoDB [coming soon]
How LATE Works