Michael Snoyman | 30 Jul 20:28 2011

Re: [Yesod] Re: [web-devel] Question about changes in Yesod.Form.Fields

Greg's right: you won't be able to install Yesod without installing
the newest Persistent first. That can definitely be put into the
documentation... once we *have* some documentation on the new repo
setup.

Michael

On Sat, Jul 30, 2011 at 4:06 AM, Greg Weber <greg@...> wrote:
> I am unsure from your response whether you tried to install the latest
> version of Persistent. The previous error message stated you were missing 2
> of the latest persistent packages, so after those are installed you should
> at least have a different error message now. Or did you not want to install
> the latest version of persistent?
>
> On Fri, Jul 29, 2011 at 4:10 PM, Michael Litchard <michael@...>
> wrote:
>>
>> Thanks for the reply. But yesod 0.9.0 still won't install. This is the
>> goal. But only because I need Yesod.Fields.Form 0.3.0. This is the
>> larger goal. I need multiSelect. My reports thus far have been to help
>> out with beta testing. Let me know what you'd like me to try, I have a
>> fairly free weekend.
>>
>> On Fri, Jul 29, 2011 at 2:28 PM, Greg Weber <greg@...> wrote:
>> On Fri, Jul 29, 2011 at 2:28 PM, Greg Weber <greg@...> wrote:
>> > Hi Michael Litchard,
>> > I will let Michael analyze that dependency issue. For now you can also
>> > use
>> > the pre-release version of Persistent.
>> > git clone http://github.com/yesodweb/persistentfar
(Continue reading)

Michael Snoyman | 30 Jul 20:39 2011

Re: [Yesod] Render a formlet without running it

On Fri, Jul 29, 2011 at 5:25 PM, Paul Brauner <polux2001@...> wrote:
>> Check out this page:
>> http://www.yesodweb.com/wiki/non-standard-versions . It describes the
>> motivation for the versioning scheme and how to work around it.
>
> I was thinking: maybe you could have a meta package (a package with only
> dependencies, as yesod) called yesod-unstable that depends on the last most
> advanced consistent set of yesod-* packages?
> Paul

Ideally, I wish that Hackage would allow us to upload beta versions of
packages, but that doesn't seem to be happening. Another thing I'm
considering is having an even/odd version numbering scheme for
post-1.0, where 1.1 would be the devel branch of 1.0. But I'm not
certain of anything right now, and doubt we'll be making any changes
to our release approach until 1.0 is out the door.

Michael

Luite Stegeman | 31 Jul 12:42 2011
Picon

[Yesod] yesod-form validation

hi,

I've been trying to use yesod-form (0.2.0.1) in my web application,
but unfortunately I have run into some limitations. I'd like the form
library to handle more complex validation than it seems to be designed
for. While it's possible to handle all example situations (below)
outside the form library, I think it's much nicer if yesod-form
supported them directly, and this makes it much easier to display
validation error messages the same way as the field parser errors.

Please note that I'm still fairly new to yesod-form and to yesod in
general, so please correct me if things I say don't make sense or are
plainly wrong.

I'd like to see support for the following situations in applicative
forms:

1. Simple (pure) validation, for example a ranged integer field

2. Advanced validation: A date field that allows only dates in the
future, a username field that only allows usernames that aren't
already taken.

3. Form consistency: Are the contents of the two password fields the
same? Is the selected payment option compatible with the shipping
option?

I think none of these is properly supported by yesod-form:

1. While it's possible to do this with fieldParse, I think it's not
(Continue reading)

Michael Snoyman | 31 Jul 20:39 2011

Re: [Yesod] yesod-form validation

On Sun, Jul 31, 2011 at 1:42 PM, Luite Stegeman <stegeman@...> wrote:
> hi,
>
> I've been trying to use yesod-form (0.2.0.1) in my web application,
> but unfortunately I have run into some limitations. I'd like the form
> library to handle more complex validation than it seems to be designed
> for. While it's possible to handle all example situations (below)
> outside the form library, I think it's much nicer if yesod-form
> supported them directly, and this makes it much easier to display
> validation error messages the same way as the field parser errors.
>
> Please note that I'm still fairly new to yesod-form and to yesod in
> general, so please correct me if things I say don't make sense or are
> plainly wrong.

You're absolutely correct that the current design needs to be fixed,
and I'm very glad you've taken the time to address it.

> I'd like to see support for the following situations in applicative
> forms:
>
> 1. Simple (pure) validation, for example a ranged integer field
>
> 2. Advanced validation: A date field that allows only dates in the
> future, a username field that only allows usernames that aren't
> already taken.

It seems the only difference between these two is that (2) involves
monadic actions, right?

(Continue reading)


Gmane