Developers warn the new standard could introduce unprecedented uncertainty, while executives praise its flexibility and reduced documentation requirements.
I don’t know shit about your codebase. But it sounds like you aren’t abstracting your API calls property. Ideally you have an API Client that consumes those blobs and converts them to some generically typed return value.
On top of that you have your actual API, which accepts actions and returns actual objects/collections, or just fucking fails and bubbles up as a generic error because something’s gone fucking wrong.
It’s mainly because, for the industry we’re in, we’re not very big. So we have small teams with few devs…
We also have web, native ios and Android, an internal portal for support staff and cms, all consuming the same dB and many of the same api endpoints. This means they can be undefined for one, but not the other.
So even though on Web you will always have join_table_id… It could be undefined (for another platform)
I don’t know shit about your codebase. But it sounds like you aren’t abstracting your API calls property. Ideally you have an API Client that consumes those blobs and converts them to some generically typed return value.
On top of that you have your actual API, which accepts actions and returns actual objects/collections, or just fucking fails and bubbles up as a generic error because something’s gone fucking wrong.
It’s mainly because, for the industry we’re in, we’re not very big. So we have small teams with few devs…
We also have web, native ios and Android, an internal portal for support staff and cms, all consuming the same dB and many of the same api endpoints. This means they can be undefined for one, but not the other.
So even though on Web you will always have
join_table_id… It could be undefined (for another platform)