You have to make a function to apply the brand via a cast, the article explains this as well.
function makeObjectId(id: string): ObjectId {
return id as ObjectId;
}You have to make a function to apply the brand via a cast, the article explains this as well.
function makeObjectId(id: string): ObjectId {
return id as ObjectId;
} const accountId = "125314" as AccountId
It makes sense that the technique uses casting. const myCompanyId = something_complicated as CompanyId;
where something_complicated actually is a UserId, not a bare string.It is way too easy to accidentally destroy type safety with `as`, there are absolutely 0 safeguards.
I fear every single instance of `as` in any Typescript source I see.
But what if I instead wrote:
const accountId = AccountId ("125314" );
There would be the needed checks and balances in the function
AccountId(). Wouldn't that do pretty much the same thing? const accountId = "125314" as AccountId;
or const accountId = new AccountId("125314");
or const accountId = accountIdFromString("125314");
is all "explicit" casting in my understanding, one way or the other, and the first ... as ... being on the lowest level.I'd rather go for something like "do the casting close to the source, and in general use 'parse, don’t validate'[0] when getting input from the outer world".
[0]: https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-va...
If you do add valuation, make it an honest asValidatedAccountId("123"), not an accountIdFromString("123") that may or may not do more than casting.
(PS, very much off topic: speaking of hidey-holes, are any of the AOP monstrosities still operational?)
const accountId = AccountId (“43525”)
being less explicitAnother way you can implement the same: through a class constructor like new UserId('some string') which can also throw or let you handle operations on the class itself while allowing you to get the value.