Expose AST for schema before call about dry-validation

[solnic]

You have access to rule AST via YourSchema.rules. We need to see how we could use that for hints, it should be enough as all the relevant info is there. I was planning to add a "hint compiler" that would use this AST to produce hints.

[timriley]

Ah, thanks for pointing me towards .rules! I didn't realise it existed :)

[solnic]

Right, actually I forgot that it's an AST wrapped in DSL objects, so you gotta do rules.map(&:to_ary) to get a pure AST

[solnic]

I added support for hints. Is there anything special you need in order to implement your form builder?

[timriley]

The AST is pretty much all we should need, I think, but the hints will hopefully make it even nicer :)

Feel free to close this on, I reckon, and I can raise smaller things separately if I come across any other issues when we get to integrating the validation.

Thanks :)

On 18 Dec 2015, at 4:40 AM, Piotr Solnica [email protected] wrote:

I added support for hints. Is there anything special you need in order to implement your form builder?

—
Reply to this email directly or view it on GitHub.

[solnic]

Roger that

[kurko]

FYI I needed to get just the keys (incl. nesting) to shove into strong_parameters, so I write this for whoever needs this in the future:

    def self.creative_keys_ast
      [ast_predicate(MySchema)]
    end

    # Recursive algorithm to fetch dry-validation schema's keys
    def self.ast_keys(rule, ast = [])
      if rule.respond_to?(:rules)
        rule.rules.map(&:to_ary).each do |node_rule|
          subtree = ast_keys(node_rule[1].rules[1].rules[1].rules[0])
          if subtree.blank?
            ast << node_rule[0]
          else
            ast << {
              node_rule[0] => subtree
            }
          end
        end
      end

      ast.flatten
    end

I had to figure out how to get those rules arrays used. It looks pretty messy.