Display event log ID and description if present

If the Event ID and Description event log properties
are present, display the error log title as <ID>: <Desc>
and move the Message property down into the box with the
other additional data fields.

If they aren't present, or not filled in (which in the case of
the event ID is a value of 'None'), leave the title as it
currently is, which is the Message property.

Tested: Verify UI fields when the event ID is valid, when
it's still in the event data but not valid, and when it isn't
in the event data at all.

Resolves openbmc/openbmc#3056

Change-Id: I455fc257b7d3713aceee2975d5240fb226cfa87e
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
5 files changed
tree: 10b01c5c19db53241fadfc22854c28c9bbea0ab9
  1. app/
  2. gulp_tasks/
  3. .babelrc
  4. .clang-format
  5. .gitignore
  6. bower.json
  7. format-code.sh
  8. gulp-options.js
  9. gulpfile.js
  10. karma.conf.js
  11. LICENSE
  12. MAINTAINERS
  13. package.json
  14. postcss.config.js
  15. README.md
  16. sonar-project.properties
  17. webpack.config.js
README.md

openbmc

UX Design repo for OpenBMC

OpenBMC

TODO: Write a project description

Requirement

nodejs npm

Installation

npm install

Running

npm run-script server

This will run it locally in http://localhost:8080.

Example Usage with OpenBMC

  1. Browse to https://<bmc-ip> and bypass the secure warning. You will see a JSON response with Login required message.
  2. In the same session, navigate to http://localhost:8080. Enter the BMC IP, Username and Password (defaults: root/0penBmc).

Now you are logged in.