Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

variables and properties should be case insensitive. #23

Open
cbueno opened this issue Jun 2, 2010 · 1 comment
Open

variables and properties should be case insensitive. #23

cbueno opened this issue Jun 2, 2010 · 1 comment

Comments

@cbueno
Copy link

cbueno commented Jun 2, 2010

I don't see a good reason for variables on template be case sensitive.

A issue example:

When get data from a database, append this data to a collection of objects (that map some database table) and then send this array of objects to h2o template, all the properties of my current object must respect the case sensitive to work properly. Unfortunately some times, change the case of table column name is necessary and it will make the h2o page brake, without either a warning or error message. The reason is because that column name (a property of object) was previously wrote with a different case.

@speedmax
Copy link
Owner

speedmax commented Jun 2, 2010

Hi cubeno,

Case sensitivity of record attribute is outside the scope of a template engine.

You could down case all the hash key or object attribute before you pass into h2o context, in this case you can use your preferred case in the template

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants