Getting Started with API Extension Building
I've been using
Long story short, I'm integrating with a... let's just call it "legacy" system and for a number of reasons—some sensible, some not—I'm going to need APIs that better resemble the existing infrastructure. I can't even really call these a "standard" so much as... I don't even know.
Additionally, there's a team here looking to standardize internal service communication using gRPC.
Both of these require creating API exensions, I presume. The legacy JSON one should be the easiest starting place. Where is the best place to start (besides just diving into the source, which is going to have to happen anyway)? I didn't see an obvious guide (although missing something that already exists would be par for the course).
And any tips for where to start to get something quick and dirty out quickly? (The "legacy API" would basically but like... "spit back the resource as JSON" and "deserialize a JSON object" in most cases.)
AshJsonApi pretty much since I started with Ash. My goal was to make some improvements to it and continue on.Long story short, I'm integrating with a... let's just call it "legacy" system and for a number of reasons—some sensible, some not—I'm going to need APIs that better resemble the existing infrastructure. I can't even really call these a "standard" so much as... I don't even know.
Additionally, there's a team here looking to standardize internal service communication using gRPC.
Both of these require creating API exensions, I presume. The legacy JSON one should be the easiest starting place. Where is the best place to start (besides just diving into the source, which is going to have to happen anyway)? I didn't see an obvious guide (although missing something that already exists would be par for the course).
And any tips for where to start to get something quick and dirty out quickly? (The "legacy API" would basically but like... "spit back the resource as JSON" and "deserialize a JSON object" in most cases.)
