eezing·3 か月前·議論Not sure if this equates to more spend. Smarter models make fewer mistakes and thus fewer round trips.
eezing·7 か月前·議論Aside from the following, JSDoc is absolutely TypeScript.Discriminated unions, conditional types, mapped types, template literal types, recursive type aliases, higher-kinded type patterns, generic constraints with conditional inference, the infer keyword, never type exhaustiveness checking, const assertions, readonly tuple and array inference, exact object types, key remapping in mapped types, indexed access types, variance annotations, assertion signatures, strict null checking with flow-sensitive narrowing, definite assignment assertions, the satisfies operator, declaration merging, module augmentation, symbol-typed properties, type-safe enums…and not written via comments
eezing·昨年·議論Have you actually tried to tag, edit, or leave comments when you come across questionable content?I’ve found that the system works pretty well. It’s not perfect, but I can’t think of a better solution.
eezing·2 年前·議論This is actually very nice, thanks for posting.Not sure this will save you time and money, but it is very comprehensive.
eezing·2 年前·議論It’s Salesforce v2. A ridiculously expensive proprietary “easy-to-build” application platform with an ecosystem of ridiculously expensive consultants.