-
Notifications
You must be signed in to change notification settings - Fork 62
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
457: Support specifying features with `@service` r=omus a=omus While working on #384 I encountered a situation where the change I was making was breaking so in order to have to make a major release I wanted to make the change opt-in. Unfortunately doing that would result in every single AWS.jl API call being modified to opt-in to the new behaviour making updating quite tedious. The ``@service`` feature support added in this PR allows end users to opt-in to new behaviour when using the ``@service`` macro (e.g. ``@service` S3 my_new_feature=true`). This interface is much more convenient and probably is a pattern we want to use for incorporating future behaviour. Currently this PR defines no features. Additionally for low-level API calls I've introduced the `set_features` function (e.g. `set_features(::Service; my_new_feature=true)`) which allows for setting the feature set to be used for a service instance. The only issue I can think of with this is if an end user makes use of multiple ``@service`` calls to the same service in the same module then the last call will define the behaviour. As doing this will result in a module being redefined I don't think this is a situation anyone will notice. Co-authored-by: Curtis Vogt <curtis.vogt@gmail.com>
- Loading branch information
Showing
286 changed files
with
45,468 additions
and
6,861 deletions.
There are no files selected for viewing
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
Oops, something went wrong.