browser
snapbox
browser | snapbox | |
---|---|---|
3 | 6 | |
310 | 110 | |
0.0% | 1.8% | |
0.0 | 9.4 | |
over 1 year ago | 10 days ago | |
Elm | Rust | |
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
browser
-
Utilizing Elm in a Web Worker
What's going on here? First, we import Platform, which provides us with the function Platform.worker. Most of the time, when writing an Elm app, we're leaning on elm/Browser to create apps that bind to the DOM. But in this case, we don't have a DOM to bind to, so we utilize Platform to create a basic app that doesn't do that. worker takes three inputs: init, update, and subscriptions (it's basically the same as Browser.element, from our Main.elm example).
-
Great thanks to the rust community for having a book (sort of like the rust book) for some crates as well. Makes everything infinitely approachable
For example: https://package.elm-lang.org/packages/elm/browser/latest/
-
Functional Programming Languages Sentiment Ranking
A couple of problems that I faced recently were this one concerning long lists in debug mode (https://github.com/elm/browser/issues/90) and an IP address parsing oddity (https://github.com/elm/parser/issues/14#issuecomment-560092383).
snapbox
-
Announcing diff.rs!
If needed, here is an example of per-word diffing and highlighting of trailing newline differences.
-
Trycmd just ignores my tests
I see. I would try writing the same name as in your Cargo.toml. For example, if yours was toml [package] name = "caesor_cipher" I would try bin.name = "caesor_cipher" It seems that trycmd might ignore a test if the bin.name field is incorrect: https://github.com/assert-rs/trycmd/issues/105
-
Rust: A Critical Retrospective
I find rustdoc lacking for clap. rustdoc does a good job with API reference documentation and is improving in its handling of examples but derive reference and tutorial documentation are a weak point.
For examples, its improving with the example scraping work (e.g. https://docs.rs/clap/latest/clap/struct.ArgMatches.html#meth...) but testing of example is still lacking. I've written trycmd to help (https://github.com/assert-rs/trycmd).
For derive reference and tutorial documentation, your choices are
- A very long, hard to navigate top-level documentation, see https://docs.rs/structopt/latest/structopt/
- External documentation, see https://serde.rs/
- Dummy modules to store your documentation (I've seen this used but can't remember one off the top of my head)
For clap, my documentation examples are best served as programs and we've had a problem with these being broken. The Rust CLI book has a decent strategy for this by pulling in code from external files (https://rust-cli.github.io/book/index.html). I was tempted to do that for clap where example code and output (all verified via trycmd) are pulled into an mdbook site but I've stopped short and just have a README that links out to everything (https://github.com/clap-rs/clap/blob/master/examples/tutoria...). Its not great.
-
Great thanks to the rust community for having a book (sort of like the rust book) for some crates as well. Makes everything infinitely approachable
Another problem we found in clap was it was easy for our examples to build but harder to make sure they worked. This is why I wrote trycmd (example "tests").
-
ANN: `trycmd` v0.7.0 released!
Would love feedback on on some of the known questions or whatever else is on your mind!
-
trycmd: Snapshot testing for a herd of CLI tests
The design is inspired by trybuild with thought given to how mdBook books could pull in content so you can verify a code sample, the command for running it, and the output. In considering how to keep clap's website up-to-date, I had this idea and threw it together to see how well it works. Overall, seems good with room for improvement. I'll have to give this a try on a real world program soon.
What are some alternatives?
vite-elm-web-worker
clap-rs - A full featured, fast Command Line Argument Parser for Rust
typos - Source code spell checker
editsc - Survivalcraft world editor
biscuit - Biscuit research OS
vite-elm-template - A default template for building Elm applications using Vite.
steam-for-linux - Issue tracking for the Steam for Linux beta client
elm-vanilla-js-web-worker
cargo-public-api - List and diff the public API of Rust library crates between releases and commits. Detect breaking API changes and semver violations via CI or a CLI.
vite - Next generation frontend tooling. It's fast!
heapless - Heapless, `static` friendly data structures