Change it so the categories endpoint is consistent by removing slugify#276

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Conversation

Copy link

Contributor

ACR1209 commentedJun 1, 2025

Description

This change removes the use of theslugify function from the categories endpoint when fetching the json data, as this is inconsistent with the rest of the endpoints, which do not do this step.

Type of Change

✨ New snippet
🛠 Improvement to an existing snippet
🐞 Bug fix
📖 Documentation update
🔧 Other (please describe):

Checklist

I have tested my code and verified it works as expected.
My code follows the style and contribution guidelines of this project.
Comments are added where necessary for clarity.
Documentation has been updated (if applicable).
There are no new warnings or errors from my changes.

Related Issues

Closes#275

Additional Context

This was failing due to inconsistent rules regarding if the passed language is slugged or not. On snippets they're not slugged, thus simply removing this fixes the consistency problem.

Meaning, the current syntax to denote a sub-language (eg.javascript--react) was getting slugged like it was it's own language (eg.javascript-react).