Add support for address range commands (GNU extension)#260
Add support for address range commands (GNU extension)#260LoukasPap wants to merge 1 commit intouutils:mainfrom
Conversation
|
GNU sed testsuite comparison: |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #260 +/- ##
==========================================
+ Coverage 82.07% 82.09% +0.02%
==========================================
Files 13 13
Lines 5445 5452 +7
Branches 293 297 +4
==========================================
+ Hits 4469 4476 +7
Misses 974 974
Partials 2 2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
GNU sed testsuite comparison: |
|
Thank you! This is a GNU extension, so the feature should not be available under |
|
Got it! I'll fix these and push again. |
|
Found out that the problem happens with the |
|
I'd suggest one commit for all commands. Try to unify the check for POSIX. |
|
GNU sed testsuite comparison: |
2 similar comments
|
GNU sed testsuite comparison: |
|
GNU sed testsuite comparison: |
81e0901 to
698f2b7
Compare
|
Squashed all my commits having removed the merge commit which was not mine. The POSIX check now happens in one place. I will update the README.md too. |
|
GNU sed testsuite comparison: |
d980254 to
a73f56d
Compare
|
GNU sed testsuite comparison: |
|
I see you're progressing! Try running the various CI tasks locally to avoid CI failures. Please also close the PRs that you've folded into this one. |
|
These two tests are failing because the supported addresses are now 2 and not 1 (like the tests assert):
Would it be "correct" to change the tests to check for 2 addresses; What I mean is, do these tests represent the standard I hope I am clear :) |
|
I would expect that rather than storing / returning a number you would store
I suggest that you also store and process |
dspinellis
left a comment
There was a problem hiding this comment.
Please consider the initial comments I made on the code and fix the CI errors. Will then follow-up with a more complete review.
Thank you for helping me out! Indeed, I recently noticed I could run the CI tasks locally. It will be much faster than pushing and then checking for errors.
Yes, I will finish this issue before moving to another. For a reason, I hadn't noticed your new comments and I was searching for another issue while I was waiting. |
|
GNU sed testsuite comparison: |
|
GNU sed testsuite comparison: |
|
GNU sed testsuite comparison: |
|
Returning to that issue, are there any other changes to be made? Or, is the approach to the problem "correct"? Maybe simpler/cleaner solutions exist. |
|
@sylvestre I think we were reviewing concurrently. Would the proposed scheme for a single field address your concerns? What's your opinion regarding it? |
|
sure, sounds good :) |
…based on POSIX flag - Update `get_cmd_spec()` and `get_verified_cmd_spec()` to accept a boolean POSIX param - Add unit and high level tests - Update README.md
Fixes issue 234
a,iand=commandsn_addrconditional based on POSIX flag