Closed andrew-w-ross closed 2 years ago
Sweet, I never even considered the possibility that the schema might coexist in the same place as the UI and documents, but I can see good reasons for that being the case in some instances. Good idea and good solution!
@danielwaltz I'm actually experimenting using vite
as my until build chain for both server and client side code. There is a project called vite-node
that vitest
uses.
:tada: This issue has been resolved in version 2.1.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Description
Watch mode only seems to look for changes in the document. I've created this repo to recreate the issue. Make sure you're in the watch-issue branch and run dev. Changes to a document, App.tsx for example work fine. But changes to the schema don't.
Looking at the plugin code it seems like this function just needs to be updated to take schema into account. I opened up a pr #8 to fix this if you like.