You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Adding Features to the Feature Model via Quick Fix puts them into wrong place #207
From what I remember this error was always there since UNASSIGNED becomes a secondary root and the file can have at most one root. The UNASSIGNED row should be removed when the features under it are sorted properly.
When we implemented this feature we wanted the error so that you wouldn't commit your feature-model with unassigned features.
If you have a suggestion on how this could work better please feel free to give some details.
I understand. I think in the past it actually worked (not sure anymore), but maybe we can have a proper error message remembering developers to remove it instead of a parsing error?
Activity
johmara commentedon May 26, 2026
From what I remember this error was always there since UNASSIGNED becomes a secondary root and the file can have at most one root. The UNASSIGNED row should be removed when the features under it are sorted properly.
When we implemented this feature we wanted the error so that you wouldn't commit your feature-model with unassigned features.
If you have a suggestion on how this could work better please feel free to give some details.
Kevin3112 commentedon May 27, 2026
I understand. I think in the past it actually worked (not sure anymore), but maybe we can have a proper error message remembering developers to remove it instead of a parsing error?