Unable to override the default breakpoints

[three60five]

I tried to set custom breakpoints using flexa object:

const nightTheme = {
  flexa: {
    gutter: {
      xs: 1,
      sm: 2,
      md: 2,
      lg: 3,
    },
    breakpoints: {
      xs: 0,
      sm: 22,
      md: 44,
      lg: 66,
    },
    columns: 24,
  },

The columns and gutter changed but the breakpoints remained the flexa defaults.

Expected Behavior
The custom breakpoints are displayed.

[aaronvanston]

@three60five can you provide an example of how you're using the flexa theme? For example where you set the <ThemeProvider />

This might also provide more information: https://github.com/aaronvanston/react-flexa#custom-theme

[three60five]

Yes, I have set up the <ThemeProvider> like:
<ThemeProvider theme={nightTheme}>. I am using styled-components 2.1.0. As I stated before, the column and gutter overrides in the theme object are applied correctly, just not the breakpoints.

[aaronvanston]

Thanks @three60five I will take a look! Will update hopefully with a fix/solution ASAP!

[three60five]

Thanks for looking into it. If it helps, I've seeing this in a very basic app started with create-react-app where I'm checking out your library.

[aaronvanston]

@three60five To give you an update: We have located the issue at hand. When creating the media queries for the component, it does not pull from the custom theme but rather bypasses it and goes straight to the default theme. We will release a patched release ASAP.

Thank you for spending the time to submit an issue!

[aaronvanston]

The fix for the media is taking longer than expected, unfortunately, sorry! One hacky solution, for now, is to modify the default theme inside `/node_modules/react-felxa/dist/theme/defaultTheme.js` We will update you when the proper solution is released.

…

On 28 June 2017 at 00:51, Dave Allen ***@***.***> wrote: Is there a workaround I can use today? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIpd1LjGsAlbkgpJFxxR88FQAM5Oxc6wks5sIRb1gaJpZM4OGL_I> .

[aaronvanston]

@three60five massive apologies for the delay on this fix. I was actually stuck on a solution for some time.

The fix for this has now been merged and release with version 0.6.0!

Thank you for spending the time to fill out an issue.