Open gregorykan opened 7 years ago
Chuckles - very good :)
Here are some of the things I found challenging on this ship so far:
feathers-actions
docs and those of the related libraries; have a look at the server.js
and services
filesfeathers-actions
doing so much
feathers-actions
/hooks
and redux-observable
dogstack-agents
ramda
recompose
dumb components
redux-fp
and its updaters
TaskWorker
/TaskStepper
) implementations
offerings
and intents
, let alone building good (UI-wise) forms for them
This is great. Used it for the first bullet point already :grinning:
I found looking at the migrations in db/migrations
a good to way to find what is actually being stored in the database.
re https://github.com/root-systems/cobuy/pull/120/commits/656dda9eb8e1aa5adb452ce37f260e684497b9a7
updates for how we do container queries:
the problem is we want to make it easy to declare what data you need for your component, but sometimes queries depend on each other having been complete before you do another. so far i'm trying an approach with a query(props) => queries
and shouldQueryAgain(props, requestsStatus) => Boolean
, not sure if it's the right idea but it works for now.
the change i made was to have each request have an isReady
state, which is updated by an action fired after a response has been returned by the server. the reason we couldn't tell if a request was ready or pending before was that by default, all requests are persistent and listen to any changes as they come in live, so it always seemed like all requests were pending.
According to lore, the three-masted schooner was found west of Greenland by the whaler Herald on 11 October 1775. The boarding party took only the captain's log before leaving the vessel, because they were unwilling to search it. The last entry in the log was from 11 November 1762, which meant that the ship had been lost in the Arctic for 13 years. As the log was frozen, it slipped from the binding, leaving only some of the pages in it. All that could be recovered follows.