WIP: Add Field::ActiveStorage

[goosys]

• issue Pull in administrate-field_active_storage #2899
• thanks https://github.com/Dreamersoul/administrate-field-active_storage
• ref https://railsguides.jp/active_storage_overview.html

WIP

index	form

Usage

apt install lib-vips

# config/application.rb
config.load_defaults "#{Rails::VERSION::MAJOR}.#{Rails::VERSION::MINOR}"
# Or,
# config/enviroments/development.rb
config.active_storage.variant_processor = :vips

bin/rails db:migrate

TODO

• Field
  • Base
  • PreviewRenderer
  • ItemsRenderer
  • Refactor
• Upload
  • has_one_attached
  • has_many_attached
• Direct Upload
  • Upload
  • Error handling
• Replace
  • has_one_attached
• Append
  • has_many_attached
• Remove
  • has_one_attached
  • has_many_attached
  • JS implementation
• Preview
  • Image
    • Original
    • Variant
  • Audio
    • Original
    • Previewable
  • Video
    • Original
    • Previewable
  • SVG
  • PDF
  • Previewable
  • File
  • Other file type(?)
• Delivery
  • rails_blob_url
  • Proxy (Rails.application.config.active_storage.resolve_model_to_route)
  • Proxy and CDN
  • Authenticated Controllers
• Style
• Test
• Document

[goosys]

@pablobm @nickcharlton

I'm thinking of using this Field with relatively complex behavior as a good example of RenderableObject. What do you think?

By introducing RenderableObject like this, we can separate the logic from the view layer, allowing application developers to tweak layouts or add styles without worrying about the underlying logic.

Or do you think it would be better not to use RenderableObject here? I’d love to hear your thoughts.

[nickcharlton]

Yeah, let's try RenderableObject and see how it feels. If it makes a complex change much nice, it's definitely worth it.