endlesstrax/pyanchor

Find your broken links, so users don't.

pyanchor's Issues

Track broken link origin

When a broken link is found, then a user should be able to track the origin of the link. Especially when dealing with large sets of links from a sitemap, for instance.

Make default output use `rich`

Enhance default table output with the very popular rich project - https://rich.readthedocs.io/en/latest/

Package into an executable file

Provide a standalone .exe for easier distribution. This will allow it to be added to package managers as well as make it useful for non-python devs.

Update usage Gifs

Update usage gifs for current release versions.

Allow result to be output into a `csv`

The user should have the option to output the results to a CSV file instead of the default terminal Table

Rename `master` branch to `main`

Start Test Web app on a subprocess

Currently, to test PyAnchor, the testing Flask app needs to be started in a separate terminal session before tests can be run against it.

Ideally the test suite should do this automatically, and end the process when testing is complete.

Documentation for Contributing / Testing PyAnchor

Contribution and "How to Test" documentation needed for future contributors.

Add LinkAnalysis feature to CLI

Add the ability to run LinkAnalysis over a set of anchor tags from the CLI.

Should output the results in an easy to read format, such as a table.

Dealing with relative links

Currently the check_link_for_http_scheme method in the LinkResults class returns None when it sees a relative link starting with a ./ or ../. Same applies to links that start with #.

This links should be parsed and a full URL determined so that it can be passed to the final links dictionary.

Parse sitemap of sitemaps.

Not all sitemaps are a list of pages on a website. For larger sites, the main sitemap may be a list of sub-sitemaps. This is sometimes common with CMS frameworks.

PyAnchor should be configured to work with this multiple sitemap structure.

Distribute via `winget`

Depends on #35.

Terminal colorization inconsistent

It appears that the terminal colorization provided by Typer (which is inherited from Click) doesn't display on all terminals. Most notably, PowerShell and CMD.