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

Fix direct responses #463

Merged
merged 7 commits into from
Jan 17, 2025
Merged

Fix direct responses #463

merged 7 commits into from
Jan 17, 2025

Conversation

devkral
Copy link
Contributor

@devkral devkral commented Dec 23, 2024

The original edge cases have been fixed here by don't mangling direct responses

Changes:

  • direct responses aren't mangled
  • split out the data routing test case in a seperate file

Former:

This PR contains tests for some edge cases.

They are required for e.g. building a login form.

@devkral devkral force-pushed the devkral/issues/test_cases branch from 2b2dcb8 to 7789cad Compare January 9, 2025 12:21
- rename test methods
- add test for route with GET and POST
- bypass ResponseContainer when LilyaResponse was found
- Update edge cases

Note: there was a trick: forward strings aren't resolved correctly but
removing from __future__ helped
- split edge cases tests
@devkral devkral force-pushed the devkral/issues/test_cases branch from 7789cad to 5748808 Compare January 17, 2025 12:30
@devkral devkral changed the title failing edge cases Fix direct responses Jan 17, 2025
@tarsil tarsil merged commit 2dadbd6 into main Jan 17, 2025
11 checks passed
@tarsil tarsil deleted the devkral/issues/test_cases branch January 17, 2025 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants