-
Notifications
You must be signed in to change notification settings - Fork 800
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
Feature/react webapp #210
Feature/react webapp #210
Conversation
Codecov Report
@@ Coverage Diff @@
## react-web #210 +/- ##
=============================================
+ Coverage 37.3% 37.45% +0.15%
=============================================
Files 115 136 +21
Lines 22106 22347 +241
Branches 0 37 +37
=============================================
+ Hits 8246 8370 +124
- Misses 13129 13233 +104
- Partials 731 744 +13
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello! Thank you for this large PR!
I've left comments on the main things that I've noticed that need changes.
Even after that, there are some things I'll need to clarify with Thrasher regarding the front end before we can look to merge it
👍
3e5fa04
to
feb1c0e
Compare
See the Readme file in the web folder. For electron dev you should do npm start before. For the other on npm run build as documented in Readme. |
Alright with the npm start for dev. The first screen was with npm run build -> npm run electron still has the pathing issues |
Let me check that tonight after work. Will have some time then. |
7838d3f
to
92b730d
Compare
I have asked for help on that pathing issue in following places. facebook/create-react-app#1718 On the other hand we can continue development also on the browser, so do we need to wait for the electron fix? Copy of the explanation I gave on other github issue
static resources like images do not work.
Neither fetching data using relative paths is working. e.g.
It will try to access them using an absolute path starting with So instead of trying to access at: Same for the image: Any ideas on how to resolve that? |
…side using relative paths See https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#proxying-api-requests-in-development for more details on how it works
92b730d
to
492bafd
Compare
No description provided.