Currently the only two options of using the GET /files//GET /groups/ API endpoints are:
api.file_list(oprions) that performs params validation and returns a smart Uploadcare::Api::ResourceList which user might not need
api.get("/files/", oprions) that performs no validation, returns raw API response and requires user to know the endpoint URLs
My proposal is to add two methods: api.files(options) and api.groups(options) that both will return raw API responces but perform same validations as api.file_list/api.group_list does and encapsulate the endpoint URLs
This will provide users with a convinient alternative to api.get("/files/"). Оffcource they will still have to use api.get(response['next']) in order to fetch next pages.
Currently the only two options of using the
GET /files//GET /groups/API endpoints are:api.file_list(oprions)that performs params validation and returns a smart Uploadcare::Api::ResourceList which user might not needapi.get("/files/", oprions)that performs no validation, returns raw API response and requires user to know the endpoint URLsMy proposal is to add two methods:
api.files(options)andapi.groups(options)that both will return raw API responces but perform same validations asapi.file_list/api.group_listdoes and encapsulate the endpoint URLsThis will provide users with a convinient alternative to
api.get("/files/"). Оffcource they will still have to useapi.get(response['next'])in order to fetch next pages.