It has the return type declared to be double.

Every day pretty much with Unix tools. Vim, awk, sed, etc.

That’s what the If-Match header is for. It prevents this problem.

That being said, I generally think PUTs are preferable to PATCHes for simplicity.

It’s about making APIs more flexible, permissive, and harder to misuse by clients. It’s a user-centric approach to API design. It’s not done to make it easier on backend. If anything, it can take extra effort by backend developers.

But you’d clearly prefer vitriol to civil discourse and have no interest in actually learning anything, so I think my time would be better spent elsewhere.

As I already said, it’s very simple with JSON Patch:

[
  { *op": "replace", "path": "/Name™, "value": "otherName"}
]

Good practice in API design is to permissively accept either undefined or null to represent optionality with same semantics (except when using JSON Merge Patch, but JSON Patch linked above should be preferred anyway).

The semantics of the API contract is distinct from its implementation details (lazy loading).

Treating null and undefined as distinct is never a requirement for general-purpose API design. That is, there is always an alternative design that doesn’t rely on that misfeature.

As for patches, while it might be true that JSON Merge Patch assigns different semantics to null and undefined values, JSON Merge Patch is a worse version of JSON Patch, which doesn’t have that problem, because like I originally described, the semantics are explicit in the data structure itself. This is a transformation that you can always apply.

Zalando explicitly forbids it in their RESTful API Guidelines, and I would say their argument is a very good one.

Basically, if you want to provide more fine-grained semantics, use dedicated types for that purpose, rather than hoping every API consumer is going to faithfully adhere to the subtle distinctions you’ve created.

Only if using JSON merge patch, and that’s the only time it’s acceptable. But JSON patch should be preferred over JSON merge patch anyway.

Servers should accept both null and undefined for normal request bodies, and clients should treat both as the same in responses. API designers should not give each bespoke semantics.

Used in English translations of the Bible, so if you grew up Christian you probably have heard it before.

Confused what you mean. OpenAPI has nothing to do with JS.

Omaha is a lot less left-leaning in my experience. It’s very purple. Lincoln is solidly blue.

I just recently purchased a house in Lincoln. Just quickly looking on Zillow for Omaha and home prices look to be very similar to what I was seeing here in Lincoln. Property taxes in Omaha are also a fair bit higher than Lincoln.

There’s other stuff too, like lower crime rate in Lincoln, better/more parks, LPS being generally a lot better than OPS, etc.

I guess it ultimately depends on what you’re after. If you want something more big city, then Omaha obviously has Lincoln beat. But for a more relaxed pace of life and for raising a family, Lincoln is where it’s at.

There are a number of blue cities in the Midwest. What’s the lowest temp you want? I live in Lincoln, Nebraska and it’s pretty great: nice weather most of the year, low cost of living, blue city, tons of parks. Only downside is dealing with red state bullshit from the state government.

Glad you got fired. Vaccines should always be mandatory save for legitimate, doctor-validated medical exemptions.

Anti-vaxxers are fucking stupid and should either be educated properly or, if they still refuse to do their civic duty after being de-programmed of misinformation, punished. You are only allowed to participate in society if you take the necessary steps that you are morally and ethically obligated to do in order to protect it from preventable, transmissible disease. We had eradicated polio until stupid motherfuckers like yourself decided that it would be a good idea to forgo the standard polio vaccine schedule that we’ve had for decades. Now, we saw the first case in 30 years in 2022 because someone selfishly thought that their personal beliefs were more important than the health and livelihood of everyone else.

The issues are primarily with Azure, I believe.

Nope, just dumped INT.

Common Lisp isn’t a functional programming language. Guile being based on Scheme is closer, but I’d still argue that opting into OOP is diverging from the essence of FP.

Gross. Yeah, no. You should definitely be asking for consent if nothing explicit has been said. I’ve done it many times and it was always appreciated (including by my now wife on our second date when I asked her if I could kiss her), but more importantly, it was the right thing to do. If for some reason there’s a person that is put off by asking, that’s kind of a red flag to be honest. Good communication in relationships and sex is essential and the foundation of any healthy relationship.

There are many ways of asking, too. It doesn’t have to be some stitled “Would you like to have sex with me right now?” Also just generally communicating a lot before and during sex acts as consent and helps to build trust.

A lot of women have had truly awful experiences with men. Good communication and obtaining consent is not only treating women with the kindness and respect they deserve, but it also makes you stand out among the many men with poor social skills that make unwanted advances all the time.

https://curl.se/ has been account free since 1998.

Never understood why people keep trying to use proprietary tools for this, especially when curl is so good.

I have a directory of shell scripts I use to test out endpoints. I persist request/response data either with environment variables or regular files. Oh and since these are just shell scripts, it’s pretty trivial to do stuff like iterate over a CSV (or JSON array) and make a request for each row, conditionally make requests, or whatever else you want.

Oh and honorable mention goes to jo and jq for making it super easy to make/process JSON data.

If the MR is anything bigger than a completely trivial change in a file or 2, it most likely should be broken into multiple commits.

A feature is not atomic. It has many parts that comprise the whole.

Commits should be reasonably small, logical, and atomic. MRs represent a larger body of work than a commit in many cases. My average number of (intentionally crafted) commits is like 3-5 in an MR. I do not want these commits squashed. If they should be squashed, I would have done so before making the MR.

People should actually just give a damn and craft a quality history for their MRs. It makes reviewing way easier, makes stuff like git blame and git bisect way more useful, makes it possible to actually make targeted revert commits if necessary, makes cherry picking a lot more useful, and so much more.

Merge squashing everything is just a shitty band-aid on poor commit hygiene. You just get a history of huge, inscrutable commits and actively make it harder for people to understand the history of the repo.