sinclairzx81

@peguerosdc @Lonli-Lokli @abuaboud @matjaeck Hi! Apologies for the delay in reply here (I've been exceptionally busy with other project as of late) So, I may convert this issue into a...

@sdeprez Hi, > In that case, the type of T is {}, which in Typescript actually validates every non-null values, so the following assignments are all valid: This is somewhat...

@sdeprez Hi! > But maybe we can at least improve the type {} for Type.object({}), which is arguably wrong because it allows any non-null values? It could use object for...

@sdeprez Hiya, I've given this quite a bit of thought, but will probably defer here for now. At this stage, I am keen to keep on with the open `{}`...

@itsyoboieltr @Kudo Hi, > fwiw, the Object call is from babel runtime. this is the transpiled component of your index.tsx I think an ideal solution would simply be to ensure...

@itsyoboieltr Hiya, Good to hear you have a workaround :) > Is there a way that we could mention this workaround for react native/babel users in the TypeBox docs? I...

@paulius-valiunas Hi, This is an interesting issue. You would expect TypeScript to be able to correctly determine that the type isn't valid for the left-side assignment, but it looks like...

@noelsoong Try ```typescript import { Value } from '@sinclair/typebox/value' const result = Value.Decode(Type.String(), 'hello') ```

@ehaynes99 Hi, thanks for helping to take a look at this! So here was the implementation I was looking at. I do think the expectation would be that decode should...

@ehaynes99 Hey, thanks for the follow up. > In my other linked issue, you mentioned that TypeBox uses that technique internally (your link doesn't point to the right line in...