API method names

Hey there!

I am coming to the Choo universe (chooniverse?) from React and so far I like the lighter-weight approach. There were some confusing things about the Nanocomponent API that held me up a bit. I’m curious about the reasoning behind the API method names.

1. Why isn’t update() called something like shouldUpdate()? As a user, I would expect the component to re-render if I call this.update()
2. Why are the lifecycle methods all lowercase, but don’t use the on prefix? Is there a precedent for this? Same issue as above, where I would expect load() and unload() to do something different. Maybe it would make more sense to use mount / unmount since those terms are used elsewhere in the Choo documentation?

These questions may have simple answers but they weren’t obvious to me. Thanks for all your work!

[ungoldman]

Going to close this since changing method names in a future major release isn’t on the roadmap for now. Open to making this a priority if enough people feel it’s important.

Putting this issue to bed for now 🛌😴

[ungoldman]

Hi @blahah – I believe generally the idea was to follow existing conventions from the DOM spec. So createElement comes from document.createElement()