OpenAPITools / OpenAPITools/openapi-generator

[REQ] C++ server for esp32 and arduino

Open
#15,381 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement: Feature Server: C++
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

My target is to use it to develop a REST api for automation on a microcontroller
(although it is a pretty large one it doesn't allow pistache, restbed or qt)

so I would need to generate some generic C++ code that would be able to interface with one of those (microcontroller) servers
that use very similiar architecture:
https://github.com/me-no-dev/ESPAsyncWebServe (ESP32) or
https://github.com/khoih-prog/Portenta_H7_AsyncWebServer. (ARM)

The dependencies should be limited to whatever may run on an microcontroller.

I see in the road map that there is a mid term goal:
C++ Server, any framework (server)

What does it actually mean? Is there some way to help or someone that could help me (mentoring).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the roadmap entry for “C++ Server, any framework (server)” and compare the constraints described here with ESPAsyncWebServe and Portenta_H7_AsyncWebServer. Define the supported target, framework boundary, dependencies, generated output, and acceptance tests before implementation; the issue does not identify project files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
arduino, cpp
Domain
backend-api-design, embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.