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

Refactor JobExecutionResource #1629

Closed
ghillert opened this issue Aug 8, 2017 · 1 comment
Closed

Refactor JobExecutionResource #1629

ghillert opened this issue Aug 8, 2017 · 1 comment
Labels
type/help-needed Calling help type/technical-debt Techical Dept

Comments

@ghillert
Copy link
Contributor

ghillert commented Aug 8, 2017

For 2.0 (breaking change) we should revisit the structure of JobExecutionResource. It feels messy ... Not only do we handle internally in JobExecutionController#list() with TaskJobExecutions but also with JobExecution inside JobExecutionResource.

Furthermore, there are String representations of date/time values in the resource class.

We should come up with a proper domain object representation.

@cppwfs
Copy link
Contributor

cppwfs commented Nov 12, 2024

Closing this issue due to inactivity. If you think this is closed in error please leave a comment.

@cppwfs cppwfs closed this as completed Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/help-needed Calling help type/technical-debt Techical Dept
Projects
None yet
Development

No branches or pull requests

4 participants