You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With sinatra 2.0.3, we now have active_support as a dependency, as introduced with #1442. I didn't dive into the code base yet on why this is necessary, so I wanted to check here first:
Was this change intentional?
Is there a good alternative to avoid adding a new dependency to the graph? On the first look it seems like we're only using active_support/core_ext/object/try.rb and backports/rails/string
Context: we're using sinatra for the new fastlane.ci project.
The text was updated successfully, but these errors were encountered:
Hey sinatra contributors,
With sinatra 2.0.3, we now have
active_support
as a dependency, as introduced with #1442. I didn't dive into the code base yet on why this is necessary, so I wanted to check here first:active_support/core_ext/object/try.rb
andbackports/rails/string
Context: we're using sinatra for the new fastlane.ci project.
The text was updated successfully, but these errors were encountered: