Skip to content

[2105] Display textual representation of expressions in the Explorer#2115

Merged
AxelRICHARD merged 4 commits intomainfrom
pcd/enh/display-expressions
Apr 15, 2026
Merged

[2105] Display textual representation of expressions in the Explorer#2115
AxelRICHARD merged 4 commits intomainfrom
pcd/enh/display-expressions

Conversation

@pcdavid
Copy link
Copy Markdown
Contributor

@pcdavid pcdavid commented Apr 7, 2026

Bug: #2105
Signed-off-by: Pierre-Charles David pierre-charles.david@obeo.fr

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

@pcdavid pcdavid added this to the 2026.5.0 milestone Apr 7, 2026
@pcdavid pcdavid force-pushed the pcd/enh/display-expressions branch 2 times, most recently from def8ba9 to e9d3a92 Compare April 7, 2026 14:40
@pcdavid pcdavid force-pushed the pcd/enh/display-expressions branch from e9d3a92 to 255713d Compare April 8, 2026 12:34
@pcdavid pcdavid requested a review from AxelRICHARD April 8, 2026 12:41
@pcdavid pcdavid force-pushed the pcd/enh/display-expressions branch 2 times, most recently from 40647b9 to 5b78496 Compare April 13, 2026 13:55
@AxelRICHARD
Copy link
Copy Markdown
Member

@pcdavid a test related to your PR failed during the build. Could you please fix it?

@pcdavid pcdavid force-pushed the pcd/enh/display-expressions branch from 5b78496 to b907bec Compare April 14, 2026 13:13
pcdavid added 3 commits April 14, 2026 16:56
Bug: #2105
Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>
Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>
Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>
@AxelRICHARD AxelRICHARD force-pushed the pcd/enh/display-expressions branch from b907bec to fc6e903 Compare April 14, 2026 14:57
Signed-off-by: Axel RICHARD <axel.richard@obeo.fr>
@AxelRICHARD AxelRICHARD merged commit de26422 into main Apr 15, 2026
4 checks passed
@AxelRICHARD AxelRICHARD deleted the pcd/enh/display-expressions branch April 15, 2026 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

By default, the Explorer should display expressions using their textual representations

2 participants