Sybren

It would seem that the decision has been reverted already: https://www.flickr.com/groups/51035612836@N01/discuss/72157721918374433/72157721918411949 Regardless, this could be a nice feature.

I can confirm this also happens with `@fieldname` notation: https://play.sqlc.dev/p/a7c029d7cc3ae678861021056b1f50cc85b2b85f431cbefeead9db529be7bfbc ```sql -- name: SetLastRendered :exec INSERT INTO last_rendereds (id, created_at, updated_at, job_id) VALUES (1, @created_at, @updated_at, @job_id) ON CONFLICT DO...

> **Describe the bug** In the HTTP world, 2xx response codes tend to be treated as success. It's stronger than that. The 2xx range is literally defined as "Successful" in...

> Would you be willing to pose a PR for this? Not sure if I have the time. It also depends on whether we settle on this code generator, or...

For me this used to be a vital source of information for visitors of the chat channels. Having to open the "room info" side-panel manually is just not a viable...

> > is this something we can reintroduce via a custom extension? > > Forks are always welcome That is not an answer to my question, though. I was asking...

> The Product team explicitly removed the topic from the header, I would not expect it to be coming back as that is quite unlikely, though I am not the...

Is there a public document that describes the motivation behind the removal of the info from the room header? So far I can only find very non-descriptive PRs, and a...

> At the end of the day, the Product team make decisions based on customer feedback There can't have been customer feedback that was a hard "remove the room topic...