Project

Profile

Help

Bug #5535

open

Improve documentation for exposed node properties

Added by Norm Tovey-Walsh over 2 years ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2022-05-24
Due date:
% Done:

0%

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

Description

The documentation about XDM nodes makes reference to the fact that we've added properties to some of the node types, but doesn't actually enumerate the properties that we expect to be public.

We should use the externs for the node classes to derive the public properties and document them.


Related issues

Related to SaxonJS - Bug #5494: Properties of attribute nodes have internal names which change from one release to anotherClosedNorm Tovey-Walsh2022-05-18

Actions
Actions #1

Updated by Norm Tovey-Walsh over 2 years ago

  • Related to Bug #5494: Properties of attribute nodes have internal names which change from one release to another added
Actions #4

Updated by Debbie Lockett about 2 months ago

We also use our own classes for namespace and attribute nodes (see NamespaceNode and AttributeNode in src/nsnode.js), and these are not documented (but they probably should be).

Please register to edit this issue

Also available in: Atom PDF Tracking page