Asbjørn Hegdahl

> > And how will we be able to deal with sass/scss? > > If you are using another language that sits on top of CSS, you will likely always...

I'm having the same issue. I'm very new to Haskell so I'm 100% convinced that this is a user error on my part. Some pointers would be appreciated though! The...

@traptw1thin I discovered that (at least for my project) GHCi was starting in `/` which explains why my local modules weren't discovered. I was able to get around it with...

Closing this as this repo seems dead and I'm not using Contentful at work anymore

@ljharb You almost gave me a heart attack there (until I saw that my changes hadn't been published to npm yet) 😄 Is that a valid propTypes declaration though? Can...

@ljharb Are you sure about that? Both the following output `function` for me: ``` console.log(typeof PropTypes.exact); console.log(typeof PropTypes.exact({ foo: PropTypes.number })); ``` I can reproduce @jaydenseric's case like this (it...

Oh, actually, you only need this in order to reproduce: ``` PropTypes.checkPropTypes(PropTypes.exact(), {}, "prop", "Foo"); ``` I'm guessing it's because the returned function has an `isRequired` property (I now understand...

The error that OP describes is not unique to `PropTypes.exact`. It happens whenever you assign _any_ validator as the outermost value of `Component.propTypes`. All of the following will result in...

Using arbitrary keys like `id`, `name` and so on seems a bit weird, and so does dumping JSON strings or object literals to the "console". But maybe outputting the `key`...

@ljharb I made a [draft PR](https://github.com/facebook/prop-types/pull/284) because I'm not feeling super confident about the idea anymore