Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge release/mapping branch #270

Merged
merged 10 commits into from
Feb 26, 2025
Merged

Merge release/mapping branch #270

merged 10 commits into from
Feb 26, 2025

Conversation

kyle1morel
Copy link
Collaborator

Description

Merge release/mapping branch to master

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING doc
  • I have checked that unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

Copy link

Coverage Report (Frontend)

Totals Coverage
Statements: 46.62% ( 3312 / 7105 )
Methods: 36.45% ( 441 / 1210 )
Lines: 54.01% ( 1905 / 3527 )
Branches: 40.79% ( 966 / 2368 )

Copy link

Coverage Report (Application)

Totals Coverage
Statements: 41.18% ( 1282 / 3113 )
Methods: 35.35% ( 187 / 529 )
Lines: 53.04% ( 829 / 1563 )
Branches: 26.05% ( 266 / 1021 )

@kyle1morel kyle1morel merged commit e016b36 into master Feb 26, 2025
19 checks passed
@kyle1morel kyle1morel deleted the release/mapping branch February 26, 2025 20:48
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.

3 participants