API Breaking Changes: Method Names about gun HOT 4 CLOSED

API breaking changes should be noted specifically on the release notes, but otherwise the changes and the underlying interfaces look fine, with the exception that changing the definition of get might be confusing. However seeing as we are pre-1.0 there's not a large impetus to care.

from gun.

Agreed on everything, including that the get change is really confusing. But I think it is ideal because now get is being used in a more "normal" sense (HTTP / REST) and the val is being more explicit (I want to get the VALUE of the data back, not the GUN reference to the data).

from gun.

"API breaking changes should be noted specifically on the release notes..." - Yes they should, and yes they will :-)

"... the changes and the underlying interfaces look fine, with the exception that changing the definition of get might be confusing." - It absolutely can be seen as confusing. I'm going to do my best in the documentation and release notes to minimize the confusion.

"However seeing as we are pre-1.0 there's not a large impetus to care." - These changes will still impact people's existing projects, so these aren't changes we're taking lightly. However, we agreed that we are pre-1.0, and we feel that in the long term these method names should be more clear.

from gun.

Has SOME documentation, but can always be improved #70. So I'm closing this.

from gun.