Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monolith needs to become an importable crate #72

Open
snshn opened this issue Oct 11, 2019 · 4 comments
Open

Monolith needs to become an importable crate #72

snshn opened this issue Oct 11, 2019 · 4 comments
Labels
todo On the current to-do list for the project

Comments

@snshn
Copy link
Member

snshn commented Oct 11, 2019

Aside from being a CLI tool, monolith has potential to be used as a library and published on crates.io. For this feature to be implemented we first need to design API for monolith, for the most part how we provide options (instead of parameters via CLI).

@snshn snshn added the todo On the current to-do list for the project label Oct 11, 2019
@jirayutza1
Copy link

Aside from being a CLI tool, monolith has potential to be used as a library and published on crates.io. For this feature to be implemented we first need to design API for monolith, for the most part how we provide options (instead of parameters via CLI).

@snshn
Copy link
Member Author

snshn commented Dec 26, 2020

Big shout out and thanks to @jstasiak for releasing the monolith crate name for this project on crates.io!

@banool
Copy link

banool commented Jun 5, 2022

I see this is now an importable crate, but it seems like much of the functionality is held within main, which can't be imported and used easily. Has anyone had any luck with using this crate as a library?

@snshn
Copy link
Member Author

snshn commented Aug 16, 2022

Yeah.... so, about that... basically, before it could be used as a library, an API of sorts needs to be drafted, and it needs to be done in a way that allows people to build their own archiving tools, consistent with how other CLI crates expose their APIs, and follows good practices. In all honesty, it's really far down the current TODO list since the tool itself needs to get more features, some highly-requested stuff like support for MHT format, blacklisting domains, recursive saving of pages, etc. Slowly but surely it'll get there, ideally I'd really love to see Firefox use it as a way to save monolithic HTML documents without any external tools or services.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
todo On the current to-do list for the project
Projects
None yet
Development

No branches or pull requests

3 participants