Start a new topic

Communicate limitation or implement JS reload on file change


When I change a python component, I can immediately test it in the xap builder.

When I change a JS component, I have to go back to the xap builder and refresh. Or I have to go back to the xap builder, save the xap in case I forgot about changes I made to the xap, then refresh. The only reason I know I need to refresh is because I know that the JS is a clientside thing, which may not be intuitive to some people that are learning the system. This also requires me to maintain a mental log of whether or not I've changed some input or wire, which is tiring. If I'm returning from editing component A's javascript, could we just reload it upon return to the xap builder?

Otherwise, we should communicate this difference somehow. Maybe flagging out-of-date components somehow?

Login to post a comment