Commit graph

11 commits

Author SHA1 Message Date
Martin Pitt
080b20af94
Ensure application CSS has priority over library CSS
Import our application CSS as the very last thing, so that it can
properly override  PatternFly variables. Before, our application CSS
could land in the first third of dist/index.css *before* PatternFly's
definitions, so that the latter overrode the former [1].

This is a long-standing bug in mini-css-extract-plugin ([2] and
countless things that point to it) with `NODE_ENV=production` builds.

As a workaround, make sure that app.scss is the absolutely last imported
CSS, instead of "almost last". It is still conceptually correct for the
application CSS to be able to override patternfly-4-overrides.scss.

Closes #362
[1] https://github.com/martinpitt/performance-graphs/issues/10
[2] https://github.com/webpack-contrib/mini-css-extract-plugin/issues/188
2020-09-08 18:53:12 +02:00
Martin Pitt
2bb8e01d2d
Port to PatternFly 4.x
Closes #343
2020-07-21 10:33:48 +02:00
Katerina Koukiou
96514e279e
main: Stop importing patternfly.css
* Stop importing cockpit's base1/patternfly.css

This is deprecated API and will be dropped at some point, in favor
of projects shipping their own CSS.

Install and import the styles from PF4 now.

* Use webpack based string replacement for removing the font-face rules from PF4

Doing the seddery in Makefile breaks `npm run build`, webpack watching,
and is generally brittle.
Do the font replacement hacking with `string-replace-loader`, which fits into webpack much more nicely.

There is still some potential simplification by not duplicating the
entire scss loader chain.

Co-authored-by: Martin Pitt <martin@piware.de>

Closes #315
2020-05-28 10:01:31 +02:00
Martin Pitt
077eba3ede Update to current eslint
This has a new rule `quote-props`, adjust the code accordingly:

    29:24  error  Unnecessarily quoted property 'hostname' found  quote-props
    32:29  error  Unnecessarily quoted property 'hostname' found  quote-props
2019-07-17 17:43:01 +02:00
Bogdan Mustiata
2a2f99b6f0 React to hostname changes
Closes #94
2019-01-29 12:18:43 +01:00
Martin Pitt
9fa5c6ab05 Properly initialize state of Application
This will otherwise crash with React 16.
2018-08-29 00:40:16 +02:00
Martin Pitt
133badfa3d Enable a lot of eslint options and plugins
Taken rules from Cockpit, which have been proven to be effective for
finding bugs and keeping clean code, and sensible (not taking
unreasonable effort to satisfy).

Fix code layout in app.jsx accordingly.

Closes #39
2018-08-28 22:57:52 +02:00
Martin Pitt
3922333029 Use eslint for everything
eslint is much more powerful and flexible than jshint, and we don't want
to promote writing new projects with pre-ES6 code.

As a side effect, this also avoids downloading PhantomJS (see
https://github.com/jshint/jshint/issues/3318), thereby cutting down
node_modules/ from 470 MB to 210 MB.
2018-08-28 22:57:52 +02:00
Lars Karlitski
7260f5c01f Add scss example
Closes #26
2018-06-22 11:15:57 +02:00
Martin Pitt
7ce7b2b40b Add i18n support
Make the "Running on.." string translatable and copy the extraction and
conversion of JSX and PO files from Cockpit.
2018-06-19 14:40:45 +02:00
Martin Pitt
1edb6a070b Remove some instances of "starter kit"
Rename some files and change some identifiers to be neutral to the
application name. This makes it simpler to change everything to a proper
name when cloning this project.

Document in the README how to find the remaining places to change.

Closes #20
2018-05-04 19:19:29 +02:00
Renamed from src/starter-kit.jsx (Browse further)