- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Wed, 14 Jun 2017 09:19:44 +0200
- To: "'Hydra'" <public-hydra@w3.org>
On Tuesday, June 13, 2017 12:12 PM, kartik adur wrote: > Not sure if this is the correct place for this reply. Let me know and I'll > send it to the appropriate place next time. Replying on the mailing list is completely fine. > Also I am still playing catch > up with the specs and previous discussions so pardon any mistakes and > misunderstandings. > > Using redux patterns within heracles: +1 Redux patterns to store data state > and building elements feels inherently modular and declarative. The discussion was about using something Redux-style for the tests.. but using such an architecture within Heracles would certainly be interesting to explore too > It would make > building requests easy and intuitive. Only for use cases that are not > predefined will the user need to imperatively define the use case, and things > could quickly become unweildy. Unless there is a strategy for approximating > actions based on 'n+1' or more actions when 'n' isn't available. So two+ > actions when one isnt available. > > Injecting json-ld into markdown: +0.5 > client needs to only display changes happen when the data state changes. > Not sure about the methodology/process. This discussion was also about tests/use case documents. Cheers, Markus -- Markus Lanthaler @markuslanthaler
Received on Wednesday, 14 June 2017 07:20:24 UTC