Compatibility with native middleman redirects

[smith]

As of Middleman 3.1.2, middleman has a built-in redirect method that you can use to generate pages with meta refreshes.

Unfortunately, the API for this is different than middleman-s3_redirect, since it uses:

redirect '/foo/bar', to: '/baz'

could there be a way to make the built-in redirects work in development, but use the s3 redirects when deploying, all with the same syntax? That would be nice. Thanks!

[dpehrson]

I've been looking into this as well and would actually just like to see this entire gem merged into middleman-s3_sync if possible.

One oddity I noticed in middleman is that there doesn't seem to be a way to access the to: value of the Middleman::Sitemap::Extensions::Redirects::RedirectResource objects. The value is stored in the request_path instance variable, but the #request_path method doesn't actually return that value, in fact the method is explicitly commented out, strangely.

@fredjean You have more experience than myself, would it be possible to hook into the newer middleman functionality and simply override the built-in functionality when building/syncing? Also, would it be possible to just merge this behavior into middleman-s3_sync?

[fredjean]

I'm currently working on getting middleman-s3_sync ready for Middleman 4.0.0. This will get me some knowledge on how to get to the sitemap.

I'm not sure yet whether I want to merge both gems, but updating the redirects to use the same syntax as the Middleman one does make sense.

[pomartel]

I just ran into this issue myself and was also wondering if there is a workaround or a fix to make this work on my local machine. Thanks!