@brutasse My broader concern is about avoiding unexpected breaks in user code when the published API contract changes. For example, adding a required ttl could have been handled with a default value first, then made explicit in a versioned API path so users have time to upgrade cleanly.
I wish @Exoscale had a more robust approach to API versioning.
Frequent breaking changes make downstream SDK maintenance harder than it needs to be.
If semantic versioning isnโt feasible, something like GitHubโs API versioning header would be a welcome improvement.
@zeddotdev has gotten good in the last year. Would love to be able to control editor padding. When you hide everything the text is too close to the border of the editor.
@Exoscale do you have any plans to support OAuth2 (e.g. Authorization Code flow) for the API for external apps? It would enable secure, user-delegated access without requiring users to create and manage API keys ๐
@JustSteveKing@julian_center@azjezz Yep, I agree, the PHPStorm isn't as smooth as I'd like it to be. I think it's a third party plugin tho, so not sure how well maintained it is.
@JustSteveKing Just like with @biomejs, I like that I donโt have to install all dependencies just to run formatting and linting in the CI. Super fast ๐จ
Hey @ProtonPrivacy, can you stop pushing offers in the desktop mail client? Iโm already paying for the highest-tier plan, so upgrade prompts make no sense.
Yes, I can hide them. But why show them at all?
@wendell_adriel Yeah I know. Personally I just put all this frontend stuff under a root /frontend folder, which has the advantage of being less nested.