reacting

.

tryna get arrested with the sauce not a decade too soon; i.e., we will not be employing "state management," and we're concerned with drawing out what "statelessness" entails (e.g., "direct linking" or url-to-url processing). yes, useReducer exists but the rest✓ is hateoas❤︎ for the web and we're ontologically committed to be exposing "actions" to a discoverable medium: our semantic web. everything can be described as a resource, not (just) objects.

your data model is not your object model is not your resource model is not your affordance model. (mike amundsen. co-author of microservice architecture)

todo

obviously this doesn't even shake a stick at mike amundsen's api-starter, but the goal is to show how one can eventually achieve the link relation types with a "popular" framework (or "library"? i don't care), if "framework wars" must be endured for the next decade. of course, we were always supposed to think to abolish the "framework" as our apps mature such that they are built-to-last, but alas, nevertheless, we can still preserve freedom and the accessibility of the accessible and not introduce performance costs due to weight and cache.

on-going list

incorporate organic bem⚚
and unit testing for sass
and behavior-driven tests (with cypress??)

since the api☂︎ is not itself rest-ful that we're hitting, we'll eventually show what it looks like for a client to suggest and encourage it civilly.

misc

run $ npm run help to see the needful. or review project files with $ npm run ~.

footnotes

☂︎ application programming interface (you might hate better)
⚚ block-element-modifier
✓ representational state transfer
❤︎ hypermedia as the engine of application state

License

nerdfiles/reacting

ErrorLooks like something went wrong!

About

Topics

Resources

License

Uh oh!

Stars

Watchers

Forks

Uh oh!

Languages

Error
Looks like something went wrong!