Jonathan MASSUCHETTI

> The example above works fine for me Yes, but it doesn't use a decorator. > If we can use useArgs inside the decorator, probably it is possible to parametrize...

@ai212983 can you provide a repro inside a stackblitz for example ? or a git repo

@ai212983 yes it does work in this case, because the args update do not trigger the decorator function to run again.

@ai212983 Indeed. I've also tried to create an addon to have a custom hook. It's harder than it looks like !

@helloint well really it's a limitation of Storybook addons in React. It's not specific to this addon. I've started to work on something to workaround it but it's a mess....

What was your previous version of `@remix-run/react` ? That will help me find the issue

@steuraa @alejoFernandezSS AFAICT, `@remix-run/react` still uses `react-router-dom@v6` (see [dependencies](https://github.com/remix-run/remix/blob/d61e6852b52fcf381874455613e0c9fe8f4c0626/packages/remix-react/package.json#L25)). @steuraa since you're still using the v3 of the addon, which imports components from `react-router-dom@v6`, it should work. Without knowing your...

Hi @yannbf it looks like I've read the documentation a bit too fast. The [section](https://storybook.js.org/docs/writing-tests/stories-in-unit-tests#override-story-properties) about overriding story properties actually gives an example about overriding global properties. Maybe that should...

It's just for convenience. Interacting with the same interface is better than juggling between the spec array and the result object. I noticed something else: `exists` checks for the value...

A flag could work. The wording here is really not ideal. Throwing for `contentAt` is fine because you don't have to deal with a type guard with TypeScript, but `exists`...