pyiron / pyiron_ontology

Combining pyiron and owlready2 for ontologically guided workflow design
BSD 3-Clause "New" or "Revised" License
4 stars 0 forks source link

Render stuff in alphabetical order by default #34

Closed liamhuber closed 10 months ago

liamhuber commented 10 months ago

Consistent ordering is important for testing examples, which need reliable output. Otherwise has no real impact as it only impacts the render.

github-actions[bot] commented 10 months ago

Binder :point_left: Launch a binder notebook on branch _pyiron/pyiron_ontology/consistentorder

codacy-production[bot] commented 10 months ago

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
:white_check_mark: -0.16% (target: -1.00%) :white_check_mark: 50.00%
Coverage variation details | | Coverable lines | Covered lines | Coverage | | ------------- | ------------- | ------------- | ------------- | | Common ancestor commit (f27223a5d72bf1c34a31ddcf59e3e24971707079) | 457 | 399 | 87.31% | | | Head commit (43e57167607af2ce57c6a803dc528b5ae9d3969a) | 459 (+2) | 400 (+1) | 87.15% (**-0.16%**) | **Coverage variation** is the difference between the coverage for the head and common ancestor commits of the pull request branch: ` - `
Diff coverage details | | Coverable lines | Covered lines | Diff coverage | | ------------- | ------------- | ------------- | ------------- | | Pull request (#34) | 4 | 2 | **50.00%** | **Diff coverage** is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: `/ * 100%`

See your quality gate settings    Change summary preferences

You may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation