Add slugify function to std

[marvinhagemeister]

Is your feature request related to a problem? Please describe.

A common part of building web apps includes generating pretty URLs based of a random string like a page title.

• Hello World -> hello-world
• déjà vu -> deja-vu
• Foo & Bar -> foo-and-bar
• ...etc

Describe the solution you'd like

Describe alternatives you've considered

[kt3k]

reference: https://www.npmjs.com/package/slugify

[kt3k]

Sounds like a good addition to std/text

[timreichen]

I can take that one. Looking over the implementation of https://www.npmjs.com/package/slugify, there are many options I think would probably not be necessary:

{
  replacement: '-',  // replace spaces with replacement character, defaults to `-`
  remove: undefined, // remove characters that match regex, defaults to `undefined`
  lower: false,      // convert to lower case, defaults to `false`
  strict: false,     // strip special characters except replacement, defaults to `false`
  locale: 'vi',      // language code of the locale to use
  trim: true         // trim leading and trailing replacement chars, defaults to `true`
}

• I think strict, remove, lower, trim should be done by default or that should be done manually.
• replacement seems like it should be separator. Does this vary with slugification -? Else instead of slugify() we could have a "remove special chars" function in combination with @std/to*Case() functions.

WDYT?

[kt3k]

I'm in favor of reducing number of options in first pass.

I think strict, remove, lower, trim should be done by default

Do you mean we would implement it like all these options are true, or these set to the same as npm:slugify?

replacement seems like it should be separator. Does this vary with slugification -

I don't think we need to make separator optional in first pass.

[kt3k]

I'd also suggest we would use str.normalize("NFD").replace(/\p{Diacritic}/gu, "") for removing diacritic characters instead of mapping with manually maintained list.

[timreichen]

I think strict, remove, lower, trim should be done by default

Do you mean we would implement it like all these options are true, or these set to the same as npm:slugify?

I am not too familiar with slugify(), I thought it should always be trimmed and lowercased. If so I propose to do it without an option. If not, it should be done like slugify("....").trim().toLowerCase(). Same with remove and strict.

[timreichen]

There seems to be differences between online slugification for example for ©: https://slugify.online returns ©, https://commentpicker.com/slugify.php returns c, npm:slugify returns (c). @ on the other hand is removed by all except npm:slugify which returns unmodified @.

[kt3k]

closed by #5646