Fabian Zitter

Sorry to do this, but we simply do not have enough people contributing to keep the package up to date

closes #73

[Multipass] Clear up API

1

For testability, the author of the original PR #65 made all functions public. In order to clear up which part is meant as the public API, we should: either make...

* [POST close](https://help.shopify.com/en/api/reference/orders/order#close) * [POST open](https://help.shopify.com/en/api/reference/orders/order#open) * [POST cancel](https://help.shopify.com/en/api/reference/orders/order#cancel)

Tests are missing some available resources, it is basically a copy-paste-and-change-the-names job. The most tedious part is to make an example request to shopify to set up a request yaml.

Add missing resources

9

There are still some resources missing [according to this list](https://help.shopify.com/api/reference). Since most of them follow the same pattern, I think this is a good first issue. EDIT: Here is a...

To prevent issues like #45 we should add tests that read out the fixture keys and validate that the struct actually defines the correct fields. Ideally we would not write...

Use nested modules to reflect nested resources?

4

When I was adding some more resources I became kind of blind to the details, pretty much lost in copy pasting and going through the same changes over and over...

Since the metafields are special snow flakes (i.e. have methods for every parent resource), we should give a more detailed explanation than just listing it in the implemented resources list.

Because we are defining `singular_resource`, `plural_resource` and `to_json` in both modules, linters will warn you about "functions can not match because a previous function will always match" ```elixir defmodule Shopify.Variant...