Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Is there any chance that any time in the future someone is going to need to ever use the underlying API along with your wrapper, or consult the underlying API documentation? Commented Mar 15, 2020 at 20:52
  • @DaveG: Valid question, see edit. Commented Mar 15, 2020 at 21:43
  • If it's merely a bolt-on to another API, and there isn't any independent reason to adjust the terminology (such as an integration with a second API that uses conflicting terms), then it'd be better to just belt up and run with the existing terminology. Commented Mar 15, 2020 at 22:18
  • How about combining options 1 and 2 - stick with it, AND comment it? Commented Mar 16, 2020 at 9:41
  • 1
    @RobinBennett: That is option 1. Of course if I stick with it I'll add a comment somewhere saying "this is the wrong thing to do, but". Commented Mar 16, 2020 at 10:03