API Breaking Changes: Method Names

[amark]

The internals are changing a bunch, but how you USE gun stays the same, with the EXCEPTION of some API renaming:

• .get will be renamed to .val
• .load will be renamed to .get
• .set will be renamed to .put
• .all will be introduced.

Are the major things, some minor details like .blank is being renamed .not or maybe depreciated.

[Xe]

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.

[amark]

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).

[metasean]

"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.

[amark]

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