Jaro

Oh, thanks, but doesn't this fundamentally undermine the epilogue philosophy of having granular control over request lifecycle? All customised behaviour will then be defined in `.before` hooks which does not...

@mbroadst Thank you for reaching back, I have created a PR with the testcase: https://github.com/dchester/epilogue/pull/156 the thing is fairly simple, the following fails on duplicate mail attribute entry, meaning, that...

@mbroadst thanks, this still however logically does not make sense. Shouldn't the actual data insertion happen in the `action` of that milestone? I would still like to use `before` and...

@mbroadst see https://github.com/dchester/epilogue/issues/155#issuecomment-209887778 A possible way would be to give the developer an option to override, or to skip the default hook: `resource.action.milestone.overrideAction(…)` or `resource.action.milestone(fn, override)` or maybe directly in...

@mbroadst I kind of like your proposal, a smart and efficient way of working this out, but as you are saying, the potential effects on existing solutions using epilogue could...

But even that way, if you call `context.skip()` in the `resource.create.write`, the `.after` hook is still skipped afaik

@mbroadst In express you build the stack yourself. Here in Epilogue you have the default stack pre-built. My idea is to intercept any of the hooks and overload them, not...

I like it, I however in no way want to force you to change the fundamentals of Epilogue, "just because some script kiddie has a different use case". Maybe i...

I completely understand, and you are doing good job! :) Anyway I did toy with the modification and it's fairly easy (see work-in-progress commit: https://github.com/dchester/epilogue/compare/master...carera:milestone_overloading) The problem with this I...

+1 I was actually looking for this even in the React-native "native" Slider component, but no success. Also I tried to transform the component using style `transform: [{rotate: '90deg'}]` but...