| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2026-05-09 | test: add second example + only test Parse | demo | |
| I have more confidence that Parse works (and works better than FindLinks), so I'm sticking with it. | |||
| 2026-05-09 | feat: implement "v2" | demo | |
| This is based on the Gophercises solution. | |||
| 2026-05-09 | feat: use better formatting when printing found links | demo | |
| 2026-05-09 | refactor: move tests to dedicated package | demo | |
| 2026-05-08 | test: start writing basic tests | demo | |
| I've also moved the html to the findlinks package directory for now. | |||
| 2026-05-08 | docs: add comments explaining the logic | demo | |
| 2026-05-08 | fix: use correct function name in doc comment | demo | |
| 2026-05-08 | feat: include link text in final output | demo | |
| This meant using the older-style node-iteration technique, instead of trying to one-shot it with html.Descendants. | |||
| 2026-05-08 | feat: use same trimmed n.Data inside business logic | demo | |
| 2026-05-08 | feat: print textnode ancestors only when textnode isn't "" | demo | |
| 2026-05-08 | feat: print ancestors when an html.TextNode is reached | demo | |
| 2026-05-08 | fix: move findlinks logic to findlinks.go | demo | |
| I had written everything inside doc.go by mistake. | |||
| 2026-05-08 | feat: separate into remote and local commands | demo | |
| I'd like to be able to read HTML locally as well. | |||
