immutable.js

Consider the following code: const person = Immutable.Map({ name: 'John', surname: 'Maverick', age: 39 }); const mutated = person.deleteAll(['name', 'age']); Expected result would be that mutated now is a new instance of Map with the keys name and age deleted. However, throws an exception: Uncaught TypeError: person.deleteAll is not a function When inspecting the available methods of Immutable.Map prototype, there is no deleteAll nor removeAll methods. Have they been removed? The method is listed in the official ImmutableJS documentation, but it is not available. What would be a native

I would like to describe the shape of a map using Immutable's flow type definitions. You can describe the shape of an object by: const stateShape: { id: number, isActive: boolean } = { id: 123, isActive: true }; Is there something similar for Immutable's Maps? TL;DR; No, but using Records you can get Flow to typecheck the shape but not the types. Longform The correct answer would be: no, since maps don't have shapes (at least in Flow and Immutable) . But Immutable does have a type for "Maps" with shapes. That would be Records . But for reasons described below (since it's not strictly relevant)

I took a TodoList example to reflect my problem but obviously my real-world code is more complex. I have some pseudo-code like this. var Todo = React.createClass({ mixins: [PureRenderMixin], ............ } var TodosContainer = React.createClass({ mixins: [PureRenderMixin], renderTodo: function(todo) { return <Todo key={todo.id} todoData={todo} x={this.props.x} y={this.props.y} .../>; }, render: function() { var todos = this.props.todos.map(this.renderTodo) return ( <ReactCSSTransitionGroup transitionName="transition-todo"> {todos} </ReactCSSTransitionGroup>, ); } }); All my data is immutable,

Given my initial redux state is : const state = { currentView: 'ROOMS_VIEW', navbarLinks: List([ {name: 'Rooms', key: 'ROOMS_VIEW'}, {name: 'Dev', key: ''} ]), roomListsSelected: {group: 0, item: 0}, roomLists: [ { name: "Filters", expanded: true, listItems: [ { icon: 'images/icon-warning.svg', name: 'Alerts', filter: room => room.hasAlert }, { icon: 'images/icon-playlist.svg', name: 'In Progress', filter: room => room.progress > 20 }, { icon: 'images/icon-playlist.svg', name: 'Almost Done', filter: room => room.progress > 90 }, { icon: 'images/icon-playlist.svg', name: 'Complete', filter:

I have built my first React application with stateful stores the "normal" way, and now I am looking into using an immutable global state like used in the Este starterkit. The state of all stores is kept together in a single immutable data structure Components have no state but access data in their render() based on a store getter function Stores are also stateless but mutate the global application state for their domain using a cursor. The top level app component listens for state changes, and re-renders the whole component tree. Components are implemented as "pure" meaning they use

Redux framework is using reducers to change app state in response to an action. The key requirement is that a reducer cannot modify an existing state object; it must produce a new object. Bad Example : import { ACTIVATE_LOCATION } from './actions'; export let ui = (state = [], action) => { switch (action.type) { case ACTIVATE_LOCATION: state.activeLocationId = action.id; break; } return state; }; Good Example : import { ACTIVATE_LOCATION } from './actions'; export let ui = (state = [], action) => { switch (action.type) { case ACTIVATE_LOCATION: state = Object.assign({}, state, {