You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the list of work to be completed for a v1.0.0 release. Items focus on simplicity, easy of management and feature completeness.
Support multiple API version. PR#17
Just like the docker API itself, the gem should support multiple API versions and should be configurable by the user in runtime.
Remove query and body parameters validation. PR#14
As the query and body parameters depend on the api version, the current setup will conflict with allowing multiple API versions. Controlling what the user can or cannot use as parameters in all existing and future releases would add a lot of complexity that I prefer to avoid, so for the moment we can drop the validation altogether. If future request come in with enough added value for the feature, this can be reviewed.
Simplify tests. PR#12
As of now, tests run requests against a true docker API. Not only this is not a practice for unit testing, it adds complexity and intermittent run failures, which slow down the development. Instead of requiring a fully functional docker setup for testing, we should use Excon stubs to mock requests when needed.
Here is the list of work to be completed for a v1.0.0 release. Items focus on simplicity, easy of management and feature completeness.
Support multiple API version. PR#17
Just like the docker API itself, the gem should support multiple API versions and should be configurable by the user in runtime.
Remove query and body parameters validation. PR#14
As the query and body parameters depend on the api version, the current setup will conflict with allowing multiple API versions. Controlling what the user can or cannot use as parameters in all existing and future releases would add a lot of complexity that I prefer to avoid, so for the moment we can drop the validation altogether. If future request come in with enough added value for the feature, this can be reviewed.
Simplify tests. PR#12
As of now, tests run requests against a true docker API. Not only this is not a practice for unit testing, it adds complexity and intermittent run failures, which slow down the development. Instead of requiring a fully functional docker setup for testing, we should use Excon stubs to mock requests when needed.