You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's certainly true that suggesting the use of \(unsafeRaw:) is incorrect; I should have updated the deprecation message long ago. Suggesting the use of \(bind:) as a replacement isn't always correct, though (or more exactly, it's incomplete) - I equally often encounter people incorrectly using \(unsafeRaw:) where they should be using \(ident:). The Real™ problem here is that the correct use of SQLQueryString itself - especially the meaning and correct usage of the various interpolations - is not really documented in any meaningful way; I'm going to include addressing that as part of fixing this issue.
Thanks for pointing this out! At least now I realize it's my own fault that people so commonly overuse (and/or misuse) \(unsafeRaw:) 😆
Awesome, thanks. Yeah, some sort of documentation on what those interpolations actually generate would be helpful. I can imagine that a lot of users just give up and go for the unsafe version.
Please summarize your feature request
I wonder if there would be any disadvantages to that?
Describe the functionality you're seeking in more detail
I wonder if there would be a scenario where we cannot suggest using
\(bind: ...)
instead of\(unsafeRaw: ...)
interpolation?Have you considered any alternatives?
No response
The text was updated successfully, but these errors were encountered: