supinic / supinic.com Goto Github PK

this line uses spaces while others use tabs

=>=> * ....
    * ...
=>=> * ....

space is a space 4HEad
=> is a tab :)

NotLikeThis

URL https://supinic.com/api/track/detail/:id is undocumented.
API endpoint https://supinic.com/api/track/list/:id (Tracka - Track - Get) looks similar.

The /:id route of the suggestion detail view clashes with the /stats route as stats is being treated as an ID. Due to this going to the stats view is impossible and returns a 404 - Invalid suggestion ID.
See suggestion ID 4169

In order to be able to merge most of supi-core with Supibot in the future, the website project must be refactored away from them.

Modules to go:

• AwayFromKeyboard (not present)
• Banphrase (not present)
• Channel (not present)
• ChatModule (not present)
• Command 340ff6b
• Filter (not present)
• Platform (not present)
• Reminder (not present)
• User 5ceceb7

S#5386 by supinic

In the Track detail route, add formatted video title name into the page's title for easier bookmarking and overall navigation.

The title is inserted into any endpoint's header in the header.pug view. You can easily add title by passing the title property into a render call.

S#5172 by just_che

have a button that directly goes to either the youtube/nicovideo link in your favorite playlist like there is in the general gachimuchi tracklist

S#5446 by supinic

have an addition to the website for trusted user to go through $tl images and flag them there

S#5414 by sylvand

Create a new detail route for bot-program which is going to display all relevant data for a given bot. You can use existing data from the list endpoint, as the bot-program API returns *.

For the detail page, use the generic-detail-table view as render target. For more info, check the project for example usages.

I want to fork this, but package.json is missing. Help.

When you visit the endpoint /bot/channel/detail/:id/alias/list and the provided :id (the provided channel) was not found, the api, that the endpoint calls, returns with data: null. However, in channel.js at line 169, we expect, that response.body.data is never null. But because it is null, the endpoint gives us a 500. (See error ID: 53550 for example)

I wasn't sure whether you want to just check for that case, when data is null, or rather change the api endpoint to return an empty array, if the channel was not found. That's why I didn't make any PR, so I'll leave the rest for you😃