Open joshco opened 8 years ago
hmm. maybe this is a curie problem...
More info, looks like it is the curies, or more specifically the key names being seen as URNs, ie 'osdi:people'. When no curie definition is present, then the hal browser will suffer a js exception and fail to render the page. In my local branch, for now I'm try/catching that method call and writing a note to console if it can't normalize a rel.
I propose (beg?) that HAL browser be more liberal in what it accepts. Many people will use HAL browser as they are learning how to build a HAL API, and if it is too strict, they will never be able to figure out how to emit a valid document.
:+1:
https://github.com/mikekelly/hal-browser/commit/2fde261922a68ca922648f09d364323ac4f1e970#diff-e684a8343f8a30c1d37d8bc45f73423a intro'd it, and i think it was a regression
same as #62
Believe PR #81 will fix this.
i can confirm PR 81 fixed this
Getting Chrome error:
When retrieving my API entry point: