Skip to content

Better type safety for DataRequestId, DataDefinitionId, ClientDataDefinitionId, etc #83

@EvenAR

Description

@EvenAR

Today these are just aliases for number and provide no type safety at all. For instance, it should not be possible to pass a DataRequestId to the DataDefinitionId parameter of a function.

One way to improve the type safety is to make the types "opaque". A singleton class could be provided for generating new id's with the correct type.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions