Auxiliary Resources OK?
Hey guys, is this correct / good practice?
I have 3 main categories of knowledge: Facts, Methods (or recipes, techniques), and Preferences
I want to search across the three via a simple system of tags. I started with a free-form independent array of tags for each one of my main resources, but I ended up entangling myself, so I went ahead and created a Tags resource with many::many relationships in an attempt to be able to search all resources like so:
But now I'm left with a lot of Resources that feel more like a workaround or a thin wrapper to a DB table instead of an accurate description of my domain:
fascicolo/lib/fascicolo/knowledge.ex
Of these 8, I only really care about 3. Is this a normal architecture, or am I grossly misinterpreting the way Ash works?
I have 3 main categories of knowledge: Facts, Methods (or recipes, techniques), and Preferences
I want to search across the three via a simple system of tags. I started with a free-form independent array of tags for each one of my main resources, but I ended up entangling myself, so I went ahead and created a Tags resource with many::many relationships in an attempt to be able to search all resources like so:
?filter[tags.name]=elixirBut now I'm left with a lot of Resources that feel more like a workaround or a thin wrapper to a DB table instead of an accurate description of my domain:
fascicolo/lib/fascicolo/knowledge.ex
Of these 8, I only really care about 3. Is this a normal architecture, or am I grossly misinterpreting the way Ash works?
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Similar Threads
Was this page helpful?
