Skip to content

Migrate to DirectedCodegen #753

@aajtodd

Description

@aajtodd
Contributor

Consider what it would take to migrate to some of the newer utilities like DirectedCodegen

The background here is that the Smithy team took a lot of the best patterns found in Kotlin/Rust/Go/etc and internalized them. We don't have to migrate but long term it may be better to standardize on what Smithy is supporting rather than owning all of the utils we have built up. I'm not sure where the API differences are though or how difficult a migration this may be.

We should also consider any other custom utilities that now have found an official equivalent in Smithy.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    no-auto-closureWe do not want this issue to be automatically closed.refactor

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @aajtodd@ianbotsf

        Issue actions

          Migrate to DirectedCodegen · Issue #753 · smithy-lang/smithy-kotlin