<@U0B8FU678> re pipeline issues, can you elaborate...
# ktoro
orangy
11/07/2018, 4:42 PM
@mp re pipeline issues, can you elaborate in this separate thread, please?
m
mp
11/07/2018, 4:43 PMSure. Basically, the mapping of features to phases is problematic when writing new features because more than once I've needed existing features to be in a different order from how they currently are so that I can access data generated by those features. The static, predefined "this is the order features/phases are applied" order is simple, which is nice, but also completely prevents certain types of reuse
mp
11/07/2018, 4:44 PMIt's nice that things Just Work out of the box, but it would be great if there was more flexibility for app authors to decide how features get mapped to phases.
mp
11/07/2018, 4:44 PMit doesn't have to be as completely free for all as servlet filters, where it's up to the web.xml author to decide the order, but having nonzero flexibility would be very helpful.
v
vonox7
11/07/2018, 4:59 PM“Pipelines” are also one of my “disliked” sides of Ktor. But thats probably because of missing graphical documentation of that feature. When creating a pipeline-interceptor I don’t feel 100% save and often just need to test until “it works”. Even after reading https://ktor.io/advanced/pipeline.html. If there was a good graphical documentation with various flow charts I think it would be all clear. @Deactivated User @orangy
g
gaetan
11/07/2018, 6:47 PM