https://yuque.com/cx5tg/dsts7/mid4h
I initially thought of the corresponding team (cx5tg) , knowledge base (dsts7) , and the random string of document (mid4h) matched through /: teamName/:baseName/:docName.

turns out it"s not. The reason comes from one of my operations:
I changed a letter from a random path ( https://yuque.com/cx5tg/dsts7/mid4h) into a https://yuque.com/cx5t/dsts7/mid4h, which shows 404. According to the previous idea, deleting a letter should still match, which made me realize that it is not that simple to match. The display of 404 makes me feel that all routes are generated in advance, of course, the Finch team will not do so. I try to determine whether the corresponding team of the path exists after I get the new path, and then jump 404. Although it can achieve the same effect, it really feels awkward. I wonder if anyone has studied the Finch or has a different opinion on this phenomenon?