Discuss collective issues impacting FAPI 1
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by Peter.Stanley (Peter.Stanley) on 2025-07-23
At the FAPI WG on 3rd July 2025 I was requested to raise an issue to ensure all pending items potentially impacting FAPI 1 are brought back to the Working Group for discussion.
The UK ecosystem has only recently moved to FAPI 1 Advanced (from FAPI 1 ID2) and having a clear view on all potential impacts to this spec, whether it is via an Errata update or a new minor release, is important for participants in the ecosystem.
Bitbucket status: open
Bitbucket origin: issue 751
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 reading the issue thread and reviewing the FAPI 1 Advanced and FAPI 1 ID2 specifications. Identify the pending items that may affect FAPI 1 and the relevant Working Group discussions. Done means producing a clear set of impacts for Working Group consideration, though the issue does not name files, tests, or a specific implementation change.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100