Closed jmartin-sul closed 5 years ago
@mjgiarlo, good catch, thank you! yeah, cheat sheet docs w/ curl commands also use Accept
. i think this was me just confusing Accept
and Accept-Encoding
.
um, yeah, not sure why that's working, but will fix to use Accept
instead.
@mjgiarlo, good catch, thank you! yeah, cheat sheet docs w/ curl commands also use
Accept
. i think this was me just confusingAccept
andAccept-Encoding
.
OK!
um, yeah, not sure why that's working, but will fix to use
Accept
instead.
:alien: :alien:
ok @mjgiarlo, ready for review again, touched up the changes to use Accept
instead of Accept-Encoding
, added a couple examples, bumped the version.
(also the force-push diff link is one of my favorite new github features of the last few months, so handy)
@jgreben, i just published ~3.0.0-beta2~ 3.0.0-beta3 of the client to npm, could you see if the updated version of getResourceWithHttpInfo
works for you? you'd want to invoke it like this:
instance.getResourceWithHttpInfo(groupId, slug, { accept: 'application/json' })
thanks!
@jmartin-sul :speech_balloon:
you'd want to invoke it like this:
instance.getResourceWithHttpInfo(groupId, slug, { acceptEncoding: 'application/json' })
acceptEncoding
or accept
?
@mjgiarlo: g)#@^^*t, yup, oversight, will fix 🙂
@mjgiarlo, ready for review once again
@jgreben, slight update to my earlier comment, correcting the param to be accept
instead of acceptEncoding
. e.g.:
instance.getResourceWithHttpInfo(groupId, slug, { accept: 'application/json' })
@jgreben, also, i just published 3.0.0-beta3
to npm
Did not merge bc @jgreben's review was requested.
LGTM, @jmartin-sul I can merge if you want me to.
@jermnelson, that'd be great, if you wouldn't mind. sounds like @jgreben is using the updated method successfully in the editor, which was primarily what i wanted his review for.
thanks!
@jermnelson @jmartin-sul got it!
this allows the caller to ask for either RDF (
application/ld+json
) or non-RDF (application/json
).see tests for usage example.
closes #76