Skip to content

Conversation

mapreal19
Copy link
Contributor

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@samnang @justin808 am I missing something here? I'm getting console is undefined on the specs

Copy link
Member

Choose a reason for hiding this comment

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

be sure that you're working off of the latest. Rebase your changes on top of the latest.

Copy link
Member

Choose a reason for hiding this comment

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

@mapreal19 We're doing a lot of reworking of the internals, so I'd first focus on the capybara tests. Especially important to get a test that verifies the created HTML for server rendering.

You might want to use the same driver we use in https://github.com/shakacode/react-webpack-rails-tutorial

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@justin808 👍

Copy link
Contributor

Choose a reason for hiding this comment

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

@mapreal19 I totally agree with @justin808 . We start with integration level is better because a lot of changes haven't merged, but the functionality should be the same.

@justin808
Copy link
Member

@mapreal19 Can you tune this up, and let's merge this if appropriate.

@justin808
Copy link
Member

@robwise Can you pull this into your own fork and see if this helps with coverage? Thanks.

@robwise
Copy link
Contributor

robwise commented Oct 19, 2015

@justin808 Coverage is the same, but it slightly increases the hits per line. Also, two of the tests were failing because I believe they were calling the wrong method, so I fixed those. One was also expecting a message that actually had an additional line return and blank space in the result. I matched it to pass, but I'm not sure if that's what we want or not.

The tests are not redundant with what we've already got, so I think they have value regardless.

Before:
image

After:
image

@robwise robwise mentioned this pull request Oct 20, 2015
@justin808
Copy link
Member

@robwise can you rebase this on top of master?

@robwise
Copy link
Contributor

robwise commented Oct 21, 2015

@justin808 Done just now, it's up on #66

Do we have any more info about the whitespace thing?

@justin808
Copy link
Member

@robwise Regarding the whitspace thing, you'd want to look at the source. My guess is that there is just whitespace in the ERB file around the tag.

@justin808 justin808 closed this Oct 21, 2015
AbanoubGhadban pushed a commit that referenced this pull request Sep 25, 2025
* React on Rails Pro Prep for Production
* JS evaluation caching
* Advanced error handling
* Many improvements to the test suite
* Doc improvements
* Based on React on Rails 11.0.7 and higher
AbanoubGhadban pushed a commit that referenced this pull request Sep 26, 2025
* React on Rails Pro Prep for Production
* JS evaluation caching
* Advanced error handling
* Many improvements to the test suite
* Doc improvements
* Based on React on Rails 11.0.7 and higher
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.

4 participants