add option --to-entry-line-number <ENTRY_LINE_NUMBER> #4905

Activity

1. wild-man

   added

   enhancementNew feature or requestNew feature or request

   on Mar 27, 2026
2. giorgiovilardo commented on Mar 27, 2026

   

   giorgiovilardo

   on Mar 27, 2026

   Last edited by giorgiovilardo

   Contributor

   More actions

   not a maintainer in any capacity here, just curious:

   given this file req.hurl:

   GET https://httpbin.org/get
   x-foo: foo
   
   DELETE https://httpbin.org/delete
   x-a-delete: true
   
   POST https://httpbin.org/post
   x-a-header: 123
   {"foo": "bar"}
   

   what would the proposed parameters give over sed?

   sed -n "4,5p" req.hurl | hurl for the delete, sed -n "4p; 8,9p" req.hurl | hurl for the delete with the args of the post, and then there are head and tail for when you know it's on top/bottom.

   I guess it's tidier/more ergonomic without the pipe? but with sed you can pick arbitrary lines...
3. wild-man commented on Mar 28, 2026

   

   wild-man

   on Mar 28, 2026

   Author

   More actions

   As I say this flag will be very useful on integration (in my case with Zed) when you edit file directly and want to exec one request from them. So this not very comfortable to place line numbers to sed especially when you edit with copy paste some big json objects in the query.

   Any way hurl already have very close parameter:
   [--to-entry <ENTRY_NUMBER>] (hurl.dev/docs/manual.html#to-entry)

   For whom is this parameter made then if we can always use SED?

   👍React with 👍1Reacted by Giorgio Vilardo
4. smilingthax commented on Mar 31, 2026

   

   smilingthax

   on Mar 31, 2026

   More actions

   I have a similar experience: When using hurl --test, it might output something like:

   error: Assert status code
       --> -:3388:6
        |
        | GET https://...some...url
   3388 | HTTP 200
        |      ^^^ actual value is <404>
        |
   
   Failure - (201 request(s) in 4524 ms)
   --------------------------------------------------------------------------------
   Executed files:    1
   Executed requests: 201 (43.2/s)
   Succeeded files:   0 (0.0%)
   Failed files:      1 (100.0%)
   Duration:          4650 ms
   

   But 3388 is a line number, not a test number...
   For me, outputting the test number (in addition to the line number) in the assert error would be good enough to rerun the test with --from-entry / --to-entry, though.