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

How can I change the visualization? Changes are not displayed in the browser. #3675

Closed
oxystin opened this issue Oct 15, 2017 · 5 comments
Closed

Comments

@oxystin
Copy link

oxystin commented Oct 15, 2017

Developers please help. I have been suffering for two days. I need to change the visualization of some graphs. Superset installed via Docker. I am modifying the container for the files nvd3_vis.js and chord.jsx. But my changes are not displayed in the browser. There is a feeling that the * .js (x) files are cached. I reset the cache in browsers, restarted the container and even deleted the file nvd3_viz.js. This did not help me. Everything works without changes. Tell me what you need to do to see the changes, after editing the files in the folder ... / superset / assets / visualizations /?

And tell me the development environment, in which it will be convenient to debug the project?

@oxystin oxystin changed the title Как изменить визуализацию? Изменения не отображаются в браузере. How can I change the visualization? Changes are not displayed in the browser. Oct 15, 2017
@xrmx
Copy link
Contributor

xrmx commented Oct 15, 2017

We're in 2017 where the frontend is built. You have to modify the source and then rebuild the whole thing. Next time looking at the documentation may save you two days of suffering https://superset.incubator.apache.org/installation.html#making-your-own-build

@oxystin
Copy link
Author

oxystin commented Oct 15, 2017

@xrmx Hello. Thanks for the reply. The documentation I have read. Unfortunately I'm not advanced user to understand. I need to change only the angle of the label graphics. This can be done by removing a couple of lines in the source. I thought it can be done quickly. It turned out that it is more difficult. I'll try to understand.

@oxystin
Copy link
Author

oxystin commented Oct 15, 2017

@xrmx thank you for the tip! It worked for me!
Tell me, this procedure must be run after each edit of the sources?
It is long enough. How then to debug your code?

@mistercrunch
Copy link
Member

npm run dev will watch the files for modifications and re-compile as you edit

@brentEich
Copy link

@mistercrunch I'm attempting to edit files such as static/assets/src/actions.js, just simple edits such as success alerts. I've rebuilt and cleared my cache, but the changes still don't register in the browser. You mentioned npm run dev is this a prerequisite to seeing the changes or does this just make it quicker to view the changes?

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

4 participants