Closed (fixed)
Project:
Swiper formatter
Version:
2.1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Feb 2026 at 09:28 UTC
Updated:
6 Mar 2026 at 01:00 UTC
Jump to comment: Most recent
Comments
Comment #3
anybodyHere we go!
Comment #4
bbu23Thanks @anybody, that was fast!
With this occasion, can we pls remove the static routes from the routing file, update the Entity to use the
AdminHtmlRouteProviderroute_providerand maybe add just some simple test that the entity paths are accessible by the expected user and non-accessible otherwise (or whatever relevant test for this bug)?Comment #5
anybodySorry @bbu23 - someone can do that of course, but I won't have the time in the next weeks, sorry. Too many maintained projects myself ;)
Comment #6
bbu23@anybody no problemo, I'm happy to work on it as soon as I get the chance.
Comment #7
bbu23Comment #8
bbu23While writing the tests I discovered that even a small change like this one could come with a flaw. The path for add form in the annotation was still different than the one defined in the route.
Proposed annotation path:
/admin/config/content/swiper-formatter/addVS.
Route definition:
/admin/config/content/swiper_formatter/addEven so, the original route, the one with underscore, seems to be inconsistent with the others, so this ticket will ensure that all paths have the same pattern.
Comment #11
bbu23Will be available in 2.1.0
Thank you for your contribution!