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

#180: Add additional default types and improve arguments handling #105

Merged
merged 2 commits into from
Apr 21, 2021

Conversation

martin-fleck-at
Copy link
Contributor

  • Use some known arguments in the workflow example

Fixes eclipse-glsp/glsp#180

Signed-off-by: Martin Fleck mfleck@eclipsesource.com

- Use some known arguments in the workflow example

Fixes eclipse-glsp/glsp#180

Signed-off-by: Martin Fleck <mfleck@eclipsesource.com>
@@ -0,0 +1,83 @@
/********************************************************************************
* Copyright (c) 2020 EclipseSource and others.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* Copyright (c) 2020 EclipseSource and others.
* Copyright (c) 2021 EclipseSource and others.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch!


import org.eclipse.emf.common.util.EMap;

public final class GArguments extends LinkedHashMap<String, Object> {
Copy link
Contributor

Choose a reason for hiding this comment

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

In contrast to the GLayoutOptions the arguments map can hold arbitary key-value pairs so explicit subclassing and limiting the values you can put into the map doesn't make sense Imo.
I think this rather should be a GArgumentsUtil instead of Map subclass (similar to the util class for ClientOptions)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure I fully agree since the GArguments map can also hold arbitrary key-value pairs but It's better to be consistent ;-) I changed the structure to a utility class similar to ClientOptions.

Copy link
Contributor

@tortmayr tortmayr left a comment

Choose a reason for hiding this comment

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

Thanks. Looks good to me 👍

@martin-fleck-at martin-fleck-at merged commit 5f458da into master Apr 21, 2021
@martin-fleck-at martin-fleck-at deleted the issues-180 branch April 21, 2021 12:34
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.

Discussion: Provide a default shape mapping on the client for standard node types
2 participants