guyben cdcd5c2a0e Remove the "create" funtion from the Resource JS class ... The original thought was that the actions you can do on a resource is: - create it - read it - update it (I guess you should have "delete" as well, but that isn't currently there) Although we use "read" and "update", we never use "create". So having it goes against the YAGNI principle :) Also, it had a bug: when sending a "create", the opt_newId in send_() would permanentily change the uri of the request, causing any subsequent request to go to the wrong endpoint. By removing the "create" we can simplify the rest of the code (the send_() function). ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=213029499		2018-09-14 21:29:57 -04:00
..
com/google/testing/builddefs	Format .bzl files with buildifier	2018-07-14 01:37:03 -04:00
google/registry	Remove the "create" funtion from the Resource JS class	2018-09-14 21:29:57 -04:00