WIP: feat: add tests for finding the api url #1019
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#1019
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/test-api-finder"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-Up for
26213d5e8c
Since the api-finding stuff recently broke, I figured we should have tests for it. I'm not quite sure yet how to properly test this, my best idea is to pass a function that resolves or reject depending on the current url. Open for ideas.
I'm not experienced in this, regardless I stumbled recently across testing api end points via service workers that replicate the api 1:1.
E.g. via https://mswjs.io/ (probably there are other solutions, was basically the first hit)
EDIT: also found this: https://github.com/Netflix/pollyjs