Fixing Material-UI dependency version

[realslimshanky]

I'm submitting a ...

• bug report
• feature request

Current behavior:
Currently, Material-UI is set to next in the project dependency or package.json which is the pre-release and not stable.

Expected behavior:
We should be using the stable and version. Which means the version should be stated as the latest stable which currently is 0.20.0 as stated in NPM. Let's use pin this version and then move forward.

Steps to reproduce:
Just look at Package.json

[anurag-majumdar]

So we need to set the version of material-ui back to 0.20 and install the dependencies? I can take up this issue.

[realslimshanky]

@anurag-majumdar 0.20.0 is the correct version. Go ahead raise a PR. I'm assigning this issue to you.

[anurag-majumdar]

Will let you know asap I fix the version and the dependencies. Thanks @realslimshanky.

[anurag-majumdar]

There is one thing I saw, the existing styles and all would seem to break and need to refactor those areas for changing the version from 'next' to 0.20. I will also refactor those areas as much as possible.

I have initiated a PR, but I will be working on streamlining the changes from 'next' to '0.20' in order to get the app working. This is a dependency on version change. I will be adding further commits to the PR #51

@realslimshanky @divyamrastogi @palnabarun @blenderskool

[blenderskool]

@realslimshanky @anurag-majumdar It is good to be on stable version, but looking at 0.20.0 documentation, I see many differences in styling compared to next version which is more close to real guidelines.

Also overriding components with this version is easier and allows more options 🙂

[anurag-majumdar]

@blenderskool is actually right regarding this area, even if 0.20 is a stable version, it does not have some of the new features as next has. Also, next and 0.20 are not completely backwards compatible and a lot of refactoring needs to be done here.

[ritikrishu]

I think material UI recommends to use next version for new projects. So this is fine. But yeah, instead of @next we should be using a fixed version number whichever is latest