Kai Sassnowski

Again, relying on a resource identifier being hard to guess is not a valid security strategy. If wizards should be restricted to certain users, this should actually be _enforced_ by...

Sooo... basically reimplementing Nova, I guess 😅

Thanks for the PR! A couple of thoughts on this. Your example suggests that you'd mainly use the currentStepIndex to determine the previous and next step of the wizard. This...

I don't think static `next` and `previous` links like you suggested would work. They're relative links, meaning they always need to know what the currently active step is. That information...

Thanks for the PR, I didn't even realize that this wasn't currently possible. That being said, this implementation has a couple of issues: 1. It forces you to specify the...

Hey there, I haven't used that package so far. Can you tell me what exactly makes it incompatible with this one?

There is already a [release candidate available](https://github.com/ksassnowski/venture/releases/tag/4.0.0-RC4) that should be stable. I don't expect the actual code to change much until the release so this should be safe to use....

Ah, you're right. It should probably be `protected`

Sounds good. You could maybe also double check if the same is true for the `DefaultWorkflowJobState`

It's fine :+1: