10
45
Fork
You've already forked doipjs
28

WIP: Test DOIP fetchers through API mocking #81

Draft
vladimyr wants to merge 1 commit from vladimyr/doipjs:test-fetchers into dev
pull from: vladimyr/doipjs:test-fetchers
merge into: keyoxide:dev
keyoxide:main
keyoxide:dev
keyoxide:fix-irc-fetcher
keyoxide:new-claim-eveonline-143
keyoxide:prepare-new-release
keyoxide:fix-jsdoc-types
keyoxide:yarn-to-npm
keyoxide:support-openpgp-aspe-claims
keyoxide:support-html-alias
keyoxide:improve-activitypub-support
keyoxide:v1-restructure
keyoxide:into-es-module
keyoxide:support-aspe
keyoxide:fix-js-lsp-issues
keyoxide:improve-linting
keyoxide:add-markers
keyoxide:support-opencollective-claim
keyoxide:support-entity-decoding
keyoxide:use-rome-tools
keyoxide:support-cloudflare-buster
keyoxide:support-fediverse-posts
keyoxide:matrix-room-verification
No description provided.
test: Matrix fetcher using MSW
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
e548f0ab33 
Echo back JSON with `_debug` field containing request headers
and Matrix API call arguments.
@ -0,0 +1,114 @@
/*
Copyright 2024 Yarmo Mackenbach
Owner
Copy link

You created it. I'm not sure, whether you should impersonate Yarmo.

You created it. I'm not sure, whether you should impersonate Yarmo.
Author
Member
Copy link

There, I said it publicly: I have zero idea how to work with license headers and every time I encounter one I feel like is that really the best way of doing it? 🙃 So, yeah I'm bound to do it wrong but I will educate myself at some point!

There, I said it publicly: I have zero idea how to work with license headers and every time I encounter one I feel like is that really the best way of doing it? 🙃 So, yeah I'm bound to do it wrong but I will educate myself at some point!

Let me know when you would like to have a review. I'm okay with giving one during work on it. But some people consider this distracting.

Let me know when you would like to have a review. I'm okay with giving one during work on it. But some people consider this distracting.
Author
Member
Copy link

If there are any distractions I highly endorse and encourage PR reviews are definitely one of those! That being said after I made this I took a step back to the drawing board and I'm still in the process of coming up with what I think would be the right approach.

If there are any distractions I highly endorse and encourage PR reviews are definitely one of those! That being said after I made this I took a step back to the drawing board and I'm still in the process of coming up with what I think would be the right approach.
Owner
Copy link

Wow, this one flew under my radar! I need to try this. If it works, I can help making mock tests for the other ones.

  1. This should be rebased for npm (sorry)
  2. Don't mind the copyright headers. I prefer REUSE so I'll make a PR at some point replacing the headers. And I can put you in the header for this file
Wow, this one flew under my radar! I need to try this. If it works, I can help making mock tests for the other ones. 1. This should be rebased for `npm` (sorry) 2. Don't mind the copyright headers. I prefer REUSE so I'll make a PR at some point replacing the headers. And I can put you in the header for this file
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
This pull request has changes conflicting with the target branch.
  • package.json
  • yarn.lock
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u test-fetchers:vladimyr-test-fetchers
git switch vladimyr-test-fetchers
Sign in to join this conversation.
No reviewers
Labels
Clear labels
bug
Something is not working

Archived

enhancement
New feature

Archived

Contribution welcome
Get started contributing here
Good first issue
Good if you are new to the project or to open source contributions
Impact
External
 Affects the people using the project
Impact
Internal
 Affects on the people working on the project
Priority
Critical
 Work on right now
Priority
High
 Work on at earliest convenience
Priority
Low
 Work on in spare time
Priority
Medium
 Work on regularly
Review
Duplicate
 Already exists
Review
Off Topic
 Does not fall within the scope of the repo/project
Status
Backlog
 Is not being worked on yet
Status
Blocked
 Is waiting on something or someone
Status
Completed
 Is done
Status
In Progress
 Is being worked on
Status
Investigating
 Is waiting on research or questions
Status
Needs Decision
 Is waiting on a decision by the devs/contributors
Status
Needs Info
 Is waiting on additional information before it can be solved
Status
Needs Triage
 Is new issue that needs reviewing
Status
Testing
 Is being checked and verified
Status
Waiting For Review
 Is waiting on reviewers to approve
Status
Won't Fix
 Won't be fixed
Type
Bug
 Related to something not working as intended
Type
CI
 Related to continuous integration
Type
Documentation
 Related to documentation
Type
Enhancement
 Related to a new feature or an improved one
Type
New Claim
 Related to a new identity claim/proof
Type
Security
 Related to security
Type
Tests
 Related to code tests
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
keyoxide/doipjs!81
Reference in a new issue
keyoxide/doipjs
No description provided.
Delete branch "vladimyr/doipjs:test-fetchers"

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?