Skip to content

Ensure LotusJson<Option<T>> is marked as optional in the OpenRPC spec #4331

Description

@lemmih

Does this fix an encountered issue? Perhaps a simple test is in order to verify that LotusJson<Option<T>> encodes/decodes the way we expect. It's a couple of lines of code, but goes a long way, especially if this code is ever touched by somebody else.

I leave this up to you, non-blocking.

Originally posted by @ruseinov in #4330 (comment)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions