DesignLiquido / DesignLiquido/xslt-processor
Running into max stack eceeded error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 124
- Forks
- 35
- Avg merge
- 21h 9m
- Merged PRs (30d)
- 1
Description
Hi,
I would like to use the js based xsltProcessor but I'm running into error "max stack eeeded .." and I don't know how to debug it.
The xml and xslt working fine when using the xsltProcessor still embedded in Chrome/Edge Browser. Thus, I think I need to improve my xslt code to work with this js based XsltProcessor. What is the best way for debugging? Or are there any tipps how to write xslt for ot running into stack exceeeding issue?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No XML, XSLT, stack trace, or source file is included. Start by obtaining the failing XML and XSLT and reproducing them with the JavaScript-based XSLTProcessor, then compare the result with Chrome and Edge. Done means identifying whether the failure is in the processor or the stylesheet and documenting a reproducible case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100