e86108e18f
The article ID parser looks for a string at the end of a URL path with a bunch of hex digits. But it also has to handle user, tag, and search URLs. * /@ba5eba11 * /tag/0ddba11 * /search?q=ba5eba11 Some URLs are encoded as params. The parser used to look at the result of the path first, then the params. But paths that ended in `global-identity-2` messed that up because `2` is a hex digit at the end of the path. This changes the logic to parse params first and paths second which gets around this. |
||
|---|---|---|
| .. | ||
| article_id_parser.cr | ||
| embedded_converter.cr | ||
| gist_scanner.cr | ||
| gist_store.cr | ||
| markup_converter.cr | ||
| page_converter.cr | ||
| paragraph_converter.cr | ||
| rate_limited_gist_store.cr | ||