on master help sign in
notice for api in gall
commitb7a84ff4a91717ed478ddcc0af33a8eaf72dee74 authorjoshuareagan <joshuareagan@gmail.com> dateThu 4 Oct 2018, 18:16 (8 years ago) parent7ead3eb
1 file changed+3−7
docs/tutorials/gall/api.umd+3−7
docs/tutorials/gall/api.umd+3−7
@@ -7,6 +7,8 @@
77
88# API Connectors
99
10+> Note: This lesson depends on some code that needs to be updated before the examples will work correctly. This will be addressed in the near future. We apologize!
11+
1012Most people have lots of data stored in online services, many of
1113which have APIs. API connectors allow the user to access this
1214data from within their Urbit.
@@ -86,13 +88,7 @@ for a particular piece of data, while `%y` is a request for a
8688directory listing. Roughly, `%x` means Unix `cat` and `%y` means
8789Unix `ls`.
8890
89−> Sometimes you wish to expose a tree where a part of the path
90−> can't be enumerated. For example, a `%y` of `/issues/by-repo`
91−> "should" produce a list of all Github users, but we don't do
92−> that because it's too long. Instead, we just produce our own
93−> username (from the `web.plan` file). You can still access
94−> repos from other users, you just don't see them in the
95−> directory listing.
91+> Sometimes you wish to expose a tree where a part of the path can't be enumerated. For example, a `%y` of `/issues/by-repo` "should" produce a list of all Github users, but we don't do that because it's too long. Instead, we just produce our own username (from the `web.plan` file). You can still access repos from other users, you just don't see them in the directory listing.
9692
9793The usual flow for implementing this tree of data makes heavy use
9894of the `connector` library. This library is well documented in