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

[Issue 138] Afford unwrapping API response #139

Merged
1 commit merged into from Apr 12, 2022
Merged

[Issue 138] Afford unwrapping API response #139

1 commit merged into from Apr 12, 2022

Conversation

ghost
Copy link

@ghost ghost commented Apr 12, 2022

This will handle the serialization but not applying response status based on ApiResponse Meta ApiStatus. Thinking about it still.

@coveralls
Copy link

coveralls commented Apr 12, 2022

Pull Request Test Coverage Report for Build 2156194509

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 0.0%

Totals Coverage Status
Change from base Build 2111355126: 0.0%
Covered Lines: 0
Relevant Lines: 0

💛 - Coveralls

@ghost ghost marked this pull request as draft April 12, 2022 14:41
@ghost ghost marked this pull request as ready for review April 12, 2022 16:07
@ghost ghost merged commit 510cc44 into 2.x Apr 12, 2022
@ghost ghost deleted the 2.x-unwrap branch April 12, 2022 16:17
This pull request was closed.
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.

Weaver WS controller outbound mechanism to enable endpoints to return RESTful response based on request
2 participants