aboutsummaryrefslogtreecommitdiffstats
path: root/Gemfile.lock
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #29859 from dwightwatson/feature/rack-testRafael Mendonça França2017-07-241-65/+70
|\ | | | | | | Update rack-test dependency constraint
| * Update rack-test dependency constraintDwight Watson2017-07-241-68/+77
| |
* | Merge pull request #29908 from deivid-rodriguez/fix_warnings_in_railties_testsRafael França2017-07-241-10/+20
|\ \ | | | | | | Fix warnings in railties tests
| * | Fix warnings in railties testsDavid Rodríguez2017-07-241-10/+20
| |/ | | | | | | This warning has been fixed in sass-rails. This change picks up the fix.
* / Refactor Active Record to let Arel manage bind paramsSean Griffin2017-07-241-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A common source of bugs and code bloat within Active Record has been the need for us to maintain the list of bind values separately from the AST they're associated with. This makes any sort of AST manipulation incredibly difficult, as any time we want to potentially insert or remove an AST node, we need to traverse the entire tree to find where the associated bind parameters are. With this change, the bind parameters now live on the AST directly. Active Record does not need to know or care about them until the final AST traversal for SQL construction. Rather than returning just the SQL, the Arel collector will now return both the SQL and the bind parameters. At this point the connection adapter will have all the values that it had before. A bit of this code is janky and something I'd like to refactor later. In particular, I don't like how we're handling associations in the predicate builder, the special casing of `StatementCache::Substitute` in `QueryAttribute`, or generally how we're handling bind value replacement in the statement cache when prepared statements are disabled. This also mostly reverts #26378, as it moved all the code into a location that I wanted to delete. /cc @metaskills @yahonda, this change will affect the adapters Fixes #29766. Fixes #29804. Fixes #26541. Close #28539. Close #24769. Close #26468. Close #26202. There are probably other issues/PRs that can be closed because of this commit, but that's all I could find on the first few pages.
* Move back to @matthewd's close io fixed rb-inotify.Kasper Timm Hansen2017-07-191-2/+11
|
* Add bootsnap to default Gemfile:Burke Libbey2017-07-171-0/+4
| | | | | | Bootsnap precomputes load path resolution and caches ruby ISeq and YAML parsing/compilation, reducing application boot time by approximately 50% on supported configurations.
* Test thor masterRafael Mendonça França2017-07-071-1/+7
|
* Commit gemfile.lockRafael Mendonça França2017-07-041-1/+1
|
* Use bulk INSERT to insert fixturesKir Shatrov2017-06-201-1/+1
| | | | | | | | Improves the performance from O(n) to O(1). Previously it would require 50 queries to insert 50 fixtures. Now it takes only one query. Disabled on sqlite which doesn't support multiple inserts.
* Merge pull request #29488 from utilum/update_gemfileMatthew Draper2017-06-181-9/+2
|\ | | | | | | Fixes FIXME: rb-inotify 0.99 has been released
| * Fixes FIXME: rb-inotify 0.99 has been releasedutilum2017-06-171-11/+3
|/
* Bundle capybara 2.14.1 that includes fix for Ruby warningsyuuji.yaginuma2017-06-081-2/+2
| | | | Ref: https://github.com/teamcapybara/capybara/pull/1868
* Let's test nokogiri 1.8 against edge Rails, and vice versaAkira Matsuda2017-06-061-8/+8
|
* Merge pull request #29187 from robin850/remove-mathnRafael França2017-05-301-2/+0
|\ | | | | Remove requirement on mathn
| * Remove requirement on mathnRobin Dupret2017-05-301-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | The test using mathn was first introduced in f1d9179 to check that the `distance_of_time_in_words` properly doesn't use the `Fixnum#/` method by explicitly requiring this library as it redefines this method. Given that `mathn` has been gemified in Ruby 2.5 and is deprecated since version 2.2, we can certainly safely assume that people will most-likely not require this library in their application. However, to make sure that we don't regress, let's add a test similar to the one before f1d9179.
* | Bump RuboCop to 0.49.1Koichi ITO2017-05-301-1/+1
| |
* | Bump `delayed_job_active_record` gemyuuji.yaginuma2017-05-281-4/+4
| |
* | Switch to rb-inotify masterMatthew Draper2017-05-271-5/+5
| | | | | | | | https://github.com/guard/rb-inotify/pull/49 has been merged.
* | Bump rubocop and dependent gem versionsKoichi ITO2017-05-241-2/+5
|/
* bundle up sidekiq to the one with safer integration with Rails 5Akira Matsuda2017-05-211-3/+3
| | | | see: https://github.com/mperham/sidekiq/blob/master/5.0-Upgrade.md
* bundle up redis to the one that does not warn about ::Fixnum deprecationAkira Matsuda2017-05-211-2/+2
|
* mathn has been gemified in ruby 2.5Akira Matsuda2017-05-191-0/+2
|
* bundle mail 2.6.5 that includes fix for ::Fixnum warningAkira Matsuda2017-05-191-1/+1
|
* Bump rack versionyuuji.yaginuma2017-05-161-1/+1
|
* Allow capybara minor releasesJustin Coyne2017-05-051-6/+6
| | | | | | Capybara 2.14.0 was released. Loosen the tight constraint in the generated Gemfile, so that Rails applications can take advantage of the new version
* Don't pass `arel.engine` to `Arel::SelectManager.new`Ryuta Kamizono2017-05-051-1/+1
| | | | | | The argument of `Arel::SelectManager.new` is `table`, not `engine`. https://github.com/rails/arel/blob/v8.0.0/lib/arel/select_manager.rb#L10
* Use mysql2 0.4.6 to suport MySQL 8.0.1Yasuo Honda2017-05-041-3/+3
| | | | Follow up #28733 and brianmario/mysql2#840
* Ask for a sane version of SDocZachary Scott2017-04-231-4/+4
| | | | | This will allow me to push a release, including bug fixes, without having to update Rails everytime.
* Fix all style guides violationsRafael Mendonça França2017-04-191-2/+2
| | | | | Closes #28382 Closes #28651
* Bump the bundled GlobalID version.Kasper Timm Hansen2017-04-161-5/+5
|
* Revert "Avoid broken faraday 0.12.0 release"Matthew Draper2017-04-021-1/+0
| | | | This reverts commit 82a7593e3ac427215a280dae5bd6cd42f9404650.
* Avoid broken faraday 0.12.0 releaseMatthew Draper2017-04-021-1/+2
|
* Start Rails 5.2 developmentMatthew Draper2017-03-221-35/+41
|
* Bump Capybara and include Minitest::Assertionseileencodes2017-03-171-2/+2
| | | | | | | | | | | | | | | | | | | | | Capybara was updated in teamcapybara/capybara#1841 to use Minitest style assertions so that system test output shows x number of assertions, x numbe of failures, etc. Before: ``` 6 runs, 0 assertions, 0 failures, 0 errors, 0 skips ``` After: ``` 6 runs, 7 assertions, 1 failures, 0 errors, 0 skips ``` This change bumps Capybara from 2.7.0 to 2.13.0 and includes the required minitest assertion file in the test case. :tada:
* Restore action_cable.js UMD module support. Fixes #28366Javan Makhmali2017-03-111-0/+2
|
* Preparing for 5.1.0.beta1 releaseRafael Mendonça França2017-02-231-33/+33
|
* Use released arelRafael Mendonça França2017-02-211-8/+2
|
* Move and rename system testseileencodes2017-02-201-5/+1
| | | | | | | | | | * Move system tests back into Action Pack * Rename `ActionSystemTest` to `ActionDispatch::SystemTestCase` * Remove private base module and only make file for public `SystemTestCase` class, name private module `SystemTesting` * Rename `ActionSystemTestCase` to `ApplicationSystemTestCase` * Update corresponding documentation and guides * Delete old `ActionSystemTest` files
* Turn system testing into it's own gem and renameeileencodes2017-02-201-2/+6
| | | | | | | | | | Renames `Rails::SystemTestCase` to `ActionSystemTest` and moves it to a gem under the Rails name. We need to name the class `ActionSystemTestCase` because the gem expects a module but tests themselves expect a class. Adds MIT-LICENSE, CHANGELOG, and README for the future.
* Add tests for system testingeileencodes2017-02-201-0/+10
| | | | | | | | | | * Adds test case test * Adds driver adapter test * Adds tests for capybara seleium driver (testing the settings not actually opening the browser to test capybara w/ selenium because that would so so so slow) * Adds tests for rack test driver * Adds tests for generators
* Test with the newest i18nAkira Matsuda2017-02-111-1/+1
| | | | which is bundled in new apps by default
* Use released resqueyuuji.yaginuma2017-02-101-12/+7
|
* Fix rubocop violationsRafael Mendonça França2017-02-091-1/+3
|
* delayed_job and delayed_job_active_record gems with AR5 support are availableAkira Matsuda2017-01-291-17/+7
|
* bundle update some gemsAkira Matsuda2017-01-291-3/+3
| | | | | | * puma 3.7.0: to let kill("TERM") properly terminate the process in railties test (3.6.2 doesnot on my machine) * amq-protocol 2.1.0: to reduce warnings in AJ tests * rails-html-sanitizer: missing change in a previous commit that updated Gemfile
* Change ActionView ERB Handler from Erubis to ErubiJeremy Evans2017-01-251-2/+4
| | | | | | | | | | | | | | | | | | | | | | | Erubi offers the following advantages for Rails: * Works with ruby's --enable-frozen-string-literal option * Has 88% smaller memory footprint * Does no freedom patching (Erubis adds a method to Kernel) * Has simpler internals (1 file, <150 lines of code) * Has an open development model (Erubis doesn't have a public source control repository or bug tracker) * Is not dead (Erubis hasn't been updated since 2011) Erubi is a simplified fork of Erubis that contains just the parts that are generally needed (which includes the parts that Rails uses). The only intentional difference in behavior is that it does not include support for <%=== tags for debug output. That could be added to the ActionView ERB handler if it is desired. The Erubis template handler remains in a deprecated state so that code that accesses it directly does not break. It can be removed after Rails 5.1.
* Revert "I guess we're ready for the randomized tests now"Akira Matsuda2017-01-181-3/+1
| | | | | | This reverts commit 8c155c932f37fd2de5b530bc076ed60a03bc926c. Not really :cry:
* I guess we're ready for the randomized tests nowAkira Matsuda2017-01-181-1/+3
|
* Fix all rubocop violationsRafael Mendonça França2017-01-171-15/+13
|