DEV Community

Discussion on: The Strictest TypeScript Config

 
artxe2 profile image
Yeom suyun

Yes, indeed.
If you have been using the strict option in TypeScript, applying additional stricter options may not introduce many new errors.
However, for types like Array or Record, there are clear use cases, and it's not accurate to categorize them as inherently bad.
For instance, I found type casting cumbersome in cases like the code below to eliminate errors.

/**
 * @param {string} text
 * @returns {string}
 */
let _default = text => {
  let regex = ""
  let len = text.length - 1
  for (let i = 0; i < len; i++) {
    let t = /** @type {string} */(text[i])/**/
    regex += first_consonant_letters[t] ?? get_letter_range(t)
  }
  return regex + get_letter_range(
    /** @type {string} */(text[len])/**/
  )
}
Enter fullscreen mode Exit fullscreen mode
Thread Thread
 
what1s1ove profile image
Vladyslav Zubko

Agreed!
In general, as always, it depends on the situation 😁

Thread Thread
 
bwca profile image
Volodymyr Yepishev

Just dropping my 2 cents, the possible undefined problem of the aforementioned record can be solved by an explicit cast in the value lookup, it's just that both the object and its key need to be casted.

let obj: Record<string, { func: Function }> = {}

for (let key of Object.keys(obj)) {
  (obj[key] as typeof obj[typeof key]).func(); // ✅
}
Enter fullscreen mode Exit fullscreen mode

Though the case seems rather artificial, as you'd probably be using .values or .entries :P

Thread Thread
 
what1s1ove profile image
Vladyslav Zubko • Edited

Hey @bwca !
Thank you for sharing your approach to solving the problem!
I believe it's challenging to assess it solely based on this small code snippet. In real projects, everything can be significantly different 🥲