feat: support "+json"-suffixed response media types

[bunny-therapist]

Giving route handlers a response media type of the form "application/+json" automatically uses json encoding for the response.

Closes #3088

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (bfeb5e9) 98.23% compared to head (e0f34e4) 98.25%.
Report is 48 commits behind head on develop.

❗ Current head e0f34e4 differs from pull request most recent head 4247e47. Consider uploading reports for the commit 4247e47 to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3096      +/-   ##
===========================================
+ Coverage    98.23%   98.25%   +0.02%     
===========================================
  Files          312      320       +8     
  Lines        14121    14363     +242     
  Branches      2430     2307     -123     
===========================================
+ Hits         13872    14113     +241     
- Misses         107      109       +2     
+ Partials       142      141       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bunny-therapist]

The documentation preview does not have my changes. Am I supposed to build it manually somehow?

[provinzkraut]

The documentation preview does not have my changes. Am I supposed to build it manually somehow?

Seems to be there?

https://litestar-org.github.io/litestar-docs-preview/3096/usage/responses.html#json-responses

[bunny-therapist]

"build docs" failed for the commit with

/home/runner/work/litestar/litestar/docs/reference/cli.rst:7: ERROR: "<class 'litestar.cli._utils.LitestarExtensionGroup'>" of type "litestar.cli:litestar_group" is not click.Command or click.Group."click.BaseCommand"

Sphinx parallel build error:
tools.sphinx_ext.run_examples.StartupError: App docs/examples/data_transfer_objects/factory/providing_values_for_nested_data.py failed to come online
make: *** [Makefile:152: docs] Error 2
reading sources... [ 89%] usage/databases/piccolo .. usage/metrics/prometheus
Error: Process completed with exit code 2.

I can't see how I could have caused this or what I can do about it?

[provinzkraut]

"build docs" failed for the commit with

/home/runner/work/litestar/litestar/docs/reference/cli.rst:7: ERROR: "<class 'litestar.cli._utils.LitestarExtensionGroup'>" of type "litestar.cli:litestar_group" is not click.Command or click.Group."click.BaseCommand"

Sphinx parallel build error:
tools.sphinx_ext.run_examples.StartupError: App docs/examples/data_transfer_objects/factory/providing_values_for_nested_data.py failed to come online
make: *** [Makefile:152: docs] Error 2
reading sources... [ 89%] usage/databases/piccolo .. usage/metrics/prometheus
Error: Process completed with exit code 2.

I can't see how I could have caused this or what I can do about it?

This was fixed in main already iirc. Should be good now here too.

[bunny-therapist]

"build docs" failed for the commit with

/home/runner/work/litestar/litestar/docs/reference/cli.rst:7: ERROR: "<class 'litestar.cli._utils.LitestarExtensionGroup'>" of type "litestar.cli:litestar_group" is not click.Command or click.Group."click.BaseCommand"

Sphinx parallel build error:
tools.sphinx_ext.run_examples.StartupError: App docs/examples/data_transfer_objects/factory/providing_values_for_nested_data.py failed to come online
make: *** [Makefile:152: docs] Error 2
reading sources... [ 89%] usage/databases/piccolo .. usage/metrics/prometheus
Error: Process completed with exit code 2.

I can't see how I could have caused this or what I can do about it?

This was fixed in main already iirc. Should be good now here too.

But this is not based on main, but on develop, which is 9 commits behind main.

[provinzkraut]

But this is not based on main, but on develop, which is 9 commits behind main.

Yeah, that was the issue. develop wasn't up to date. The fix was to update develop and subsequently your branch so they had the latest changes from main. Sorry if my initial explanation was a bit vague 👀

[bunny-therapist]

Some checks failed with docker compose errors now?

[provinzkraut]

I've got one comment about the example, other than that this is good to go in!

[bunny-therapist]

A test failed mysteriously, but I think it is marked as "flaky".

[bunny-therapist]

Huh. I guess dict[str, Any] only became a thing in python 3.9. I will update.

[bunny-therapist]

All checks are passing now. I am not sure what "update branch" strategy is preferred (merge vs rebase) so I will leave that to you.

[provinzkraut]

All checks are passing now. I am not sure what "update branch" strategy is preferred (merge vs rebase) so I will leave that to you.

Do whatever you prefer. Personally, I like rebase more, but it doesn't really make a difference here since we squash merge PRs anyway.

[github-actions]

Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/3096

[bunny-therapist]

Should I have been added to some "all contributors" file? I see that happening in other PRs but I don't know how this works.

[provinzkraut]

Yes, you should have!

You can just request that yourself by making a comment like this:

@all-contributors add @bunny-therapist for code.

[allcontributors]

@provinzkraut

I've put up a pull request to add @bunny-therapist! 🎉