Hacker News Reader

Fair enough, I suppose. I still think the additional complexity of having to bring in the context for the save of passing 1 variable through the whole tree is overkill though.

View on HN

I'm developping a web app with fairly complex forms (imagine form sections, form templating...). The immediate use case of Context that comes to mind would be to pass down the `readonly` prop from the top-level Form component all the way down to the Field component, without having to drill through `FormSection`, `Template`, `TemplateSection` or any other component between the Form and the Field.

In the case of a form, what’s wrong with composing a whole tree of custom “presentation” components in one render? Does this take up too much space?

You don’t always need to pass the prop through each individual component, instead you can render a section (or the whole form) together as one larger context-specific UI component, where everything in the render call has access to the same prop values.

That's entirely true. It becomes much more applicable where there's more complex state that's used throughout an application.

Reply on news.ycombinator.com