Closed samwaseda closed 2 months ago
The same thing could be used also elsewhere (like io?)
Coverage variation | Diff coverage |
---|---|
:white_check_mark: +0.02% (target: -1.00%) | :white_check_mark: 100.00% |
Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
mixin/semantics.py | 6 | 96.69% | ||
<!-- | Total: | 6 | --> |
Totals | |
---|---|
Change from base Build 10969418713: | 0.02% |
Covered Lines: | 2999 |
Relevant Lines: | 3286 |
The same thing could be used also elsewhere (like io?)
Yes, I imagine there's a few places where it's useful, but I couldn't name them all off the top of my head. When it's used as here to strictly add to the information returned, I am totally behind this.
The previous error message in this situation was:
Could not find attribute Compositions on tesile (Workflow) or among its children (dict_keys(['Composition', 'BoxSize', 'Seeds', 'Grid', 'Elasticity', 'Plasticity', 'Phase', 'Homogenization'])).
. It was sort of difficult to figure out which one I wanted to say for this large number of possibilities. So I addedget_close_matches
to append the message:Did you mean 'Composition' and not 'Compositions'?
Also, in general I find the error messages in
pyiron_workflow
difficult to understand. It must be difficult for @liamhuber to figure it out alone so I'm gonna make suggestions in the upcoming weeks.