Shorter access to encodings

[angiehjort]

you asked for things that are hard or annoying, so here is one

I find myself stumbling every time when typing marker.encoding.get("selected") as compared to marker.selected. Both in the code and in console when i want quick-check something. It's not only the length of a thing to type but also hitting "" and () correctly, which i can rarely do because i'm in a different keyboard layout or on a different keyboard. Additionally .get("selected") doesn't get auto-suggested by console, versus .selected.

I understand that the new way is dictated by a good architecture, but can there also be a shortcut somehow?

[jheeffer]

Understood and agreed!

…

On Thu, Dec 19, 2019, 09:33 Angie the Fairytale ***@***.***> wrote: you asked for things that are hard or annoying, so here is one I find myself stumbling every time when typing marker.encoding.get("selected") as compared to marker.selected. Both in the code and in console when i want quick-check something. It's not only the length of a thing to type but also hitting "" and () correctly, which i can rarely do because i'm in a different keyboard layout or on a different keyboard. Additionally .get("selected") doesn't get auto-suggested by console, versus .selected. I understand that the new way is dictated by a good architecture, but can there also be a shortcut somehow? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#23>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMFVJ2TNCXJX3EXHN3HJX3QZMWVPANCNFSM4J47QLXQ> .

[jheeffer]

Now it's marker.encoding.selected.

We could still see if we can create shortcuts such as marker.selected or marker.x.concept instead of marker.encoding.x.data.concept.