We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instead of
type alias Proposal = { id : String , ... }
we should use
type alias Proposal = { id : ProposalId , ... } type ProposalId = ProposalId String
Same goes for ParticipantId and AccessToken.
ParticipantId
AccessToken
This way we strengthen type safety and get better self-documenting code when passing this values around.
The text was updated successfully, but these errors were encountered:
Will have to check if it's worthwhile or too much boilerplate. Deferred for now.
Sorry, something went wrong.
Recently Richard Feldman wrote that union types may get comparable sometime.
Working with wrapped types would become much easier then and we should use them for type safety.
Sounds good.
No branches or pull requests
Instead of
we should use
Same goes for
ParticipantId
andAccessToken
.This way we strengthen type safety and get better self-documenting code when passing this values around.
The text was updated successfully, but these errors were encountered: