Search Results for "what changed"

...It can also annotate pull requests with comments that highlight how the bundle changed, making performance regressions visible to reviewers early. With the --why flag, size-limit can analyze what contributes most to bundle size and show a dependency breakdown (using Statoscope).

critique is a beautiful terminal-oriented user interface tool for reviewing git diffs that makes inspecting source control changes more intuitive and readable directly from the command line. The tool provides a styled, split-view diff layout with syntax highlighting and word-level diffing, which gives developers clear insight into what has changed in each file beyond simple line additions or deletions. It supports viewing diff ranges across commits, staged versus unstaged changes, and even comparisons between branches, turning the diff output into a more interactive, readable experience than traditional git diff. Critique is built with a terminal UI foundation and can also generate a web preview of diffs by converting ANSI escape codes into styled HTML, which can be shared temporarily via a cloud worker for collaborative review.

...This means that there are two sources of truth for your schema and changes in either have to be reflected in both locations. As your schema scales to hundreds of types and many different resolvers, it can get more difficult to track what code needs to be changed if you want to add a new field, deprecate or delete an existing one, or fix a bug in the resolver code. graphql-kotlin-schema-generator aims to simplify this process by using Kotlin reflection to generate the schema for you. All you need to do is write your schema code in a Kotlin class.

JVM-based program & library for installation testing. Helps determine what changed during an installation/removal or similar process. ChangeScan has been rewritten in Kotlin. Its new home is here: https://github.com/william-hood/ChangeScan

...It supports common patterns like reordering within a list, moving items between multiple lists, and integrating with virtualized lists. Clear lifecycle callbacks expose what changed during a drag so you can persist updates or trigger side effects reliably.

This project is a curated collection of readings, notes, and reflections on the evolution of books, publishing, writing tools, and reading habits. The repository engages both historical and contemporary perspectives—examining how the form of the book has changed from print to digital, how readers and authors interact in new environments, and what remains of the “book” metaphor. It includes commentary on writing platforms, self-publishing ecosystems, and design of reading experiences, making it useful to writers, educators, technologists, and book-enthusiasts alike. Rather than simply listing titles, the project links readings to categories like writing tools, reading devices, publishing models, and distribution systems, helping you place each resource in context. ...

JPPF makes it easy to parallelize computationally intensive tasks and execute them on a Grid.

Saros brings multi-writer synchronous distributed editing to the Eclipse IDE, e.g. for joint code reviews, explaining code remotely, or distributed pair programming -- all also for more than 2 participants; we call this Distributed Party Programming. It includes refined awareness functionality, text chat, and a simple distributed whiteboard/sketching facility. Eclipse Update Site: https://www.saros-project.org/update-site/eclipse

...It represents desired system state in a declarative model and coordinates agents to converge reality with that model, handling steps like install, start, verify, and promote. The system provides auditing and versioning of deployments, so operators can trace what changed, when, and why. A central console and APIs allow visualizing the topology, triggering rollouts, and performing controlled actions such as canaries and rolling updates. Under the hood it coordinates distributed nodes, tolerating partial failures while continuing to drive toward the target state. By separating deployment recipes from environment specifics, glu encourages repeatable, testable releases for multi-service stacks.

...It offers both top-down (mock-based) and bottom-up testing styles, helps ease migration from clojure.test, and promotes graceful syntax for developer-friendly test expression. Midje has loaded the tests and run them for the first time. It's also watching for file changes. When it sees them, it loads the changed files and any dependencies. But notice that you still have a repl prompt. That means you can move rapidly and smoothly among typing at the repl to try out code samples or look up documentation, having your editor send code snippets to the repl to evaluate, and saving source or test files to immediately see what passes or fails.

JDiff is a Javadoc doclet which emits an HTML report of all the packages, classes, methods, and so on, which are different (the "diff" part) when two Java APIs are compared. Great for reporting what has changed between two releases of your product.