Node and OAuth on the Command Line -- Twin Cities Code Camp 2018

Node provided a way to bring JavaScript out of the browser and on to server and desktop. In addition to building web applications, now you can build command line interface applications using JavaScript! Come explore some tools and libraries that will help you in your development, and even learn how to complete an OAuth flow from the command line.

Transcript

1. Node and OAuth on the Command Line Scott McAllister @stmcallister
4. Why CLI? • Quick interactions with sheets and users • Great for prototyping • Shell scripting automation • Comfortable for IT admins already living in command line • Relatively small amount of dev work
5. Why Node? • JavaScript Ecosystem ◦ Large number of developers ◦ Large number of available libraries • npm - Platform independent package manager ◦ Largest package repository in the world • Runs well on all platforms -- macOS, Windows, Linux, etc • Shallow learning curve for JS developers
6. Why Node? • Important that it's easy to start hacking on a new command and contribute back. • Performance isn’t generally a big issue ◦ Usually just waiting on an API call • Not likely to contain complex code
7. NPMCompare Tool that allows you to compare the features of comparable npm packages https://npmcompare.com/compare/commander,minimist,nomnom,optimist,yar gs
8. Libraries • Commander • Inquirer • Fs-extra • Opn • Http
9. Commander.js • Parses command-line arguments and options • Able to handle Git-like subcommands ◦ sscli sheet list ◦ sscli auth login • Provides declarative and readable organization • Automatically generates help screens
12. sscli-sheet.js
13. sscli-sheet.js
14. sscli-sheet.js
15. sscli-sheet.js
16. lib/sheet.js
17. Inquirer.js Accepts various types of user input by providing an input prompt for your CLI applications
18. sscli-user.js
19. sscli-user.js
20. sscli-user.js
21. sscli-user.js
22. OAuth 2 • An open standard for providing secure access to user accounts on an HTTP service. • In other words, a user can get access to their data from a third-party application. • Limit user's scope of access
23. OAuth 2: What we need • Client ID • Client Secret • Redirect URL • Access Scopes
24. OAuth 2: What we need • Client ID • Client Secret • Redirect URL • Access Scopes
25. OAuth 2
26. OAuth 2 authenticate.js
27. OAuth 2 authenticate.js
28. OAuth 2 authenticate.js
29. OAuth 2 authenticate.js
30. OAuth 2 authenticate.js
31. OAuth 2 authenticate.js
32. OAuth 2
33. OAuth 2
34. OAuth 2
35. OAuth 2 authenticate.js
36. OAuth 2 authenticate.js
37. OAuth 2 authenticate.js
38. OAuth 2 authenticate.js
39. OAuth 2 authenticate.js
40. OAuth 2 authenticate.js
41. OAuth 2 authenticate.js
42. OAuth 2 authenticate.js
43. OAuth 2 authenticate.js
44. fs-extra Library for interacting with the file system. fs-extra adds file system methods that aren't included in the native fs library. Adds promise support to fs methods.
45. fs-extra authenticate.js
46. fs-extra authenticate.js
47. fs-extra authenticate.js
48. fs-extra authenticate.js
49. Further Reading Commander.js https://github.com/tj/commander.js Fs-extra https://www.npmjs.com/package/fs-extra
50. Further Reading google-apps-script CLI project (Google OAuth Example) https://github.com/maartendesnouck/google-apps-script Smartsheet-CLI https://github.com/smartsheet-samples/smartsheet-cli NPMCompare https://npmcompare.com/compare/commander,minimist,nomnom,optimist,yargs
51. Resources @SmartsheetDev https://developers.smartsheet.com https://github.com/smartsheet-samples/smartsheet-cli Scott McAllister @stmcallister