Skip to content

v4 planning #86

@sondrelg

Description

@sondrelg
  • Make ID generator and validator generic, implement transformer (mirror asgi-correlation-id)
  • Split celery functionality into a separate package
  • Split sentry functionality into a separate package
  • Create extras for both
  • Update license
  • Update test project to handle Django deprecation warnings
  • Update to Poetry v1.2
  • Update classifiers
  • Rework docs (drop sphinx and just have readmes per module?)
  • Remove get_guid and set_guid
  • Create example projects for each feature

Essentially we want to de-bloat the core a little, making it possible to install the core middleware without anything else. It's possible to install the middleware today, without adding celery as a dependency, but the celery code is still contained in the wheel.

There's also some Sentry + Celery logic to consider @JonasKs. Do we put that in its own third package? Something to think about 🤔

Metadata

Metadata

Labels

suggestionA feature request/suggestion

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions