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

The ChangeContext operation modifies the self value for the next siblings, not just for its children #2399

Open
2 of 4 tasks
theogiraudet opened this issue Sep 18, 2023 · 0 comments · May be fixed by #4083
Open
2 of 4 tasks
Milestone

Comments

@theogiraudet
Copy link

  • I have checked that this bug has not yet been reported by someone else
  • I have checked that this bug appears on Chrome
  • I have specified the version: latest
  • I have specified my environment: All
  • my computer: Windows

Steps to reproduce

  • Have a tool/widget with three operations A, B and C with B child of A and C following sibling of A. By default, the self is a model element foo. A changes the context from foo to bar. B sets a value of bar. C sets a value of foo.
  • Create a model based on the initial metamodel and a representation and execute the tool/widget.

Expected behavior

The correct attributes of foo and bar have been modified.

Actual behavior

Only bar has a modified attribute. If the attribute the language designer wants to modify for bar is also present in foo, the attribute of foo is modified instead of the bar attribute.
The changeContext doesn't introduce a new context where the value of self is only modified for its children. This has side effects on the next siblings.

pcdavid added a commit that referenced this issue Oct 9, 2024
pcdavid added a commit that referenced this issue Oct 9, 2024
@pcdavid pcdavid added this to the 2024.11.0 milestone Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants