Hmm, yeah. And I should have mentioned I modified Ulf's exprecs to have slightly different syntax but the main thing was to also use types in records to add calls to convert (which I may change to check...) for setting each attribute of a record.<div>
<br></div><div><a href="https://github.com/tsloughter/maru/blob/master/lib/maru_models/src/maru_model_transform.erl">https://github.com/tsloughter/maru/blob/master/lib/maru_models/src/maru_model_transform.erl</a></div><div>
<br></div><div>Add support for validating email addresses and more complicated types is in my plan for dealing with that model creation. But no reason to have it not be a secondary piece of sheriff now :)</div><div><br></div>
<div>Tristan<br><br><div class="gmail_quote">On Tue, Feb 14, 2012 at 10:01 AM, Loïc Hoguin <span dir="ltr"><<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Right, forgot about that. I also want pre-defined functions for validating things like emails, URLs and others that string() or binary() types can't define. But I'm not sure this should go in sheriff proper, it could very well just be another library, perhaps generated based on RFCs or something.<div class="im">
<br>
<br>
On 02/14/2012 04:24 PM, Tristan Sloughter wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
It would be nice if the validation of a type could be defined as a fun.<br>
<br>
I was going to build something similar to this for validation on models<br>
in a web framework. So for validating email addresses and things like<br>
that. More complicated than a simple type.<br>
<br>
Tristan<br>
<br>
On Tue, Feb 14, 2012 at 8:35 AM, Loïc Hoguin <<a href="mailto:essen@ninenines.eu" target="_blank">essen@ninenines.eu</a><br></div><div class="im">
<mailto:<a href="mailto:essen@ninenines.eu" target="_blank">essen@ninenines.eu</a>>> wrote:<br>
<br>
In the short term fixing bugs, adding the missing iolist() and<br>
iodata() validation and a couple other less documented types.<br>
<br>
In the long term it would be nice to find a way to generate<br>
validation functions also for types found in the Erlang libs, or at<br>
least a certain subset for the most used of the lot, like the<br>
calendar module for example.<br>
<br>
I'm open to any and all suggestions at this point.<br>
<br>
<br>
On 02/14/2012 02:38 PM, Ignas Vyšniauskas wrote:<br>
<br>
Hi,<br>
<br>
I'm confused why no-one is excited about this, this looks<br>
awesome! I am<br>
already looking forward to using this in our project.<br>
<br>
Loïc, are there any milestones/plans regarding further<br>
developement of this?<br>
<br>
Regards,<br>
Ignas<br>
<br></div><div class="im">
On <a href="tel:2012.02.13%2010" value="+12012021310" target="_blank">2012.02.13 10</a> <tel:2012.02.13%2010>:52, Loïc Hoguin wrote:<br>
<br>
Hello!<br>
<br>
We just released the first beta version of the sheriff parse<br>
transform.<br>
It allows you to validate data against types defined through<br>
the Erlang<br>
type system.<br>
<..><br>
<br>
<br>
<br>
--<br>
Loïc Hoguin<br>
Erlang Cowboy<br>
Nine Nines<br></div>
______________________________<u></u>___________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@<u></u>erlang.org</a>><br>
<a href="http://erlang.org/mailman/__listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/__<u></u>listinfo/erlang-questions</a><br>
<<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/<u></u>listinfo/erlang-questions</a>><br>
<br>
<br>
</blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
-- <br>
Loïc Hoguin<br>
Erlang Cowboy<br>
Nine Nines<br>
</div></div></blockquote></div><br></div>