Q. How to use this tool ? about prisma-case-format HOT 8 CLOSED

@iiian
I Found it

this model makes ploblem

model sessions {
  session_id String  @id @localContainer.VarChar(128)
  expires    Int     @localContainer.UnsignedInt
  data       String? @localContainer.Text
}

from prisma-case-format.

Hey @sacru2red . Looks like you're using the beta version of 2.1.0. You've got two options here, roll back to ~2.0.0 or ^1.0.0,

Orrrr if you're feeling really generous, you could describe your schema/issue/usage in greater detail because you've managed to find a bug I couldn't create during my testing.

from prisma-case-format.

Hey @sacru2red . Looks like you're using the beta version of 2.1.0. You've got two options here, roll back to ~2.0.0 or ^1.0.0,

Orrrr if you're feeling really generous, you could describe your schema/issue/usage in greater detail because you've managed to find a bug I couldn't create during my testing.

Thanks,
I try [email protected]. It seems to work

btw, I think [email protected] must have "latest" tag
[email protected] must have "beta" tag in npm

from prisma-case-format.

Got it, yeah that could save me some problems. So could you describing your set up 😉

from prisma-case-format.

so, It has been confirmed that model names ending in "s" are problematic.

from prisma-case-format.

Thanks for the update @sacru2red, your investigation will be helpful to me. I'll try and dig into this at my earliest availability.

from prisma-case-format.

@sacru2red could you please and thanks share how you're invoking prisma-case-format? I copied your schema in as a unit test and it seems to run just fine.

Thanks!

from prisma-case-format.

hey. I test on 2.1.0-beta.0
check https://github.com/sacru2red/prisma-case-format-issue

I think this library must check npm tags.
why "2.1.0" doesnt have "latest" tag.
2.0.2 has "latest" tag
It looks strange.

check it
https://docs.npmjs.com/cli/v10/commands/npm-dist-tag

but I recommand use release-it cli

Thanks

Hey @sacru2red . Looks like you're using the beta version of 2.1.0. You've got two options here, roll back to ~2.0.0 or ^1.0.0,
Orrrr if you're feeling really generous, you could describe your schema/issue/usage in greater detail because you've managed to find a bug I couldn't create during my testing.

Thanks, I try [email protected]. It seems to work

btw, I think [email protected] must have "latest" tag [email protected] must have "beta" tag in npm

from prisma-case-format.