It’s 2026, not 1976. We have unicode and can distinguish a minus sign from any of a panoply of dashes and hyphens. All programming languages should support kebab-case naming.
![import { displayAs } from "../tooling/displayAs";
import { C, B, A } from "../tooling/placeholders";
import { proper } from "../tooling/proper";
// [C] [B] [A] long-billed-lark == [C] [[B] B] A
export const longBilledLark = proper([ [C], [B], [A] ], [ [C], [[B], B], A ]);
displayAs({ 'long-billed-lark': longBilledLark });](https://files.functional.cafe/media_attachments/files/117/552/821/430/787/916/original/319352c18e9b711d.png)
1 Boost
0 Likes
@shanecelis Supporting en-kebab-case requires supporting—and requiring—thin spaces on either side of each en-dash.
@shanecelis It was a joke based on a very common typesetting guidance that when using en dashes to indicate a range, there should be a thin space on either side of an en dash.
e.g. “40 - 50” in “40 - 50 feral hogs” would use thin spaces and an en dash.
@shanecelis It was a joke based on a very common typesetting guidance that when using en dashes to indicate a range, there should be a thin space on either side of an en dash.
e.g. “40 - 50 feral hogs” would use thin spaces and an en dash.
@raganwald
en–kebab–case
em—kebab—case