redgeoff / mson-react Goto Github PK

View Code? Open in Web Editor NEW

80.0 5.0 13.0 14.67 MB

React and Material-UI Rendering Layer for MSON

License: Apache License 2.0

HTML 1.13% Shell 0.10% JavaScript 98.74% CSS 0.02%

mson react material-ui json validation

mson-react's Introduction

MSON-React

UI Rendering Layer for React and Material-UI

Getting Started

Getting Started App

The best way to get started with MSON is to play with the Getting Started App. In just a few lines of MSON, you'll generate an app that can list, edit, filter and sort a list of contacts. And, for extra fun, you can use Firebase to make it real-time capable.

Autogenerate forms in React and Material-UI with MSON

Implementing great forms can be a real time-waster. With just a few lines of JSON, you can use MSON to generate forms that perform real-time validation and have a consistent layout.

Adding MSON-React to Your Existing React Project

yarn add mson-react or npm install mson-react
Add the following to the head section of your index.html:
```
<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">
```
Note: MSON-React uses font icons as the user can specify any Icon during runtime and the alternative of bundling all the icons as SVG icons would make your JS bundle huge

MSON Demo

You may find it useful to fire up the MSON demo locally:

$ git clone https://github.com/redgeoff/mson-react && cd mson-react && yarn install
$ yarn start
Visit http://localhost:3000 in a web browser

You can also run the demo with a local version of MSON, if you want to experiment with local changes to MSON:

$ git clone https://github.com/redgeoff/mson && cd mson && yarn install && yarn compile && yarn link && cd ..
$ git clone https://github.com/redgeoff/mson-react && cd mson-react && yarn install && yarn link mson
$ yarn start
Visit http://localhost:3000 in a web browser

More info

See MSON for details

mson-react's People

Contributors

Stargazers

Watchers

Forkers

brightloudnoise bq1028 metacoding p-r-t fajrendajs mrakibmiah niksde joshglenn mhiphip zerolethanh s-limo vivmagarwal yogishs

mson-react's Issues

Missing Form Builder Features

Multiple option for SelectField
Ability to edit help text

An in-range update of react-testing-library is breaking the build 🚨

The dependency react-testing-library was updated from `6.1.0` to `6.1.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-testing-library is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v6.1.1

6.1.1 (2019-04-05)

Bug Fixes

act: wait until react-dom-16.9.0 is released (#344) (180179e)

Commits

The new version differs by 1 commits.

180179e fix(act): wait until react-dom-16.9.0 is released (#344)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Sanity check all react components

See https://github.com/redgeoff/mson-react/blob/master/src/fields/field.js for template

Fix search bar on mobile

When on a small screen, hide search bar and show search icon. When search icon is clicked then hide everything in app bar and just show search
Like https://material-ui.com/, when click, expand box
X button to delete all text in search box

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.4.4 to 7.5.0.

The devDependency @babel/core was updated from 7.4.5 to 7.5.0.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.4.4 to 7.5.0.
The devDependency @babel/plugin-transform-runtime was updated from 7.4.4 to 7.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.4.4 to 7.5.0.

The devDependency @babel/core was updated from 7.4.5 to 7.5.0.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.4.4 to 7.5.0.
The devDependency @babel/plugin-transform-runtime was updated from 7.4.4 to 7.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Icon rendering

How to get Component to render icons properly? Take a look at the screen shot, based on inserting the demo, "Contact" Component into an existing CRA project (with existing use of material-ui).

import React from "react";
import ReactDOM from "react-dom";
import Component from "mson-react/lib/component";

const definition = {
  component: "Form",
  fields: [
    {
      name: "heading",
      component: "Text",
      text: "# Form using [MSON](https://github.com/redgeoff/mson)"
    },
    {
      name: "firstName",
      component: "TextField",
      label: "First Name",
      required: true,
      block: false
    },
    {
      name: "lastName",
      component: "TextField",
      label: "Last Name",
      required: true
    },
    {
      name: "email",
      component: "EmailField",
      label: "Email",
      help: "Any email address except [email protected] and [email protected]"
    },
    {
      name: "submit",
      component: "ButtonField",
      type: "submit",
      label: "Submit",
      icon: "Save"
    },
    {
      name: "reset",
      component: "ButtonField",
      label: "Reset",
      icon: "Clear"
    }
  ],
  validators: [
    {
      where: {
        "fields.email.value": "[email protected]"
      },
      error: {
        field: "email",
        error: "must not be {{fields.email.value}}"
      }
    }
  ]
};

export const SurveyorMSON = () => (
  <Component
    definition={definition}
    onMount={({ component }) => {
      // Load any initial data, e.g. from an API
      component.setValues({
        id: "abc123",
        firstName: "Bob",
        lastName: "Marley",
        email: "[email protected]"
      });
    }}
    // Clear the form
    onReset={({ component }) => component.reset()}
    onSubmit={({ component }) => {
      // TODO: Contact some API with the data
      console.log("submitting", component.getValues());

      // Simulate response from API saying that email address is already in use and report this
      // error to the user
      if (component.get("fields.email.value") === "[email protected]") {
        component.set({ "fields.email.err": "already in use" });
      } else {
        // Everything was successful so redirect, show confirmation, etc...
      }
    }}
  />
);

An in-range update of mson is breaking the build 🚨

The dependency mson was updated from `1.0.1` to `1.0.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mson is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of react is breaking the build 🚨

There have been updates to the react monorepo:

- The devDependency react was updated from 16.6.1 to 16.6.2.

The devDependency react-dom was updated from 16.6.1 to 16.6.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of material-ui-pickers is breaking the build 🚨

The devDependency material-ui-pickers was updated from `1.0.0-rc.17` to `1.0.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

material-ui-pickers is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/core was updated from 7.3.4 to 7.4.0.

The devDependency @babel/plugin-proposal-class-properties was updated from 7.3.4 to 7.4.0.
The devDependency @babel/plugin-transform-runtime was updated from 7.3.4 to 7.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Define propTypes

Use propTypes to require applicable React props. See

mson-react/src/snackbar.js

Line 61 in 2e33271

Snackbar.propTypes = {

as a template

An in-range update of react-beautiful-dnd is breaking the build 🚨

The dependency react-beautiful-dnd was updated from `10.0.4` to `10.1.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-beautiful-dnd is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for 10.1.0

🎧🎶 Release notes designed to be listed to with: "Once there were dragons" @ 4:05

Highlights 🤾‍♀️

👩‍🎨 Stunning animation improvements
📖 Overhauled documentation
📱 More predictable touch dragging
🏠 Simplified home list styling
💅 New project design
📝 Blogs of our learnings

Beautiful 🏔

This release pushes react-beautiful-dnd to new summits of interaction design.

We have removed instant movement (snapping) when moving between lists. Snapping breaks the visual language of moving physical objects around that react-beautiful-dnd is trying to emulate.

✅ No snapping when moving between lists

❌ This is what it used to be (snapping in the 🏠 home list after a drop)

You do not need to do anything to get the new animation pattern. I have marked this change as a feature release as it is new design behaviour.

Blog: Beautiful interactions 📝

There was a huge amount of work to remove snapping when moving between lists. Who would have thought? Not me 🥵. I wrote a blog which goes over the journey of this feature in depth. Personally, I think it well worth your time!

📝Blog → Beautiful interactions: Crafting elegant and robust drag and drop animations

New logo 👩‍🎨

We have moved to a logo that encapsulates the playfulness and delight that we are striving for with react-beautiful-dnd

Blog: Logo creation 📝

Maryanne Nguyen, a very talented designer at Atlassian, has detailed her creative process in creating the new react-beautiful-dnd logo in a blog 🎨

📝Blog → maryannemade: react-beautiful-dnd logo

More predictable touch dragging 📱

react-beautiful-dnd tries to respect standard browser interactions as much as possible. Currently, the library plays well with force touch interactions:

If the user force presses on the element before they have moved the element (even if a drag has already started) then the drag is cancelled and the standard force press action occurs. For an anchor, this is a website preview.

Unfortunately, heavy presses can cancel a drag. It can be tricky at times to get the right amount of pressure to correctly use touch dragging. This can be frustrating for users.

We have added an option for you to opt-out of respecting force touch interactions. This option will disable force press interactions on the drag handle. However, it allows for a more consistent touch dragging interaction.

We have added shouldRespectForceTouch as a prop to <Draggable />. It defaults to true in order to respect force touch interactions, but you can set it to false to opt out of respecting force touch

<Draggable
  draggableId="draggable"
+ shouldRespectForceTouch={false}
>
</Draggable>

This change resulted in a feature release. The default behaviour matches the behaviour of previous versions.

Should force touch be respected by default?

Right now shouldRespectForceTouch defaults to true in order to respect browser interactions. However, for this specific use case, I am thinking that the default could be to not respect force touch in order to have a more consistent touch dragging experience out of the box.

I have created a request for discussion to collect other people's thoughts on what the default should be.

Simplified home list styling 🏠

We have added a new value to the DroppableStateSnapshot: draggingFromThisWith

type DroppableStateSnapshot = {|
  isDraggingOver: boolean,
  draggingOverWith: ?DraggableId,
+ draggingFromThisWith: ?DraggableId,
|};

draggingFromThisWith is populated with the draggableId of the dragging item in the 🏠 home list for the entire drag. This allows you to style the home list differently from the other lists if you like. We recommend you do this to make it clear which list the user is dragging from. You can read more about the thinking behind this in my blog

In this example we set the background-color of the home list to pink when we are dragging over the list. We set the background-color of the home list to blue when not dragging over the home list.

Overhauled documentation 📖

We have totally overhauled our documentation to be easier to find and use information.

Our README.md was getting too big. It was hard for new comers to know where to start, and it was hard for consumers of the library to quickly find information. We have simplified our README.md and added a comprehensive documentation section which links off to categories of information.

The README.md now contains a high-level introduction to the project, feature set, how to get started and then links to the rest of the documentation.

For new comers and evaluators 👶

Information in the README.md:

Big gif showing off what the library is about
Reduced badges to the critical subset to reduce noise
High level motivation of the project
Feature set and limitations
Getting started guide
An About section which links off information useful to understand, evaluate and get started with the library.

For consumers 👩‍🎤

The documentation has been broken down into more logical independent chunks to make it clearer where to find topical information. Previously API was under a wall of design thinking information which would not be useful to a non-evaluator
All documentation pages have a link back to the documentation root for quickly jumping around

Documentation engineering health 👨‍⚕️

Added a test to ensure that there are no more broken links 🎉. This is by far the cause of the most issues
Added test to ensure consistent usage of component names
Added test to ensure all documentation pages end with a backlink to the documentation root

Refreshed examples 🦸‍♂️ #1096

We have made our examples brighter and more colourful

Previous	New style

We have also upgraded to Storybook v5 and added our new logo to the header

Other improvements

Only attaching to the redux devtools when process.env.NODE_ENV === 'development' #1085. Thanks @teleaziz!!
More collision engine refinements

Fixes 🐛

A transition for a property other than transform that finished during a drop animation on a Draggable could cause the drop to end suddenly #1096
position:fixed lists on ie11 #1091 #1088. Thanks @InvisibleBacon for raising this one
Typo in docs #1102. Thanks @jDeppen

Engineering health

Upgraded to flow 0.94 #1119
Upgrade of all dev dependencies #1119
Moved example website to use emotion 👩‍🎤 #1128
Moving browser tests to cypress.io. Also added a few more browser tests #1122

Commits

The new version differs by 14 commits.

45cc88a v10.1.0
67b96c8 Merging dev to master (it's happening) (#1158)
1c1f42e Fix broken example source link (#1121)
c782b2a Fix dead link in README.md (#1106)
dedd3c9 Fix typo (#1102)
4518e53 Ie 11 window scroll fix (#1091)
2e93958 adding options to storybook setup (#1087)
adc5a2e compose with redux dev tools in development mode only (#1085)
fc61e8a More storybook popping (#1083)
5fb1532 pop out button (#1082)
fa03b1f adding iframe pop decorator (#1081)
65770cc Join the community on Spectrum! (#1080)
a7438c1 goodbye for now (#1076)
d6be548 adding nvmrc (#1077)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/core was updated from 7.3.4 to 7.4.0.

The devDependency @babel/plugin-proposal-class-properties was updated from 7.3.4 to 7.4.0.
The devDependency @babel/plugin-transform-runtime was updated from 7.3.4 to 7.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.6.0 to 7.6.2.

The devDependency @babel/core was updated from 7.6.0 to 7.6.2.
The devDependency @babel/plugin-transform-runtime was updated from 7.6.0 to 7.6.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Documentation on how to create a custom component

An in-range update of react-testing-library is breaking the build 🚨

The dependency react-testing-library was updated from `5.6.0` to `5.6.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-testing-library is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v5.6.1

5.6.1 (2019-02-11)

Bug Fixes

TS: typing of testHook (#292) (8436c7e)

Commits

The new version differs by 1 commits.

8436c7e fix(TS): typing of testHook (#292)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of material-ui is breaking the build 🚨

There have been updates to the material-ui monorepo:

- The devDependency @material-ui/core was updated from 3.4.0 to 3.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the material-ui group definition.

material-ui is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v3.5.0

Nov 12, 2018

Big thanks to the 13 contributors who made this release possible!

Here are some highlights ✨:

Introduce a new @material-ui/styles package 💅 (#13503).

The Material-UI's styling solution has pretty much stayed the same for the last 12 months.
Some interesting CSS-in-JS libraries like styled-components, emotion or linaria have emerged.
This new package is a significant step forward. Some of the key features:

Supports 4 different APIs: hooks, styled-components, higher-order components and render props.
Allow accessing the component's props from within the style object.
Replace the usage of the old React APIs with the new ones.
15.0 KB gzipped.

Here is an example: https://codesandbox.io/s/vjzn5z4k77.

import Button from '@material-ui/core/Button';
import React from 'react';
import { makeStyles } from '@material-ui/styles';
// Like https://github.com/brunobertolini/styled-by

const styledBy = (property, mapping) => props => mapping[props[property]];
const useStyles = makeStyles({

  root: {

    background: styledBy('color', {

      red: 'linear-gradient(45deg, #FE6B8B 30%, #FF8E53 90%)',

      blue: 'linear-gradient(45deg, #2196F3 30%, #21CBF3 90%)',

}),

    border: 0,

    borderRadius: 3,

    boxShadow: styledBy('color', {

      red: '0 3px 5px 2px rgba(255, 105, 135, .3)',

      blue: '0 3px 5px 2px rgba(33, 203, 243, .3)',

}),

    color: 'white',

    height: 48,

    padding: '0 30px',

},

});
function MyButton(props) {

const { color, ...other } = props;

const classes = useStyles(props);

  return <Button className={classes.root} {...other} />;

}
function AdaptingHook() {

  return (

<div>

<MyButton color="red">Red</MyButton>

<br />

<br />

<MyButton color="blue">Blue</MyButton>

</div>

);

}
export default AdaptingHook;

Powered by JSS.

Remove some usages of the old React's APIs (#13487, #13529, #13503) @eps1lon.
Add a language menu in the documentation and persist states between repeated visits (#13544, #13567) @mbrookes
And many more 🐛 bug fixes and 📝 documentation improvements.

`@material-ui/[email protected]`

[OutlinedInput] Remove Firefox workaround (#13519) @Studio384
[TextField] Fix style focus issue on mobile (#13511) @ekoeditaa
[InputBase] Remove legacy lifecycle methods (#13487) @eps1lon
[Chip] Alignment fix (#13536) @izyb
[Badge] Add invisible property (#13534) @joshwooding
[Table] Use stable context API (#13529) @eps1lon
[TablePagination] Allow more rows per pages (#13524) @oliviertassinari
[LinearProgress] Fix TypeScript definition (#13562) @AdamMcquiff

`@material-ui/[email protected]`

@material-ui/styles (#13503) @oliviertassinari

Docs

[docs] Advanced filter added to the documentation (#13528) @ashkank83
[docs] Save one component in the demo (#13537) @levelingup
[docs] Make the lab > core dependency more explicit (#13542) @Robindiddams
[docs] Remove redundant text (#13547) @EbiEbiEvidence
[docs] Add language menu (#13544) @mbrookes
[docs] Misc fixes (#13555) @oliviertassinari
[docs] Add cookie for persistant colors (#13567) @mbrookes

Core

[test] Improve tests related to lists (#13517) @eps1lon
[core] Remove recompose/wrapDisplayName usage (#13525) @oliviertassinari
[core] Fix the CDN release (#13540) @oliviertassinari
[core] Pass import filename through normalizePath function (#13565) @joshwooding

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.5.0 to 7.5.5.

The devDependency @babel/core was updated from 7.5.4 to 7.5.5.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.5.0 to 7.5.5.
The devDependency @babel/plugin-transform-runtime was updated from 7.5.0 to 7.5.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel-loader is breaking the build 🚨

The devDependency babel-loader was updated from `8.0.4` to `8.0.5`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

babel-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for 8.0.5

Update find-cache-dir to 2.0

Commits

The new version differs by 8 commits.

20c9e0e 8.0.5
de51b5d chore: Update ava
66f92af Remove docs mention about sourceMap option being ignored (#750)
6df8af1 Update dependencies and run all tests (#745)
2c61de5 Add node 11 and 10 (#744)
1bda840 Fix config issue in example (#708)
364387d Merge pull request #698 from MattGurneyAMP/patch-1
98f936d Fix license header and link

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of mson is breaking the build 🚨

The devDependency mson was updated from `1.1.0` to `1.1.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mson is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of jest-dom is breaking the build 🚨

The dependency jest-dom was updated from `3.1.2` to `3.1.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

jest-dom is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v3.1.3

3.1.3 (2019-03-12)

Bug Fixes

toBeVisible ignoring hidden attribute (#85) (4d5427b)

Commits

The new version differs by 2 commits.

4d5427b fix: toBeVisible ignoring hidden attribute (#85)
238cc91 docs: remove extra bracket from toBeVisible example (#83)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.4.3 to 7.4.4.

The devDependency @babel/core was updated from 7.4.4 to 7.4.5.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.4.0 to 7.4.4.
The devDependency @babel/plugin-transform-runtime was updated from 7.4.3 to 7.4.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/core was updated from 7.3.3 to 7.3.4.

The devDependency @babel/plugin-proposal-class-properties was updated from 7.3.3 to 7.3.4.
The devDependency @babel/plugin-transform-runtime was updated from 7.2.0 to 7.3.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.2.0 to 7.2.3.

The devDependency @babel/core was updated from 7.2.2 to 7.3.3.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.3.0 to 7.3.3.
The devDependency @babel/plugin-transform-runtime was updated from 7.1.0 to 7.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Adding/Altering space within and between components?

As the title suggests, I would like to know how I can change the space between components. For instance, in my form, I would like to have more space above my "headings" and less space below them. May I please know how I can achieve that here?

An in-range update of react-select is breaking the build 🚨

The dependency react-select was updated from `2.4.1` to `2.4.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-select is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v2.4.2 / 2019-03-11

Bug fixes

#3446 Fix bug with select input value not being selectable. Thanks @kangweichan
#3445 Fix accessibility bug. Disabled options are now focusable and announced by screen-readers but not selectable. Thanks @sarahbethfederman

Updates

Fixed typo in style docs. Thanks thiagodebastos.
#3460 Added description for actionTypes to docs. Thanks @mikekellyio

Commits

The new version differs by 13 commits.

285f4d4 v2.4.2
6a8c3c3 📜 v2.4.2 CHANGELOG
9f09c77 Merge branch 'master' of https://github.com/JedWatson/react-select
76f621b Merge pull request #3455 from thiagodebastos/fix-typo-in-documentation
25c39e5 Merge pull request #3460 from mikekellyio/patch-1
770ba08 Merge pull request #3445 from JedWatson/disabled-focus
77ae928 Merge pull request #3446 from kangweichan/kangweichan-cursor-click
eebf3dd make options a bulleted list
530f872 add explanations for what the various actionTypes are
af1afa6 fix typo in styles documentation
169c093 Change currentTarget to target in mousedown event to detect when input is selected
62b4e65 make disabled options keyboard focusable
19f223c fixed test data for a disabled option

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

CollectionField: create automatic routes for viewing, updating, etc…

When the CollectionField is used with the App component, there should be automatic routes for viewing, updating, etc…, e.g. /contacts/someid/update. Otherwise, the back button is broken when editing items in the collection

An in-range update of react-scripts is breaking the build 🚨

The devDependency react-scripts was updated from `2.1.3` to `2.1.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-scripts is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Data types not matching defined components

Hello,
I have a schema that's using the IntegerField component and when I use .getValues() on the form, the data for this field is a string. Is this a bug or is there a way to get the data in the correct types?

Thanks in advance.

Is it possible to render only the form without the menu and left navbar?

I am using React + Material UI to build a web application. There are a few forms that are required as part of the application.
I have been able to render the form generated using mson-react but it displays the menu and the side nav.
Is it possible to render only the form without the menu and left navbar?

Does not compile by using material-ui-pickers v2.x.x

I'm not sure if this topic was already covered, but I'm unable to compile my project by using a 2.x.x version of the material-ui-pickers package.

You can try on CodeSand as well, which logs something like:

Error in sandbox:
ModuleNotFoundError: Could not find module in path: 'material-ui-pickers/utils/date-fns-utils' relative to '/node_modules/mson-react/lib/fields/date-field.js'
Error in sandbox:
ModuleNotFoundError: Could not find module in path: 'material-ui-pickers/utils/date-fns-utils' relative to '/node_modules/mson-react/lib/fields/date-field.js'

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.4.4 to 7.5.0.

The devDependency @babel/core was updated from 7.4.5 to 7.5.0.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.4.4 to 7.5.0.
The devDependency @babel/plugin-transform-runtime was updated from 7.4.4 to 7.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Add @date-io/date-fns, date-fns and material-ui-pickers as dependencies (no alpha)

Getting the following error after installing mson-react. I tried adding mson too.

./node_modules/mson-react/lib/fields/date-field.js
Module not found: Can't resolve '@date-io/date-fns' in 
'/home/user/dexter/client/node_modules/mson-react/lib/fields'

and

./node_modules/mson-react/lib/fields/date-field.js                                                            
Module not found: Can't resolve 'material-ui-pickers/DatePicker' in '/home/user/dexter/client/node_modules/react/lib/fields'

Use componentDidMount instead of componentWillMount

mson-react/src/app.js

Line 348 in 410a6bc

componentWillMount() {

An in-range update of react-scripts is breaking the build 🚨

The devDependency react-scripts was updated from `3.0.1` to `3.1.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v3.1.0

3.1.0 (2019-08-09)

v3.1.0 is a minor release that adds ESLint 6 support as well as experimental support for extended and customizing the ESLint config along with other minor bug fixes and documentation updates.

Highlights

ESLint 6: #7415
Experimental ESLint config customization: #7036
More Jest config options: #6055
Option to configure or disable image inlining: #6060

🚀 New Feature

eslint-config-react-app, react-error-overlay, react-scripts
- #7415 Add ESLint 6 support (@mrmckeb)
eslint-config-react-app, react-scripts
- #7036 Add ESLint extend support to eslint-loader (@mrmckeb)
react-dev-utils
- #7277 Handle browser arguments (@arvigeus)
react-scripts
- #6060 Add environment variable to control image inlining threshold (@peterbe)
- #6055 Support for graceful extension of Jest config (@jamesmfriedman)

💥 Breaking Change

react-scripts
- #7176 Fix RegExp from navigateFallbackBlacklist (workbox) (@nuragic)
- #7378 Update url-loader to 2.0.1 (@heyimalex)
eslint-config-react-app, react-error-overlay, react-scripts
- #7415 Add ESLint 6 support (@mrmckeb)

🐛 Bug Fix

react-dev-utils
- #7444 Fix for #6720: HMR not working in Firefox if proxy option present (@dmile)
react-scripts
- #5829 Resolve relative paths for preprocessor styles (@iamandrewluca)
- #7433 Add explicit check for --watchAll=false (@mrmckeb)
- #7378 Update url-loader to 2.0.1 (@heyimalex)
eslint-config-react-app
- #7230 jsx-no-duplicate-props ignore case fix (@rommguy)
- #7219 fix: eslintrc overrides key should be an array, not object (@ivan-aksamentov)
- #7079 Adjust typescript-eslint to not warn about typedefs when used before defined (@vincentjames501)
react-error-overlay, react-scripts
- #7257 Upgrade webpack to 4.35.0 to fix dynamic import issue (@iansu)

💅 Enhancement

react-scripts
- #7497 add readonly modifier for css module (@xiaoxiangmoe)
- #7496 bump sass-loader (@xiaoxiangmoe)
- #7176 Fix RegExp from navigateFallbackBlacklist (workbox) (@nuragic)
- #7080 Support configuring coveragePathIgnorePatterns (@kentcdodds)
- #7482 100% lighthouse score for progressive web app (@dscanlan)
- #5951 Set jsonpFunction by default (@sibiraj-s)
- #7472 Typescript init: suggest jsx: "react" in tsconfig (@kingdaro)
- #7118 Append title element to SVG component via title prop (@sudkumar)
react-dev-utils
- #7028 Add vscodium to the editor list (@leonardodino)
- #7277 Handle browser arguments (@arvigeus)
eslint-config-react-app, react-error-overlay, react-scripts
- #7415 Add ESLint 6 support (@mrmckeb)
eslint-config-react-app
- #7179 Disabled Typescript no-undef rule per typescript-eslint #477 (@andyhopp)
create-react-app
- #6941 Fix compatibility of create-react-app to Node.js v0.10+ (@tobiasbueschel)

📝 Documentation

Other
- #7488 Adjusted deployment documentation for ZEIT Now (@leo)
- #7462 Added dependencies to bootstrap article when using custom SCSS. (@eclectic-coding)
- #7340 Update testing-library related npm package names in README (@balazsorban44)
- #7423 Add question issue template (@iansu)
- #7260 Docs: remove an outdated TypeScript-related note (@MidnightDesign)
- #7372 proposal dynamic import are stage 4 (@gespispace)
- #7374 docs(svg): add tip for title props accessibility (@sudkumar)
- #7182 Update minimum Node versions in docs (@JESii)
- #7317 Fix typo (@mvasin)
- #7262 Docs: replace the command line to install relay/macro (@soufDev)
- #7170 Update deprecated package reference (@bnewcomb)
- #7133 Make the OOM abreviation more clear (@tlehtimaki)
- #7086 Improve breaking changes info for CRA 3.0.0 (@falldowngoboone)
- #7059 Correct spelling of browserslist (@amyrlam)
- #7039 docs: fix env-cmd example in deployment section (@VMois)
- #7041 Updates the relay docs (@orta)
eslint-config-react-app
- #7451 Update README for ESLint config (@mrmckeb)
- #7274 Update peer dependencies (@ThewBear)
react-error-overlay, react-scripts
- #7355 Fix typos (@minho42)

🏠 Internal

babel-preset-react-app
- #5818 Remove unused dependencies in babel-preset-react-app (@iansu)
- #7208 Use correct babel transform for dynamic import in dependencies (@jamesknelson)
react-scripts
- #7433 Add explicit check for --watchAll=false (@mrmckeb)
- #6877 Upgrade svgr to 4.2.0 (@iansu)
Other
- #7385 Attempt at fixing CI issue on windows (@heyimalex)
- #7269 Update issue templates (@mrmckeb)
- #7220 Disable Travis build (@ianschmitz)
- #7096 Add Azure DevOps build pipeline (@ianschmitz)
- #6858 Add test to make sure .d.ts files are ignored when checking for TypeScript (@iansu)
react-error-overlay, react-scripts
- #7355 Fix typos (@minho42)

🔨 Underlying Tools

babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
- #7473 Bump dependencies (@ianschmitz)
eslint-config-react-app, react-error-overlay, react-scripts
- #7415 Add ESLint 6 support (@mrmckeb)
eslint-config-react-app, react-scripts
- #7036 Add ESLint extend support to eslint-loader (@mrmckeb)
react-scripts
- #7118 Append title element to SVG component via title prop (@sudkumar)
- #7222 Update @typescript-eslint package versions (@ianschmitz)
- #7131 Update fsevents dependency version (@eps1lon)
react-dev-utils
- #7058 fix: Replaced opn (deprecated) with open (@jamesgeorge007)

Committers: 46

Adeel Imran (@adeelibr)
Alex Guerra (@heyimalex)
Amy Lam (@amyrlam)
Andrea Puddu (@nuragic)
Andrew Luca (@iamandrewluca)
Andy Hopper (@andyhopp)
Balázs Orbán (@balazsorban44)
Ben Newcomb (@bnewcomb)
Brian Muenzenmeyer (@bmuenzenmeyer)
Brody McKee (@mrmckeb)
Chuck (@eclectic-coding)
Darius Tall (@kingdaro)
Dmitry Lepskiy (@dmile)
Guy Romm (@rommguy)
Ian Schmitz (@ianschmitz)
Ian Sutherland (@iansu)
Igor Muchychka (@mucsi96)
Ivan Aksamentov (@ivan-aksamentov)
Ivan Pegashev (@gespispace)
Jack Cross (@crosscompile)
James Friedman (@jamesmfriedman)
James George (@jamesgeorge007)
James K Nelson (@jamesknelson)
Jon Seidel (@JESii)
Kent C. Dodds (@kentcdodds)
Leo Lamprecht (@leo)
Leonardo Dino (@leonardodino)
Mikhail Vasin (@mvasin)
Min ho Kim (@minho42)
Nikolay Stoynov (@arvigeus)
Orta (@orta)
Peter Bengtsson (@peterbe)
Rudolph Gottesheim (@MidnightDesign)
Ryan Boone (@falldowngoboone)
Ryan Marsh (@ryanwmarsh)
Sebastian Silbermann (@eps1lon)
Sibiraj (@sibiraj-s)
Soufiane AIT AKKACHE (@soufDev)
Sudhir Mitharwal (@sudkumar)
Thew Dhanat (@ThewBear)
Tobias Büschel (@tobiasbueschel)
Toni (@tlehtimaki)
Vincent Pizzo (@vincentjames501)
Vladyslav Moisieienkov (@VMois)
ZHAO Jinxiang (@xiaoxiangmoe)
dominic scanlan (@dscanlan)

Migrating from 3.0.1 to 3.1.0

Inside any created project that has not been ejected, run:

npm install --save --save-exact [email protected]

yarn add --exact [email protected]

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.4.4 to 7.5.0.

The devDependency @babel/core was updated from 7.4.5 to 7.5.0.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.4.4 to 7.5.0.
The devDependency @babel/plugin-transform-runtime was updated from 7.4.4 to 7.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.1.5 to 7.2.0.

The devDependency @babel/core was updated from 7.2.0 to 7.2.2.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.2.0 to 7.2.1.
The devDependency @babel/plugin-transform-runtime was updated from 7.1.0 to 7.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Use npm version minor/patch with hooks instead of scripts/publish.sh

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.4.3 to 7.4.4.

The devDependency @babel/core was updated from 7.4.3 to 7.4.4.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.4.0 to 7.4.4.
The devDependency @babel/plugin-transform-runtime was updated from 7.4.3 to 7.4.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

How to use custom styles in buttons or how to wrap buttons inside divs with its own styles?

I was wondering how to send a button to the left and another button to the right
(using float or flex) of my layout.

Thanks!

Can't resolve 'mson/lib/form/form-builder'

downloading and running npm i and running start script results in runtime error

Can't resolve 'mson/lib/form/form-builder'

using node 11 on windows 7

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.5.0 to 7.5.5.

The devDependency @babel/core was updated from 7.5.4 to 7.5.5.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.5.0 to 7.5.5.
The devDependency @babel/plugin-transform-runtime was updated from 7.5.0 to 7.5.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.1.2 to 7.1.5.

The devDependency @babel/core was updated from 7.1.2 to 7.1.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.2.0 to 7.2.3.

The devDependency @babel/core was updated from 7.2.0 to 7.2.2.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.2.3 to 7.3.0.
The devDependency @babel/plugin-transform-runtime was updated from 7.1.0 to 7.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

100% code coverage on react components

Use Enzyme or React Testing Library for 100% code coverage on react components: https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#testing-components

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.2.3 to 7.4.3.

The devDependency @babel/core was updated from 7.4.0 to 7.4.3.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.3.4 to 7.4.0.
The devDependency @babel/plugin-transform-runtime was updated from 7.4.0 to 7.4.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Querystring in mson / mson-react

I see in app.js that the queryString gets saved into a globals object:

mson-react/src/app.js

Lines 247 to 253 in 1ecd7fb

    
           globals.set({ 
        
             route: menu.toRoute({ 
        
               parameters, 
        
               queryString: location.search.substr(1), 
        
               hash: location.hash.substr(1) 
        
             }) 
        
           });

My question is, at the component level, or in MSON, how do I access that queryString to use its data in a specific component?

For example, I have tried:

import globals from 'mson/lib/globals';

then

console.log(globals);
console.log(globals.get('route'));

and although those functions work and output object info to the console, the global route object that got set in app.js does not appear to be available in other components. It is just empty.

Shouldn't those globals be accessible to me? Any idea what I might be doing wrong?

list-field with no duplicates allowed?

Is it possible to easily prevent the entry of duplicates in a list-field?

For example, a list could contain {dog, cat, fish}...

But not {dog, dog, cat, fish}.

Thanks, for any help you can provide, and thanks for an awesome library!

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.1.2 to 7.1.5.

The devDependency @babel/core was updated from 7.1.5 to 7.1.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

	globals.set({
	route: menu.toRoute({
	parameters,
	queryString: location.search.substr(1),
	hash: location.hash.substr(1)
	})
	});

redgeoff / mson-react Goto Github PK

mson-react's Introduction

MSON-React

Getting Started

Getting Started App

Autogenerate forms in React and Material-UI with MSON

Adding MSON-React to Your Existing React Project

MSON Demo

More info

mson-react's People

Contributors

Stargazers

Watchers

Forkers

mson-react's Issues

The dependency react-testing-library was updated from 6.1.0 to 6.1.1.

6.1.1 (2019-04-05)

Bug Fixes

There have been updates to the babel7 monorepo:

There have been updates to the babel7 monorepo:

The dependency mson was updated from 1.0.1 to 1.0.2.

There have been updates to the react monorepo:

The devDependency material-ui-pickers was updated from 1.0.0-rc.17 to 1.0.0.

There have been updates to the babel7 monorepo:

The dependency react-beautiful-dnd was updated from 10.0.4 to 10.1.0.

Highlights 🤾‍♀️

Beautiful 🏔

Blog: Beautiful interactions 📝

New logo 👩‍🎨

Blog: Logo creation 📝

More predictable touch dragging 📱

Should force touch be respected by default?

Simplified home list styling 🏠

Overhauled documentation 📖

For new comers and evaluators 👶

For consumers 👩‍🎤

Documentation engineering health 👨‍⚕️

Refreshed examples 🦸‍♂️ #1096

Other improvements

Fixes 🐛

Engineering health

There have been updates to the babel7 monorepo:

There have been updates to the babel7 monorepo:

The dependency react-testing-library was updated from 5.6.0 to 5.6.1.

5.6.1 (2019-02-11)

Bug Fixes

There have been updates to the material-ui monorepo:

Nov 12, 2018

@material-ui/[email protected]

@material-ui/[email protected]

Docs

Core

There have been updates to the babel7 monorepo:

The devDependency babel-loader was updated from 8.0.4 to 8.0.5.

The devDependency mson was updated from 1.1.0 to 1.1.1.

The dependency jest-dom was updated from 3.1.2 to 3.1.3.

3.1.3 (2019-03-12)

Bug Fixes

There have been updates to the babel7 monorepo:

There have been updates to the babel7 monorepo:

There have been updates to the babel7 monorepo:

The dependency react-select was updated from 2.4.1 to 2.4.2.

Bug fixes

Updates

The devDependency react-scripts was updated from 2.1.3 to 2.1.4.

There have been updates to the babel7 monorepo:

The devDependency react-scripts was updated from 3.0.1 to 3.1.0.

3.1.0 (2019-08-09)

Highlights

🚀 New Feature

💥 Breaking Change

🐛 Bug Fix

💅 Enhancement

📝 Documentation

🏠 Internal

🔨 Underlying Tools

Committers: 46

Migrating from 3.0.1 to 3.1.0

There have been updates to the babel7 monorepo:

There have been updates to the babel7 monorepo:

The dependency react-testing-library was updated from `6.1.0` to `6.1.1`.

The dependency mson was updated from `1.0.1` to `1.0.2`.

The devDependency material-ui-pickers was updated from `1.0.0-rc.17` to `1.0.0`.

The dependency react-beautiful-dnd was updated from `10.0.4` to `10.1.0`.

The dependency react-testing-library was updated from `5.6.0` to `5.6.1`.

`@material-ui/[email protected]`

`@material-ui/[email protected]`

The devDependency babel-loader was updated from `8.0.4` to `8.0.5`.

The devDependency mson was updated from `1.1.0` to `1.1.1`.

The dependency jest-dom was updated from `3.1.2` to `3.1.3`.

The dependency react-select was updated from `2.4.1` to `2.4.2`.

The devDependency react-scripts was updated from `2.1.3` to `2.1.4`.

The devDependency react-scripts was updated from `3.0.1` to `3.1.0`.