Skip to content

Conversation

@mcharfadi
Copy link
Contributor

@mcharfadi mcharfadi commented Dec 29, 2025

Bug: #1771

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

@mcharfadi mcharfadi added this to the 2026.1.0 milestone Dec 29, 2025
@mcharfadi mcharfadi force-pushed the mch/enh/detail-helpText branch 4 times, most recently from 24e566d to 64d60b9 Compare December 30, 2025 15:08
@mcharfadi mcharfadi marked this pull request as ready for review December 30, 2025 15:41
@mcharfadi mcharfadi force-pushed the mch/enh/detail-helpText branch from 64d60b9 to bc395dc Compare December 30, 2025 16:27
Copy link
Member

@AxelRICHARD AxelRICHARD left a comment

Choose a reason for hiding this comment

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

I will fix the comments myself, rebase and merge the PR.
Thank you!

- In diagrams, an _items_ compartment is now available on `PortDefinition` graphical nodes to display `ItemUsage`.
- In diagrams, an `ItemUsage` graphical border node is now available on `PortDefinition` graphical nodes.
- In diagrams, when creating an element from a compartment, it will not be displayed by default on the diagram, but only in the compartment.
- In the advanced property view, __isComposite__ and __isReference__ checkboxes now have a help text.
Copy link
Member

Choose a reason for hiding this comment

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

In the advanced property view, isComposite and isReference checkboxes now have a help text. => In the Advanced tab of the Details view, isComposite and isReference properties (checkboxes widgets) now have a help text.

* @author mcharfadi
*/
@Service
public class IsCompositeIsReferenceDetailViewHelpTextProvider implements IDetailViewHelpTextProvider {
Copy link
Member

Choose a reason for hiding this comment

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

Detail => Details with an s (always)

*
* @author mcharfadi
*/
public interface IDetailViewHelpTextProvider {
Copy link
Member

Choose a reason for hiding this comment

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

Detail => Details with an s (always)

import org.eclipse.syson.sysml.Element;

/**
* Provides custom Help text for the detail view widgets.
Copy link
Member

Choose a reason for hiding this comment

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

detail => details with an s (always)

.then(requestIsPortionHelpText)
.thenCancel()
.verify(Duration.ofSeconds(10));

Copy link
Member

Choose a reason for hiding this comment

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

useless empty line

assertThat(helpText).isEmpty();
};


Copy link
Member

Choose a reason for hiding this comment

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

useless empty line

precondition.setPredicateExpression("aql:not(self.oclIsKindOf(sysml::AnnotatingElement))");
return precondition;
}

Copy link
Member

Choose a reason for hiding this comment

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

useless empty line

Bug: #1771
Signed-off-by: Michaël Charfadi <michael.charfadi@obeosoft.com>
@AxelRICHARD AxelRICHARD force-pushed the mch/enh/detail-helpText branch from bc395dc to 6037df4 Compare December 31, 2025 13:19
@AxelRICHARD AxelRICHARD merged commit 62d39d5 into main Dec 31, 2025
4 checks passed
@AxelRICHARD AxelRICHARD deleted the mch/enh/detail-helpText branch December 31, 2025 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add help info near "isComposite" and "isReference" checkboxes in Details view

3 participants