Additional support for custom options.slugger

[agrohs]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)
• If applicable, I’ve added docs and tests

Description of changes

This adds new support for an additonal option containing a custom slugger implementation. By default it still uses the "built in" (opinionated) github-slugger but also supports your own customer slugger:

This could be another popular third party package such as slugify and/or your own custom implementation.

Ex usage (custom slugger):

  rehype()
    .data('settings', {fragment: true})
    .use(rehypeSlug, {
      slugger: {
        slug: (_value) =>
          `test--${_value.replace(/\W/g, '').toLowerCase()}--test`
      }
    })

Ex usage (making uses of slugify):

  rehype()
    .data('settings', {fragment: true})
    .use(rehypeSlug, {
      prefix: 'prefix--',
      slugger: {
        slug: slugify,
        // Can be used with custom options such as:
        // slug: (_value) => slugify(_value, {lower: true, strict: true, replacement: '__'})
      }
    })

Related to #16
Closes #17

[codecov-commenter]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (1c61632) 100.00% compared to head (a5e93e5) 100.00%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #18   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           37        65   +28     
=========================================
+ Hits            37        65   +28     

Impacted Files	Coverage Δ
index.js	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[wooorm]

Eh, I’ll close this. Again: thanks but no thanks.
You asked if a PR would be accepted, I said no, and then you made a PR. So… that’s not going to be accepted.

[agrohs]

FIgured the code would likely be helpeful for others even though your earlier comment appears dismissive and against the intent of most open source projects (and your own code of conduct)

[agrohs]

@RichardLitt and/or Olivia Hugger I'd love to chat any time offline on the interaction in the community here.

[RichardLitt]

Sure, @agrohs. My email is not hard to find (see my profile). Apologies for not understanding your LinkedIn connection until now - feel free to drop me a line.

[agrohs]

Will do, thanks @RichardLitt - I'll shoot you an email direct!

[RichardLitt]

No rush! I am offline for a bit, if it takes a minute for me to respond.

…

On Saturday, March 11, 2023, Adam Grohs ***@***.***> wrote: Will do, thanks @RichardLitt <https://github.com/RichardLitt> - I'll shoot you an email direct! — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG6LIIDCE2BWNN434LZCATW3TYSTANCNFSM6AAAAAAVXSCASA> . You are receiving this because you were mentioned.Message ID: ***@***.***>