leehwmj-junta opened a new issue #4650: Have to repeat build and install each 
time when I modify and test jsx in superset/assets/javascript
URL: https://github.com/apache/incubator-superset/issues/4650
 
 
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [o ] I have checked the superset logs for python stacktraces and included 
it here as text if any
   - [ x] I have reproduced the issue with at least the latest released version 
of superset
   - [ o] I have checked the issue tracker for the same issue and I haven't 
found one similar
   
   
   ### Superset version
   0.22.0
   
   ### Expected results
   
   
   ### Actual results
   
   
   ### Steps to reproduce
   
   The 0.22.0 version of superset is currently in development.
   
   I am looking for a handy way to change the code in the jsx file and see how 
it actually works and works.
   
   For example, line 59 of $ SUPERSET_HOME / superset / assets / javascript / 
addSlice / AddSliceContainer.jsx file looks like this:
   
   <p> {t ('Choose a datasource')} </ p>
   
   I want to change this as follows.
   <p> {t ('Choose a DATABASE')} </ p>
   
    And when I save and refresh it, the changes do not take effect. Restarting 
superset runserver does not work either.
    In order to apply this, I did the following.
   1. Go to the $ SUPERSET_HOME / superset / assets folder
   2. Run the yarn run build again
   3. Go to $ SUPERSET_HOME folder
   4. Run python setup.py install again
   5. Run the superset runserver again
   
   I was able to verify that my jsx changes were applied after I did the above.
   But I think this process is too inefficient and time consuming. And I 
believe there will be a good way to check my changes without repeating the 
above process.
   But I have no idea about it.
   
   I am concerned that it may be related to configuration files such as webpack 
or package.json, but I do not know for sure.
   
   
   So I ask for help here.
   
   
   Thank you
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to