knod

So one thing I've come up with that's cleaner in some ways, but more complicated in others. We have these requirements functions: ```js let reqs = { q1: function (client,...

Another option is to have the functions return components or null: ```js let getQuestions = { q1: function (client, otherData) { let passes = false; if (client.hasSection8 && client.household[0].disabled &&...

You don't really get to see what I mean about passing around props. Hmm. I'll edit that last one.

Previous couple of comments edited, though I don't think those are great examples.

Alternative option - each client property has a side-effects function. We could have an object keeping track of what questions are shown. The side-effects could be used to update the...

Btw, each State might need to be containing their own code for the form sections considering how different it can be per State. We can't know how much code really...

@wacii : Thanks for the feedback! Yeah, this is still a WIP and that was just a step along the way of metamorphosis. It's still not done. I'm working from...

Hmm, maybe I've been going about this the wrong way, but I've found classes to be really hard to work with at times to override semantic-ui-react styles. It's ended up...

@dylanesque : Hold off on that till we've had some discussion about our next steps forward on this and some reasonable bounds. Also, don't remove id's in the js code...

I'm not sure. 'semantic-ui-react' does include some id's, so I suspect their styles sometimes use them. Also, for some page features, id's make sense. There are styles that are unique...