ActionDispatch::Assertions::SelectorAssertions — autoloading issue? #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
This is actually a workaround for Issue #2. |
|
Herewith I'm confirming both the problem as well as the fix. Please pull from rubychan fxn. |
|
+1 |
1 similar comment
|
+1 |
|
+1 fixes issue on rails 3.1.0.rc6. @fxn |
Member
|
Thanks, will release a new gem shortly, please use the git repo meanwhile. |
fxn
added a commit
that referenced
this pull request
Aug 22, 2011
…3f1cd3d ActionDispatch::Assertions::SelectorAssertions — autoloading issue?
Author
|
Thanks :D |
korny
pushed a commit
to korny/prototype-rails
that referenced
this pull request
Apr 11, 2022
CI-1614 Add back the disableFormElements functionality
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the prototype-rails won't load on Rails 3.1.0rc2+.
Somehow, requiring ActionDispatch::Assertions before ActionDispatch::Assertions::SelectorAssertions fixed it.