Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Is it possible for me to make this work if I'm using React version 0.12.0? #10

Closed
jessegrosjean opened this issue Oct 30, 2014 · 1 comment
Closed

Is it possible for me to make this work if I'm using React version 0.12.0? #10

jessegrosjean opened this issue Oct 30, 2014 · 1 comment
Labels
core Infrastructure work going on behind the scenes

Comments

@jessegrosjean
Copy link

Right now I'm seeing problems because internally material-ui is using React 0.11.1 to create the elements and when I try to use them in React 0.12.0 I see an error. Is there something I can do about this on my end or should I just wait for you to update?

Thanks, I'm looking forward to trying this out!
@hai-cea
Copy link
Member

hai-cea commented Oct 30, 2014

Ahh yes. It looks like there are some breaking changes. Let me see if I can get that fixed today.

patrykkopycinski pushed a commit to Syncano/material-ui that referenced this issue Sep 22, 2015
@yongxu
Merge pull request mui#10 from yongxu/mui
9657fd3 
Mui
DavidNgv added a commit to DavidNgv/material-ui that referenced this issue Dec 8, 2016
@DavidNgv
commit mui#10: karmar.tests.js : // Needed for onTouchTap
1396d19 
                              import injectTapEventPlugin from 'react-tap-event-plugin';
                              injectTapEventPlugin();
oliviertassinari referenced this issue in oliviertassinari/material-ui Dec 2, 2017
@oliviertassinari
[docs] Continue the rebranding (#10)
b91b12d
eps1lon added a commit that referenced this issue Jun 12, 2019
@eps1lon
Persist snize snapshot (#10)
d9e3b73 
* WIP

* check on non-fork branch

* Full impl

* Dry run

* Rerun

* Look for credentials

* Look again

* The search continues

* Maybe in global scope?

* Inspect env

* Full run

* Dont persist on PR

* Cleanup
eps1lon added a commit that referenced this issue Jun 12, 2019
@eps1lon
Persist snize snapshot (#10)
a0e8e96 
* WIP

* check on non-fork branch

* Full impl

* Dry run

* Rerun

* Look for credentials

* Look again

* The search continues

* Maybe in global scope?

* Inspect env

* Full run

* Dont persist on PR

* Cleanup
eps1lon added a commit that referenced this issue Jun 13, 2019
@eps1lon
[core] Move size tracking to azure pipelines (#16182)
151d2f9 
* Set up CI with Azure Pipelines

[skip ci]

* Persist snize snapshot (#10)

* WIP

* check on non-fork branch

* Full impl

* Dry run

* Rerun

* Look for credentials

* Look again

* The search continues

* Maybe in global scope?

* Inspect env

* Full run

* Dont persist on PR

* Cleanup

* Run danger on azure (#9)

* Run danger on azure

* Fix missing danger env variables

* Run size snapshot exclusively on azure (#11)

* Run size snapshot exclusively on azure

* debug

* Revert "debug"

This reverts commit bff6dd2.

* Fix empty size snapshot being persisted

* Fix test_production CircleCi job

* Poke azure

* Add azure pipelines badge
eps1lon added a commit that referenced this issue Jun 19, 2020
@eps1lon
feat(injector): add reconcilePropTypes (#10)
7b0bff9
mbrookes pushed a commit to mbrookes/material-ui that referenced this issue Nov 11, 2020
@oliviertassinari @eps1lon
[DatePicker] Squash compat commits
0b069d9 
Move picker sources into lab (#4)

Update README.md

[DatePicker] Refactor pickers tests to testing-library and mocha (#5)

[TimePicker] Migrate tests to testing library (mui#8)

[DateTimePicker] Migrate tests  (mui#9)

Fix all pickers linter errors (mui#10)

Fix all circular dependencies (mui#11)

* Fix all circular dependencies

* Enable mocha eslint rules for typescript tests

[test] The last step to a green CI (mui#15)

Migrate pickers docs (mui#12)

Downgrade to withStyles for pickers sources (mui#16)

Add public api exports for pickers components (mui#17)

Consolidate component namespace and theme augmentation  (mui#18)

Describe conformance for pickers sub-components (mui#19)

Autogenerate proptypes for typescript sources  (mui#20)

Proper build output (mui#21)

Clear migration artifacts  (mui#23)

Eslint rule for lower-case test name convention  (mui#24)

DateRangePicker  (mui#25)

yarn deduplicate

Remove GridListTile

[DateTimePicker] Fix migration unit tests

Fix types

Fix typescript types migration issues

Fix yarn lerna build (mui#33)

Fix karma tests

use window.Touch for CI karma tests

Remove more outdated diff noise (mui#34)

Replace not valid formats with valid ISO strings

Try to fix CI touch tests

Skip tests if Touch events are not supported

Fix merge conflicts

Actually type-check

Fix safari tests

Remove lowercase test name rule

The casing is up to the test author.
We're not the grammar police in tests.

Fix lint

Format

Remove overzealous eslint-disable*

Debug failing tests

Better debugging

Timezones are fun

was isoString th efix?

Let's find out what's failing and then skip it

Branch for safari

Skip DateRangePicker in browsers

review

Matt's review

Co-authored-by: Matt <github@nospam.33m.co>

format

docs:i18n
@oliviertassinari oliviertassinari added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Dec 25, 2022
@zannager zannager added core Infrastructure work going on behind the scenes and removed status: waiting for maintainer These issues haven't been looked at yet by a maintainer labels Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
core Infrastructure work going on behind the scenes
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jessegrosjean @hai-cea @oliviertassinari @zannager