holidayextras / holidayextras/partner-api-docs
Remove internal only keys from responses
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 1
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 1
Description
For example STN6 returns the key tripAppIntroduction which also contains unprocessed markup such as:
[date from=30-10-2023 to=11-12-2023]
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
Start by locating the STN6 response documentation and the tripAppIntroduction field. Check whether the field contains the shown unprocessed markup or is documented as an internal-only key. Done means internal-only keys are no longer exposed in the relevant response documentation, without changing public fields.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100