Skip to content

ALFMOB-317: Create Readme.md#71

Open
joaosamueldiogo-mindera wants to merge 8 commits into
mainfrom
task/ALFMOB-317-Create-README.md
Open

ALFMOB-317: Create Readme.md#71
joaosamueldiogo-mindera wants to merge 8 commits into
mainfrom
task/ALFMOB-317-Create-README.md

Conversation

@joaosamueldiogo-mindera
Copy link
Copy Markdown
Contributor

What

Added a Readme.md file.

Why

In order to give a overview of project details and setup.

See

Link to JIRA: ALFMOB-317

@github-actions
Copy link
Copy Markdown

LCOV of commit 674c7a5 during CI #689

Summary coverage rate:
  source files: 157
  lines.......: 86.2% (2544 of 2950 lines)
  functions...: no data found
  branches....: 80.9% (768 of 949 branches)
Message summary:
  111 ignore messages:
    inconsistent: 111

Files changed coverage rate: n/a

Full coverage report

@github-actions
Copy link
Copy Markdown

LCOV of commit 2080aee during CI #691

Summary coverage rate:
  source files: 157
  lines.......: 86.2% (2544 of 2950 lines)
  functions...: no data found
  branches....: 80.9% (768 of 949 branches)
Message summary:
  111 ignore messages:
    inconsistent: 111

Files changed coverage rate: n/a

Full coverage report

@silvaric silvaric requested review from silvaricMindera and removed request for silvaricMindera May 13, 2026 11:05
silvaric
silvaric previously approved these changes May 13, 2026
@silvaric silvaric requested review from silvaric and silvaricMindera and removed request for silvaricMindera May 13, 2026 11:06
Comment thread README.md

This project uses the MVVM architecture model as reccommended by the [Flutter Documentation](https://docs.flutter.dev/app-architecture/guide).

### View
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Think this and ViewModel aren't really needed as they are, a dev coming into the project should know that a view shouldn't have business logic or that a ViewModel represents the domain data to be used for the view

Comment thread README.md
- Executes `alfie_flutter/test_coverage.sh` to run tests and generate coverage.
- Optionally runs smoke integration tests on Android when enabled.
- Uploads LCOV coverage reports as a PR message.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of things I think we could add:

  • Branch Naming convention
  • Commit message convention
  • PR rules (template)
  • code reviews expectations
  • Merging/Rebasing rules (something like we prefer merge over rebase)
  • riverpod, with links to the documentation

We may not include every single one of these and some don't need much detail, but think they're useful when starting out in a project

@silvaric thoughts on these?

@github-actions
Copy link
Copy Markdown

LCOV of commit 09b6d6d during CI #718

Summary coverage rate:
  source files: 157
  lines.......: 86.3% (2544 of 2948 lines)
  functions...: no data found
  branches....: 81.0% (768 of 948 branches)
Message summary:
  111 ignore messages:
    inconsistent: 111

Files changed coverage rate: n/a

Full coverage report

Co-authored-by: Copilot <copilot@github.com>
@silvaric silvaric requested a review from silvaricMindera May 19, 2026 14:03
@silvaric silvaric dismissed their stale review May 19, 2026 14:03

Wrong

@silvaric silvaric requested review from silvaric and silvaricMindera and removed request for silvaric and silvaricMindera May 19, 2026 14:03
@github-actions
Copy link
Copy Markdown

LCOV of commit 671d5d9 during CI #736

Summary coverage rate:
  source files: 157
  lines.......: 86.3% (2544 of 2949 lines)
  functions...: no data found
  branches....: 80.9% (769 of 950 branches)
Message summary:
  112 ignore messages:
    inconsistent: 112

Files changed coverage rate: n/a

Full coverage report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants