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

[DOI-1298] New problem property to return UI messages #79

Closed
wants to merge 1 commit into from

Conversation

blancfabian
Copy link

New problem property to return UI messages

@blancfabian blancfabian force-pushed the doi-1298-add-problem-ui-message branch from 90baa53 to b0e8c3d Compare April 8, 2024 16:16
@@ -14,6 +14,7 @@ public abstract class Problem : BaseModel
public abstract string detail { get; }
public abstract int status { get; }
public abstract int errorCode { get; }
public virtual string message { get; set; }
Copy link
Member

Choose a reason for hiding this comment

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

I am not sure if adding this property to the base class is a good idea because it does not follow Problem Details for HTTP APIs Standard.

Also, it could be a problem for the localization. In place, The clients could use error and status codes to infer the right message or, if you want a generic non-localizable message you could use detail field.

@blancfabian blancfabian closed this Apr 8, 2024
@blancfabian blancfabian deleted the doi-1298-add-problem-ui-message branch April 8, 2024 17:59
@blancfabian blancfabian restored the doi-1298-add-problem-ui-message branch April 8, 2024 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants