hello 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…

I’ve only experimented with it, but I’d love to see it stretch its wings, and as soon as I have need of it I’ll be pushing its limits again. Yep! Thats right. If they don’t have endpoints then you are likely looking for embedded resources, the :map type, or a fully custom type.

Ok. Wrangling json schemas is not my favorite thing but if it can become a richer tool it can be a very powerful tool to build an integration project

followup whats "entity_path \"#{config[:entity_path]}\"" in relation to the OpenAPI JSON spec? OpenAPI Specification v3.1.1 The OpenAPI Specification (OAS) defines a standard, programming language-agnostic interface description for HTTP APIs.

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.

pushed some notes to my blog [image] Starting devekko.store Ash Phoenix Ecommerce Project ### Background I've been working with Elixir Phoenix since I think 1.4 and I enjoy the functional

splitting out the ash_json_gen_ecommerce_api to accompany my fork of ash_json_api_wrapper my idea is to make an easily installable ash json gen package that consume the Ecommerce API and creates a Resource. I have a closed sourced proprietary app which I want to use these apps in also soon I want…

Seeking feedback exploring ash_json_api_wrapper

Questions & Help Questions

niccolox January 14, 2025, 2:22am 4

followup

whats "entity_path \"#{config[:entity_path]}\"" in relation to the OpenAPI JSON spec?