-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Improved feat: add bulk edit mode for request headers #3209
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
base: main
Are you sure you want to change the base?
Conversation
Nice feature! |
love it |
What does the bulk editor look like if the header has been unchecked? Also, will support for bulk editing params be implemented as well? |
What's left to get this over the finish line? I would like to move to Bruno but lack of bulk header editing has been a blocker for my workflow for some time. Thanks and Happy Holidays! |
This got missed when fixing merge conflicts.
- Updated QueryParams - Updated RequestHeaders - Reverted VarsTable changes
…ed params are prefixed with `//` now.
if (!bulkEdit) { | ||
setBulkText( | ||
headers | ||
.filter((header) => header.enabled) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you update it to use the //
prefix for disabled variables, similar to how it's done for query parameters
setBulkText( | ||
headers | ||
.filter((header) => header.enabled) | ||
.map((header) => `${header.name}: ${header.value}`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's also a formatting inconsistency query parameters use the format key:value
without a space after the colon, while headers use key: value
with a space. It would be good to standardize this.
Description
This PR improves the PR #706, addressing existing conflicts and updating the feature implementation.
Screen.Recording.2024-09-27.at.3.29.28.PM.mov
Contribution Checklist:
Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.