It's a huge pain to maintain open API files and the generators are of varying quality supporting different specs. They also handle some parts differently in the output.
Which generator have you used for typescript? There are 4 of them and all of them have different issues.
I find the axios one the most stable but keen to know.
How do you also handle refreshing token, incepting request while passing the client through configuration in these?
I find interception and changing response breaks some of the client methods without a way to handle the failure.
Any example or resources you found useful would be appreciated.
> The same code you write to validate your request/response should automatically generate the OpenAPI see my comment here
Or even better the opposite: I have a mini-framework [0] which does the validation and routing based on an OpenAPI spec, so the devs can focus on writing the business logic.
Many legacy codebase don't have an easy way to add schema and make code changes so you end up maintaining a separate file to avoid making changes in the codebase.
Not that painful when you’ve a dedicated API designer or API writer, or when the teams realize the importance of maintaining OAS files as the single source of truth of API design.
I'm not surprised the neo bank idea was shut down. The profit margins are really low and moving forward, capital is going to be expensive.
In India, most neobank startups are bleeding money through rewards and incentives funded by VCs and they are all shutting down one by one.
There is no moat. Support is expensive. They are still tied up with a traditional bank because getting bank license is not an option for startups. This is the case almost everywhere, not confined to India. You would be working with a legacy bank and inherit all the limitations.
Banking is free for most people. UPI and rupay run by government agencies result in 0% charge for merchant and consumers. So you can forget about any transaction related fees.
This might not be common across the world but there is no lock in when investing in funds in India. You cannot lock in customers for mutual funds and related investment legally anymore as of last year, I believe. So not possible to make profit on investment management side.
I agree with you around the analysis, but how do you explain the success of Ramp in the US then? Re India, will RazorPay win on the neobank side as well? As they have the critical size?
Because our tests are already written with Cypress and we don't want to change again (we just moved from Protractor after Angular said it was dying, so we've already rewritten them once).
In generak, it can reach it easily on a dev machine, but it seems like the norm. And my linux experience is at 1/5th or 1/10th the amount of data read/write tha comparable tasks.
Looking at this thread, it seems this is the way with macOS.
It's a huge pain to maintain open API files and the generators are of varying quality supporting different specs. They also handle some parts differently in the output.
Which generator have you used for typescript? There are 4 of them and all of them have different issues.
I find the axios one the most stable but keen to know.
How do you also handle refreshing token, incepting request while passing the client through configuration in these?
I find interception and changing response breaks some of the client methods without a way to handle the failure.
Any example or resources you found useful would be appreciated.