Harrison Healey

Funny you should mention that since it was the original vision of the package, but unfortunately, it got out of hand quickly with a huge amount of stuff being added...

I guess my core problem here is that I've never thought it was a good idea for plugins to import from the web app since it could affect stability of...

With it being out of date, I know that there's some new features certain plugins want to use, but I don't think that needs to be part of the starter...

Whoops. I submitted these in the wrong order 😛 That makes sense. I still have my doubts about whether most plugins will need the new stuff, but that's not my...

Yeah, we're continuing with the mattermost-webapp dependency, but I don't remember where we ended up on setting the version. No matter what version we set it to, it'll remain unchanged...

> Or is there any chance of making this an NPM package? The end goal will be a few smaller NPM packages that include the shared stuff we need without...

FYI, when we next update the web app package, we're going to start running into issues with importing parts of the webapp because of the monorepo. We'll likely going to...

@hanzei Perhaps what we could do is change the command to be like `/preferences get ` so the user can specify both? We could even extend it to allow printing...

Some preferences still have human-readable names like the `sidebar_settings` category has preferences named things like `close_unused_direct_messages` and `show_unread_section`. Since this is a demo plugin, I think it's fine if the...

Here's a recording I took in the MM desktop app since I do see it there as well. That's strange that it didn't repro for you. Perhaps it's something to...