Alex LaFroscia

Related issue: https://github.com/workmanw/ember-qunit-assert-helpers/issues/18

On second though, maybe it should just be an `Ember.warn` rather than an `Ember.assert`. In reality, it's not _that_ bad if `initialStep` or `linear` change, it should just be made...

Once this is resolved, it makes most sense to approach argument validation that way: https://github.com/ember-decorators/argument/issues/65

Interesting idea! At the moment, [step names can be numbers](https://github.com/alexlafroscia/ember-steps/blob/f92d648fc0fbd3210573bb91a48c63f3b2f27445/addon/-private/types.ts#L1), so I am concerned that that and this feature request would conflict with each other... Any ideas on how this...

Hey @AriPerkkio -- sorry about that! It seems I had checked in the "fix" that I found by mistake (which is documented at the end of the repo's README), which...

As far as I know I haven't used a launch config to debug tests; the [Vitest plugin for VSCode](https://github.com/vitest-dev/vscode) is excellent, and I use that a bunch. I also use...

I have tried playing with an `EventsFor` type (again, borrowed from #24) that extracts the supported events, in the hopes that that would help illuminate what's going on ```ts export...

Thanks to some help from a co-worker, I was able to get to a version of `TypedEventEmitter` that works with my helper function! Basically, the issue ended up being that...

I'm going to close this issue, since my problem is resolved; I don't know if that's a change you'd want to make to this library, but hopefully this helps resolve...

I see now that there's already #88 open, which never landed. Even if this doesn't land, that's fine with me -- we may just publish the modernized version in that...