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

feat: Case specific data functionality (#93) #175

Merged

Conversation

gromdimon
Copy link
Contributor

Tasks:

  • Implemet
  • Test

@gromdimon gromdimon linked an issue Oct 27, 2023 that may be closed by this pull request
@codecov
Copy link

codecov bot commented Oct 27, 2023

Codecov Report

Merging #175 (fd8d9b8) into main (162ae13) will increase coverage by 3.62%.
Report is 1 commits behind head on main.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #175      +/-   ##
==========================================
+ Coverage   79.73%   83.36%   +3.62%     
==========================================
  Files         110       35      -75     
  Lines        3119      571    -2548     
  Branches      775        0     -775     
==========================================
- Hits         2487      476    -2011     
+ Misses        587       95     -492     
+ Partials       45        0      -45     

see 76 files with indirect coverage changes

@gromdimon gromdimon enabled auto-merge (squash) October 30, 2023 13:33
@gromdimon gromdimon merged commit 247d9b1 into main Oct 30, 2023
9 checks passed
@gromdimon gromdimon deleted the 93-allow-user-to-provide-case-specific-data-for-analysis branch October 30, 2023 13:38
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.

Allow user to provide case-specific data for analysis
1 participant