highsource / highsource/ogc-schemas
Object comparison fails because of the prefixes
Open
- Dominant language
- JavaScript
- Stars
- 84
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
- discreteCurveCoverage.responseDescribeCoverage.xmltodo
- discreteCurveCoverage.responseGetCapabilities.xmltodo
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with discreteCurveCoverage.responseDescribeCoverage.xmltodo and discreteCurveCoverage.responseGetCapabilities.xmltodo, then trace the object-comparison path that reports prefix differences. Clarify the expected prefix-insensitive behavior and consider the issue complete when both named comparisons pass without false prefix mismatches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100