Skip to content

APIs with left out fields don't compose well with APIs using non-purescripty casing #60

@ysangkok

Description

@ysangkok

If I use camelCase in my codebase, and an API uses snake_case, it seems like I have to use prismaticCodec and create converter functions that convert {field_name :: Foo} to {fieldName :: Foo}.

Using the alternative CA.prop API, I can specify the key name, so there is no issue. But then I can't have left-out fields as there is no pendant to recordPropOptional. Why is there no recordPropOptionalWithCustomKeyName?

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