You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea would be to somehow leverage the information in Hugo configuration and be able to at least, given the path on disk, understand what the permalink is. Then we could either cache it in memory or in the helper database. Seems easy enough. This would help with sending and receiving webmentions, as well as maybe other social protocols in the future.
The hard thing here is to determine the permalink without glue. With glue, it is always possible. But that's not good.
The text was updated successfully, but these errors were encountered:
There are two problems at play here:
Most things for me have a 1:1 location, but not the posts and the categories. There is a bit of glue to make this work:
eagle/core/parser.go
Lines 72 to 77 in 799ba83
eagle/cmd/eagle/broken-links.go
Lines 70 to 73 in 799ba83
Idea
The idea would be to somehow leverage the information in Hugo configuration and be able to at least, given the path on disk, understand what the permalink is. Then we could either cache it in memory or in the helper database. Seems easy enough. This would help with sending and receiving webmentions, as well as maybe other social protocols in the future.
The hard thing here is to determine the permalink without glue. With glue, it is always possible. But that's not good.
The text was updated successfully, but these errors were encountered: