In the examples, I used prefixes to demonstrate API versioning, but you're not limited to this approach. Prefixes can be used for general route structuring as well (like grouping entities, etc.), not just for versioning.
In this example, routes are split into routers by entities, which are then grouped into an api_v1 router, and finally, this api_v1 router is added to the main router.
I've been using the silly hack of using two versions of Firefox side-by-side (so, multiple browsers but they are both Firefox today), one which is Default in the OS and focuses on a single profile and Container Tab management. The other launches into the ProfileManager at startup to choose a Profile and doesn't pick up random links because it isn't Default.
Better Profile Management tools may be nice to see. Maybe I won't need dueling builds of Firefox. Or maybe I'll keep it, we'll see.
If you're working against an GraphQL based API, you should be able to pull a schema file. And use that to implement your own API.
All you would get from an Mitmproxy is example queries and mutations. With the additional complexity of extra tooling to stich together the schema file
Pulling the schema file can, and often is, disabled server side. And GraphQL APIs can, and often do, decline to serve other than persisted queries, and those can't be really inferred even with known schema.
So I am working with a new company that has a ton of graphql queries. What I wanted to do was write an integration test for them in the fastest and easiest way possible.
I don't want to sit and read each query to identity where it is in the user flow. So I was thinking if I run this in the background and go through a happy flow, I can get the APIs in order and write an integration test.
Before articles about this started to show up on the web, I've noticed that my weekly suggestion playlist (which refreshes every monday) sometimes had music with either low quality or encoding artifacts (just like AI music).
But after reading about this phenomenon, I also started to dig deeper into which artists were actually suggested each week. And to my surprise there were quite a bit of artists I've never heard of, and were hard to find further information on.
Hopefully Spotify won't touch weekly release playlist (the one which refreshes every friday) of artists you already listen to and have saved into personal playlists.
I've been eye balling a pair of those for a while now.
Any other quirks you're willing to share? Such as: how's the input latency (from key press to seeing it)? early signs of tear? do I need to invest in spare parts?
No latency. No tearing that I've noticed. They can be configured to run at 60 Hz or 120 Hz.
I couldn't find any spare parts and honestly, I think that's because the brand is trying to liquidate the RayNeo Air 2 models in favor of RayNeo Air 2s and newer. It's admittedly the lower in quality than other offerings, but passable, and not bad for just $200.
It's only possible for me to work with these when font size is increased and the scaling is turned up. Trading information density for back/neck relief is worth it in my opinion.
It's exactly what I was looking for