-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.5.0 broke the slug
option
#135
v2.5.0 broke the slug
option
#135
Comments
Thx for reporting, I will fix this in a patch release ASAP. |
@emmercm would you mind testing temporarily with |
@webketje I agree with all of your thoughts there. I don't mind testing at all! But I'm going to be out of town this weekend and may not get a chance until later next week. |
@emmercm any news on this? |
I didn't realize npm was able to install from GitHub branches like that, that's awesome. Looks like
|
Ah sorry, I forgot there's a build step indeed (which is not versioned). Here's the built version: permalinks-bugfix-351.zip |
I'm pretty sure that branch did the trick @webketje , it looks to be using my slug function again. Thank you for the fast turnaround! |
Describe the bug
Permalinks is ignoring a custom function given via the
slug
option.To Reproduce
Given this config:
https://github.com/emmercm/www/blob/6d190e3ee94fa142de6b2377e66e5c8ba24bbdde/index.js#L436-L445
there is something going on with this code:
permalinks/src/index.js
Lines 169 to 171 in c7a1436
where the linksets end up using the default
slugify
function and not the provided one.Expected behaviour
The custom
slug
function is called.Screenshots
N/A
Environment
Should be OS and Node.js agnostic, but this appears on macOS and in Ubuntu CI, on Node.js 16.
Additional context
Nothing that I can think of.
The text was updated successfully, but these errors were encountered: