aboutsummaryrefslogtreecommitdiffstats
path: root/actiontext/test/dummy
Commit message (Collapse)AuthorAgeFilesLines
* Upgrade webpack-dev-server version in test appsSharang Dashputre2019-03-092-435/+229
|
* Use the latest stable release of webpackerSharang Dashputre2019-03-092-2000/+3727
|
* SQLite3: Implement `add_foreign_key` and `remove_foreign_key`Ryuta Kamizono2019-02-111-0/+1
| | | | | | | | | | | | I implemented Foreign key create in `create_table` for SQLite3 at #24743. This follows #24743 to implement `add_foreign_key` and `remove_foreign_key`. Unfortunately SQLite3 has one limitation that `PRAGMA foreign_key_list(table-name)` doesn't have constraint name. So we couldn't implement find/remove foreign key by name for now. Fixes #35207. Closes #31343.
* Allow changing text and blob size without giving the `limit` optionRyuta Kamizono2019-01-292-2/+2
| | | | | | | | | | | | | | In MySQL, the text column size is 65,535 bytes by default (1 GiB in PostgreSQL). It is sometimes too short when people want to use a text column, so they sometimes change the text size to mediumtext (16 MiB) or longtext (4 GiB) by giving the `limit` option. Unlike MySQL, PostgreSQL doesn't allow the `limit` option for a text column (raises ERROR: type modifier is not allowed for type "text"). So `limit: 4294967295` (longtext) couldn't be used in Action Text. I've allowed changing text and blob size without giving the `limit` option, it prevents that migration failure on PostgreSQL.
* Revert "Apply `t.timestamps` changes in Action Text and Action Mailbox"Ryuta Kamizono2019-01-291-0/+0
| | | | This reverts commit 30f666f87ab873258b797b39f29cf852f7621bea.
* Apply `t.timestamps` changes in Action Text and Action MailboxRyuta Kamizono2019-01-291-0/+0
| | | | Follow up #34956.
* Make `t.timestamps` with precision by defaultRyuta Kamizono2019-01-262-8/+7
|
* Changed webserver to web server.alkesh262019-01-221-1/+1
|
* Allow using Action Mailbox on MySQL 5.5Ryuta Kamizono2019-01-181-5/+5
| | | | | | | | | | Active Record still support MySQL 5.5 which doesn't support datetime with precision. https://github.com/rails/rails/blob/9e34df00039d63b5672315419e76f06f80ef3dc4/activerecord/lib/active_record/connection_adapters/abstract_mysql_adapter.rb#L99-L101 So we should check `supports_datetime_with_precision?` on the connection.
* Move all npm packages to @rails scopeJavan Makhmali2019-01-101-1/+1
| | | | Fixes #33083
* Test actiontext on Rails 6.0bogdanvlviv2019-01-054-3/+4
| | | | | | | | | | | | - config.load_defaults 6.0 in the dummy app and fix the test since by default rails 6.0 configured does not generate "utf8" hidden input, see #32125 - Use `ActiveRecord::Migration[6.0]` in the dummy app since actiontext will be since Rails 6.0 - Fix `CreateActiveStorageTables` migration in the dummy app. Add `t.foreign_key :active_storage_blobs, column: :blob_id` It was added in 2ae3a29508e. - `rails/actiontext$ yarn install`
* Import Action TextGeorge Claghorn2019-01-0483-0/+7377