Next Release Updates

[georgedias]

Fixes to the (docs/features.md) - when viewing from the gh-pages.

• The dashboard optional flags table - the problem may be that the [top] link needs an empty space after the last table entry.
• Fix the dashboard entries alignment - all headers need a space after the [top] link
• Align the dashboards [top] link with the dashboard group name
• Remove bundle exec from help (emasser post artifacts upload help)
• add --name to the artifacts upload
• test the export artifacts endpoint
• Add POST /api/api-key to the features documentation
• user-uid is not require, need to make the variable in the .env optional. As of eMASS API specification v3.10 the use of accounts is not required to use the eMASS API
• Test the artifacts export - out states that the file is exported to the temp directory - not there

---

Add the NOTICE file see here for content

---

Update the post.rb class Register
line 57: result = EmassClient::RegistrationApi.new.register_user(Emasser::POST_API_KEY_RETURN_TYPE)

---

Add to the `constants.rb

  POST_API_KEY_RETURN_TYPE = {
    debug_return_type: 'Object'
  }.freeze

---

Add to the README

Development

After checking out the repo, run bundle install (after making sure you have a compatible version of bundle installed) to install dependencies. Then, run bundle exec rake test to run all tests or bundle exec rake rubocop to run the linter.

If there are any additional components created (i.e. folders that contain gems in them somewhere), make sure to specify the top level folder in components.rb.

To install this gem onto your local machine, run bundle exec rake install.