last couple of days I have been exploring the ash_json_api_wrapper in a ecommerce store app I am building and I looking for feedback on the design and intent of this library
I see its experimental, and has no docs, and I think I have an ok working knowledge of it, I added an array type and a description type, the later I think its a kludge.
I am working against the Ecommerce API 3.0 from API Deck which based on a quick search seems reasonable Ecommerce API - Apideck
questions:
anyone else using ash_json_api_wrapper in research or development or production?
is the intent to be a way to interact with a JSON API endpoint? i.e. generate a Resource based on an JSON API and then interact with that API sending and receiving?
how should I handle schemas that dont have endpoints? i.e. components.schemas.EcommerceOrderLineItem doesnt have a path in the Ecommerce API?
my goal is to use the Ecommerce API from API Deck to build Ash Resources Domains JSON and GraphSQL and then integrate this with Next JS Commerce app in the same repo
the data in my Ash Ecommerce store than can be synced via API Deck into other platforms such as Shopify etc
It’s been a while since I’ve looked at that code but IIRC that is the path in the response that the resource in question can be found. like if you got a response like %{data: [%{"id" => 1}, %{"id" => 2}]} then entity_path would be something like data.