Skip to content

ST6RI-938 NPE when calling "instantiatedType" on an "InstantiationExpression"#766

Merged
seidewitz merged 1 commit into
masterfrom
ST6RI-938
Jun 13, 2026
Merged

ST6RI-938 NPE when calling "instantiatedType" on an "InstantiationExpression"#766
seidewitz merged 1 commit into
masterfrom
ST6RI-938

Conversation

@AxelRICHARD

@AxelRICHARD AxelRICHARD commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

This PR avoids a potential NullPointerExpression when calling the operation InstantiationExpression.instantiatedType(). If an InstantiationExpression has an ownedMembership that is not a FeatureMembership but invalidly has no memberElement, then calling InstantiationExpression.instantiatedType() results in a NullPointerException. Even though the Membership is invalid, the system should not produce an exception when the operation is called.

Signed-off-by: Axel RICHARD <axel.richard@obeo.fr>
@AxelRICHARD AxelRICHARD marked this pull request as ready for review June 12, 2026 08:39
@seidewitz seidewitz changed the title ST6RI-938 Fix NPE on InstantiationExpression.instantiatedType ST6RI-938 NPE when calling "instantiatedType" on an "InstantiationExpression" Jun 13, 2026
@seidewitz seidewitz self-assigned this Jun 13, 2026
@seidewitz seidewitz added the bug Something isn't working label Jun 13, 2026
@seidewitz seidewitz added this to the 2026-05 milestone Jun 13, 2026
@seidewitz seidewitz merged commit 241934d into master Jun 13, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Calling "instantiatedType" on an "InstantiationExpression" with its missing require membership causes an NPE

3 participants