Project

Profile

Help

Bug #4604

SaxonJS.transform() API - documentation and usability issues

Added by Michael Kay 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Low
Assignee:
Category:
API
Sprint/Milestone:
-
Start date:
2020-06-18
Due date:
% Done:

0%

Estimated time:
Applies to JS Branch:
Fix Committed on JS Branch:
Fixed in JS Release:
SEF Generated with:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

  • It seems we accept the globalContextItem option but this is not documented. (And in particular, it's not documented what conversion is applied, especially in the presence of an xsl:global-context-item declaration that specifies the required type.)

  • Switching to using a stylesheet parameter, with a declared type of array(map(xs:string, xs:anyAtomicType)) I was hoping to be able to pass a Javascript array of objects. No such luck. I ended up converting the value to lexical JSON and then parsing the JSON from the XSLT code.

  • I tried specifying {destination: "file", baseOutputURI: "profile.html"} and it rejects "profile.html" as an invalid URI. I think if a relative path is given here (in Node.js) we should resolve it against the current directory.

History

#1 Updated by Michael Kay 3 months ago

  • Description updated (diff)

#2 Updated by Debbie Lockett 3 months ago

  • Category set to API

Please register to edit this issue

Also available in: Atom PDF Tracking page