mrc-4011 Add step prop to number input

[EmmaLRussell]

We need to provide custom step values for MINT as an increment of 1 is not appropriate for all parameter values. This adds optional step prop to number inputs.

Test by viewing example/index.html and note that under 'Advanced Options', the 'Decimal parameter' value increments by 0.1 using the spinner arrows.

Some additional housekeeping that was required:

• retire the old travis build and add a github action. Update build status badge on readme (will be updated to master branch on merge).
• explicitly assert non-nulls in tests
• do not use default coverageProvider - fix for error as described here

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@0c537c7). Click here to learn what that means.
Patch has no changes to coverable lines.

❗ Current head eeea85d differs from pull request most recent head 22b0f59. Consider uploading reports for the commit 22b0f59 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             master       #45   +/-   ##
==========================================
  Coverage          ?   100.00%           
==========================================
  Files             ?         2           
  Lines             ?        49           
  Branches          ?        34           
==========================================
  Hits              ?        49           
  Misses            ?         0           
  Partials          ?         0           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[M-Kusumgar]

Hey emma, nice job, the stepper works as expected. However, while i don't think this is a super important point, it is good to keep in mind: the read only form will only display values with precision of 0.001. So for example if you set the step to 0.0005, it will not accurately display the value. Perhaps that is a note to include in the documentation or something like that. For our purposes however, i don't see that being particularly important!

[LekanAnni]

LGTM

Just some suggestions

[LekanAnni]

 on: push:
    branches:
      - 'main'
  pull_request:
    branches:
      - 'main'

[EmmaLRussell]

Good call, don't need it on every push. But I don't want to limit the PR branches to 'main' as we do sometimes have PRs into non-main branches, so I won't specify branch for `pull-request'

[LekanAnni]

Suggested change

	- run: npm install
	- run: npm ci

[EmmaLRussell]

Hey emma, nice job, the stepper works as expected. However, while i don't think this is a super important point, it is good to keep in mind: the read only form will only display values with precision of 0.001. So for example if you set the step to 0.0005, it will not accurately display the value. Perhaps that is a note to include in the documentation or something like that. For our purposes however, i don't see that being particularly important!

Good point, will add to docs

[LekanAnni]

I understand we may need to trigger a job when pull request is opened against other branches. However, you have not specified any target and I do not think you can have an empty pull_request: without a target.

[LekanAnni]

Suggested change

	pull_request:
	pull_request:
	branches:
	types: [opened, reopened, edited]

[LekanAnni]

Maybe you can, just a bit confusing.

[EmmaLRussell]

I've put in a ~ which should hopefully make it a bit more obvious that it's an empty 'any' target

[LekanAnni]

Maybe you can, just a bit confusing.