Correct inconsistent Markdown in the Redux-Ecosystem-Links Repo

[dberget]

Currently the Redux-Ecosystem-Links repo has some inconsistencies in the markdown formatting that prohibits the parser from making a consistent JSON structure.

The normal pattern that the parser expects is :

<h3></h3> at the top of the page for the main category name. Only 1 per page. <h4></h4> for each subcategory.

For every repository, the valid structure is: A paragraph. Bold title string. Linebreak. Valid GitHub repo URL string. Linebreak. Description string.

Example of correct MD structure:

### Component/Local State and Encapsulation

#### Component/Local State

- **redux-ui**  
  https://github.com/tonyhb/redux-ui  
  Easy UI state management for react redux.  Think of redux-ui as block-level scoping for UI state.

- **redux-react-local**  
  https://github.com/threepointone/redux-react-local  
  Creates component wrappers with per-instance local state stored in Redux, as well as locally scoped actions and reducers

- **redux-component**  
  https://github.com/tomchentw/redux-component  
  Manage a component's local state using a local redux store.  A isolated redux store is created for each React component instance.

#### Simplified / Key-Value State

- **Redux Cursor**  
  https://github.com/Dashlane/redux-cursor  
  Local private slices of a global store for component encapsulation in a Redux model.  Redux does not like the cursors in their general implementation, but the criticism is focused purely on the low-level ability to mutate the state at will. redux-cursor resolves that by relying on actions just as base Redux.

- **redux-mount**  
  https://github.com/popc0rn/redux-mount  
  Mount data on a path and change state values on the fly. No need to create reducers, actions, or selectors to handle view-specific state yourself.

- **reduceless**  
  https://github.com/nosovsh/reduceless  
  Redux helpers to avoid odd reducers, actions and constants.  Specify a path into your state, get it passed in and a setter to update it.

List of Pages With Issues

The parser identified the following pages with errors, we'll have to go through and manually tweak each one as necessary to match the correct pattern. There will be some cases which will require more discussion and possibly changes to the parser if appropriate. Lets open up an issue as those come up.

• [ ] action-reducer-generators.md

Repository Fredux of subcategory Boilerplate Reduction and Simplification has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] actions.md

Repository to-redux-type of subcategory Action Creation Utilities has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] apps-and-examples.md

Repository Redux Saga Examples of subcategory Purpose-Built Demos and Examples has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Redux Counter Example of subcategory Purpose-Built Demos and Examples has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Firefox DevTools - Memory Tool and Debugger of subcategory Applications has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository CarteJaune of subcategory Applications has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Linode Manager of subcategory Applications has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Winamp2-js of subcategory Applications has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository "Ask HN: Open source projects written in React?" of subcategory Other Application Lists has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository React Apps and Libraries List of subcategory Other Application Lists has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Twitter: mobile.twitter.com of subcategory Redux Usage Stories has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Lystable: Real World Redux of subcategory Redux Usage Stories has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository KarmaCRM: Launching an Enterprise React & Redux App – Part 1 of subcategory Redux Usage Stories has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository WaveHQ of subcategory Redux Usage Stories has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Neos CMS Goes for a Full UI Rewrite with React and Redux of subcategory Redux Usage Stories has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Reddit frontend engineering team AMA of subcategory Redux Usage Stories has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Redux for Realtime Gaming of subcategory Redux Usage Stories has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] component-state.md

Repository Redux "subapps" example of subcategory Component/Local State has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-container-state of subcategory Component/Local State has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-internal-state of subcategory Component/Local State has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-doghouse of subcategory Component/Local State has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-atom of subcategory Component/Local State has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-features of subcategory Modularity and Encapsulation has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-modules-enhancer of subcategory Modularity and Encapsulation has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] devtools.md

Repository reselect-tools of subcategory DevTools has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository purityWarningReduxConnect of subcategory Mutation Detection has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository mutation-sentinel of subcategory Mutation Detection has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. A <h4> is not followed by repositories. Repository react-transform-render-visualizer of subcategory Component Update Monitoring has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository "WhyDidYouUpdateMixin" of subcategory Component Update Monitoring has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository react-wastage-monitor of subcategory Component Update Monitoring has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] immutable-data.md

Repository Immutable.js of subcategory Immutable Data Structures (Specialized) has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository immutability-helper of subcategory Immutable Update Utilities has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository blazing-edge/update of subcategory Immutable Update Utilities has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-tcomb-actions of subcategory Immutable/Redux Interop has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository reduxdb of subcategory Alternate Data Management Concepts has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] library-integration.md

Repository number 1 of subcategory React has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] middleware-async.md

Repository redux-awaiter of subcategory Promises has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-queue-offline of subcategory Timeouts and Delays has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] middleware-network-requests.md

<h3> appears more than once.

• [ ] middleware-sockets-adapters.md

Repository redux-socket.io-connect of subcategory Websockets has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] middleware.md

Repository redux-aop of subcategory Action Grouping and Interception has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] other-resources.md

Repository Redux Docs: Ecosystem of subcategory Redux Links has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Reactiflux of subcategory Redux Links has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Black Pixel Redux Handbook of subcategory Community-Defined Standards has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] reducers.md

Repository redux-merge-reducers of subcategory Reducer Utilities has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository combineMultiKeyReducers of subcategory Reducer Utilities has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-exr of subcategory Reducer Utilities has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. <h4> is not followed by repositories. Repository redux-operations of subcategory Advanced Reducer Use Cases has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-list-reducer of subcategory Advanced Reducer Use Cases has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-reducer-factory of subcategory Advanced Reducer Use Cases has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository reducer-generator of subcategory Advanced Reducer Use Cases has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository sliced-redux of subcategory Dynamic Reducer Injection has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-reducers-injector of subcategory Dynamic Reducer Injection has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-async-injector of subcategory Dynamic Reducer Injection has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] side-effects.md

Repository redux-thunk of subcategory Widely Used Tools has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository number 1 of subcategory Side Effect Libraries By Approach has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository number 2 of subcategory Side Effect Libraries By Approach has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository number 3 of subcategory Side Effect Libraries By Approach has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository number 4 of subcategory Side Effect Libraries By Approach has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] store-persistence.md

Repository redux-offline of subcategory Persistence Libraries has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-persist-migrate-semver of subcategory Redux-Persist Addons has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] store.md

Repository redux-live of subcategory Synchronization has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Redux Share of subcategory Synchronization has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-bolt of subcategory Synchronization has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-dispatch-monitor of subcategory Other has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] testing.md

Repository redux-actions-assertions of subcategory Actions has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] use-cases.md

<h3> appears more than once. Repository redux-dag-history of subcategory Undo-Redo has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] utilities.md

Repository bo-selecta of subcategory Selectors has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository red-ux of subcategory Selectors has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository redux-fun of subcategory Functional Programming has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

• [ ] widgets.md

Repository react-redux-idle-monitor of subcategory Assorted Components has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository react-block-ui of subcategory Assorted Components has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string. Repository Repanel of subcategory Layout has wrong structure. It should be : paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string.

[wilbertliu]

Hey @dberget, thanks for pointing this out! 🙂 I think what we can do here as an “outsider” of the redux-ecosystem-link project is to make workarounds from time to time, which is ineffective to reach a state where all of the data could be parsed appropriately.

The best way I can think at the moment is to put an issue inside the redux-ecosystem-link instead, so that people at there could aware of what’s the state here and perhaps would fix their markdowns or searching for other solution.

Cheers! 🍻

[markerikson]

It would be helpful to see what the inconsistencies actually are. How many of them are non-Github-repo links, vs missing whitespace, vs something else? Could you tweak the parser to print out what it saw vs what was next expected?

[wilbertliu]

I don’t think knowing deeper than what we’ve known through the current robot is necessary, @markerikson. If not, feel free to mention why do you need that and some use cases, that would be more helpful to us. 🙂

I said so because we already have some clues on repos that have problems and what we expect as the correct format. Wouldn’t it enough to open the respective markdown that has errors and fix the repos directly according to the proper format that the robot has given? Unless you expect the fix should be done by the robot as well, which is not the focus of this project.

[markerikson]

@wilbertliu : there's several dozen items listed that don't fit the expected structure. Seeing the same "should be paragraph -> bold title string -> linebreak -> valid github repo url string -> linebreak -> description string" doesn't really help, because that's the same expectation every time. If we're going to run an automated check, it's more helpful to print what the single next expected token/item should be, and what it actually found instead.

Some of those inconsistencies are "expected". For example, I know that the "Apps and Examples" page has a bunch of links to non-repo pages in it, like some Twitter threads.

I also know I have a few places where I link to other related categories, and I suspect some of those are showing up in here.

I'm definitely in favor of cleaning up any real problems, but I want to see which items are real problems first.

[dberget]

I made some updates to the validator and I've got it working a bit closer to what you are suggesting @markerikson. It shows the current structure of any repos with errors now.

I also removed the specific github url check and it brought the error count down by quite a bit. Non-github links work just fine in the actual app so they shouldn't count as an error here in my opinion.

action-reducer-generators.md

• Boilerplate Reduction and Simplification: Fredux Header: strong,Fredux linebreak Link: https://github.com/trabe/fredux linebreak Description: https://github.com/trabe/fredux-api-utils

actions.md

• Action Creation Utilities: to-redux-type Header: strong,to-redux-type linebreak Link: https://github.com/Dash-OS/to-redux-type linebreak Description: Converts camelCase to SCREAMING

apps-and-examples.md

• Purpose-Built Demos and Examples: Redux Saga Examples Header: strong,Redux Saga Examples linebreak Link: https://github.com/kuy/redux-saga-examples linebreak Description: http://kuy.github.io/redux-saga-examples/

• Applications: Firefox DevTools - Memory Tool and Debugger Header: strong,Firefox DevTools - Memory Tool and Debugger linebreak Link: https://dxr.mozilla.org/mozilla-central/source/devtools/client/memory linebreak Description: https://dxr.mozilla.org/mozilla-central/source/devtools/client/debugger

• Applications: CarteJaune Header: strong,CarteJaune linebreak Link: https://github.com/nikgraf/CarteJaune A React Native/Redux (+Saga) application to keep track of your vaccinations undefined Description: undefined

• Applications: Linode Manager Header: strong,Linode Manager linebreak Link: https://github.com/Linode/manager linebreak Description: https://engineering.linode.com/2016/05/16/Announcing-the-new-open-source-manager.html

• Applications: Winamp2-js Header: strong,Winamp2-js linebreak Link: https://jordaneldredge.com/projects/winamp2-js/ linebreak Description: https://github.com/captbaritone/winamp2-js

• Applications: pixelpusher Header: strong,pixelpusher linebreak Link: https://github.com/automerge/pixelpusher linebreak Description: https://medium.com/@pvh/pixelpusher-real-time-peer-to-peer-collaboration-with-react-7c7bc8ecbf74

• Other Application Lists: React Apps and Libraries List Header: strong,React Apps and Libraries List linebreak Link: https://gist.github.com/sAbakumoff/7b8510adcb16bded189d747e34f5e114 linebreak Description: https://medium.com/@sAbakumoff/react-entourage-6d51e7df9944

• Redux Usage Stories: Reddit frontend engineering team AMA Header: strong,Reddit frontend engineering team AMA linebreak Link: https://www.reddit.com/r/webdev/comments/5c2vie/were em,reddits Description: frontend

component-state.md

• Component/Local State: redux-container-state Header: strong,redux-container-state linebreak Link: https://github.com/HansDP/redux-container-state linebreak Description: https://github.com/HansDP/redux-container-state-globalstate

• Component/Local State: redux-internal-state Header: strong,redux-internal-state linebreak Link: https://github.com/josepot/redux-internal-state linebreak Description: https://github.com/josepot/react-redux-internal-state

• Component/Local State: redux-doghouse Header: strong,redux-doghouse linebreak Link: https://github.com/DataDog/redux-doghouse linebreak Description: http://engineering.datadoghq.com/redux-doghouse--creating-reusable-react-redux-components-through-scoping/

• Component/Local State: redux-atom Header: strong,redux-atom

https://github.com/bulicmatko/redux-atom Link: linebreak https://github.com/bulicmatko/react-redux-atom Description: linebreak

• Modularity and Encapsulation: redux-features Header: strong,redux-features linebreak Link: https://github.com/jcoreio/redux-features linebreak Description: https://github.com/jcoreio/react-redux-features

• Modularity and Encapsulation: redux-modules-enhancer Header: strong,redux-modules-enhancer linebreak Link: https://github.com/BEllis/redux-modules-enhancer linebreak Description: https://github.com/BEllis/react-redux-module

devtools.md

• DevTools: reselect-tools Header: strong,reselect-tools linebreak Link: https://github.com/skortchmark9/reselect-tools linebreak Description: https://github.com/skortchmark9/reselect-devtools-extension

• Mutation Detection: purityWarningReduxConnect Header: strong,purityWarningReduxConnect linebreak Link: https://gist.github.com/lelandrichardson/ff2392199b62c26759f2bf235676758b linebreak Description: A shallow-equality comparison function and wrapper for

• Mutation Detection: mutation-sentinel Header: strong,mutation-sentinel linebreak Link: https://github.com/flexport/mutation-sentinel linebreak Description: https://flexport.engineering/optimizing-react-rendering-part-2-7b2e9a9ea21f

• <h4> is not followed by repositories.

• Component Update Monitoring: react-transform-render-visualizer Header: strong,react-transform-render-visualizer linebreak Link: https://github.com/spredfast/react-transform-render-visualizer linebreak Description: A react-transform version of the render visualizer. Transforms

• Component Update Monitoring: react-wastage-monitor Header: strong,react-wastage-monitor linebreak Link: https://github.com/MalucoMarinero/react-wastage-monitor linebreak Description: https://blog.listium.com/introducing-react-wastage-monitor-404565d679b2

• Component Update Monitoring: shallow-equal-explain Header: strong,shallow-equal-explain linebreak Link: https://github.com/OliverJAsh/shallow-equal-explain linebreak Description: A function that returns an object explaining the difference (instead of the usual boolean). Useful for debugging React

immutable-data.md

• Immutable Update Utilities: immutability-helper Header: strong,immutability-helper linebreak Link: https://github.com/kolodny/immutability-helper linebreak Description: "React Immutability Helpers" most likely are

• Immutable Update Utilities: power-assign Header: strong,power-assign linebreak Link: https://github.com/phenyl-js/phenyl/tree/master/modules/power-assign Immutable updater of POJO using MongoDB's operator, easier access to nested values. undefined Description: undefined

• Immutable Update Utilities: blazing-edge/update Header: strong,blazing-edge/update linebreak Link: https://github.com/blazing-edge-labs/update linebreak Description: https://blog.blazingedge.io/immutable-update/

• Alternate Data Management Concepts: reduxdb Header: strong,reduxdb linebreak Link: https://github.com/wizawu/reduxdb linebreak Description: Redux with MongoDB-like API. Dispatches internal Redux actions in response to API calls like

library-integration.md

• React: number 1 Header: React-Redux undefined Link: undefined undefined Description: undefined

middleware-async.md

• Promises: redux-awaiter Header: strong,redux-awaiter linebreak Link: https://github.com/yenshih/redux-awaiter linebreak Description: A Redux middleware for giving opportunities to await and receive actions in anywhere. Allows use of

• Timeouts and Delays: redux-queue-offline Header: strong,redux-queue-offline linebreak Link: https://github.com/mathieudutour/redux-queue-offline linebreak Description: https://github.com/mathieudutour/redux-queue-offline-listener

middleware-network-requests.md

• <h3> appears more than once.

middleware-sockets-adapters.md

• Websockets: redux-socket.io-connect Header: strong,redux-socket.io-connect

https://github.com/michaelmitchell/redux-socket.io-connect Link: linebreak Relays Redux actions to the server, where reducer-like "handlers" can execute server code and dispatch actions back to the client. Description: undefined

middleware.md

• Action Grouping and Interception: redux-aop Header: strong,redux-aop linebreak Link: https://github.com/modernserf/redux-aop linebreak Description: Aspect-Oriented Programming helpers for Redux middleware. This is a collection of helper functions (or "combinators") for common patterns in redux middleware. It borrows ideas and terminology from Aspect-Oriented programming, and may remind you of alias

reducers.md

• Reducer Utilities: redux-merge-reducers Header: strong,redux-merge-reducers linebreak Link: https://github.com/kuy/redux-merge-reducers linebreak Description: A utility to chain reducers instead of combining them by slice. Similar to

• Reducer Utilities: redux-exr Header: strong,redux-exr linebreak Link: https://github.com/paska27/redux-exr linebreak Description: A set of

• <h4> is not followed by repositories.

• Advanced Reducer Use Cases: redux-operations Header: strong,redux-operations linebreak Link: https://github.com/mattkrick/redux-operations linebreak Description: https://medium.com/@matt.krick/solving-redux-s-shortcoming-in-150-locs-540979ce6cf9

• Advanced Reducer Use Cases: redux-reducer-factory Header: strong,redux-reducer-factory linebreak Link: https://github.com/mclauia/redux-reducer-factory linebreak Description: https://github.com/mclauia/redux-reducer-meld

• Advanced Reducer Use Cases: reducer-generator Header: strong,reducer-generator linebreak Link: https://github.com/Dash-OS/reducer-generator-array-map linebreak Description: https://github.com/Dash-OS/reducer-generator-object-map

• Dynamic Reducer Injection: sliced-redux Header: strong,sliced-redux linebreak Link: https://github.com/carnesen/sliced-redux linebreak Description: A store enhancer that adds an

• Dynamic Reducer Injection: redux-reducers-injector Header: strong,redux-reducers-injector linebreak Link: https://github.com/GuillaumeCisco/redux-reducers-injector linebreak Description: https://github.com/GuillaumeCisco/redux-sagas-injector

• Dynamic Reducer Injection: redux-async-injector Header: strong,redux-async-injector linebreak Link: https://github.com/webliving/redux-async-injector linebreak Description: A store creation wrapper function that makes an

side-effects.md

• Widely Used Tools: redux-thunk Header: strong,redux-thunk linebreak Link: https://github.com/gaearon/redux-thunk linebreak Description: The simplest possible side effects approach: dispatch functions instead of objects, which then get access to

• Side Effect Libraries By Approach: number 1 Header: [object Object] Side Effects - Functions Link: undefined undefined Description: undefined

• Side Effect Libraries By Approach: number 2 Header: [object Object] Side Effects - Generators Link: undefined undefined Description: undefined

• Side Effect Libraries By Approach: number 3 Header: [object Object] Side Effects - Observables Link: undefined undefined Description: undefined

• Side Effect Libraries By Approach: number 4 Header: [object Object] Side Effects - Reducers/Other Link: undefined undefined Description: undefined

store-persistence.md

• Persistence Libraries: redux-offline Header: strong,redux-offline linebreak Link: https://github.com/jevakallio/redux-offline linebreak Description: https://github.com/redux-offline/redux-offline

store.md

• Synchronization: redux-live Header: strong,redux-live linebreak Link: https://github.com/eitak/redux-live linebreak Description: https://github.com/eitak/redux-live-localdb

• Synchronization: Redux Share Header: strong,Redux Share linebreak Link: https://github.com/baptistemanson/redux-share-server linebreak Description: https://github.com/baptistemanson/redux-share-client

• Synchronization: redux-bolt Header: strong,redux-bolt linebreak Link: https://github.com/vvinhas/redux-bolt linebreak Description: https://github.com/vvinhas/redux-bolt-server

testing.md

• Actions: redux-actions-assertions Header: strong,redux-actions-assertions linebreak Link: https://github.com/redux-things/redux-actions-assertions linebreak Description: https://github.com/redux-things/redux-actions-assertions-js

use-cases.md

• <h3> appears more than once.
• Undo-Redo: redux-dag-history Header: strong,redux-dag-history linebreak Link: https://github.com/Microsoft/redux-dag-history linebreak Description: https://blog.atsid.com/exploring-interaction-history-d09a52a7d186

utilities.md

• Selectors: bo-selecta Header: strong,bo-selecta linebreak Link: https://github.com/hnrysmth/bo-selecta linebreak Description: Syntactic sugar for redux selectors:

• Selectors: red-ux Header: strong,red-ux linebreak Link: https://github.com/codemeasandwich/red-ux linebreak Description: Provides a genSelectState utility to improve selector caching behavior, and a shouldUpdate function for simple

• Functional Programming: redux-fun Header: strong,redux-fun

https://github.com/guillaumearm/redux-fun Link: linebreak Utilities for composing and piping reducers, selectors, and middleware Description: undefined

widgets.md

• Assorted Components: react-redux-idle-monitor Header: strong,react-redux-idle-monitor linebreak Link: https://github.com/cchamberlain/redux-idle-monitor linebreak Description: https://github.com/cchamberlain/react-redux-idle-monitor

• Assorted Components: react-block-ui Header: strong,react-block-ui

Link: linebreak https://github.com/Availity/react-block-ui Description: linebreak

• Layout: Repanel Header: strong,Repanel linebreak Link: https://github.com/StJohn3D/repanel A configurable panel framework inspired by blender.org undefined Description: undefined

[dberget]

While looking through a lot of the errors, a high % of them are due to a second url. By figuring out how we want to handle those cases we can fix most of the errors.

@wilbertliu, would you be able to add the ability to capture a 2nd url to the robot's capabilities very easily?

Otherwise, the first options that come to mind are to either manually move the 2nd url to the description as a "See also: ...", or split off to own item on the list if appropriate.

[wilbertliu]

@markerikson Alright, I got the intention and will get back to it as soon as I can. 👌🏻

@dberget

would you be able to add the ability to capture a 2nd url to the robot's capabilities very easily?

For sure bro! 🙂 But hang tight, let's revise our markdown structure first. Before that, I think I will make some fix for the robot, then we'll see what @markerikson thought about that. I believe his response will revise our pattern structure that we already used.

Thanks all! 🙏🏻