jaredgeddy
Cloud Apps
Joined 3 years ago
User Profile
User Widgets
Contributions
Local development environments as a better workflow
This probably breaks community guidelines but I thought it was worth bringing to the attention of my fellow Sisense software engineers that I've raised the idea of a local development environment in the product feedback forum. My hope is to garner enough attention/kudos to pursuade Sisense to pursue this idea in hopes of making all our lives easier. While I understand if you're working in a custom developed UI you don't have to endure the pain, and ensuing frustration, of being forced to interrupt your development workflow to upload your add-on to a live environment just to be able to see/test your work, but I'd ask for your support none the less. Here's the link to the forum post, thank you for your support and consideration in an attempt to make Sisense better. https://community.sisense.com/t5/product-feedback-forum/local-development-environment/idi-p/23483535Views2likes0CommentsLocal Development Environment
Idea: Allow developers to build/test add-ons in a local environment rather than requiring a live environment. Note that this would be for the purpose of creating custom add-ons for additional functionality that would require testing on the "out of the box" Sisense UI. Background/Context: In most development workflows it is common practice to work on your code locally on your machine and deploy to a local server aka "localhost" to test/view your work in the browser. An example of this is building and deploying a local React.js app to your browser. As you make changes to the code it will recompile locally and update what you see on your localhost. If you're using Sisense out of the box however, to test/view any changes to an add-on developers are forced to upload the files in some way to a live Sisense Environment. This not only limits the innovation of add-ons to developers with an active license and live environment, it makes it painfully inefficient to develop customizations on top of the Sisense application. I understand there are likely some business concerns with allowing the use of the product locally but I'd argue that there are ways to prevent that, such as enforcing some default sample data etc., but in such a way that would give developers a "local playground" to develop/innovate on.