Many actions, like layer name changes or spelling errors cause CartoCSS strings to have inconsistent layer naming, both with the column name, and within the string itself. Windshaft ignores these problems, but our local parser is a bit more strict with layer naming. It doesn't need to be the same name as the table, but the name must be consistent within the CSS string.
Since there are a whole lot of examples with inconsistent naming, it'd probably be a good idea to handle it so that styles are correctly rendered anyway.
Many actions, like layer name changes or spelling errors cause CartoCSS strings to have inconsistent layer naming, both with the column name, and within the string itself. Windshaft ignores these problems, but our local parser is a bit more strict with layer naming. It doesn't need to be the same name as the table, but the name must be consistent within the CSS string.
Since there are a whole lot of examples with inconsistent naming, it'd probably be a good idea to handle it so that styles are correctly rendered anyway.