-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding props to a component are not directly reflected #21
Comments
I encounter the same issue only in Windows 7. Actually, I'm not sure about the reason of the issue though. Here are the systems that I've tested:
I'd much appreciate it if you help me to understand the reason in your OS. Could you tell me what OS and NodeJS version you are using? |
Hi, sure, I using Windows 10 Enterprise (1909) with Node.js (13.6.0). Also I'm using Chrome (80.0) |
Would you mind to provide testing of this case?
The idea is to track if the watcher library can see changes in files. If there is no activity I'll try to investigate the reason. |
The watcher is on the server side, so you should see console log in the terminal window (command line) where you were typing |
@SoftHai, thanks. That means that |
Mhhh strange. Don't have a very exotic setup ;-) thanks for your support. |
Hi,
when having a component without props definition (initial) and then adding some, the Webcodesk UI don't shows automatically the added props in the preview screen or when using the component. A Reload of the Webcodesk application, in the browser, is needed to see the changes.
The text was updated successfully, but these errors were encountered: