Check if the issue you want to report already exists.
Feel free to create a new issue and someone will help you! Give as much details as you think is needed but don't include irrelevant details.
Please include the following:
- The version of the app you are using. You can find the version in the About > Third-party licenses section of the app.
- A detailed description of what you have done.
- What you expected to happen and what actually happened.
The Alpha version also provides access to the Chrome DevTools via the bug button in the top right corner. If you are not familiar with web development: Check if there are any errors shown in the Console tab. In that case please include the error message.
You can suggest features either in the issues tracker or in one of the listed forums.
Due to licensing, the YAML files containing the crunch elements from the books are not included in this repository but in a separate private one. If you only plan to contribute something independent of the database, you can just get the database from an alpha installation. On Windows, for example, the database is available under Resources/app.asar.unpacked/app/Data inside the installation folder. If you plan to contribute anything to the database itself and thus need to access its source, please join my Discord Server and text me in a channel on the server or PN me (@elyukai).
- Branches follow Git Flow. Please try to follow Git Flow as well if you edit this repository. But if it's possible, please fork this repo and create PRs.
- Commits need to follow Conventional Commits, which is enforced by the CI and Git Hooks locally.
- Please check out the Style Guide for more information on that topic! Sadly, TSLint cannot ensure the whole style so you partially need to take care of that on your own!
- There is a page covering Naming Conventions as well!
- The key criteria for the project are mentioned in the README. They also apply to pull requests. A feature usually does not consist of the technical part only. Much more important is how the feature presents itself to the user. And that must be planned and discussed.
- Code should follow functional programming practices while maintaining readablilty – which can be an issue using JavaScript/TypeScript, which is why in certain circumstances imperative/OOP code is allowed. It is also possible to write Reason/OCaml code, which compiles to JS.
- The contribution has to be easy to understand not only for players using the app, but also for coders trying to further enhance the app: Please document at least module exports!
- Git — https://git-scm.com/downloads or via a package manager
- Node.js with npm — https://nodejs.org/en/ or via
nvm - Optional: Visual Studio Code — https://code.visualstudio.com/ (you can use your own editor as well, there are project-specific VSCode settings within this repository, though)
Clone the repo, including the private submodule.
git clone --recurse-submodules https://github.com/elyukai/optolith-client.gitMake sure Node.js (lastest version) is installed and run
npm iThis installs all necessary packages.
Compile the source code. js: is for TypeScript/Webpack, re: for Reason/OCaml and css: for CSS/Sass. Webpack does not check the TypeScript validity, to check this, use ts: commands.
You have to run the Reason build first as it generates TypeScript files...
npm run ts:build
npm run css:build
npm run js:build(There's also a shorthand for that:)
npm run build…or watch it for better performance for subsequent compiling on save (you need to use separate terminal instances then).
npm run re:watch
npm run css:watch
npm run js:watchTo check the TypeScript validity, either check once or watch for changes (I'd always recommend to do the latter one).
npm run ts:build
npm run ts:watchRun the app:
npm startTo compile the SCSS files, use
npm run css:buildClean the files built by the Reason compiler, if there are any issue with it.
npm run re:cleanLint all project TS files using ESLint.
npm run lint