Re: [Openinteract-dev] Generic way to translate error messages

[Perrin H. <pe...@el...>]

Chris Winters wrote:
> The only problem with this is using an error code -- it doesn't
> immediately *feel* right to me. But I don't really see any way around
> this

The usual way to do it is to use constants, so you can say something 
like $INVALID_EMAIL_ADDRESS instead of 15387.  You could even use a name 
like that as the error's ID instead of a number.

> Using a database makes things easier for us -- no file locking issues,
> etc. -- so we'll almost certainly stick to it. I have some potential
> changes below.

Is it really necessary to use a database for this?  It seems like this 
would be a read-only file in production.  I think this could be done 
with a simple file structure, which would make it easy enough to edit by 
hand (while still allowing tools to be built) and avoid the performance 
issues.

Things like this straddle the line between templates and data.  In 
general, I like to put things on the file system when possible so that 
they're easy to get at.

- Perrin