It isn't unknown, or even bad practice, to have string values with dots in them when needed in Java to avoid collisions. For example, the package names of Android apps use that format, even though the dots in them mean nothing. Often a constant in a class will have the exact same String value as it's location:
package blah1.blah2;
class Blah3 {
private static final String BLAH_KEY = "blah1.blah2.Blah3.BLAH_KEY"
Which helps a lot when you see the value somewhere else as well. Often if you are told to put some String keyed values into a general purpose message container going to another program, the string keys you use again use values to look like that to avoid collision, as recommended by the Android documentation itself. Similarly used for persisting application values to a single XML file. Then of course we also have technologies like GWT, where programmers write in Java, and it is compiled to JavaScript. I could easily see that generating property names with packages in them.
So anyway, you see dots for sub-objects, but you also see dots simply as part of a way to avoid name collisions, as in Java package naming and sharing String key namespace best practices. Just because it isn't used for sub-objects or method calls or properties doesn't mean it is wrong or bad.
hey, I'm the author of the article. I didn't write that using dots in the property name is a bad practice, but rather that other parts of the code let me assume that they didn't know a lot about js
package blah1.blah2; class Blah3 { private static final String BLAH_KEY = "blah1.blah2.Blah3.BLAH_KEY"
Which helps a lot when you see the value somewhere else as well. Often if you are told to put some String keyed values into a general purpose message container going to another program, the string keys you use again use values to look like that to avoid collision, as recommended by the Android documentation itself. Similarly used for persisting application values to a single XML file. Then of course we also have technologies like GWT, where programmers write in Java, and it is compiled to JavaScript. I could easily see that generating property names with packages in them.
So anyway, you see dots for sub-objects, but you also see dots simply as part of a way to avoid name collisions, as in Java package naming and sharing String key namespace best practices. Just because it isn't used for sub-objects or method calls or properties doesn't mean it is wrong or bad.