Active Storage Validations is a gem that allows you to add validations for Active Storage attributes.
This gems is doing it right for you! Just use validates :avatar, attached: true, content_type: 'image/png'
and that's it!
- Getting started
- Validators
- Upgrading from 1.x to 2.x
- Internationalization (I18n)
- Test matchers
- Contributing
- Additional information
Active Storage Validations work with Rails 6.1.4 onwards. Add this line to your application's Gemfile:
gem 'active_storage_validations'
And then execute:
$ bundle
Once you have installed the gem, you need to add the gem I18n error messages to your app. See Internationalization (I18n) section for more details.
Optionally, to use the image metadata validators (dimension
, aspect_ratio
and processable_file
), you will have to add one of the corresponding gems:
gem 'mini_magick', '>= 4.9.5'
# Or
gem 'ruby-vips', '>= 2.1.0'
Plus, you have to be sure to have the corresponding command-line tool installed on your system. For example, to use mini_magick
gem, you need to have imagemagick
installed on your system (both on your local and in your CI / production environments).
To use the video and audio metadata validators (dimension
, aspect_ratio
, processable_file
and duration
), you will not need to add any gems. However you will need to have the ffmpeg
command-line tool installed on your system (once again, be sure to have it installed both on your local and in your CI / production environments).
List of validators:
- Attached: validates if file(s) attached
- Limit: validates number of uploaded files
- Content type: validates file content type
- Size: validates file size
- Total size: validates total file size for several files
- Dimension: validates image / video dimensions
- Duration: validates video / audio duration
- Aspect ratio: validates image / video aspect ratio
- Processable file: validates if a file can be processed
Proc usage
Every validator can use procs instead of values in all the validator examples:
class User < ApplicationRecord
has_many_attached :files
validates :files, limit: { max: -> (record) { record.admin? ? 100 : 10 } }
end
Validates if the attachment is present.
The attached
validator has no options.
Use it like this:
class User < ApplicationRecord
has_one_attached :avatar
validates :avatar, attached: true
end
en:
errors:
messages:
blank: "can't be blank"
The error message for this validator relies on Rails own blank
error message.
Validates the number of uploaded files.
The limit
validator has several options:
min
: defines the minimum allowed number of filesmax
: defines the maximum allowed number of files
Use it like this:
class User < ApplicationRecord
has_many_attached :certificates
validates :certificates, limit: { min: 1, max: 10 } # restricts the number of files to between 1 and 10
end
en:
errors:
messages:
limit_out_of_range:
zero: "no files attached (must have between %{min} and %{max} files)"
one: "only 1 file attached (must have between %{min} and %{max} files)"
other: "total number of files must be between %{min} and %{max} files (there are %{count} files attached)"
limit_min_not_reached:
zero: "no files attached (must have at least %{min} files)"
one: "only 1 file attached (must have at least %{min} files)"
other: "%{count} files attached (must have at least %{min} files)"
limit_max_exceeded:
zero: "no files attached (maximum is %{max} files)"
one: "too many files attached (maximum is %{max} files, got %{count})"
other: "too many files attached (maximum is %{max} files, got %{count})"
The limit
validator error messages expose 2 values that you can use:
min
containing the minimum allowed number of files (e.g.1
)max
containing the maximum allowed number of files (e.g.10
)count
containing the current number of files (e.g.5
)
Validates if the attachment has an allowed content type.
The content_type
validator has several options:
with
: defines the exact allowed content type (string, symbol or regex)in
: defines the allowed content types (array of strings or symbols)spoofing_protection
: enables content type spoofing protection (boolean, defaults tofalse
)
As mentioned above, this validator can define content types in several ways:
- String:
image/png
orpng
- Symbol:
:png
- Regex:
/\Avideo\/.*\z/
Use it like this:
class User < ApplicationRecord
has_one_attached :avatar
validates :avatar, content_type: 'image/png' # only allows PNG images
validates :avatar, content_type: :png # only allows PNG images
validates :avatar, content_type: /\Avideo\/.*\z/ # only allows video files
validates :avatar, content_type: ['image/png', 'image/jpeg'] # only allows PNG and JPEG images
validates :avatar, content_type: { in: [:png, :jpeg], spoofing_protection: true } # only allows PNG, JPEG and their variants, with spoofing protection enabled
end
When using the content_type
validator, it is recommended to reflect the allowed content types in the html accept
attribute in the corresponding file fields in your views. This will prevent users from trying to upload files with not allowed content types (however it is only an UX improvement, a malicious user can still try to upload files with not allowed content types therefore the backend validation).
For example, if you want to only allow PNG and JPEG images, you can do this:
class User < ApplicationRecord
ACCEPTED_CONTENT_TYPES = ['image/png', 'image/jpeg'].freeze
has_one_attached :avatar
validates :avatar, content_type: ACCEPTED_CONTENT_TYPES
end
<%= form_with model: @user do |f| %>
<%= f.file_field :avatar,
accept: ACCEPTED_CONTENT_TYPES.join(',') %>
<% end %>
If you choose to use a content_type 'shorthand' (like png
), note that it will be converted to a full content type using Marcel::MimeType.for
under the hood. Therefore, you should check if the content_type is registered by Marcel::EXTENSIONS
. If it's not, you can register it by adding the following code to your config/initializers/mime_types.rb
file:
Marcel::MimeType.extend "application/ino", extensions: %w(ino), parents: "text/plain" # Registering arduino INO files
By default, the gem does not prevent content type spoofing. You can enable it by setting the spoofing_protection
option to true
in your validator options.
##### What is content type spoofing?
File content type spoofing happens when an ill-intentioned user uploads a file which hides its true content type by faking its extension and its declared content type value. For example, a user may try to upload a `.exe` file (application/x-msdownload content type) dissimulated as a `.jpg` file (image/jpeg content type).##### How do we prevent it?
The spoofing protection relies on both the linux `file` command and `Marcel` gem. Be careful, since it needs to load the whole file io to perform the analysis, it will use a lot of RAM for very large files. Therefore it could be a wise decision not to enable it in this case.Take note that the file
analyzer will not find the exactly same content type as the ActiveStorage blob (ActiveStorage content type detection relies on a different logic using content+filename+extension). To handle this issue, we consider a close parent content type to be a match. For example, for an ActiveStorage blob which content type is video/x-ms-wmv
, the file
analyzer will probably detect a video/x-ms-asf
content type, this will be considered as a valid match because these 2 content types are closely related. The correlation mapping is based on Marcel::TYPE_PARENTS
.
##### Edge cases
The difficulty to accurately predict a mime type may generate false positives, if so there are two solutions available: - If the ActiveStorage blob content type is closely related to the detected content type using the `file` analyzer, you can enhance `Marcel::TYPE_PARENTS` mapping using `Marcel::MimeType.extend "application/x-rar-compressed", parents: %(application/x-rar)` in the `config/initializers/mime_types.rb` file. (Please drop an issue so we can add it to the gem for everyone!) - If the ActiveStorage blob content type is not closely related, you still can disable the content type spoofing protection in the validator, if so, please drop us an issue so we can fix it for everyone!en:
errors:
messages:
content_type_invalid:
one: "has an invalid content type (authorized content type is %{authorized_human_content_types})"
other: "has an invalid content type (authorized content types are %{authorized_human_content_types})"
content_type_spoofed:
one: "has a content type that is not equivalent to the one that is detected through its content (authorized content type is %{authorized_human_content_types})"
other: "has a content type that is not equivalent to the one that is detected through its content (authorized content types are %{authorized_human_content_types})"
The content_type
validator error messages expose 7 values that you can use:
content_type
containing the content type of the sent file (e.g.image/png
)human_content_type
containing a more user-friendly version of the sent file content type (e.g. 'TXT' for 'text/plain')detected_content_type
containing the detected content type of the sent file usingspoofing_protection
option (e.g.image/png
)detected_human_content_type
containing a more user-friendly version of the sent file detected content type usingspoofing_protection
option (e.g. 'TXT' for 'text/plain')authorized_human_content_types
containing the list of authorized content types (e.g. 'PNG, JPEG' for['image/png', 'image/jpeg']
)count
containing the number of authorized content types (e.g.2
)filename
containing the filename
Validates each attached file size.
The size
validator has several options:
less_than
: defines the strict maximum allowed file sizeless_than_or_equal_to
: defines the maximum allowed file sizegreater_than
: defines the strict minimum allowed file sizegreater_than_or_equal_to
: defines the minimum allowed file sizebetween
: defines the allowed file size range
Use it like this:
class User < ApplicationRecord
has_one_attached :avatar
validates :avatar, size: { less_than: 2.megabytes } # restricts the file size to < 2MB
validates :avatar, size: { less_than_or_equal_to: 2.megabytes } # restricts the file size to <= 2MB
validates :avatar, size: { greater_than: 1.kilobyte } # restricts the file size to > 1KB
validates :avatar, size: { greater_than_or_equal_to: 1.kilobyte } # restricts the file size to >= 1KB
validates :avatar, size: { between: 1.kilobyte..2.megabytes } # restricts the file size to between 1KB and 2MB
end
It is always a good practice to limit the maximum file size to a reasonable value (like 2MB for avatar images). This helps prevent server storage issues, reduces upload/download times, and ensures better performance. Large files can consume excessive bandwidth and storage space, potentially impacting both server resources and user experience.
Plus, not setting a size limit inside your Rails app might lead into your server throwing a 413 Content Too Large
error, which is not as nice as a Rails validation error.
en:
errors:
messages:
file_size_not_less_than: "file size must be less than %{max} (current size is %{file_size})"
file_size_not_less_than_or_equal_to: "file size must be less than or equal to %{max} (current size is %{file_size})"
file_size_not_greater_than: "file size must be greater than %{min} (current size is %{file_size})"
file_size_not_greater_than_or_equal_to: "file size must be greater than or equal to %{min} (current size is %{file_size})"
file_size_not_between: "file size must be between %{min} and %{max} (current size is %{file_size})"
The size
validator error messages expose 4 values that you can use:
file_size
containing the current file size (e.g.1.5MB
)min
containing the minimum allowed file size (e.g.1KB
)max
containing the maximum allowed file size (e.g.2MB
)filename
containing the current file name
Validates the total file size for several files.
The total_size
validator has several options:
less_than
: defines the strict maximum allowed total file sizeless_than_or_equal_to
: defines the maximum allowed total file sizegreater_than
: defines the strict minimum allowed total file sizegreater_than_or_equal_to
: defines the minimum allowed total file sizebetween
: defines the allowed total file size range
Use it like this:
class User < ApplicationRecord
has_many_attached :certificates
validates :certificates, total_size: { less_than: 10.megabytes } # restricts the total size to < 10MB
validates :certificates, total_size: { less_than_or_equal_to: 10.megabytes } # restricts the total size to <= 10MB
validates :certificates, total_size: { greater_than: 1.kilobyte } # restricts the total size to > 1KB
validates :certificates, total_size: { greater_than_or_equal_to: 1.kilobyte } # restricts the total size to >= 1KB
validates :certificates, total_size: { between: 1.kilobyte..10.megabytes } # restricts the total size to between 1KB and 10MB
end
en:
errors:
messages:
total_file_size_not_less_than: "total file size must be less than %{max} (current size is %{total_file_size})"
total_file_size_not_less_than_or_equal_to: "total file size must be less than or equal to %{max} (current size is %{total_file_size})"
total_file_size_not_greater_than: "total file size must be greater than %{min} (current size is %{total_file_size})"
total_file_size_not_greater_than_or_equal_to: "total file size must be greater than or equal to %{min} (current size is %{total_file_size})"
total_file_size_not_between: "total file size must be between %{min} and %{max} (current size is %{total_file_size})"
The total_size
validator error messages expose 4 values that you can use:
file_size
containing the current file size (e.g.1.5MB
)min
containing the minimum allowed total file size (e.g.1KB
)max
containing the maximum allowed total file size (e.g.2MB
)
Validates the dimension of the attached files.
The dimension
validator has several options:
width
: defines the exact allowed width (integer)min
: defines the minimum allowed width (integer)max
: defines the maximum allowed width (integer)in
: defines the allowed width range (range)
height
: defines the exact allowed height (integer)min
: defines the minimum allowed height (integer)max
: defines the maximum allowed height (integer)in
: defines the allowed height range (range)
min
: defines the minimum allowed width and height (range)max
: defines the maximum allowed width and height (range)
Use it like this:
class User < ApplicationRecord
has_one_attached :avatar
validates :avatar, dimension: { width: 100 } # restricts the width to 100 pixels
validates :avatar, dimension: { width: { min: 80, max: 100 } } # restricts the width to between 80 and 100 pixels
validates :avatar, dimension: { width: { in: 80..100 } } # restricts the width to between 80 and 100 pixels
validates :avatar, dimension: { height: 100 } # restricts the height to 100 pixels
validates :avatar, dimension: { height: { min: 600, max: 1800 } } # restricts the height to between 600 and 1800 pixels
validates :avatar, dimension: { height: { in: 600..1800 } } # restricts the height to between 600 and 1800 pixels
validates :avatar, dimension: { min: 80..600, max: 100..1800 } # restricts the width to between 80 and 100 pixels, and the height to between 600 and 1800 pixels
end
en:
errors:
messages:
dimension_min_not_included_in: "must be greater than or equal to %{width} x %{height} pixel"
dimension_max_not_included_in: "must be less than or equal to %{width} x %{height} pixel"
dimension_width_not_included_in: "width is not included between %{min} and %{max} pixel"
dimension_height_not_included_in: "height is not included between %{min} and %{max} pixel"
dimension_width_not_greater_than_or_equal_to: "width must be greater than or equal to %{length} pixel"
dimension_height_not_greater_than_or_equal_to: "height must be greater than or equal to %{length} pixel"
dimension_width_not_less_than_or_equal_to: "width must be less than or equal to %{length} pixel"
dimension_height_not_less_than_or_equal_to: "height must be less than or equal to %{length} pixel"
dimension_width_not_equal_to: "width must be equal to %{length} pixel"
dimension_height_not_equal_to: "height must be equal to %{length} pixel"
media_metadata_missing: "is not a valid media file"
The dimension
validator error messages expose 6 values that you can use:
min
containing the minimum width or height allowedmax
containing the maximum width or height allowedwidth
containing the minimum or maximum width allowedheight
containing the minimum or maximum width allowedlength
containing the exact width or height allowedfilename
containing the current filename in error
Validates each attached audio / video file duration.
The duration
validator has several options:
less_than
: defines the strict maximum allowed file durationless_than_or_equal_to
: defines the maximum allowed file durationgreater_than
: defines the strict minimum allowed file durationgreater_than_or_equal_to
: defines the minimum allowed file durationbetween
: defines the allowed file duration range
Use it like this:
class User < ApplicationRecord
has_one_attached :avatar
validates :avatar, duration: { less_than: 2.minutes } # restricts the file duration to < 2 minutes
validates :avatar, duration: { less_than_or_equal_to: 2.minutes } # restricts the file duration to <= 2 minutes
validates :avatar, duration: { greater_than: 1.second } # restricts the file duration to > 1 second
validates :avatar, duration: { greater_than_or_equal_to: 1.second } # restricts the file duration to >= 1 second
validates :avatar, duration: { between: 1.second..2.minutes } # restricts the file duration to between 1 second and 2 minutes
end
en:
errors:
messages:
duration_not_less_than: "duration must be less than %{max} (current duration is %{duration})"
duration_not_less_than_or_equal_to: "duration must be less than or equal to %{max} (current duration is %{duration})"
duration_not_greater_than: "duration must be greater than %{min} (current duration is %{duration})"
duration_not_greater_than_or_equal_to: "duration must be greater than or equal to %{min} (current duration is %{duration})"
duration_not_between: "duration must be between %{min} and %{max} (current duration is %{duration})"
The duration
validator error messages expose 4 values that you can use:
duration
containing the current duration size (e.g.2 minutes
)min
containing the minimum allowed duration size (e.g.1 second
)max
containing the maximum allowed duration size (e.g.2 minutes
)filename
containing the current file name
Validates the aspect ratio of the attached files.
The aspect_ratio
validator has several options:
with
: defines the exact allowed aspect ratio (e.g.16/9
)in
: defines the allowed aspect ratios (e.g.16/9..16/10
)
This validator can define aspect ratios in several ways:
- Symbols:
- prebuilt aspect ratios:
:square
,:portrait
,:landscape
- custom aspect ratios (it must be of type
is_xx_yy
)::is_16_9
,:is_4_3
, etc.
- prebuilt aspect ratios:
Use it like this:
class User < ApplicationRecord
has_one_attached :avatar
validates :avatar, aspect_ratio: :square # restricts the aspect ratio to 1:1
validates :avatar, aspect_ratio: :portrait # restricts the aspect ratio to x:y where y > x
validates :avatar, aspect_ratio: :landscape # restricts the aspect ratio to x:y where x > y
validates :avatar, aspect_ratio: :is_16_9 # restricts the aspect ratio to 16:9
validates :avatar, aspect_ratio: %i[square is_16_9] # restricts the aspect ratio to 1:1 and 16:9
end
en:
errors:
messages:
aspect_ratio_not_square: "must be square (current file is %{width}x%{height}px)"
aspect_ratio_not_portrait: "must be portrait (current file is %{width}x%{height}px)"
aspect_ratio_not_landscape: "must be landscape (current file is %{width}x%{height}px)"
aspect_ratio_not_x_y: "must be %{authorized_aspect_ratios} (current file is %{width}x%{height}px)"
aspect_ratio_invalid: "has an invalid aspect ratio (valid aspect ratios are %{authorized_aspect_ratios})"
media_metadata_missing: "is not a valid media file"
The aspect_ratio
validator error messages expose 4 values that you can use:
authorized_aspect_ratios
containing the authorized aspect ratioswidth
containing the current width of the image/videoheight
containing the current height of the image/videofilename
containing the current filename in error
Validates if the attached files can be processed by MiniMagick or Vips (image) or ffmpeg (video/audio).
The processable_file
validator has no options.
Use it like this:
class User < ApplicationRecord
has_one_attached :avatar
validates :avatar, processable_file: true # ensures that the file is processable by MiniMagick or Vips (image) or ffmpeg (video/audio)
end
en:
errors:
messages:
file_not_processable: "is not identified as a valid media file"
The processable_file
validator error messages expose 1 value that you can use:
filename
containing the current filename in error
If you are upgrading from 1.x to 2.x, you will be pleased to note that a lot of things have been added and improved!
Added features:
duration
validator has been added for audio / video filesdimension
validator now supports videosaspect_ratio
validator now supports videosprocessable_image
validator is nowprocessable_file
validator and supports image/video/audio- All error messages have been given an upgrade and new variables that you can use
But this major version bump also comes with some breaking changes. Below are the main breaking changes you need to be aware of:
-
Error messages
- We advise you to replace all the v1 translations by the new v2 rather than changing them one by one
- The error messages have been completely rewritten to be more consistent and easier to understand (not breaking but might be a good idea to update them with the new versions)
- Some validator errors have been totally changed:
limit
validator keys have been totally reworkeddimension
validator keys have been totally reworkedcontent_type
validator keys have been totally reworkedprocessable_image
validator keys have been totally reworked
- Some keys have been changed:
image_metadata_missing
has been replaced bymedia_metadata_missing
aspect_ratio_is_not
has been replaced byaspect_ratio_not_x_y
- Some error messages variables names have been changed to improve readability:
aspect_ratio
validator:aspect_ratio
has been replaced byauthorized_aspect_ratios
content_type
validator:authorized_types
has been replaced byauthorized_human_content_types
size
validator:min_size
has been replaced bymin
max_size
has been replaced bymax
total_size
validator:min_size
has been replaced bymin
max_size
has been replaced bymax
-
content_type
validator- The
:in
option now only accepts 'valid' content types (ie content types deemed by Marcel as valid).- The check was mistakenly only performed on the
:with
option previously. Therefore, invalid content types were accepted in the:in
option, which is not the expected behavior. - This might break some cases when you had for example
content_type: ['image/png', 'image/jpg']
, becauseimage/jpg
is not a valid content type, it should be replaced byimage/jpeg
.
- The check was mistakenly only performed on the
- An
ArgumentError
is now raised ifimage/jpg
is used to make it easier to fix. You should now only useimage/jpeg
.
- The
-
processable_image
validator- The validator has been replaced by
processable_file
validator, be sure to replaceprocessable_image: true
toprocessable_file: true
- The associated matcher has also been updated accordingly, be sure to replace
validate_processable_image_of
tovalidate_processable_file_of
- The validator has been replaced by
Active Storage Validations uses I18n for error messages. Add these keys in your translation files to make them available:
en:
errors:
messages:
content_type_invalid:
one: "has an invalid content type (authorized content type is %{authorized_human_content_types})"
other: "has an invalid content type (authorized content types are %{authorized_human_content_types})"
content_type_spoofed:
one: "has a content type that is not equivalent to the one that is detected through its content (authorized content type is %{authorized_human_content_types})"
other: "has a content type that is not equivalent to the one that is detected through its content (authorized content types are %{authorized_human_content_types})"
file_size_not_less_than: "file size must be less than %{max} (current size is %{file_size})"
file_size_not_less_than_or_equal_to: "file size must be less than or equal to %{max} (current size is %{file_size})"
file_size_not_greater_than: "file size must be greater than %{min} (current size is %{file_size})"
file_size_not_greater_than_or_equal_to: "file size must be greater than or equal to %{min} (current size is %{file_size})"
file_size_not_between: "file size must be between %{min} and %{max} (current size is %{file_size})"
total_file_size_not_less_than: "total file size must be less than %{max} (current size is %{total_file_size})"
total_file_size_not_less_than_or_equal_to: "total file size must be less than or equal to %{max} (current size is %{total_file_size})"
total_file_size_not_greater_than: "total file size must be greater than %{min} (current size is %{total_file_size})"
total_file_size_not_greater_than_or_equal_to: "total file size must be greater than or equal to %{min} (current size is %{total_file_size})"
total_file_size_not_between: "total file size must be between %{min} and %{max} (current size is %{total_file_size})"
duration_not_less_than: "duration must be less than %{max} (current duration is %{duration})"
duration_not_less_than_or_equal_to: "duration must be less than or equal to %{max} (current duration is %{duration})"
duration_not_greater_than: "duration must be greater than %{min} (current duration is %{duration})"
duration_not_greater_than_or_equal_to: "duration must be greater than or equal to %{min} (current duration is %{duration})"
duration_not_between: "duration must be between %{min} and %{max} (current duration is %{duration})"
limit_out_of_range:
zero: "no files attached (must have between %{min} and %{max} files)"
one: "only 1 file attached (must have between %{min} and %{max} files)"
other: "total number of files must be between %{min} and %{max} files (there are %{count} files attached)"
limit_min_not_reached:
zero: "no files attached (must have at least %{min} files)"
one: "only 1 file attached (must have at least %{min} files)"
other: "%{count} files attached (must have at least %{min} files)"
limit_max_exceeded:
zero: "no files attached (maximum is %{max} files)"
one: "too many files attached (maximum is %{max} files, got %{count})"
other: "too many files attached (maximum is %{max} files, got %{count})"
media_metadata_missing: "is not a valid media file"
dimension_min_not_included_in: "must be greater than or equal to %{width} x %{height} pixel"
dimension_max_not_included_in: "must be less than or equal to %{width} x %{height} pixel"
dimension_width_not_included_in: "width is not included between %{min} and %{max} pixel"
dimension_height_not_included_in: "height is not included between %{min} and %{max} pixel"
dimension_width_not_greater_than_or_equal_to: "width must be greater than or equal to %{length} pixel"
dimension_height_not_greater_than_or_equal_to: "height must be greater than or equal to %{length} pixel"
dimension_width_not_less_than_or_equal_to: "width must be less than or equal to %{length} pixel"
dimension_height_not_less_than_or_equal_to: "height must be less than or equal to %{length} pixel"
dimension_width_not_equal_to: "width must be equal to %{length} pixel"
dimension_height_not_equal_to: "height must be equal to %{length} pixel"
aspect_ratio_not_square: "must be square (current file is %{width}x%{height}px)"
aspect_ratio_not_portrait: "must be portrait (current file is %{width}x%{height}px)"
aspect_ratio_not_landscape: "must be landscape (current file is %{width}x%{height}px)"
aspect_ratio_not_x_y: "must be %{authorized_aspect_ratios} (current file is %{width}x%{height}px)"
aspect_ratio_invalid: "has an invalid aspect ratio (valid aspect ratios are %{authorized_aspect_ratios})"
file_not_processable: "is not identified as a valid media file"
Other translation files are available (here)[https://github.com/igorkasyanchuk/active_storage_validations/tree/master/config/locales].
The gem also provides RSpec-compatible and Minitest-compatible matchers for testing the validators.
In spec_helper.rb
, you'll need to require the matchers:
require 'active_storage_validations/matchers'
And include the module:
RSpec.configure do |config|
config.include ActiveStorageValidations::Matchers
end
Matcher methods available:
describe User do
# aspect_ratio:
# #allowing, #rejecting
it { is_expected.to validate_aspect_ratio_of(:avatar).allowing(:square) }
it { is_expected.to validate_aspect_ratio_of(:avatar).rejecting(:portrait) }
# attached
it { is_expected.to validate_attached_of(:avatar) }
# processable_file
it { is_expected.to validate_processable_file_of(:avatar) }
# limit
# #min, #max
it { is_expected.to validate_limits_of(:avatar).min(1) }
it { is_expected.to validate_limits_of(:avatar).max(5) }
# content_type:
# #allowing, #rejecting
it { is_expected.to validate_content_type_of(:avatar).allowing('image/png', 'image/gif') }
it { is_expected.to validate_content_type_of(:avatar).rejecting('text/plain', 'text/xml') }
# dimension:
# #width, #height, #width_min, #height_min, #width_max, #height_max, #width_between, #height_between
it { is_expected.to validate_dimensions_of(:avatar).width(250) }
it { is_expected.to validate_dimensions_of(:avatar).height(200) }
it { is_expected.to validate_dimensions_of(:avatar).width_min(200) }
it { is_expected.to validate_dimensions_of(:avatar).height_min(100) }
it { is_expected.to validate_dimensions_of(:avatar).width_max(500) }
it { is_expected.to validate_dimensions_of(:avatar).height_max(300) }
it { is_expected.to validate_dimensions_of(:avatar).width_between(200..500) }
it { is_expected.to validate_dimensions_of(:avatar).height_between(100..300) }
# size:
# #less_than, #less_than_or_equal_to, #greater_than, #greater_than_or_equal_to, #between
it { is_expected.to validate_size_of(:avatar).less_than(50.kilobytes) }
it { is_expected.to validate_size_of(:avatar).less_than_or_equal_to(50.kilobytes) }
it { is_expected.to validate_size_of(:avatar).greater_than(1.kilobyte) }
it { is_expected.to validate_size_of(:avatar).greater_than_or_equal_to(1.kilobyte) }
it { is_expected.to validate_size_of(:avatar).between(100..500.kilobytes) }
# total_size:
# #less_than, #less_than_or_equal_to, #greater_than, #greater_than_or_equal_to, #between
it { is_expected.to validate_total_size_of(:avatar).less_than(50.kilobytes) }
it { is_expected.to validate_total_size_of(:avatar).less_than_or_equal_to(50.kilobytes) }
it { is_expected.to validate_total_size_of(:avatar).greater_than(1.kilobyte) }
it { is_expected.to validate_total_size_of(:avatar).greater_than_or_equal_to(1.kilobyte) }
it { is_expected.to validate_total_size_of(:avatar).between(100..500.kilobytes) }
# duration:
# #less_than, #less_than_or_equal_to, #greater_than, #greater_than_or_equal_to, #between
it { is_expected.to validate_duration_of(:introduction).less_than(50.seconds) }
it { is_expected.to validate_duration_of(:introduction).less_than_or_equal_to(50.seconds) }
it { is_expected.to validate_duration_of(:introduction).greater_than(1.minute) }
it { is_expected.to validate_duration_of(:introduction).greater_than_or_equal_to(1.minute) }
it { is_expected.to validate_duration_of(:introduction).between(100..500.seconds) }
end
(Note that matcher methods are chainable)
All matchers can currently be customized with Rails validation options:
describe User do
# :allow_blank
it { is_expected.to validate_attached_of(:avatar).allow_blank }
# :on
it { is_expected.to validate_attached_of(:avatar).on(:update) }
it { is_expected.to validate_attached_of(:avatar).on(%i[update custom]) }
# :message
it { is_expected.to validate_dimensions_of(:avatar).width(250).with_message('Invalid dimensions.') }
end
To use the matchers, make sure you have the shoulda-context gem up and running.
You need to require the matchers:
require 'active_storage_validations/matchers'
And extend the module:
class ActiveSupport::TestCase
extend ActiveStorageValidations::Matchers
end
Then you can use the matchers with the syntax specified in the RSpec section, just use should validate_method
instead of it { is_expected_to validate_method }
as specified in the shoulda-context gem.
If you want to contribute to the project, you will have to fork the repository and create a new branch from the master
branch. Then build your feature, or fix the issue, and create a pull request. Be sure to add tests for your changes.
Before submitting your pull request, run the tests to make sure everything works as expected.
To run the gem tests, launch the following commands in the root folder of gem repository:
BUNDLE_GEMFILE=gemfiles/rails_6_1_4.gemfile bundle exec rake test
to run for Rails 6.1.4BUNDLE_GEMFILE=gemfiles/rails_7_0.gemfile bundle exec rake test
to run for Rails 7.0BUNDLE_GEMFILE=gemfiles/rails_7_1.gemfile bundle exec rake test
to run for Rails 7.1BUNDLE_GEMFILE=gemfiles/rails_7_2.gemfile bundle exec rake test
to run for Rails 7.2BUNDLE_GEMFILE=gemfiles/rails_8_0.gemfile bundle exec rake test
to run for Rails 8.0
Snippet to run in console:
BUNDLE_GEMFILE=gemfiles/rails_6_1_4.gemfile bundle
BUNDLE_GEMFILE=gemfiles/rails_7_0.gemfile bundle
BUNDLE_GEMFILE=gemfiles/rails_7_1.gemfile bundle
BUNDLE_GEMFILE=gemfiles/rails_7_2.gemfile bundle
BUNDLE_GEMFILE=gemfiles/rails_8_0.gemfile bundle
BUNDLE_GEMFILE=gemfiles/rails_6_1_4.gemfile bundle exec rake test
BUNDLE_GEMFILE=gemfiles/rails_7_0.gemfile bundle exec rake test
BUNDLE_GEMFILE=gemfiles/rails_7_1.gemfile bundle exec rake test
BUNDLE_GEMFILE=gemfiles/rails_7_2.gemfile bundle exec rake test
BUNDLE_GEMFILE=gemfiles/rails_8_0.gemfile bundle exec rake test
Tips:
- To focus a specific test, use the
focus
class method provided by minitest-focus - To focus a specific file, use the TEST option provided by minitest, e.g. to only run
size_validator_test.rb
file you will launch the following command:bundle exec rake test TEST=test/validators/size_validator_test.rb
We have a long list of valued contributors. Check them all at:
https://github.com/igorkasyanchuk/active_storage_validations/graphs/contributors
The gem is available as open source under the terms of the MIT License.