We should be able to assure unique ids for a given feature. We have the luxury and option to be able to parse the html for a given view and make sure each id reference is prefixed with a well defined feature path.
It can't have namespace - you might have the same view multiple times on the page. A unique identifier for the container should be established, this should then be part of the naming!
We should be able to assure unique ids for a given feature. We have the luxury and option to be able to parse the html for a given view and make sure each id reference is prefixed with a well defined feature path.
typical would be when we have a form input:
To ensure uniqueness in the DOM, we would like to have a more specific name, but this shouldn't be needed during development:
Would also have to be able to parse any knockout bindings relying on id i.e.:
attr