Skip to content

Fix double-option of nullable useOpt fragments #553

Description

@zth

When doing useOpt we need to account for whether the fragment itself is optional too. Right now we get option<option<fragment>> in that case, but we should just get option<fragment>.

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 labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions