mirror of
https://github.com/lichess-org/mobile.git
synced 2026-05-26 13:50:52 +00:00
Gaurav Baghel
54456d43de
* feat(engine): show 0.0 on evaluation gauge in neutral positions When the position is equal or the game is a draw, the evaluation gauge now displays "0.0" instead of being empty. This provides better feedback to the user that the engine is active. Co-Authored-By: Claude <noreply@anthropic.com> * style: fix formatting in EngineGauge tests Co-Authored-By: Claude <noreply@anthropic.com> * fix(engine): Ensure 0.0 evaluation has no sign Update evaluation string logic to return '0.0' for any value that rounds to 0.0, avoiding '+0.0' or '-0.0' displays. This matches the behavior of the Lichess web UI and provides a cleaner display when the engine is drifting near zero. Also added a test case for small evaluations. * style: Format engine gauge test file --------- Co-authored-by: Claude <noreply@anthropic.com>
Lichess Mobile
Second iteration of the Lichess mobile app.
How to contribute
Contributions to this project are welcome!
If you want to contribute, please read the contributing guide.
If you are new to this project, you can read the documentation to get started. The CLAUDE.md is also a good resource to understand the codebase.
Setup
tl;dr: Install Flutter, clone the repo, run in order:
flutter pub getdart run build_runner watchflutter analyze --watch,
and you're ready to code!
See the dev environment docs for detailed instructions.
Running the app
To run the app, you can use the following command:
# if not already done, run the code generation
dart run build_runner build
# run the app on all available devices
flutter run -d all
Running tests
To run the tests, you can use the following command:
# if not already done, run the code generation
dart run build_runner build
flutter test
Internationalisation
Do not edit the app_en.arb file by hand, this file is generated.
For more information, see Internationalisation.
Releasing
Only for members of lichess team.
- Bump the pubspec.yaml version number. This can be in a PR making a change or a separate PR. Use semantic versioning to determine which part to increment. The version number after the + should also be incremented. For example 0.3.3+000303 with a patch should become 0.3.4+000304.
- Run workflow Deploy to Play Store
- Publish on F-Droid