fix: Escape html-like labels in DotRenderer #2383
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2383 +/- ##
=======================================
Coverage 82.16% 82.17%
=======================================
Files 244 244
Lines 44759 44762 +3
Branches 40541 40541
=======================================
+ Hits 36775 36781 +6
+ Misses 5984 5981 -3
Partials 2000 2000
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
mark-koch
approved these changes
Jun 30, 2025
ss2165
pushed a commit
that referenced
this pull request
Jul 3, 2025
fixes #2286  It looks like there's a graphviz bug that causes nodes to be too narrow when using the monospace font. I'll open a separate issue to make a workaround for that.
ss2165
pushed a commit
that referenced
this pull request
Jul 3, 2025
🤖 I have created a release *beep* *boop* --- ## [0.12.3](hugr-py-v0.12.2...hugr-py-v0.12.3) (2025-07-03) ### Features * add toposort to HUGR-py ([#2367](#2367)) ([ba8988e](ba8988e)) * **core, llvm:** add array unpack operations ([#2339](#2339)) ([74b25aa](74b25aa)), closes [#1947](#1947) * **py:** Helper methods to get the neighbours of a node ([#2370](#2370)) ([1ed6440](1ed6440)) ### Bug Fixes * Escape html-like labels in DotRenderer ([#2383](#2383)) ([c7a43a6](c7a43a6)) * Fixed invalid extension name in test. ([#2319](#2319)) ([fbe1d9c](fbe1d9c)) * **py:** correct ConstString JSON encoding ([#2325](#2325)) ([325168b](325168b)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
ss2165
pushed a commit
that referenced
this pull request
Jul 3, 2025
🤖 I have created a release *beep* *boop* --- ## [0.12.3](hugr-py-v0.12.2...hugr-py-v0.12.3) (2025-07-03) ### Features * add toposort to HUGR-py ([#2367](#2367)) ([ba8988e](ba8988e)) * **core, llvm:** add array unpack operations ([#2339](#2339)) ([74b25aa](74b25aa)), closes [#1947](#1947) * **py:** Helper methods to get the neighbours of a node ([#2370](#2370)) ([1ed6440](1ed6440)) ### Bug Fixes * Escape html-like labels in DotRenderer ([#2383](#2383)) ([c7a43a6](c7a43a6)) * Fixed invalid extension name in test. ([#2319](#2319)) ([fbe1d9c](fbe1d9c)) * **py:** correct ConstString JSON encoding ([#2325](#2325)) ([325168b](325168b)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #2286
It looks like there's a graphviz bug that causes nodes to be too narrow when using the monospace font. I'll open a separate issue to make a workaround for that. (#2385)