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

Improved TC collections merging #1407

Closed
bombillazo opened this issue Nov 14, 2023 · 10 comments
Closed

Improved TC collections merging #1407

bombillazo opened this issue Nov 14, 2023 · 10 comments
Labels
feature request New feature or request

Comments

@bombillazo
Copy link

Please describe feature/problem details and the solution you'd like.

When multiple devs make individual changes to a thunder client collection, at the time of merging and resolving conflicts, there are issues to keep the desired changes. At the moment, we manually resolve conflicts.

Describe alternatives you've considered

Ideally one can have a type of conflict resolver UI to see diff and in a smart intuitive way be able to keep or merge individual requests instead of doing it directly in the JSON code.

Are you using the free version/paid version/trial:

Paid

@bombillazo bombillazo added the feature request New feature or request label Nov 14, 2023
@rangav
Copy link
Collaborator

rangav commented Nov 14, 2023

Thanks @bombillazo for the feedback.

Did you try using the vscode 3 way merge editor?

@bombillazo
Copy link
Author

bombillazo commented Nov 14, 2023

Hey, no I have not tried it. How can I try it out? Our main issues happen when we merge the main branch to our feature branch.

@rangav
Copy link
Collaborator

rangav commented Nov 14, 2023

See this link for details
https://code.visualstudio.com/docs/sourcecontrol/overview#_3way-merge-editor

@bombillazo
Copy link
Author

bombillazo commented Nov 14, 2023

Ahh, yes, we've used this, but it's still not a "smart" way to merge things in the context of API requests. One has to reconcile objects in the code manually...

This is for sure a nice to have since it's a bit complex to analyze the current vs incoming changes in a way that one can see the discreet request properties that changed instead of simply JSON code sections. I am thinking something like what Postman does: https://learning.postman.com/docs/collaborating-in-postman/using-version-control/reviewing-pull-requests/#viewing-the-diff

@rangav
Copy link
Collaborator

rangav commented Nov 15, 2023

Thanks for the feedback, Will review it.

You can also try the 4 way vscode editor as an alternative - microsoft/vscode#155277 (comment)

@rangav
Copy link
Collaborator

rangav commented Mar 21, 2024

Hi @bombillazo

We have a feature request for splitting collection into multiple request files to reduce merge conflicts - #1507

Can you please let me know your feedback as its related to this

@rangav
Copy link
Collaborator

rangav commented May 15, 2024

@bombillazo

We have implemented a new database design to reduce merge conflicts.

Update extension to v2.23.0 and follow the instructions in the below link

https://github.com/thunderclient/thunder-client-support/releases/tag/v2.23.0

Please upgrade to the new format and let us know your feedback.

@rangav rangav closed this as completed May 16, 2024
@rangav
Copy link
Collaborator

rangav commented May 16, 2024

@bombillazo any feedback?

@bombillazo
Copy link
Author

Hey, so far it works

@rangav
Copy link
Collaborator

rangav commented May 16, 2024

Thanks @bombillazo for the confirmation.

let me know if you have any issues with the new format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants