7 ms·
super minor but unless I'm mistaken SPA stands for "Single Page Application", so the first sentence in the post is a bit jarring: > AlphaSights’ recruitment pl
by jc4p 11y ago
super minor but unless I'm mistaken SPA stands for "Single Page Application", so the first sentence in the post is a bit jarring:
> AlphaSights’ recruitment platform evolved from a Rails application into a _classic SPA app_.
Update 20s later: is "Wepack" in the diagram supposed to be "Webpack"?
Update 60s later: Can you explain _what_ you're actually using that runs into CORS issues? Are browsers talking to the api.* address directly? The diagram seems to imply that all api.* communication is routed through app.*, in which case CORS wouldn't be an issue, right?
- jc4p 11y ago> Wow, my first thought was “headers are messy and this is so restrictive”. As a lazy developer, I’ve shied away from dealing with headers, relying on abstractions provided by libraries and frameworks. I'm sure this is a common thought, but oh man it hurts me to read it.
- vittore 11y agoThe whole thing hurts to read. it could only hurt more if he'd discover the fact that there are in fact other verbs than GET and POST at the same time.
- 33degrees 11y agoThe diagram is bad, the browser is running code loaded on app.* and making requests to api.*; I've used similar setups and have run into the same issues the author is describing.
- bostonvaulter2 11y agoHow did you end up dealing with them?