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

Add empty default operation to service operations #89

Closed
jeaf-anaptecs opened this issue Mar 7, 2024 · 0 comments · Fixed by #153
Closed

Add empty default operation to service operations #89

jeaf-anaptecs opened this issue Mar 7, 2024 · 0 comments · Fixed by #153
Assignees

Comments

@jeaf-anaptecs
Copy link
Contributor

jeaf-anaptecs commented Mar 7, 2024

Feature Description

When working with services it is currently not possible to add new operations to a serivce without having a breaking change.
Goal of this feature is to be able to extend existing services without having breaking changes in the code of the service provider.


Idea

  • It is possible to mark a service operation that it should have a default implementation. Of course this default implementation does not have any business logic but at least it avoids that implementations have compile errors
  • Concerning the implementation it should be possible to:
    • just do nothing / return null
    • throw a NotYetImplementedException(...)
    • return default value as defined in the UML model
    • execute a custom generator template that provides an implementation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant