Hello world-changing Rubyists,
I’m experimenting with ActiveStorage and questions popped up. Since they revolve around features, I thought I’d post them here. Most of the „missing“ features have been listed by the author of Shrine in this reddit post <https://www.reddit.com/r/ruby/comments/6lm251/activestorage_a_brandnew_framework_for_managing/djvnlgv>, yet not all of them are necessary to begin using ActiveStorage in production or early alpha. One feature I find important though is handling validation errors. I don’t want Blobs in my database which are never actually attached to my records. Would that not be the next feature to implement? That is to say, solving this exclamation-mark riddle in the current README in ActiveStorage: def create message = Message.create! params.require(:message).permit(:title, :content) message.images.attach(params[:message][:images])end But let’s say that I can work around that with transactions and JS validations, I’d still be facing another problem. I have one S3 bucket per environment and everything neatly organized in directories, yet ActiveSupport clutters up the root directory. Would that *conceptually* be solved like this commit <https://github.com/halo/rails/commit/c8bc88dbfa4c73813b7459a80c0c4f7e83d13980> ? Lastly, if I were to document for developers how to use ActiveStorage (even in this early stage) - would I do that right in the ActiveStorage README? I'm missing the up-to-date equivalent to this section <https://github.com/rails/rails/blob/9330d01ada9ce6768d14c59b99cd3860e209737a/activestorage/README.md#installation> . Thank you for your guidance. halo -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
