James - very good news indeed! Giving a meaningful message for the missing ID should catch at least 80% of the errors - especially if you indicate which class has the problem.
Specific mapping errors that have given me grief in the short time I've been using FNH: 1. Trying to automap lists of simple value types (IList<float>, etc. http://stackoverflow.com/questions/1690775/how-do-you-automap-listfloat-or-float-with-fluent-nhibernate) 2. Trying to automap more than one list of the same type in a class (http://groups.google.com/group/fluent-nhibernate/browse_thread/thread/ 945b8bb9ddeebd4e?hl=en#) Now, someone could argue that these two scenarios are common enough that FNH should be able to automap them without special workarounds. (and I've tried to make that argument in the past - especially for lists of simple data types). But if that's not feasible, it would still be very desirable to get a meaningful error message when FNH can't successfully map these constructs, (or any others, for that matter). Finally, thanks again for all the great work you've done - and continue to do - on this project! -Tom On Feb 1, 4:07 pm, James Gregory <[email protected]> wrote: > Hey everyone, > > I've just committed a change to the master branch that might be of interest. > I've added a validation phase to FNH that aims to reduce the obtuse XSD > validation errors you can receive when you create invalid mappings. > Currently the only case that's supported is missing ids, but that also seems > to be the most common one anyway. When you update to the latest commit, > validation will be enabled by default. > > If anyone has any suggestions to errors they'd like to see caught, then > please leave a message. -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
