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.

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

feature: migrate to react 16 #141

Merged
merged 9 commits into from
Oct 4, 2017
Merged

Conversation

jasonkuhrt
Copy link
Owner

@jasonkuhrt jasonkuhrt commented Oct 3, 2017

Will close #135.

  • react 16
  • class syntax
  • no custom portal
  • remove unused test deps

@jasonkuhrt
Copy link
Owner Author

@knowbody here's my start. It seems to be working so far. Going to tweak a few more things and see if I can break anything.

@Kerumen
Copy link
Contributor

Kerumen commented Oct 3, 2017

Working? The first layout glitch is still there. Even worse. (NB: I clicked once, for the first toggle)

kapture 2017-10-03 at 10 14 14

Latest Chrome.

@jebarjonet
Copy link

On my computer (and latest Chrome) it works well, that is a strange behavior

@Kerumen
Copy link
Contributor

Kerumen commented Oct 3, 2017

Ok I managed to narrow the bug. It appears only when you resize the "Action Logger" until the component window is exactly 554px height (displayed in the bottom right corner). It seems to be an edge case where the positioning system can't find the spot between above and right.

@jasonkuhrt
Copy link
Owner Author

@Kerumen Hey, yeah I've seen that before and I think there was an issue at one time about it. Maybe its come back... It looks like an instance of this edge case. Integrating Forto #95 should make this issue go away for good though. Anyways not sure this is an issue particular to this PR. I'll try recreating on master.

@jasonkuhrt
Copy link
Owner Author

@Kerumen I'm not able to reproduce the issue at 554px height locally or at https://littlebits.github.io/react-popover. But I don't doubt what you saw. I don't see an evidence that this PR is the culprit though.

@Kerumen
Copy link
Contributor

Kerumen commented Oct 3, 2017

@jasonkuhrt Yes the particular 554px edge case is weird but it won't happen on a real app.
And you're right, I don't guess it's related to this PR.

package.json Outdated
"prettier": "^1.7.3",
"ramda": "^0.18.0",
"react": "^15.4.2",
"react-dom": "^15.4.2",
"react": "16",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably would be better to not use exact v16 and instead use ^16.0.0

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yeah, not used to yarn upgrade@... yet. Shouldn't we make react deps peer deps too?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But meh this is still an issue yarnpkg/yarn#2479 so whatever will leave peer deps definition for now.

lib/index.js Outdated
}
constructor (props) {
super(props)
this.checkTargetReposition = this.checkTargetReposition.bind(this)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you use arrow functions then you wouldn't need to bind functions in the constructor:

checkTargetReposition = () => {
  // ...
}

@knowbody
Copy link

knowbody commented Oct 3, 2017

thank you for working on this @jasonkuhrt!

@jasonkuhrt jasonkuhrt merged commit b57870c into master Oct 4, 2017
@jasonkuhrt jasonkuhrt deleted the feature/135/migrate-to-react-16 branch October 4, 2017 01:44
@jasonkuhrt
Copy link
Owner Author

Thanks everyone for your feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

React v16.0 & Popover issue
4 participants