The solution proposed on SO looks sensible to me. I think the optional trailing slash is a bad idea because you won’t have a unique identifier for representation any longer.
Regards, Xavier Ordoquy, Linovia; > Le 13 avr. 2018 à 11:39, German Prostakov <gprostm...@gmail.com> a écrit : > > Is it possible to do without such workaround suggested on SO: > https://stackoverflow.com/questions/46163838/how-can-i-make-a-trailing-slash-optional-on-a-django-rest-framework-simplerouter? > Is it planned to allow optional trailing space in Routers? I think I'm not > the only one who thinks this is a lack of convenience, especially if you > switch your backend to Django and you had optional trailing slashes in routes > in previous backend framework (Express.js) > > -- > You received this message because you are subscribed to the Google Groups > "Django REST framework" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-rest-framework+unsubscr...@googlegroups.com > <mailto:django-rest-framework+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Django REST framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-rest-framework+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
