Updates to the PG problem editor PGML conversion for corresponding changes to PG. - #3101
Merged
Alex-Jordan merged 2 commits intoAug 4, 2026
Conversation
drgrice1
force-pushed
the
pgml-convert-pgeditor-revised
branch
2 times, most recently
from
July 28, 2026 12:13
2d46a9d to
447c83d
Compare
Remove the plural on the PGML convert error as was done on the PG side as there is only ever one error. Remove the `<pre><code>` wrapper. That is not right for this type of message.
drgrice1
force-pushed
the
pgml-convert-pgeditor-revised
branch
from
August 3, 2026 22:08
447c83d to
39ce98d
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This is built on top of #3046 which basically sets up the PG problem editor for the initial changes on the PG side.
The plurality of the
errorkey in the response was removed as was done on the PG side since there is only ever one error.Also, remove the
<pre><code>wrapper. That is not right for this type of message.