consul/ui-v2/tests
John Cowen b29546e578 Looking into atob functionality, consequence of Value: null
The Consul API can pass through `Value: null` which does not get cast to
a string by ember-data. This snowballs into problems with `atob` which
then tried to decode `null`.

There are 2 problems here.

1. `Value` should never be `null`
  - I've added a removeNull function to shallowly loop though props and
  remove properties that are `null`, for the moment this is only on
  single KV JSON responses - therefore `Value` will never be `null`
  which is the root of the problem

2. `atob` doesn't quite follow the `window.atob` API in that the
`window.atob` API casts everything down to a string first, therefore it
will try to decode `null` > `'null'` > `crazy unicode thing`.
  - I've commented in a fix for this, but whilst this shouldn't be
  causing anymore problems in our UI (now that `Value` is never `null`),
  I'll uncomment it in another future release. Tests are already written
  for it which more closely follow `window.atob` but skipped for now
  (next commit)
2018-07-05 13:35:06 +01:00
..
acceptance Merge pull request #4331 from hashicorp/feature/hedge-empty-node-ids 2018-07-03 16:11:31 +01:00
helpers Looking into atob functionality, consequence of Value: null 2018-07-05 13:35:06 +01:00
integration WIP: First draft intentions 2018-06-25 12:25:14 -07:00
lib/page-object Comment up custom visitable and add a couple of comments to be clearer 2018-06-12 11:24:36 +01:00
pages Use html5 oninput instead of onkeyup for native textual inputs 2018-07-03 15:40:15 +01:00
unit Looking into atob functionality, consequence of Value: null 2018-07-05 13:35:06 +01:00
index.html Find a way to test pre-ember load 2018-06-15 13:56:45 +01:00
pages.js Merge remote-tracking branch 'connect/f-connect' 2018-06-25 19:42:51 +00:00
steps.js Use html5 oninput instead of onkeyup for native textual inputs 2018-07-03 15:40:15 +01:00
test-helper.js UI V2 (#4086) 2018-05-10 19:52:53 +01:00