Skip to content

Conversation

arnavgautam
Copy link
Collaborator

Renames the attribute, and adds an alias for the old 'marginal' name which includes a deprecation warning
See #530

@codecov
Copy link

codecov bot commented May 1, 2020

Codecov Report

Merging #706 into master will increase coverage by 0.02%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #706      +/-   ##
==========================================
+ Coverage   80.02%   80.05%   +0.02%     
==========================================
  Files          38       38              
  Lines        2854     2858       +4     
==========================================
+ Hits         2284     2288       +4     
  Misses        570      570              
Flag Coverage Δ
#unittests 80.05% <100.00%> (+0.02%) ⬆️
Impacted Files Coverage Δ
src/core/build.jl 100.00% <100.00%> (ø)
src/core/model.jl 81.81% <100.00%> (ø)
src/core/types/model.jl 100.00% <100.00%> (ø)
src/mcs/montecarlo.jl 86.63% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7f5c47d...bf87665. Read the comment docs.

Copy link
Collaborator

@corakingdon corakingdon left a comment

Choose a reason for hiding this comment

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

This looks great! The one thing I was wondering is if you tested out the getproperty function you added for catching old calls to the "marginal" name. Maybe we should just keep one of the lines in the test file you updated as the old way, to make sure the warning appears as intended?

@arnavgautam
Copy link
Collaborator Author

Ah yeah I had done manual testing by keeping one of the old lines and running the test suite. The line showed up as a properly formatted warning, but the tests still passed. If you want, I can put that back in, but I figured users would be confused if it showed up for them.

@corakingdon
Copy link
Collaborator

The value of keeping it in would be to make sure that the new function you added gets tested properly, but I'm surprised to see that the coverage tests that ran say that 100% of the diff is hit... I would've thought that it would miss those lines... Maybe it's possible that the model tests (i.e. DICE and FUND) that get run by the test suite are hitting those lines of the function... Either way I think it would make sense to just leave one in the test file, and add a comment that says you are testing the soon-to-be-deprecated behavior

@lrennels
Copy link
Collaborator

lrennels commented May 4, 2020

Yea I agree, we've done that with some of the other deprecated code, just do leave a note and it'll be easy for us to find it later!

@lrennels lrennels self-requested a review May 4, 2020 20:57
lrennels
lrennels previously approved these changes May 4, 2020
@arnavgautam
Copy link
Collaborator Author

Updated it with the test, sorry for the git weirdness but I guess the VSCode interface messed me up

@lrennels lrennels self-requested a review May 9, 2020 16:48
@corakingdon
Copy link
Collaborator

corakingdon commented May 11, 2020

@lrennels do you know why some of your most recent commits are showing up here in the diffs of the "Files changed" even though they've already been commited to master? I mean I think it's fine to just merge this I'm just confused why they are showing up as different against master if they are already on master...

@lrennels
Copy link
Collaborator

@ckingdon95 Oh that's strange no I don't know, I was thinking maybe if I approved it would re-compare to master but it didn't. Odd ...

@lrennels
Copy link
Collaborator

lrennels commented May 11, 2020

@ckingdon95 I just merged a little toml update so I'll update this branch and see if that helps ... looks like it did! So I think somehow the comparison just didn't get redone. Shall I merge?

@lrennels lrennels added this to the v0.10.0 milestone May 11, 2020
@corakingdon
Copy link
Collaborator

awesome thanks Lisa!

@corakingdon corakingdon merged commit 7f5b8bf into mimiframework:master May 11, 2020
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