Skip to content

Bugfix/creating a feature should be the default in the feature diagram editor #739#1760

Open
dbinkele wants to merge 15 commits into
maintenance/mps20241from
bugfix/Creating-a-Feature-should-be-the-default-in-the-feature-diagram-editor-#739
Open

Bugfix/creating a feature should be the default in the feature diagram editor #739#1760
dbinkele wants to merge 15 commits into
maintenance/mps20241from
bugfix/Creating-a-Feature-should-be-the-default-in-the-feature-diagram-editor-#739

Conversation

@dbinkele

@dbinkele dbinkele commented Apr 21, 2026

Copy link
Copy Markdown
Member

solves IETS3/iets3.core#739

@dbinkele dbinkele requested review from kbirken and mfsoliveira and removed request for arimer and jonaskraemer April 21, 2026 13:51
…ould-be-the-default-in-the-feature-diagram-editor-#739
…ould-be-the-default-in-the-feature-diagram-editor-#739
…ould-be-the-default-in-the-feature-diagram-editor-#739

@kbirken kbirken left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When a new node in the feature model tree is created, it is always a Feature now. The ticket says

switching a Feature to a FeatureInclude should be done differently (e.g., via pressing :)

Unfortunately, pressing : after the feature name does not convert it into a FeatureModelInclude anymore (the ticket still assumes this is working, but we obviously had a regression). Now the only way to create a FeatureModelInclude is by intention. Pls. fix the regression, so that pressing : converts a Feature to a FeatureInclude. Also add a test so that functionality does not get lost anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants