Skip to content

[2251] Allow expression-related operations on their parent element#2252

Draft
pcdavid wants to merge 3 commits into
mainfrom
pcd/enh/expression-parent
Draft

[2251] Allow expression-related operations on their parent element#2252
pcdavid wants to merge 3 commits into
mainfrom
pcd/enh/expression-parent

Conversation

@pcdavid
Copy link
Copy Markdown
Contributor

@pcdavid pcdavid commented Jun 2, 2026

Bug: #2251
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 added 2 commits June 2, 2026 14:53
Bug: #2119
Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>
Bug: #2251
Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>
- Make sure it gets the keyboard focus on open so that the user can
  start typing immediatly.
- Add support for Ctrl-RET to apply/update directly from the keyboard.

Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>
@AxelRICHARD AxelRICHARD force-pushed the pcd/enh/expressions-details-view branch from 013ae29 to 408d19a Compare June 4, 2026 10:04
Base automatically changed from pcd/enh/expressions-details-view to main June 4, 2026 15:49
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.

Some operations targetting expressions should be directly available from their parent/owner element

1 participant