kotlin-result
redux
Our great sponsors
kotlin-result | redux | |
---|---|---|
35 | 268 | |
936 | 60,454 | |
- | 0.3% | |
8.8 | 9.0 | |
5 days ago | 5 days ago | |
Kotlin | TypeScript | |
ISC License | 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.
kotlin-result
-
JEP draft: Exception handling in switch
Author here. I have no idea what you could possibly mean with this comment. The coroutineBinding implementation correctly uses the coroutines API for parallel decomposition of Result bindings, exactly how the Kotlin Corotines guide tells you to (backed by a [Mutex](https://github.com/michaelbull/kotlin-result/blob/master/kot...)). The coroutineBinding isn't even the main selling point of the library, you can use it without using this feature entirely.
Please could you elaborate on what "looking thread safe" means to you? The only portion of the library that supports concurrency *is* thread safe - the unit tests prove it and the use of concurrency primitives such as Kotlin's Mutex are indicative of this. I truly have no idea how you've judged the entirely of the lbirary on whether it's "thread safe" when there is a single function that's related to concurrency and it is very clearly using concurrency primitives.
-
How do you define errors?
Sealed classes in combination with a library like https://github.com/michaelbull/kotlin-result will get you what you need. Essentially at that point you'll be doing error handling the way you would in Rust, where a 1-level deep sealed class containing data classes as children act as the root error type and each of its variants. If you have errors coming from two different domains you just create a wrapper error type for each domain.
-
Result Class with Generic Type for both Success and Failure States
This is a great result lib: https://github.com/michaelbull/kotlin-result
-
Is runCatching in use in any of your projects ? My team is abusing it
Lastly I do not like kotlin's Result and we use the kotlin-result library which is more expressive and not tied to Throwable (similar to Arrow's Either).
-
Struggling with software robustness with Kotlin
In my own code, I started to use explicit error handling. I'm currently experimenting with Result (from https://github.com/michaelbull/kotlin-result) and Raise (from https://arrow-kt.io/).
-
Thoughts on Kotlin Multiplatform?
un-related to multiplatform i've found it extremely helpful to wrap things in a Result type. If something can throw an error, it get's a Result return type. It sounds like that would help your use case too. The built in Result may be useful too
-
Programming with Result
This is a better impl.
- It seems like I'm forced to make this choice at least once a day
-
Are nearly all your functions suspend?
Using a result type can help to differentiate quite nicely. https://github.com/michaelbull/kotlin-result
-
Kotlin Nitpicks: Language and Standard Library
kotlin-result
redux
-
A Comprehensive Guide to React State Management
Redux
-
Full Stack Web Development Concept map
redux - Redux is a key tool used in managing state across an application. This can be used with any web technology including React, Vue and Angular docs
-
State Management Nx React Native/Expo Apps with TanStack Query and Redux
Redux is a client-state library.
- Redux 101
-
The 20 most used React libraries
react-redux: A powerhouse for efficient state management and data flow control. Learn more
-
React State Management in 2024
Reducer-based: requires dispatching actions to update a big centralised state, often called a “single source of truth”. In this group, we have Redux and Zustand.
- Redux Toolkit 2.0: new features, faster perf, smaller bundle sizes (plus major versions for all Redux family packages!)
-
Redux Toolkit 2.0: new features, faster perf, smaller bundle sizes, and more
I am _thrilled_ to announce that:
Redux Toolkit 2.0 is LIVE!!!
- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0
This major version has new features, faster perf, smaller bundle size, and removes deprecated options.
It's accompanied by majors for all our Redux family packages
## RTK 2.0:
- a new `combineSlices` method for lazy-loading reducers - Updates to `createSlice` to include a `selectors` field and allow defining thunks inside
- Immer 10 w/ faster updates
- Removal of deprecated options
See the migration guide:
- https://redux.js.org/usage/migrations/migrating-rtk-2
All of the Redux libraries now have modernized packaging with full ESM/CJS compat. They also ship modern JS (no transpiling for IE11), which means smaller bundle sizes.
We've also done byte-shaving work to shrink the bundles (extracting error messages, de-duping imports)
## Redux core 5.0:
- The TS conversion we did in 2019!
- Action types _must_ be strings
- `UnknownAction` as the default action type
- Better preloaded state types
- Internal subscription improvements
- Still marks `createStore` as deprecated!
- https://github.com/reduxjs/redux/releases/tag/v5.0.0
## React-Redux 9.0:
- *Now requires React 18 and RTK 2.0 / Redux 5.0*
-
HTML Data Attributes: One of the Original State Management Libraries
DEV is a Rails monolith, which uses Preact in the front-end using islands architecture. The reason why I mention all this is that it's not a full-stack JavaScript application, and there is no state management library like Redux or Zustand in use. The data store, for the most part on the front end, is all data attributes.
-
Blogged Answers: My Experience Modernizing Packages to ESM
Oh hey, that's my post!
(yes I spend too much time refreshing HN :) )
FWIW I did end up with a packaging combination that seems to work sufficiently. I never did fix the "FalseCJS" issue that `are-the-types-wrong` is detecting. I played with double-emitting TS typedefs, and the `tsup` tool _does_ actually have support for that now (added by Andrew Branch from the TS team). So it might be more feasible now. But ultimately I decided I was tired of messing with packaging setup and that what I've got is good enough. (hopefully)
We're actually about to launch Redux Toolkit 2.0 and Redux 5.0 this week, assuming the last couple pieces come together. Here's the latest RCs - you can see the current `package.json` files in there:
- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0...
- https://github.com/reduxjs/redux/releases/tag/v5.0.0-rc.1
What are some alternatives?
result4k
zustand - 🐻 Bear necessities for state management in React
kotlin-monads - Monads for Kotlin
remix - Build Better Websites. Create modern, resilient user experiences with web fundamentals.
Result - The modelling for success/failure of operations in Kotlin and KMM (Kotlin Multiplatform Mobile)
SWR - React Hooks for Data Fetching
Arrow Meta - Functional companion to Kotlin's Compiler
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla
Komprehensions - Do comprehensions for Kotlin and 3rd party libraries [STABLE]
swift-composable-architecture - A library for building applications in a consistent and understandable way, with composition, testing, and ergonomics in mind.
Kategory - Λrrow - Functional companion to Kotlin's Standard Library
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]