Can we have a video on api naming for non CRUD operations or atleast what standard they used to follow at Google. Most videos or tutorials on the internet just cover the basic CRUD stuff. Would be really gratefuly if you can explain how to name apis for more complex use cases like file upload, file download, login, logout, reset password, send otp etc ie conventions for non crud operations.
@@harrydayexe let's say login.. i felt it's a non crud operation because all u create is a token.. u are not updating nor creating nor deleting a resource from the database.. let me know if my reasoning is wrong here
are you sure that new ArrayList(images) performs a deep copy? I just recently implemented this at my work & it didn't work. the ARRAYLIST was a new reference in memory, but each object in the list pointed to the exact same object as before. (Shallow copy vs deep copy). This is VERY important if you intend to modify the underlying objects! also: pin me please
It depends on the what the list stores. You're right that if it were a list objects, it would not perform a deep copy. If we were storing primitives like ints, it would create a deep copy. Strings are unique since they are immutable. Technically it's not a deep copy, but since the strings cannot be modified it doesn't matter in this case. But you're definitely correct to point it out.
