Improved warnings if using Pages and input names are 'reserved/inuse' words #122
Originally created by Paul King.
If you have some html like this:
Then trying to have a Page object with the following:
Will get confused by 'title' as the accessor for getting the browser title. Also, 'content' and possibly others ('at', 'url' not tested).
The workaround is to just use another name but it would be nice if you received a better error message or warning. Currently you receive:
The text was updated successfully, but these errors were encountered:
Originally posted by Luke Daley.
We need to have a list of �reserved words� and consult them when parsing the content DSL to fail fast with a nice warning.
We could generate the list by reflecting on the Browser and Page classes, though there would be a performance cost. We might better generating the list and saving as a static data structure.