apply rules to do `.foo` vs `["foo"]`

Question

apply rules to do `.foo` vs `["foo"]`

caridy opened this issue 10 years ago · 5 comments

this surface today when trying to do something like this:

root.I13N_config.section.2sv = {"id":"module-2sv","pp":{}};

In theory, we should be able to construct the proper namespace.

Answer 1 · 2014-09-02T18:25:55.000Z

I don't understand the problem. Could you elaborate? The example code in the issue seems fine to me.

Answer 2 · 2014-09-02T19:34:48.000Z

Identifiers can't start with a number (2sv in caridy's example).

Answer 3 · 2014-09-02T20:03:42.000Z

Ah yes, so not a valid namespace. It was an explicit decision to only support namespacing, i.e. dot-notation in Express State. Reason being that usually it's an abuse of the library if need something more complex.

@caridy in this example can you explain why you can't do:

res.expose(i13n.config, 'I13N_config');

…instead of exposing two levels of sub-props?

Answer 4 · 2014-09-02T20:08:20.000Z

in this particular case, it is because sections is built by each individual parts of the page, adding page sections to that namespace, and it is actually sugared by something like this:

res.trackSection('sec-value', 'DOM-id', {});

which translate into the corresponding expose() call.

Answer 5 · 2014-09-03T15:50:59.000Z

I still don't think we should change how this package works to accommodate this change in definition of what a namespace is to Express State. A namespace should always be able to be accessed via dot notation — this change would conflate a namespace with data.