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

use stable version 1.0 for "reactjs/react-php-v8js" #56

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

use stable version 1.0 for "reactjs/react-php-v8js" #56

wants to merge 1 commit into from

Conversation

mscharl
Copy link

@mscharl mscharl commented Jan 10, 2016

No description provided.

@talyssonoc
Copy link
Owner

@mscharl Can you please check the breaking test?

@TomCaserta
Copy link
Contributor

Is the breaking test not caused by the v8js extension not being added to php.ini in the test environment? It appears to be failing on my PR too.

@talyssonoc
Copy link
Owner

@mscharl could you rebase it now that the errors are fixed?

@mscharl
Copy link
Author

mscharl commented Jan 25, 2016

I should look into my Github Inbox more often.

It seems as if its even worse now.
Before rebasing only PHP 5.4 failed - now all of them fail.

@TomCaserta
Copy link
Contributor

Hmm it looks like its here:

+'Warning: React.renderToString is deprecated. Please use ReactDOMServer.renderToString from require('react-dom/server') instead.Hello, react-laravel'

This is because we just updated React to 0.14 and the stable version of react-php-v8js I presume uses React.renderToString.

For this to work we will have to either revert back to the old react, implement our own error handler to ignore that warning, create our own polyfill for the console for serverside javascript (so it doesnt actually throw an error for that warning) or finally just not use the stable version of react-php-v8js.

@mscharl
Copy link
Author

mscharl commented Jan 25, 2016

That sucks ^.^
I think the best solution for now is to not use the stable version and wait :)

@sisve
Copy link

sisve commented Feb 4, 2016

I've filed an issue with react-php-v8js to issue another release with the fixes. reactjs/react-php-v8js#21

@sisve
Copy link

sisve commented Feb 4, 2016

I've been informed by @TomCaserta that an update in react-php-v8js will not be enough to solve this issue since react-laravel is on a newer version of React than react-php-v8js.

@zpao
Copy link

zpao commented Feb 5, 2016

Thanks for filing that issue @sisve. I commented there about what we want to call the version number.

since react-laravel is on a newer version of React than react-php-v8js

Not sure what that means. react-php-v8js in master right now just depends on React 0.14 APIs. We haven't published a newer version of React so not sure how react-laravel would be incompatible (looks like it's using 0.14.6). Once a new stable version of react-php-v8js is out you should be fine.

@TomCaserta
Copy link
Contributor

Yeah he was talking about the current stable version of react-php-v8js being on an older version of react, ie. why this library cannot use the stable version of react-php-v8js without incurring the warnings about React.renderToString being depreciated.

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.

5 participants