Skip to content
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: erf debug utilities #68

Open
javiergarea opened this issue May 18, 2024 · 0 comments · May be fixed by #71
Open

feat: erf debug utilities #68

javiergarea opened this issue May 18, 2024 · 0 comments · May be fixed by #71

Comments

@javiergarea
Copy link
Member

javiergarea commented May 18, 2024

Generated code is hard to debug even for developers familiar with the source. Since the exported modules are generated based on the provided OpenAPI Spec, it's not easy for users to ask for traces of the proper functions. Developers usually either add debug traces to the whole generated modules or write them to files for further inspection.

A more convenient way of debugging the routing/validation process is required. A possible solution would be providing an erf_dbg module exposing some methods that, given known parameters such as the operationId, would add convenient debug traces on generated modules.

@github-project-automation github-project-automation bot moved this to 📑 TODO in erf May 18, 2024
LoisSotoLopez added a commit to LoisSotoLopez/erf that referenced this issue Jun 1, 2024
@LoisSotoLopez LoisSotoLopez linked a pull request Jun 1, 2024 that will close this issue
LoisSotoLopez added a commit to LoisSotoLopez/erf that referenced this issue Jun 1, 2024
LoisSotoLopez added a commit to LoisSotoLopez/erf that referenced this issue Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📑 TODO
Development

Successfully merging a pull request may close this issue.

1 participant