jannchie / biliob_backend Goto Github PK

Error 500 when user is not exist

When add a new author or video, execute the crawler immediately.

Some author or video should be tracked more frequently.

The backend should handle the request and schedule the tracking task.

With the search function in https://www.biliob.com/author
If I type Lex,
I would see LexBurner and 萧忆情Alex, which name contains lex

But if I type 神楽めあ
https://www.biliob.com/api/author?page=0&text=神楽めあ&sort=0
There is no 神楽めあOfficial

But if I type 神楽めあOfficial
https://www.biliob.com/api/author?page=0&text=神楽めあofficial&sort=0
There she is...

It seems to be the problem of めあ
If I type 神楽 it works, めあ it does not.
https://www.biliob.com/api/author?page=0&text=神楽&sort=0
And with 神楽 it will also show me 神樂めあOfficiaI, which is not the same characters?

I believe this is not expected?

Front end search sample

let authors = {
  ...Array(10000)
  .fill()
  .map(() => String(Math.random()))
}

let search = string => {
  let keys = string.split('')
  let result = Object.keys(authors)
    .map(mid => ({ mid, index: 0, uname: authors[mid] }))
  keys.map(key => {
    result = result
      .map(object => {
        return ({
          ...object,
          index: object.uname.indexOf(key, object.index) + 1
        })
      })
      .filter(({ index }) => index)
  })
  return result
}

User's records save the user's operations result. It is necessary because users are able to launch tracking tasks asynchronously, which has the potential to fail.

By recording the operations of users, we can easily know how users spend credits and whether users execute the tasks correctly.

the Data of author or video could be very big. Then it will slow down the speed of client loading data.

So the backend should filter the data, reduce the number of being displayed data.