New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: create Firecamp Echo Server compatible with Postman #106
Comments
I'd like to work on this. To clarify, what still needs to be done? The methods that return |
@nkBrew yes, need to create echo apis those are marked as yet to implement. Also it would be same as postman echo server apis (expected request and response should be same as in pm echo server) |
@nkBrew are you working on this issue? please share the draft PR so we can collaborate on it. |
@Nishchit14 Yeah, sorry was working on it locally. |
Thank you @nkBrew, I will start the PR review once the PR is ready. Appreciate your contribution 👏🎉 |
Gentle reminder @nkBrew |
Description:
Firecamp currently has a minimal echo server that is compatible with Postman's echo server features and APIs. We should create a Firecamp Echo Server that implements the same endpoints and functionality as Postman's echo server so that we can maintain the highest level of compatibility for those users who're coming from the postman background.
This will allow Firecamp users to have parity with Postman when testing API clients and workflows. The Echo Server can be used to validate REST calls, auth mechanisms, and response handling. It will be the single source of truth for all services and tooling in Firecamp like API Testing, Monitoring, Collaboration, and Documentation while ensuring postman compatibility. It will make it easy for users to migrate to Firecamp for API testing and development will less friction.
Firecamp Echo Server
https://github.com/firecamp-dev/firecamp/blob/main/packages/firecamp-echo-server/src/rest/rest.controller.ts
pnpm i
atpackages/firecamp-echo-server
pnpm start:dev
to start the development serverTech Stack
NestJS & Typescript
The text was updated successfully, but these errors were encountered: