Authorization examples are different from real results

[Zrce]

Description

Describe your issue here.

What type of issue is this? (place an x in one of the [ ])

• bug
• enhancement (feature request)
• question
• documentation related
• testing related
• discussion

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

---

Steps to reproduce:

1. Go to https://slack.dev/bolt-js/concepts#authorization
2. Compare with result of app.client.oauth.v2.access
3. Adapt to real result objects

Expected result:

What you expected to happen

Documentation to use a real result object and the naming of the real results. e.g.

botToken: team.access_token,
botId: team.app_id,
botUserId: team.bot_user_id

It's likely that you store the full result in a database. Then the team id would also be

if ((team.team.id 

Actual result:

botToken: team.botToken,
botId: team.botId,
botUserId: team.botUserId

if ((team.teamId

[seratch]

👋 In the document page you mentioned, the installations is a pseudo in-memory database storing OAuth results, not the direct reference to oauth.v2.access results.

If you're looking for more realistic examples or information, check the implementation in pull request #479. The PR is going to introduce the built-in implementation of the authorization logics to Bolt for JS.

[seratch]

@Zrce Hello, are you still looking for more information here? If my previous comment is helpful or you're no longer working on this, could you close this issue?