-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need access to original statement from HTTP response #144
Comments
I think I just saw the answer to this in another issue. I should be using the |
I don't know of one, but having said that you shouldn't need it to accomplish your goal. You can access the individual objects themselves, or as you've found use the serialized versions via the |
@brianjmiller Thanks for the response. The use case I'm trying to address is to export xAPI statements either to another LRS, or provide the signed statement standalone. I could use the TinCanJS module to connect to and save in a different LRS, but if I wanted to save the signed statement standalone in some other long term storage strategy, would the raw multi-part response work in your opinion? Here is an example:
|
I am creating/consuming signed statements. I would like to be able to get at the original string of the statement in a multi-part response. In LRS.js line 237, you could pass parameters to indicate you would like to keep the original statement object (minus the
content
attribute in the attachment). Or you could assign theoriginalJSON
toJSON.parse(parsedResponse[0].body)
after you created the statement. Either way, is there a reason not to set the original string of the statement from the response? I'm wanting it so I can verify/validate the JWS in the attachment, and then provide that to another LRS (exporting it so to speak). Thoughts on this export process that would be better?The text was updated successfully, but these errors were encountered: