-
Notifications
You must be signed in to change notification settings - Fork 44
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
Axum HTTP tracker: discarded PR #179
Axum HTTP tracker: discarded PR #179
Conversation
7375223
to
849633d
Compare
6b57dfd
to
13a4982
Compare
hi @da2ce7 @WarmBeer, since this PR could be too big, I'm working so that it can be merged at any time. If you want, you can review what I've done so far, and I will merge it. I will reopen it later to continue working on the next subtasks. Right now, both implementations can be executed for testing. The scaffolding for Axum is ready, and I will start implementing endpoints. |
We are going to migrate the HTTP tracker from Warp to Axum. This is the basic scaffolding for Axum. Tests have been duplicated to test the new Axum implementation. The setup allows executing both versions: the Warp version on production and both versions (Warp and Axum) on testing env.
13a4982
to
b82fb75
Compare
b82fb75
to
cffd071
Compare
If you wish to part-wise merge this pull request, split out the current work into a new dedicated pull request, then you can merge that one while keeping this pull request open. |
cffd071
to
2f62e8c
Compare
…params from url query WIP: only for mandatory params.
2f62e8c
to
9c25feb
Compare
…tracker implementations We are going to start sharing code bettween both implementation (Warp and Axum). We need to keep common code separated because Warp implementation will be removed when Axum implementation is finished.
hi @da2ce7 @WarmBeer, I've created the new child PR. I will keep this for tracking the implementation of the main issue, but I will create a new PR for each subtask. |
@josecelano This pull request was automatically merged when we merged #180, it is impossible to reopen, we should make a new parent pull-request. |
Since I'm planning to merge child PRs into It would be different if we were using stacked PRs. |
I've moved the subtask in this PR description to the issue |
This PR is a discarded parent PR. We are tracking subtasks for issue #160 within the issue instead of here.
UPDATE: 12/02/2023