Generate SDK for elm

[afreakk]

Preflight checklist

• [X] I could not find a solution in the existing issues, docs, nor discussions.
• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines.
• [ ] This issue affects my Ory Cloud project.
• [X] I have joined the Ory Community Slack.
• [ ] I am signed up to the Ory Security Patch Newsletter.

Describe your problem

We would like to use Ory sdk's for elm.

Describe your ideal solution

It would be nice to be able to use generated sdk for elm

Workarounds or alternatives

Openapi-generator-cli has some support for elm. But when generating using openapi-generator-cli generate -i v0.8.0-alpha.2.json -g elm it does generate mostly working code, but it for instance generates a broken type

type alias UiNodeInputAttributeType =
    { }

which i suspect is the reason this function also gets broken:

encodeUiNodeInputAttributeTypePairs : UiNodeInputAttributeType -> List EncodedField
encodeUiNodeInputAttributeTypePairs model =
    let
        pairs =
            ]
    in
    pairs

(Also has more issues, like AnyType and Object)

Version

v0.8.0-alpha-2 (also using hydra and oathkeeper)

Additional Context

No response

[aeneasr]

Thank you for the report! Looks like some things need to be fixed in openapi-generator first though :/

[github-actions[bot]]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️