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

Meta: Tracking issue for dropping Starlette #634

Closed
provinzkraut opened this issue Oct 21, 2022 · 11 comments
Closed

Meta: Tracking issue for dropping Starlette #634

provinzkraut opened this issue Oct 21, 2022 · 11 comments
Assignees
Labels
Meta This is a meta issue dealing with the organization

Comments

@provinzkraut
Copy link
Member

provinzkraut commented Oct 21, 2022

Tracking issue for the current progress of dropping starlette dependencies

How to use?

The following list can serve as an entry-point when tackling the remove of a specific starlette dependencies. It lists the names imported from starlette by their source module and all files that import it.

It is autogenerated with the ast module, and will be updated accordingly.

Overview

@provinzkraut provinzkraut added this to the drop starlette milestone Oct 21, 2022
@provinzkraut provinzkraut self-assigned this Oct 21, 2022
@Goldziher
Copy link
Contributor

nice!

So checkout my draft PR - I am tackling some of these there, primarily the response types and status

@Goldziher Goldziher added Enhancement This is a new feature or request Refactor This is an improvement to existing code or configuration Meta This is a meta issue dealing with the organization and removed Enhancement This is a new feature or request Refactor This is an improvement to existing code or configuration labels Oct 21, 2022
@Goldziher Goldziher changed the title [Meta] Dropping starlette tracking issue Meta: Tracking issue for dropping Starlette Oct 21, 2022
@provinzkraut
Copy link
Member Author

@Goldziher Have that on my radar already! I haven't viewed your PR in detail yet. Does it fully remove all references to the status codes and responses?

@Goldziher
Copy link
Contributor

@Goldziher Have that on my radar already! I haven't viewed your PR in detail yet. Does it fully remove all references to the status codes and responses?

Yes, it will.

@provinzkraut
Copy link
Member Author

I added a reference to the pending PR, so it's visible that it's WIP. Once that's merged tasks will be updated!

@Goldziher
Copy link
Contributor

Goldziher commented Oct 23, 2022

The remaining items for starlette.exceptions.HTTPException and starlette.responses are all tests.
I would like to keep these - we should make sure we preserve compatibility. So you can remove them from the list or strike them through or whatever.

@jtraub
Copy link
Contributor

jtraub commented Oct 24, 2022

I would like to keep these - we should make sure we preserve compatibility

Wouldn't it be better to copy existing tests involving starlette classes into a separate folder (idk, compatibility) and rewrite source tests to use starlite implementation instead? Starlite implementation should be tested too.

@Goldziher
Copy link
Contributor

I would like to keep these - we should make sure we preserve compatibility

Wouldn't it be better to copy existing tests involving starlette classes into a separate folder (idk, compatibility) and rewrite source tests to use starlite implementation instead? Starlite implementation should be tested too.

It would certainly be cleaner. But the tests are not 1:1 imports of the Starlette tests, they are heavily modified, sometimes compeltely rewritten - the point is to make sure that whatever worked in Starlette also works in our API, but we are not testing Starlette - we are testing only our code.

@provinzkraut
Copy link
Member Author

The remaining items for starlette.exceptions.HTTPException and starlette.responses are all tests. I would like to keep these - we should make sure we preserve compatibility. So you can remove them from the list or strike them through or whatever.

I noticed that as well. Will update the file later!

@Goldziher
Copy link
Contributor

testing client is done.

@Goldziher
Copy link
Contributor

ok, as discussed we will not include BaseMiddleware - we we are only keeping tests for this now. Please remove it from the list @provinzkraut

@Goldziher
Copy link
Contributor

And, we are done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Meta This is a meta issue dealing with the organization
Projects
None yet
Development

No branches or pull requests

3 participants