Skip to content
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

refacto(api): change the uri to respect the adr #7

Closed
wants to merge 1 commit into from

Conversation

tleon
Copy link
Contributor

@tleon tleon commented Nov 29, 2023

Questions Answers
Branch? dev
Description? Fix the URI paths in order for them to respect the ADR
Type? refacto
Category? BO
BC breaks? no
Deprecations? no
How to test? CI 🟢 & UI tests 🟢
UI Tests
Fixed issue or discussion? Fixes #34493
Sponsor company PrestaShop SA

@tleon tleon self-assigned this Nov 29, 2023
Copy link
Contributor

@M0rgan01 M0rgan01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find it strange to have camelcase in an API, in general it is rather advisable to have kebab-case in a URL. For example, Google better indexes URLs containing kebab case

Consider using hyphens to separate words in your URLs, as it helps users and search engines identify concepts in the URL more easily. We recommend that you use hyphens (-) instead of underscores (_) in your URLs.

https://developers.google.com/search/docs/crawling-indexing/url-structure

@tleon
Copy link
Contributor Author

tleon commented Nov 29, 2023

https://github.com/PrestaShop/ADR/pull/35/files
The ADR describes it that way. Just following it

@M0rgan01
Copy link
Contributor

I know, but I just find it strange :)

@tleon tleon changed the title refactp(api): change the uri to respect the adr refacto(api): change the uri to respect the adr Nov 29, 2023
@tleon tleon closed this Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants