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

Use ErrorMessage type from spark-commons #2170

Open
benedeki opened this issue Feb 1, 2023 · 0 comments · May be fixed by #2177
Open

Use ErrorMessage type from spark-commons #2170

benedeki opened this issue Feb 1, 2023 · 0 comments · May be fixed by #2177
Assignees
Labels
Conformance Conformance Job affected feature New feature good first issue Good for newcomers priority: medium Important but not urgent refactoring Improving code quality, paying off tech debt, aligning API, cleanup of unused code Standardization Standardization Job affected
Milestone

Comments

@benedeki
Copy link
Collaborator

benedeki commented Feb 1, 2023

Background

Let's unify the ErrorMessage type across our products and repos.

Feature

After SparkCommons:#78 have been finished and released remove the ErrorMessage definition and all common things from Enceladus and use the spark-commons one.

@benedeki benedeki added refactoring Improving code quality, paying off tech debt, aligning API, cleanup of unused code good first issue Good for newcomers feature New feature Conformance Conformance Job affected Standardization Standardization Job affected priority: medium Important but not urgent labels Feb 1, 2023
TebaleloS added a commit that referenced this issue Feb 24, 2023
TebaleloS added a commit that referenced this issue Feb 24, 2023
@TebaleloS TebaleloS linked a pull request Feb 24, 2023 that will close this issue
TebaleloS added a commit that referenced this issue Mar 2, 2023
TebaleloS added a commit that referenced this issue Mar 2, 2023
@benedeki benedeki added this to the Release 3.1 milestone Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Conformance Conformance Job affected feature New feature good first issue Good for newcomers priority: medium Important but not urgent refactoring Improving code quality, paying off tech debt, aligning API, cleanup of unused code Standardization Standardization Job affected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants