chore(release)!: Version 3.0 #3364
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
area/ci
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3364 +/- ##
==========================================
- Coverage 98.29% 97.99% -0.30%
==========================================
Files 328 326 -2
Lines 14857 14537 -320
Branches 2356 2302 -54
==========================================
- Hits 14603 14246 -357
- Misses 116 154 +38
+ Partials 138 137 -1 ☔ View full report in Codecov by Sentry. |
github-actions
bot
added
area/connection
area/contrib
github-actions
bot
added
size: large
area/kwargs
area/openapi
github-actions
bot
added
area/response
area/constants
provinzkraut
force-pushed
the
v3.0
branch
2 times, most recently
from
5570355
to
31c3ddf
Compare
|
|
Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/3364 |
provinzkraut
force-pushed
the
v3.0
branch
2 times, most recently
from
2536957
to
81081dd
Compare
* Trigger documentation build * Trigger documentation build * docs: update to v3 style * docs: move some things to litestar.dev repo, change versioning, add environment tag * docs: update landing page * chore: update lockfile * chore: add AA upper constraint * fix(docs): re-colonize * docs: enable sphinx-togglebutton * docs: use current year var * deps: update deps * fix(docs): do not link __name__ for now * fix(docs): use correct link to page --------- Co-authored-by: Peter Schutt <peter.github@proton.me>
* Remove deprecated StaticFiles and StaticFilesConfig * remove special casing of static files app from handlers/router * remove outdated docs sections * Add what's new section * Rename tests for consistency
This PR changes behavior of parameters that are typed in a union with `None`. Prior behavior was to implicitly default their value to `None` if a value wasn't provided making an apparently non-optional parameter (i.e., no declared default) actually optional. Surprising behavior at best, dangerous at worst. New behavior is to throw a client error when a parameter without a default is not provided.
* refactor: removes deprecated OpenAPIController This PR removes all deprecated elements of OpenAPIConfig and the OpenAPIController, removes any obsolete tests and refactors tests that were parametrized to test both OpenAPIController and the router-based approach. * docs: What's new entry * Update docs/usage/openapi/ui_plugins.rst Co-authored-by: Jacob Coffee <jacob@z7x.org> * Update litestar/openapi/config.py * fix: remove whitespace * fix: import table formatting (i hope) --------- Co-authored-by: Jacob Coffee <jacob@z7x.org>
…e` (#3393) * Remove 'app' parameter from `.to_asgi_response`
Remove the deprecated utility functions, `get_litestar_scope_state``, ``set_litestar_scope_state``, ``delete_litestar_scope_state``, and ``is_sync_or_async_generator``.
* remove handler names * Remove option handler creation from HTTPRoute * Remove methods attribute from BaseRoute * Move kwargs model to handlers and creation to on_registration * Store kwargs model on handlers instead of routes * Simplify HTTPRoute route_handler_map creation * Simplify Router.route_handler_method_map * Relax typing of HTTPRoute * Move handling logic to route handlers * Remove scope_type * Don't pass route to HTTPRouteHandler during handling * Don't pass scope to handle methods * Resolve and establish connections in routes; Only pass connections to handlers --------- Co-authored-by: Jacob Coffee <jacob@z7x.org> Co-authored-by: Peter Schutt <peter.github@proton.me>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Standing PR for the 3.0 release
Important
2.x, be mindful of the changes you are pulling into this branch.maininto this branch as it makes the process of merging it back intomainwith a merge commit when the release is due easiermainto keep the history of the feature commits intactBreaking Changes
Any breaking changes should be properly marked with
!in the conventional commits schema, e.g.,fix($scope)!: fix thing but it broke stuff,feat(dtos)!: add breaking feature