Development

If there is something to add to the code, whether a bug or enhancement, a ticket should be opened so that it can be discussed. If the coding goes ahead, a new branch should be created from the branch with a reference to the ticket ID, eg: 64 - Support react

Commit messages should follow the conventional commits format:

tag[(scope)]: message

Examples:

fix: this is a fix for the project as a whole
docs: updated the contributors

Wails uses a gitflow-like approach to development
Feature/Bugfix branches are created from the develop branch
Once the work is complete, pull requests should be made against the develop branch
As features are added, the develop branch is tagged with pre-release tags
Releases are made weekly, so at the end of the weekly cycle, the latest features and bugfixes that were made will be merged to master and tagged with the next appropriate version.

This is worked on and a PR is made back to develop
Once merged, is tagged with v0.14.1-pre
A ticket (#64) is opened requesting ultralight support
This is worked on and a PR is made back to develop
Once merged, develop is tagged with v0.14.2-pre
We reach the end of our week and merge v0.14.2-pre to master, tagging it as v0.15.0

The Wails cli has developer tooling built in, but needs activating. To create a developer version, do the following:

This unlocks a wails dev command that has subcommands for development.

Here is an example run:

This generates the following template.json:

Note: The key is currently unused but will be used in place of bridge in the