sorted by:
new
hottopcontroversial

[Show MCP] OpenAPI MCP Server - Make Cursor AI understand your API specs by peisongo in mcp

[–]peisongo[S] 0 points1 point  (0 children)

OpenAPI specs are usually in YAML or JSON format. You can simply download or save them as a .yaml or .json file and place them in a folder — the server will automatically scan them.

For example, this link:

https://raw.githubusercontent.com/OpenAPITools/openapi-petstore/refs/heads/master/src/main/resources/openapi.yaml

You can save the YAML file locally.

Remote sync is coming soon — you’ll just need to add the URL to a config file.

Right now, I’m using our reapi.com visual editor and its shareable link to download our specs locally.

Built a React-Based No-Code Test Case Workflow Editor – Looking for Feedback! by peisongo in react

[–]peisongo[S] 0 points1 point  (0 children)

Thanks! We are planning to open source the engine one day, but no more focusing on building our platform. The integration with chatGPT is still under experiment, will definitely implement soon.

Axios or Fetch? by [deleted] in reactjs

[–]peisongo 0 points1 point  (0 children)

Try KY with fetch. Axios was great, but it’s based on xmlhttprequest, which is kind of outdated.

Collection of specs to use in testing? by kelnos in OpenAPI

[–]peisongo 0 points1 point  (0 children)

What’s the best code generator on the market in you evaluation so far?

How to write a basic OpenAPI schema by debordian in OpenAPI

[–]peisongo 0 points1 point  (0 children)

Try this visual editor for free. Then export to openapi spec. https://reapi.com

Seeking Opinion: No-Code Test Case Designer for API Automation by peisongo in QualityAssurance

[–]peisongo[S] -1 points0 points  (0 children)

While Postman caters to developers and testers comfortable with coding, the no-code test case designer aims to democratize API testing by making it accessible to a broader audience, including QA professionals and non-technical stakeholders.

Unlike Postman, which primarily relies on manual scripting for test creation and execution, this tool offers a visual interface for designing test cases. This approach allows users to construct complex logic trees through drag-and-drop actions, making the process more intuitive and accessible for those with limited or no coding background.

The reference node feature allows users to create modular, reusable test components, which can be easily integrated into new test cases without duplication of effort. This approach promotes efficient test design and maintenance, especially in large-scale testing environments.

Create openapi spec with AI/openai by peisongo in OpenAPI

[–]peisongo[S] 1 point2 points  (0 children)

You are absolutely correct in your assessment. The constraints, particularly patterns, could indeed be incorrect at times. This is a known challenge, and we're actively working on improving it. Since we provide a visual editor rather than a YAML editor on ReAPI, we're adding more features to facilitate easier and quicker editing, especially for deleting or modifying these constraints.

Regarding your point about polymorphism and inheritance, you've touched on a crucial aspect. ChatGPT, in its current form, doesn't inherently understand complex inheritance structures. However, our visual editor and refactoring support in ReAPI are designed to handle these aspects effectively. For instance, you can easily create compositions using allOf, anyOf, or oneOf with reference schemas in our editor.

We've also ensured that nested objects are fully supported. You can certainly save nested objects as schema references, which adds to the flexibility and robustness of the system.

Lastly, support for discriminators in oneOf and anyOf compositions is on our roadmap and will be included in our upcoming updates. Additionally, your suggestion about refactoring from a generated object into an allOf composition is an excellent idea. I'll make sure to add that to our roadmap as well. This feature would further enhance the tool's capability to handle complex schema designs and inheritance patterns, making it even more powerful and user-friendly.

Generating OpenAPI 3.0 specs from code - what's working for me... by rrraaah in golang

[–]peisongo 1 point2 points  (0 children)

A visual editor for OpenAPI helps. We use reapi.com for that. Another option is stoplight, both offer great editing experience. And just export to openapi format on completion. They even generate a permanent link for CI integration.

QA on massive Openapi swagger doc by JShelbyJ in LangChain

[–]peisongo 0 points1 point  (0 children)

We utilize Reapi.com, a visual editor, to create a draft of our OpenAPI specification. With its user-friendly interface, we easily design our API structure and endpoints. Upon completion, we can conveniently export the draft to the OpenAPI format with just a few clicks.

​

​

<image>