🚀 Big News: Socket Acquires Coana to Bring Reachability Analysis to Every Appsec Team.Learn more →
Socket
Book a DemoInstallSign in
Socket
Book a DemoInstallSign in

@rails/activestorage

Package Overview
Dependencies
Maintainers
11
Versions
133
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@rails/activestorage - npm Package Compare versions

Comparing version

6.1.1
to
6.1.2

5

CHANGELOG.md

@@ -0,1 +1,6 @@

## Rails 6.1.2 (February 09, 2021) ##
* No changes.
## Rails 6.1.1 (January 07, 2021) ##

@@ -2,0 +7,0 @@

2

package.json
{
"name": "@rails/activestorage",
"version": "6.1.1",
"version": "6.1.2",
"description": "Attach cloud and local files in Rails applications",

@@ -5,0 +5,0 @@ "main": "app/assets/javascripts/activestorage.js",

2

README.md

@@ -13,3 +13,3 @@ # Active Storage

A key difference to how Active Storage works compared to other attachment solutions in Rails is through the use of built-in [Blob](https://github.com/rails/rails/blob/master/activestorage/app/models/active_storage/blob.rb) and [Attachment](https://github.com/rails/rails/blob/master/activestorage/app/models/active_storage/attachment.rb) models (backed by Active Record). This means existing application models do not need to be modified with additional columns to associate with files. Active Storage uses polymorphic associations via the `Attachment` join model, which then connects to the actual `Blob`.
A key difference to how Active Storage works compared to other attachment solutions in Rails is through the use of built-in [Blob](https://github.com/rails/rails/blob/main/activestorage/app/models/active_storage/blob.rb) and [Attachment](https://github.com/rails/rails/blob/main/activestorage/app/models/active_storage/attachment.rb) models (backed by Active Record). This means existing application models do not need to be modified with additional columns to associate with files. Active Storage uses polymorphic associations via the `Attachment` join model, which then connects to the actual `Blob`.

@@ -16,0 +16,0 @@ `Blob` models store attachment metadata (filename, content-type, etc.), and their identifier key in the storage service. Blob models do not store the actual binary data. They are intended to be immutable in spirit. One file, one blob. You can associate the same blob with multiple application models as well. And if you want to do transformations of a given `Blob`, the idea is that you'll simply create a new one, rather than attempt to mutate the existing one (though of course you can delete the previous version later if you don't need it).