Relax dependencies constraints from old versions #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello maintainers 👋
I'm creating a connector for Lookout, a care management platform in Australia.
I'd like to have workato code coming through the cli rather than using the UI. We currently have 104 endpoints in our API, due to grow a few more endpoints soon.
In order to maintain 1-to-1 parity between workato connector and our API, the best shot we have is to have workato SDK gem sitting alongside our main project.
Unfortunately for us, the gem locks the dependencies. Two examples that clashed are activesupport (gem is at v5, we run on rails 7 (latest)), and aws-sigv4 (locked at 1.2.4, we're running on 1.6.0 (latest)).
I've relaxed all the others, too.
I'd rather pull the gem from official channels rather than maintain our own version of it.
Is any part of the code that depends directly on these locked versions? If so, can it be updated?
Happy to lend a hand if needs to update some parts of it, though I have very little understanding of its internals.
Cheers
Ricardo