Getting closer on Storybook and Superforms #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've gotten quite far with these modifications. First, a patch of the current
enhancemock in the@storybook/sveltekitpackage was required, sopnpmis required to make it work for now.With that, it was possible to mock the enhance function rather well, probably good enough for you to intercept the POST request, as Alex mentioned. But there's still one problem, I wasn't able to mock the
navigatingstore, which is used in a few places when a response is returned.According to the documentation it should be possible to mock, but it didn't work for me. Maybe you can figure it out, or if it doesn't work, there has to be some special option or detection for Superforms when using it with Storybook. Let me know what you think!