jho406

Yes give it a go and ask me any questions :). I was hoping someone makes use of it. It's tightly coupled to Redux, but not React. I don't think it will work great with ember, and I say that because Breezy doesn't require any router or models (again Breezy is about the content state as opposed to business models). It reuses your Rails routes much like Turbolinks.

I wrote a library for React, Redux and Rails. Allowing you to build SPA without APIs. https://github.com/jho406/Breezy

Breezy's insight is that frontends are wildly complex due to the industry vertical (say.. childwelfare), so instead of shaping your state for business, breezy shapes it for content. Content being a header, footer, body as opposed to a post model or user model. This means each page is represented as a node in the Breezy Redux tree with its own header body and footer.

On one hand, it is annoying to traverse the pages to make updates, on the other, I can look at any running application and make close-to-correct assumptions on how to update the store. After all, most applications regardless of industry vertical has a header, body and footer somewhere.

Try this out: https://github.com/jho406/Breezy, its a library i wrote that makes working with the React/Redux portion feel like a classic Rails app. Its inspired by turbolinks and doesn't require APIs to work.

This is a headache for me too. Some questions for you:

Do you handle common area maintenance? Snow shovelling? Cleaning? Sidewalk maintenance? Do you have a requirement on the minimum num of units per building? How do you handle tenants that don't speak English? What is your pricing?

Aside from maintenance, do you have plans to get into full-on property management?

Full disclosure, I’m the author of Breezy, https://github.com/jho406/Breezy. An opinionated state shape and PJAX library for Redux.

I think “how you shape your state to make it easy to reduce and share between components” is an important topic that’s taken a backseat when discussing state management tooling.

Should I repeat my backend models? Should I use a redux ORM? How much should I denormalize or normalize?

I found it much easier to just denormalize everything and shape state for presentational purposes, e.g, I have a bunch of page nodes in my redux state each with a duplicated header. If I need to make an update to the header in response to, say, a change in user email, I change each duplicated header individually.

Sounds insane but it really works for me and let’s me keep more business logic in the backend where it belongs.

You can have the best of both. The simplicity of multipage apps with the feel of SPAs. Turbolinks is one example that comes to mind.

Or if you want the full power of React, Redux, AND the simplicity of Turbolinks/PJAX. You can use https://jho406.gitbook.io/breezy/ which is Turbolinks for React Redux Rails, you can build SPA without APIs, just by treating JSON as a navigational format.

Full disclosure, I'm the author and I've been trying to get some feedback on the project.

I'm working on an experimental tool to simplify React Redux app development. Inspired by the simplicity of Turbolinks, and powered by Rails. You can develop React and Redux SPAs without any APIs.

https://github.com/jho406/Breezy/

Unfortunately, I don't have plans to integrate with GraphQL. I wanted to keep it closer to Turbolink's approach by loading the next page's props into the store instead of firing off a bunch of API requests.

Great thing is, aside from the way it loads data, its just mostly plain Redux and React. Feel free to add your own functionality.

Author here. Been working on this for a while now, figured it was time to show hn. Love to hear some feedback!