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

[BasicAuth] section can't be empty contrary to other section #1772

Closed
jcamiel opened this issue Jul 17, 2023 · 0 comments
Closed

[BasicAuth] section can't be empty contrary to other section #1772

jcamiel opened this issue Jul 17, 2023 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jcamiel
Copy link
Collaborator

jcamiel commented Jul 17, 2023

What is the current bug behavior?

All section except [BasicAuth] can be empty:

This Hurl file is OK (all sections except [BasicAuth])

GET http://localhost:8000/hello
[QueryStringParams]
[FormParams]
[MultipartFormData]
[Cookies]
[Options]
HTTP 200
`Hello World!`

This file is KO ([BasicAuth] section added)

GET http://localhost:8000/hello
[QueryStringParams]
[BasicAuth]
[FormParams]
[MultipartFormData]
[Cookies]
[Options]
HTTP 200
`Hello World!`
$ hurl test.hurl
error: Parsing JSON
  --> tests_ok/empty_sections.hurl:3:2
   |
 3 | [BasicAuth]
   |  ^ JSON error
   |

Note: there is already an integration test => tests_ok/empty_sections.hurl

Steps to reproduce

What is the expected correct behavior?

Make all section behaves uniformly.

Execution context

  • Hurl Version (hurl --version): 4.0.0
@jcamiel jcamiel added the bug Something isn't working label Jul 17, 2023
@fabricereix fabricereix self-assigned this Aug 1, 2023
@fabricereix fabricereix linked a pull request Aug 5, 2023 that will close this issue
@jcamiel jcamiel closed this as completed Aug 5, 2023
@fabricereix fabricereix added this to the 4.1.0 milestone Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants