Programming Guidelines

Here are a list of guidelines to follow when developing for Laputa

Branches

1. Work in your own branch, submit a pull request to Luka when you're ready.
2. Clean your own code. Pull requests should not create any additional bugs.
3. Any bugfix not related to a larger change should go in its own branch.
4. Avoid merging main into your branch. Merge individual files as necessary.
5. Delete your branch after a PR merge if it is not already deleted.

Structural Issues

1. If there's an issue with the Code Standards, or some problem that affects the entire repo, discuss it with Luka before making changes.
2. If there's a inherent structural problem with a script or set of scripts, discuss it with Luka before refactoring code.

Bugs

1. Add any bugs you don't fix or don't plan to fix in the near future to the github issues page and tag them. Include screenshots or video.
2. Delete github issues when fixed.

Miscellaneous

1. Don't delete Outdated folders, they exist to keep code that might be useful in the future.
2. Trim all trailing whitespace from code.
3. Don't shadow class scripts, see code standards doc.
4. Dont declare a function to return void func Function(arg): -> void