Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove workspace app references from docs #668

Merged
merged 2 commits into from
Jan 3, 2019
Merged

Conversation

jharrilim
Copy link
Contributor

Summary

  • Related issue: Remove workspace apps references from docs #656
  • References to xoxa tokens and workspace apps have been removed.
  • A warning is placed on the refresh token option that is available on the WebClient to notify users that it is only available on the legacy workspace apps preview.

Requirements (place an x in each [ ])

@codecov
Copy link

codecov bot commented Dec 7, 2018

Codecov Report

Merging #668 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #668      +/-   ##
==========================================
- Coverage   91.94%   91.92%   -0.02%     
==========================================
  Files           7        7              
  Lines         484      483       -1     
  Branches       90       90              
==========================================
- Hits          445      444       -1     
  Misses         22       22              
  Partials       17       17
Impacted Files Coverage Δ
src/logger.ts 89.47% <100%> (-0.27%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4024612...4d9caf3. Read the comment docs.


Our app has described which scope it desires in the workspace, but a user hasn't authorized those scopes for the development workspace yet. Scroll up and click "Install App". You'll be taken to your app installation page. This page is asking you for permission to install the app in your development workspace with specific capabilities. That's right, the development workspace is like every other workspace -- apps must be authorized by a user each time it asks for more permissions.

Go ahead and click "Continue". The next page asks you which conversations the app should be able to post messages in. In this case, choose "No channels", which still allows the app to directly message users who install the App -- which means you.

When you return to the OAuth & Permissions page copy the OAuth Access Token (it should begin with `xoxa`). Treat this value like a password and keep it safe. The Web API uses tokens to to authenticate the requests your app makes. In a later step, you'll be asked to use this token in your code.
When you return to the OAuth & Permissions page copy the OAuth Access Token (it should begin with `p`). Treat this value like a password and keep it safe. The Web API uses tokens to to authenticate the requests your app makes. In a later step, you'll be asked to use this token in your code.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "it should begin with xoxp" 😅


Our app has described which scope it desires in the workspace, but a user hasn't authorized those scopes for the development workspace yet. Scroll up and click "Install App". You'll be taken to your app installation page. This page is asking you for permission to install the app in your development workspace with specific capabilities. That's right, the development workspace is like every other workspace -- apps must be authorized by a user each time it asks for more permissions.

Go ahead and click "Continue". The next page asks you which conversations the app should be able to post messages in. In this case, choose "No channels", which still allows the app to directly message users who install the App -- which means you.

When you return to the OAuth & Permissions page copy the OAuth Access Token (it should begin with `xoxa`). Treat this value like a password and keep it safe. The Web API uses tokens to to authenticate the requests your app makes. In a later step, you'll be asked to use this token in your code.
When you return to the OAuth & Permissions page copy the OAuth Access Token (it should begin with `xoxp`). Treat this value like a password and keep it safe. The Web API uses tokens to to authenticate the requests your app makes. In a later step, you'll be asked to use this token in your code.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

amended fix for
(it should begin with p)
to
(it should begin with xoxp)

@@ -233,164 +231,6 @@ Note that when calling a method with no required arguments, you **still need to

---

### Using refresh tokens
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think removing this section (and the following section) would leave users who have already built a Workspace App without information about how these options work. Instead, I think we can add warnings (similar to how the reference documentation on the options to the constructor were given warnings) to help users understand that this usage only works with the now-deprecated workspace app tokens (xoxa).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good!

@@ -186,14 +184,14 @@ getAllChannels()

### Calling methods on behalf of users

When using [workspace tokens](https://api.slack.com/docs/working-with-workspace-tokens), some methods allow your app
to perform the action [on behalf of a user](https://api.slack.com/docs/working-for-users). To use one of these methods,
When using [User tokens/Personal tokens](https://api.slack.com/docs/token-types#user), some methods allow your app
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency, we should invent the new term "Personal tokens". Let's just stick with "user tokens".

@aoberoi
Copy link
Contributor

aoberoi commented Dec 14, 2018

@jharrilim thanks so much for contributing to making our documentation better and clearer. we really appreciate it.

i left a few comments about pieces i think we can improve upon. let me know how you feel about those -- if you could update the PR to address them it would be great!

@jharrilim
Copy link
Contributor Author

Sorry for taking awhile to update it. I made the requested changes. Happy holidays!

@aoberoi
Copy link
Contributor

aoberoi commented Jan 3, 2019

@jharrilim thanks so much for following through! 🙌

@aoberoi aoberoi merged commit 3bbba95 into slackapi:master Jan 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants