SSWConsulting / SSWConsulting/SSW.Website
3rd party APIs blocked after package upgrade
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
cc @amankumarrr
During a sprint review @wicksipedia noticed events data from SharePoint was not loading.
After checking app insights, we could not see any errors, I thought it was an issue with App Insights configuration.
To try fix to events data, I reverted my package update PR from earlier #1254
This fixed the problem, and also fixed App Insights.
It looks like one of the package updates in that PR stopped all 3rd party requests from working (including App Insights tracking)
### Tasks
- [ ] Investigate which package caused the issue
- [ ] Implement integration tests to check 3rd party services
- [ ] Update packages
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 reviewing package update PR #1254 and comparing its dependency changes with the current project. Reproduce the missing SharePoint events and App Insights tracking, then identify the package causing third-party requests to fail. Done means the offending package is addressed, integration coverage exists for third-party services, and the package updates are applied safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs
- Domain
- api, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100