You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of the examples and tutorials have a variable to enable or disable interactivity. Interactivity should be disabled for docs building and testing. However, most of the users will clone the repo and try to run the examples without knowing about the interactivity variable, resulting in nothing being displayed.
My suggestion is to have an environment variable that if defined, will run these demos/tutorials/examples without interactivity. This could be defined inside the docs building process.
I think this would easy the access of new users to fury as the demos will just run in their machines, without any extra changes.
The text was updated successfully, but these errors were encountered:
Most of the examples and tutorials have a variable to enable or disable interactivity. Interactivity should be disabled for docs building and testing. However, most of the users will clone the repo and try to run the examples without knowing about the interactivity variable, resulting in nothing being displayed.
My suggestion is to have an environment variable that if defined, will run these demos/tutorials/examples without interactivity. This could be defined inside the docs building process.
I think this would easy the access of new users to fury as the demos will just run in their machines, without any extra changes.
The text was updated successfully, but these errors were encountered: