Allow initialization from endpointSpecs directory#56
Merged
Conversation
jonrandahl
approved these changes
Oct 7, 2024
Contributor
jonrandahl
left a comment
jonrandahl
left a comment
There was a problem hiding this comment.
Outside of the versioning constraint updates in the README mentioned below, this looks great to me! 👍
# Conflicts: # CHANGELOG.md # Gemfile.lock # lib/sapi_client/version.rb
This reverts commit 88399d9.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
A sapi client is normally initialised using a base URL and path to an
application.yamlfile:This PR adds the ability to pass an
endpointSpecsdirectory instead, e.g.:This is in support of https://github.com/epimorphics/fsa-rpa-api/issues/13 and retains backward compatibility with the existing initialisation method.