-
Notifications
You must be signed in to change notification settings - Fork 96
[2325] Add default and initial options to expressions popup #2337
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
Open
AxelRICHARD
wants to merge
3
commits into
main
Choose a base branch
from
ari/enh/2325
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+833
−63
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
25 changes: 25 additions & 0 deletions
25
...rg/eclipse/syson/application/expressions/dto/FeatureValueExpressionPropertiesPayload.java
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| /******************************************************************************* | ||
| * Copyright (c) 2026 Obeo. | ||
| * This program and the accompanying materials | ||
| * are made available under the terms of the Eclipse Public License v2.0 | ||
| * which accompanies this distribution, and is available at | ||
| * https://www.eclipse.org/legal/epl-2.0/ | ||
| * | ||
| * SPDX-License-Identifier: EPL-2.0 | ||
| * | ||
| * Contributors: | ||
| * Obeo - initial API and implementation | ||
| *******************************************************************************/ | ||
| package org.eclipse.syson.application.expressions.dto; | ||
|
|
||
| /** | ||
| * Properties exposed by the expression editor for expressions owned by a SysML {@code FeatureValue}. | ||
| * | ||
| * @param isDefault | ||
| * whether the feature value is marked as default. | ||
| * @param isInitial | ||
| * whether the feature value is marked as initial. | ||
| * @author arichard | ||
| */ | ||
| public record FeatureValueExpressionPropertiesPayload(boolean isDefault, boolean isInitial) { | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 changes: 12 additions & 1 deletion
13
...pplication/syson-application-configuration/src/main/resources/schema/expressions.graphqls
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that the
featureValuePropertiesis optional/nullable, is there a reason to have an explicit separate flag to indicate if it's supported?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the current implementation, I do not see a strong reason to keep the separate flag.
What the code does today in
backend/application/syson-application-configuration/src/main/java/org/eclipse/syson/application/expressions/services/ ExpressionTextualRepresentationEventHandler.java:61is:supportsFeatureValueProperties = falseandfeatureValueProperties = nullFeatureValue: supportsFeatureValueProperties = trueandfeatureValueProperties != nullAttributeUsagewithout an owningFeatureValue: supportsFeatureValueProperties = trueandfeatureValueProperties = new ... (false, false)So with the current backend behavior,
featureValueProperties == nullalready means “not supported”, andfeatureValueProperties != nullalready means “supported”. The boolean does not addinformation.
The only argument for keeping the flag would be API semantics: if you want to model “capability” separately from “current value presence”. That would matter if you wanted a valid state like:
supportsFeatureValueProperties = truefeatureValueProperties = nullBut the handler does not currently emit that state, and the frontend could infer support from nullability alone.
So the precise answer is:
As a conclusion, I will remove this flag.