loopbackio / loopbackio/strong-soap
BUG: extension namespaces
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 410
- Forks
- 162
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 7
Description
It appears fields do not get their namespaces applied properly when they are derived from a complex extension. See https://preprod.signicat.com/ws/documentservice-v2?wsdl, specifically the document->provided-document relation and the lack of namespaces for the data and description fields.
Contributor guide
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
Start by reproducing the issue against the linked documentservice-v2 WSDL, focusing on the document->provided-document relation and the data and description fields. Trace how fields derived from a complex extension receive namespaces, then verify that the generated SOAP structure applies the expected namespaces to those fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100