Giter Club home page Giter Club logo

Comments (5)

javivelasco avatar javivelasco commented on June 8, 2024

I guess there is something we could do to handle these cases explicitly. If a child component can be considered part of the parent component, they both can define (and must define) the same key. For example themr('Radio', style).

If you provide a theme via context it's going to work nicely because they use the same key but I guess that if you pass down a style to a parent of an specific type, it makes sense if this component writes in the context the updated theme. Therefore, the child would read from context the theme you passed to the parent via props.

This update is not breaking and has no downsides in my opinion apart from the cost of writing in the context when a theme is received

from react-css-themr.

raveclassic avatar raveclassic commented on June 8, 2024

@wtgtybhertgeghgtwtg
You can easily set the same theme for different keys when constructing context:

import css from './shared.css';
const context = {
 ChildComponent: css,
 ParentComponent: css
};

On the other hand, if you accept exactly the same theme in different components why not to use the same keys (names) for them?

UPDATE: If your case is about including a theme passed to props, then I believe the best way here is to explicitly extract child's theme from props and to pass it down. I've opened #24 to help with such cases.

UPDATE: The reason of avoiding context is that it can't hold dynamic values when using pure-rendering: facebook/react#2517

from react-css-themr.

javivelasco avatar javivelasco commented on June 8, 2024

Yeah, you're right, that's what we are doing with react-toolbox. Just using the same key for both child and parent if the belong to the same complex component

from react-css-themr.

raveclassic avatar raveclassic commented on June 8, 2024

@wtgtybhertgeghgtwtg What you are suggesting is a good old cascade when Parent component affects all possible Children on all levels deeper. Such behavior is unsafe and was meant to be eliminated by introduction of css-modules. However, ThemeProviders could still be nested to make such behavior explicit and #19 tracks it.
@javivelasco I believe this issue can be closed.

from react-css-themr.

javivelasco avatar javivelasco commented on June 8, 2024

Cool, thanks @raveclassic !

from react-css-themr.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.