Open source contributionsSeries
What I learnt from developing a Slack app: part 2
Hi there! How are you? I hope you are well!
So, here I was jumping right to the task. But where does someone start?
Observation 1
The documentation for Slack apps is literally all over the place!! Parts are deprecated, parts are misleading and finally some parts are totally useless (sorry Slack). You have to make decisions based on false info or without info at all!!
Start
Eventually, I created a @slack/bolt application on glitch.com!! Go figure!! Let me see if I can find the link, ok I got it but it is not public and I do not want to expose any details since when I started I had some hard-coded values in order to create the skeleton of the app, its backbone per se: an end-to-end barebones but complete functionality. Here is a photo of the UI I was working on at that point:

Of course, if you can see on the file structure on the left, this is the last copy of my glitch experimentations, you can see also an SQLite db file there, which now is gone!! Also, the main file here is still the app.js, basically everything is on that one file and the environment variables are on the .env file.
How did we get here though? Of course, the answer is from Slack documentation, hurraaaay!
… and this is a list of (not all) bookmarks I had to save on the browser to navigate through the chaos:

But, this post is getting a bit long. Let’s wrap it up and continue on the next episode of the Slack app odyssey 😀 See ya 👋
Cheers