You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: