arktype•3mo ago

`string.integer.parsed` with limits

I need a simple port number, 1 < integer < 9999 Hovewer, I want to parse it from env string so I need string.integer.parse How do I make the limited parsed integer?

26 Replies

DimavaOP•3mo ago

import { type } from 'arktype'
const oneTo9999 = type('1 <= number.integer <= 9999')

const T = type({
  PORT: ['string.integer.parse', '=>', oneTo9999],
})
const defaults: typeof T.in = {
  PORT: 123,
}

import { type } from 'arktype'
const oneTo9999 = type('1 <= number.integer <= 9999')

const T = type({
  PORT: ['string.integer.parse', '=>', oneTo9999],
})
const defaults: typeof T.in = {
  PORT: 123,
}

(this doesn't work) WIW is

const T = type({
  PORT: '1 < string.integer.parse < 9999 | 1 < integer < 9999'
})
const tIn: typeof T.in 
const tLike = T.typedAssert({
  PORT: 1234
})

const T = type({
  PORT: '1 < string.integer.parse < 9999 | 1 < integer < 9999'
})
const tIn: typeof T.in 
const tLike = T.typedAssert({
  PORT: 1234
})

ssalbdivad•3mo ago

So what is your issue?

ssalbdivad•3mo ago

t.in is a Type, not an inferred output It's t.infer like it has always been

DimavaOP•3mo ago

🤔 what was my issue again

DimavaOP•3mo ago

This

DimavaOP•3mo ago

2.0.0-rc.6

ssalbdivad•3mo ago

what is the error on T? Oh just that it's unused?

DimavaOP•3mo ago

..... Waitaminute Lemme unupdate back

ssalbdivad•3mo ago

I can't repro it

DimavaOP•3mo ago

I can't repron't it Researching...

ssalbdivad•3mo ago

I mean that type doesn't make any sense it's like it's not even trying to infer anything

DimavaOP•3mo ago

Okay this was tsconfig looking what exactly

ssalbdivad•3mo ago

I have tested it with only strictNullChecks in tsconfig and it works So I guess you have some resolution setting that is actively breaking it

DimavaOP•3mo ago

Okay it was "moduleResolution": "node",

ssalbdivad•3mo ago

But that should work I thought? Isn't that the default I know there was a problem with node resolution in a previous build so I added tests for default settings and people said their node resolution was fixed

DimavaOP•3mo ago

Okay here's repro

{
  "compilerOptions": {
    "lib": ["esnext"],
    "strictNullChecks": true
  }
}

{
  "compilerOptions": {
    "lib": ["esnext"],
    "strictNullChecks": true
  }
}

Why do I even have that lib: esnext there (╯°□°)╯︵ ┻━┻

ssalbdivad•3mo ago

Why does that break it though blah

DimavaOP•3mo ago

https://github.com/microsoft/TypeScript/blob/main/src/lib/esnext.d.ts well maybe some of those

GitHub

TypeScript/src/lib/esnext.d.ts at main · microsoft/TypeScript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output. - microsoft/TypeScript

ssalbdivad•3mo ago

Dunno it still works fine for me with that enabled

DimavaOP•3mo ago

okay idk see you tomorrow (╯°□°)╯︵ ┻━┻

type({
  LOG_SIZE_LIMIT_MB: type('string.integer.parse').pipe(type('number.integer > 0')),
)}

type({
  LOG_SIZE_LIMIT_MB: type('string.integer.parse').pipe(type('number.integer > 0')),
)}

Me don't like this Why can't I just 'string.integer.parse > 0' Or at least ['string.integer.parse', '=>', 'number.integer > 0'] Or at least ['string.integer.parse', '=>', type('number.integer > 0')]

ssalbdivad•3mo ago

You can use .to when piping to another type then pass the definition deirectly

DimavaOP•3mo ago

Can what?

ssalbdivad•3mo ago

Wtf is your type .to is only available on morphs which string.integer.parse is but it's clearly not being inferred correctly

DimavaOP•3mo ago

that 💩 magic that doesn't allow me to use stuff! It come again! (╯°□°)╯︵ ┻━┻ okay idk see you tomorrow (╯°□°)╯︵ ┻━┻

DimavaOP•3mo ago

Okay I've kleaned up my node_modules and it now work

ssalbdivad•3mo ago

Try that first next time your env is always doing weird shit🤣

Gaming

Programming

`string.integer.parsed` with limits