[PAGES-234] Template definitions endpoint should be lower/kebab-case Created: 31/Jan/20  Updated: 03/Jun/20  Resolved: 24/Apr/20

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.1

Type: Improvement Priority: Neutral
Reporter: Mikaël Geljić Assignee: Sang Ngo Huu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1.5d
Original Estimate: Not Specified

Issue Links:
causality
is causing PAGES-298 DOC: Template definitions endpoint ar... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: SPA Editor
Sprint: 6.2.1 Ramp-up 22
Story Points: 1

 Description   

Since template definitions endpoint is consumed by frontend developers, camelCase may not be the most intuitive there; lower or kebab-case is commonly preferred in the path segment of REST URIs.



 Comments   
Comment by Christopher Zimmermann [ 23/Apr/20 ]

Reopening because I think its important to provide backwards compatibility here.
This sounds contradictory to my position that we can break things in the 1.0.1 release of the frontend-helpers js libraries.
My rationale is that A) This is a change to magnolia itself, not the frontend libraries. B) We release 1.0.1 of js libs right away, while this change/fix will land only at another time (probably in May). So anyone starting with the JS libs will then hit another problem whenever they update Magnolia version.

Comment by Sang Ngo Huu [ 23/Apr/20 ]

I fixed, I just think 6.2.1 will be release soon, seem it is the same time with 1.0.1. So It does not affect to much

Generated at Mon Feb 12 06:16:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.