crater
apollo-client-devtools
Our great sponsors
crater | apollo-client-devtools | |
---|---|---|
23 | 4 | |
610 | 1,473 | |
2.8% | 0.1% | |
7.8 | 9.5 | |
29 days ago | 4 days ago | |
Rust | TypeScript | |
- | MIT License |
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.
crater
-
Semver violations are common, better tooling is the answer
yup, they reference it as an inspiration: https://github.com/rust-lang/crater
it's probably impossible to automate an entire ecosystem, and there is value to enabling a tighter integration within a project ecosystem (a subset of the language ecosystem).
-
Trip Summer ISO C++ standards meeting (Varna, Bulgaria)
Rather than hypothesising about an imagined tool you could look at the actual tool which of course is in Rust's source code repo: https://github.com/rust-lang/crater
> new proposed C++ changes - are checked against only easily and "well-known" accessible package.
Now that I have, so to say, shown you mine, lets see yours. Where is the tool to perform these checks in C++?
-
GCC 13 and the state of gccrs
The "break things" part of "move fast" is not essential, Rust cares so much about breakage they literally compile and run the tests for every crate on crates.io and github using a tool called Crater. They do this just to test changes, even for stuff thats documented to be unstable, because thats just courtesy. And tooling makes it trivial to switch between Rust versions.
-
Do one thing, and do it well, or not.
The bot's named Crater if you want to look into it more.
-
Improving Rust compile times to enable adoption of memory safety
See https://github.com/rust-lang/crater
-
Discussion about the state of neovim's plugin ecosystem
Rust compiler developers use a tool called Crater to test potentially breaking compiler changes on all crates (Rust's name for libraries) uploaded to the official repository. If plugin stability is the issue, maybe a solution along these lines would be better than merging these plugins to Neovim's core?
-
Experienced C++ users: what do you like about Rust? How would you sell it to other C++ users?
https://github.com/rust-lang/crater is the bot they use to test proposed compiler/stdlib changes against slices of the crates.io library up to and including "all of it".
-
Data-driven performance optimization with Rust and Miri
The tool you're referring to is called Crater: https://github.com/rust-lang/crater.
- GHC 9.4.2 regresses being able to do math on aarch64
-
Rust for Linux officially merged
I'm pretty certain this isn't actually true. You should look at the editions, etc. Rust also has an insane guarantee which I am certain C/C++ don't offer: It rebuilds its entire library ecosystem each time it ships to make sure nothing breaks (https://crater.rust-lang.org). I've never seen an instance were old code didn't compile on a new compiler. Rust isn't forwards compatible (new code compiles on an old compiler) of course, but what is?
apollo-client-devtools
-
Using apollo client cache for local state
This call creates canonical field allTodos on the root Query type. We can confirm this by opening apollo devtools and viewing the 'cache' tab.
-
Did I break you? Reverse dependency verification
People don't understand how their code can mess up others in unexpected ways. A few weeks ago my youtube just stopped working. Turns out, a change made to the apollo-graphql extension caused window.process to be readonly and youtube's code was not expecting that: https://github.com/apollographql/apollo-client-devtools/issu...
I know this isn't a dependency issue, but it's a great example of why things like semver don't work perfectly in practice. It's hard to figure out what the effects of your code really are in the end. You might assume a change is minor when it really is major. I wish programming languages could figure out what the version change should be for a given code change.
-
Skruv - no-dependency, no-build, small JS framework
Do you perhaps use chrome and have apollo client dev tools installed? They break import maps, which breaks the site, see here: https://github.com/apollographql/apollo-client-devtools/issues/464
-
Using Apollo to mix local and remote fields using the @client directive
It's so weird that this seems like a common use case but across the 3 channels I've asked (also asked on the official Apollo Spectrum chat & SO) it's radio silence beyond your reply! To add insult to injury, Apollo devtools was updated over the weekend and broke for v2 clients! Argh!!
What are some alternatives?
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
ublacklist - Blocks specific sites from appearing in Google search results
actix-net - A collection of lower-level libraries for composable network services.
apollo-vue-devtools - Integrate GraphQL Apollo with Vue Devtools!
AutoMapper - A convention-based object-object mapper in .NET.
ideas2 - Another 85+ Ideas for Computing https://samsquire.github.io/ideas2/
rust-prehistory - historical archive of rust pre-publication development
Protobuf - Protocol Buffers - Google's data interchange format
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
searchkit - Search UI for Elasticsearch & Opensearch. Compatible with Algolia's Instantsearch and Autocomplete components. React & Vue support
NUnit - NUnit Framework
hacker-news-pro - A browser extension for creating Hacker News themes