Skip to content
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

[Flow] Does not work after component Refresh #24

Closed
KangGS opened this issue Jan 7, 2019 · 7 comments
Closed

[Flow] Does not work after component Refresh #24

KangGS opened this issue Jan 7, 2019 · 7 comments

Comments

@KangGS
Copy link

KangGS commented Jan 7, 2019

Does not work after component Refresh.
After you update a component, it will not work until you create a new component or restart the program.

help me ..

@petersirka
Copy link
Collaborator

Hi, you need to upload component again, or restart app or just enable https://wiki.totaljs.com/flow/02-configuration/#property-debug-

@KangGS
Copy link
Author

KangGS commented Jan 8, 2019

my "config" file ->
package#flow (Object) : { url: '/flow', debug:true}

same...
Did I misuse the "debug"?

@petersirka
Copy link
Collaborator

It works, I have tested it now. You need to change a file in /flow/ directory. Then you can is in the right bottom corner a notification like this:

update-component

@vasekd
Copy link

vasekd commented Jan 8, 2019

It seems that the component is reloaded, but not registered properly.
Use case:

  1. Add debug component to the flow => You will see the status Enabled in the workspace
  2. Reload the component on the disk => the yellow notification is shown. Same as on the video
  3. The status message 'Enabled' disappear and the component is not working.

@petersirka
Copy link
Collaborator

petersirka commented Jan 8, 2019

@vasekd there was a bug 👎. I have fixed it 👍... Just download flow.package. BTW: Thank you!

@vasekd
Copy link

vasekd commented Jan 8, 2019

Thanks you very much. It works very well.

@KangGS
Copy link
Author

KangGS commented Jan 8, 2019

Thanks you very much!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants