Fernando Correa de Oliveira
Fernando Correa de Oliveira
@kawaii I've added a test for it (https://github.com/FCO/Red/commit/d0085007ff75e3eb35e1f334b24b5ee6165a6926). Is it still broken for you?
It seems 2 tests are failing with these changes...
@jonathanstowe doing that, do you think we should inflate the terms we search also? I mean: `User.^all.grep: *.password eq "bla"` should generate a SQL with `WHERE password = 'bla'` or...
if it should be inflated, should be a way to say that I don't want it to be inflated?
should inflators/deflators receive the whole object as argument? If, for example, the Password type uses the username and a salt column as salt to hash.
Maybe something like `multi infix:(Red::AST $a where *.returns ~~ Password, $)` Sent with GitHawk
https://modules.raku.org/dist/RedX::HashedPassword:cpan:JSTOWE
Would something like this make sense? lib/Red/Type/Json.pm6
I’m thinking of creating the Red::Type as you suggested and convert this JSON to use that. But more than inflate and deflate the new types, I’m thinking on how to...
A Vector Red::Type could, for example, have a module method that on queries would be translated to `sqrt(pow(x, 2) + pow(y, 2))` and would make it possible to: `Force.^all.grep: *.vector.module...