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

Render stuff in alphabetical order by default #34

Merged
merged 1 commit into from
Jan 11, 2024
Merged

Conversation

liamhuber
Copy link
Member

@liamhuber liamhuber commented Jan 11, 2024

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

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

Binder 👈 Launch a binder notebook on branch pyiron/pyiron_ontology/consistent_order

Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
-0.16% (target: -1.00%) 50.00%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (f27223a) 457 399 87.31%
Head commit (43e5716) 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: <coverage of head commit> - <coverage of common ancestor commit>

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: <covered lines added or modified>/<coverable lines 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

@liamhuber liamhuber merged commit dd90bea into main Jan 11, 2024
18 of 19 checks passed
@liamhuber liamhuber deleted the consistent_order branch January 11, 2024 20:31
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.

1 participant