Lev Khoroshansky

Seems like `styled-components@^6.0.0-beta.2` can't handle "inplace argument extension" (not sure what's the official name for that): ```ts const StyledContainer = styled.div` ${({ clickable }) => clickable && 'cursor: pointer;'} `...

Okay, seems like it doesn't like possible `false` return value. Explicit handling prevents Typescript from erroring out: ```ts const StyledContainer = styled.div` ${({ clickable }) => clickable ? 'cursor: pointer;'...

> > Okay, seems like it doesn't like possible `false` return value. > > @TmLev This was mentioned above, see https://github.com/styled-components/styled-components/issues/3696#issuecomment-1236355978 > > and there is a PR for it,...

@ZacharyLeBlanc, thanks, this works! Do you happen to know whether this is runtime or compile-time check?

I'm also interested in how one can insert UDT with an update on the conflict, like so: ```sql INSERT INTO service_statuses (ip, state) VALUES ($1, $2) ON CONFLICT (ip) DO...

Sorry, it's a typo. Actual message: ```error: unsupported type service_state for param #2```

Yep, that works, appreciate it! Is there any issue about compatibility for UDT at compile time I can follow?

@benjaminjkraft, hi! Sorry for the delay. > * One file per schema, if the schemas are completely disjoint (i.e. you're talking to several services). In this case I think right...

Would love to try it out, is it possible to release this as `beta-X`?

Any news?