Relative links aren't detected from STDIN or local files

[nacnudus]

A similar issue was reported in #183 and addressed by #217. However, this doesn't work when files are passed into STDIN, or for local files.

lychee --dump --base https://www.example.com example.html # works
lychee --dump --base https://www.example.com example # doesn't work
cat example.html | lychee --dump --base https://www.example.com # doesn't work

Could this be fixed by having --base force HTML mode?

[mre]

That's a tricky one.
I thought about assuming html input if --base was a valid URL, but Markdown files can also contain relative links and be prefixed with a URL. So that alone is not a decision criteria.

lychee has an internal file-type hint, that we could expose on the CLI, even though it sounds like a workaround.

lychee/lychee-lib/src/types/input.rs

Lines 107 to 116 in 363b95f

	/// Lychee Input with optional file hint for parsing
	#[derive(Clone, Debug, PartialEq, Eq, Hash)]
	pub struct Input {
	/// Origin of input
	pub source: InputSource,
	/// Hint to indicate which extractor to use
	pub file_type_hint: Option<FileType>,
	/// Excluded paths that will be skipped when reading content
	pub excluded_paths: Option<Vec<PathBuf>>,
	}

I'm open for suggestions on how to make the file type explicit in an ergonomic way. Alternatively maybe I'm overlooking a possibility to make it work without any file type hints.

[nacnudus]

Thank you for responding so quickly. I've attempted to address this issue in #673.