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

[API] Support for non-json content types #883

Open
brandtkeller opened this issue Jan 16, 2025 · 0 comments · May be fixed by #890
Open

[API] Support for non-json content types #883

brandtkeller opened this issue Jan 16, 2025 · 0 comments · May be fixed by #890
Labels
enhancement New feature or request triage Awaiting triage from the team

Comments

@brandtkeller
Copy link
Member

Is your feature request related to a problem? Please describe.

Adding support for the API Domain to handle non-json content-types

Describe the solution you'd like

  • Given a validation with the API domain
  • When a validate is performed and the response returns content-type that is not json
  • Then no error occurs and the data is made available as a string

Expected Deliverable

  • Modification to the API domain to support the conditional json unmarshall process.
@brandtkeller brandtkeller added the enhancement New feature or request label Jan 16, 2025
@github-actions github-actions bot added the triage Awaiting triage from the team label Jan 16, 2025
@brandtkeller brandtkeller linked a pull request Jan 17, 2025 that will close this issue
6 tasks
@brandtkeller brandtkeller moved this from 🆕 New to 🏗 In Progress in Lula and Friends Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage Awaiting triage from the team
Projects
Status: 🏗 In Progress
Development

Successfully merging a pull request may close this issue.

1 participant