Copilot has gotten substantially worse at providing valid completions for simple statements.
Always wants to add bonus brackets inside parentheses for some reason...
@fullstackfrank Reverse proxy into your already chaotic microservice architecture is the prime use case. I'd probably lean into an APIGW like Kong since caching becomes substantially simpler.
Graphql independently of the HTTP protocol to query any data you want to use as a graph anywhere.
@ianldgs@amacarthur@trunarla Again, a couple files in a demo project are not representative of working in very large TS/JS projects with many developers.
Default exports and abusing index files in applications have led to moderate (not horrific) pain from mine and my colleagues experiences.
@ianldgs@amacarthur@trunarla A common example of this is something along the lines of a file named `Form.tsx` with the component declared `class Form extends React...`
and `export default compose(Form)`
Slightly more annoying to rename the class `Form` to `_Form` `UnwrappedForm` or the like for no reason
@ianldgs@amacarthur@trunarla Expressions are an incredibly common form of default export especially working with react over the years that have made refactoring more difficult/time consuming.
3 files in a bare project are not representative of a codebase made of many thousands of files.
But u do u
@amacarthur@trunarla Auto import usually functions a bit better with named exports using TSC.
Also makes the "rename" refactor with TSC update all reference names instead of leaving the old name of the function scattered around.
@jbaruch@davidwalshblog@HermanMiller Have used many chairs in many offices and this is the only one where I experience no leg pain and no back pain from long sessions.