Skip to content
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

[4403] Add support of actions in table rows context menu #4405

Conversation

jerome-obeo
Copy link
Contributor

Bug: #4403

Pull request template

General purpose

What is the main goal of this pull request?

  • Bug fixes
  • New features
  • Documentation
  • Cleanup
  • Tests
  • Build / releng

Project management

  • Has the pull request been added to the relevant project and milestone? (Only if you know that your work is part of a specific iteration such as the current one)
  • 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:, difficulty:, type:)
  • Have the relevant issues been added to the same project and milestone as the pull request?
  • Has the CHANGELOG.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc? (Including changes in the GraphQL API)
  • In case of a change with a visual impact, are there any screenshots in the CHANGELOG.adoc? For example in doc/screenshots/2022.5.0-my-new-feature.png

Architectural decision records (ADR)

  • Does the title of the commit contributing the ADR start with [doc]?
  • Are the ADRs mentioned in the relevant section of the CHANGELOG.adoc?

Dependencies

  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • Are the new dependencies justified in the CHANGELOG.adoc?

Frontend

This section is not relevant if your contribution does not come with changes to the frontend.

General purpose

  • Is the code properly tested? (Plain old JavaScript tests for business code and tests based on React Testing Library for the components)

Typing

We need to improve the typing of our code, as such, we require every contribution to come with proper TypeScript typing for both changes contributing new files and those modifying existing files.
Please ensure that the following statements are true for each file created or modified (this may require you to improve code outside of your contribution).

  • Variables have a proper type
  • Functions’ arguments have a proper type
  • Functions’ return type are specified
  • Hooks are properly typed:
    • useMutation<DATA_TYPE, VARIABLE_TYPE>(…)
    • useQuery<DATA_TYPE, VARIABLE_TYPE>(…)
    • useSubscription<DATA_TYPE, VARIABLE_TYPE>(…)
    • useMachine<CONTEXT_TYPE, EVENTS_TYPE>(…)
    • useState<STATE_TYPE>(…)
  • All components have a proper typing for their props
  • No useless optional chaining with ?. (if the GraphQL API specifies that a field cannot be null, do not treat it has potentially null for example)
  • Nullable values have a proper type (for example let diagram: Diagram | null = null;)

Backend

This section is not relevant if your contribution does not come with changes to the backend.

General purpose

  • Are all the event handlers tested?
  • Are the event processor tested?
  • Is the business code (services) tested?
  • Are diagram layout changes tested?

Architecture

  • Are data structure classes properly separated from behavioral classes?
  • Are all the relevant fields final?
  • Is any data structure mutable? If so, please write a comment indicating why
  • Are behavioral classes either stateless or side effect free?

Review

How to test this PR?

Please describe here the various use cases to test this pull request

  • Has the Kiwi TCMS test suite been updated with tests for this contribution?

@frouene frouene added this to the 2025.2.0 milestone Jan 13, 2025
@frouene frouene linked an issue Jan 13, 2025 that may be closed by this pull request
1 task
@@ -1,5 +1,5 @@
/*******************************************************************************
Copy link
Contributor

Choose a reason for hiding this comment

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

Github indicates that this file is moved from ResizeRowHandler (that thus does not exist anymore), is it normal

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ResizeRowHandler has been removed from the table/row folder since it has been copied into rows.
RowContextMenu.types.ts is a new file.

@@ -1,73 +0,0 @@
/*******************************************************************************
Copy link
Contributor

Choose a reason for hiding this comment

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

Why deleted

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It was already copied in rows folder but not removed at this time.

@@ -126,9 +127,9 @@ export const TableContent = memo(
onPaginationChange(pagination.cursor, pagination.direction, pagination.size);
}, [pagination.cursor, pagination.size, pagination.direction]);

const handleRowHeightChange = (rowId, height) => {
function handleRowHeightChange(rowId, height) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Why this change ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This change is to avoid massive code changes.
This function is now passed as a parameter of useTableColumns located at the beginning of the component.
It would have been moved before it was passed to useTableColumns and bring with it other codes.

Copy link
Member

Choose a reason for hiding this comment

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

????

I don't understand why changing the signature of this function solves any issue

Copy link
Member

Choose a reason for hiding this comment

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

I found out by reverting this, you were using code hoisting to have access to this value before it was declared.

O______ô

Copy link
Member

Choose a reason for hiding this comment

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

The whole row-resizing feature is already in a dire need of a complete re-write, let's not add additional reason to this situation. Just move the code 20lines above instead of trying to access variables before they exist.

@jerome-obeo jerome-obeo force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch 5 times, most recently from 3aee130 to 34b2e24 Compare January 15, 2025 08:49
@jerome-obeo jerome-obeo requested a review from pcdavid as a code owner January 15, 2025 08:49
@jerome-obeo jerome-obeo force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch 3 times, most recently from bb65198 to b6f2a74 Compare January 15, 2025 12:19
@frouene frouene force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch from b6f2a74 to da1a252 Compare January 15, 2025 14:59
@jerome-obeo jerome-obeo force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch from da1a252 to 7d9aaac Compare January 22, 2025 09:26

@Override
public List<RowContextMenuEntry> getRowContextMenuEntries(IEditingContext editingContext, TableDescription tableDescription, Table table, Line row) {
return List.of(new RowContextMenuEntry(DELETE_ID, DELETE_LABEL, List.of("/icons/full/obj16/DeleteTool.svg")));
Copy link
Member

Choose a reason for hiding this comment

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

Don't just reference images from other unrelated modules like that. The Papaya example table has no real links to the support for diagrams in the view DSL.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed, I added a dedicated icon for this action

if (tableInput instanceof InvokeRowContextMenuEntryInput invokeRowContextMenuEntryInput) {
var optionalRow = this.tableQueryService.findLineById(tableContext.getTable(), invokeRowContextMenuEntryInput.rowId());
if (optionalRow.isPresent()) {
Line row = optionalRow.get();
Copy link
Member

Choose a reason for hiding this comment

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

We should really clarify this naming convention of line vs row one day.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It was originally named line but as the standard name is row we use it for new developments.
We did not refactor existing code because is not related to the current feature and we thought that a dedicated issue could be filed in future with the goal to align naming convention over all table code.

@@ -126,9 +127,9 @@ export const TableContent = memo(
onPaginationChange(pagination.cursor, pagination.direction, pagination.size);
}, [pagination.cursor, pagination.size, pagination.direction]);

const handleRowHeightChange = (rowId, height) => {
function handleRowHeightChange(rowId, height) {
Copy link
Member

Choose a reason for hiding this comment

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

????

I don't understand why changing the signature of this function solves any issue

enableColumnPinning: true,
initialState: {
showGlobalFilter: enableGlobalFilter,
columnPinning: { left: ['mrt-row-header'], right: ['mrt-row-actions'] },
Copy link
Member

Choose a reason for hiding this comment

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

What's the link with row actions?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Row header and actions columns should be sticky

representationId={representationId}
tableId={table.id}
row={row}
table={MRT_table}
Copy link
Member

Choose a reason for hiding this comment

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

Why?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

table prop has been removed


private final IObjectSearchService objectSearchService;

private final Function<EObject, UUID> idProvider = (eObject) -> UUID.nameUUIDFromBytes(EcoreUtil.getURI(eObject).toString().getBytes());
Copy link
Member

Choose a reason for hiding this comment

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

Why does that has to be a field?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Comes from copy/paste.

Copy link
Member

Choose a reason for hiding this comment

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

And now it's just some dead code...

if (precondition != null && !precondition.isBlank()) {
return this.evaluateBoolean(variableManager, interpreter, precondition);
}
return false;
Copy link
Member

Choose a reason for hiding this comment

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

Is it normal? Why return false by default instead of true?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You are right. Should be true


private boolean isValidActionPrecondition(org.eclipse.sirius.components.view.table.RowContextMenuEntry viewContextAction, VariableManager variableManager, AQLInterpreter interpreter) {
var precondition = viewContextAction.getPreconditionExpression();
if (precondition != null && !precondition.isBlank()) {
Copy link
Member

Choose a reason for hiding this comment

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

The fact that the expression may be null or blank is not your concern, remove those checks they are done within the interpreter already.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the expression evaluation has been inlined and this method removed

@jerome-obeo jerome-obeo force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch from 7d9aaac to 89d48b9 Compare January 22, 2025 17:41
@jerome-obeo jerome-obeo force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch 9 times, most recently from 1d28a58 to 6bb3e40 Compare January 28, 2025 08:43
@jerome-obeo jerome-obeo force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch from 6bb3e40 to 7c1fa9f Compare January 28, 2025 09:19
Copy link
Member

@sbegaudeau sbegaudeau 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 update the PR and merge it. As it stands today, it simply does not work in half of the use cases and crashes. I'll make sure it fails gracefully but it's really incomplete.

Tons of contributions have been submitted on tables without taking into account the whole picture on this subject. I shouldn't be the only one testing for real given that I have ensured that examples are available on Papaya.

"rowId", rowId.get().toString()
);
var result = this.rowContextMenuQueryRunner.run(variables);
Object document = Configuration.defaultConfiguration().jsonProvider().parse(result);
Copy link
Member

Choose a reason for hiding this comment

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

Why?

Copy link
Member

Choose a reason for hiding this comment

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

As I suspected it, it does nothing, I've removed it

"tableId", tableId.get(),
"rowId", rowId.get().toString());
var result = this.rowContextMenuQueryRunner.run(variables);
Object document = Configuration.defaultConfiguration().jsonProvider().parse(result);
Copy link
Member

Choose a reason for hiding this comment

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

Same comment

* @author Jerome Gout
*/
public interface IRowContextMenuEntryExecutor {
boolean canExecute(TableDescription tableDescription, String tableId, String rowId, String rowMenuContextEntryId);
Copy link
Member

Choose a reason for hiding this comment

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

It's a bit odd to provide only id's here and instance below

Copy link
Member

Choose a reason for hiding this comment

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

Done

*
* @author Jerome Gout
*/
public record RowContextMenuEntry(String id, String label, List<String> iconURLs) { }
Copy link
Member

Choose a reason for hiding this comment

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

require non null

Copy link
Member

Choose a reason for hiding this comment

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

Done

*
* @author Jerome Gout
*/
public record RowContextMenuSuccessPayload(UUID id, List<RowContextMenuEntry> entries) implements IPayload {
Copy link
Member

Choose a reason for hiding this comment

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

require non null

Copy link
Member

Choose a reason for hiding this comment

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

Done

viewer: GQLGetAllRowContextMenuEntriesViewer;
}

export interface GQLGetAllRowContextMenuEntriesViewer {
Copy link
Member

Choose a reason for hiding this comment

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

GQLViewer containing a GQLEditingContext containing a GQLRepresentationMetadata containing a GQLRepresentationDescription which can be a GQLTableDescription... The types are wrong and thus the code can crash

const rowHeaderColumn: MRT_ColumnDef<GQLLine, string> = {
id: 'mrt-row-header',
header: '',
size: 200,
Copy link
Member

Choose a reason for hiding this comment

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

Why 200? Why hardcode this?

@@ -126,9 +127,9 @@ export const TableContent = memo(
onPaginationChange(pagination.cursor, pagination.direction, pagination.size);
}, [pagination.cursor, pagination.size, pagination.direction]);

const handleRowHeightChange = (rowId, height) => {
function handleRowHeightChange(rowId, height) {
Copy link
Member

Choose a reason for hiding this comment

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

I found out by reverting this, you were using code hoisting to have access to this value before it was declared.

O______ô

@@ -126,9 +127,9 @@ export const TableContent = memo(
onPaginationChange(pagination.cursor, pagination.direction, pagination.size);
}, [pagination.cursor, pagination.size, pagination.direction]);

const handleRowHeightChange = (rowId, height) => {
function handleRowHeightChange(rowId, height) {
Copy link
Member

Choose a reason for hiding this comment

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

The whole row-resizing feature is already in a dire need of a complete re-write, let's not add additional reason to this situation. Just move the code 20lines above instead of trying to access variables before they exist.


private final IObjectSearchService objectSearchService;

private final Function<EObject, UUID> idProvider = (eObject) -> UUID.nameUUIDFromBytes(EcoreUtil.getURI(eObject).toString().getBytes());
Copy link
Member

Choose a reason for hiding this comment

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

And now it's just some dead code...

@sbegaudeau sbegaudeau force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch from 7c1fa9f to 612a8d2 Compare January 28, 2025 12:52
@sbegaudeau
Copy link
Member

Most issues detected should be fixed now, I'll wait for the build to merge it.

@sbegaudeau sbegaudeau force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch from 612a8d2 to b1dd897 Compare January 28, 2025 12:53
@sbegaudeau sbegaudeau force-pushed the jgo/enh/4403_add_actions_in_table_rows_context_menu branch from b1dd897 to 09ec261 Compare January 28, 2025 12:58
@sbegaudeau sbegaudeau dismissed frouene’s stale review January 28, 2025 13:26

I'll dismiss this review to move forward and merge the PR. I've personally fixed most of the issues detected.

@sbegaudeau sbegaudeau merged commit a9ca3b9 into eclipse-sirius:master Jan 28, 2025
3 checks passed
@jerome-obeo jerome-obeo deleted the jgo/enh/4403_add_actions_in_table_rows_context_menu branch January 28, 2025 16:28
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 support of actions in table rows context menu
3 participants