dependency issue about jquery-ui-sass-rails HOT 15 OPEN

Hey @eprothro,
yes this = dependency is intentional to make sure that the 2 gems work correctly together. You should only put jquery-ui-sass-rails in your Gemfile, since that will already pull in jquery-ui-rails in the correct version.

I tried to adjust the README accordingly: 4ec306b Please let me know (or make a PR) if I can make it even clearer.

from jquery-ui-sass-rails.

Thanks very much for the reply and the timely doc update, very helpful and
clear!

Only out of curiosity, would a ~> or an explicit >= and < make more
sense to allow for a little more flexibility to allow users access to
bugfixes or minor updates in the jquery-ui-rails dependency without
having to wait for you to update to a new version?

Thanks again!

-Evan Prothro
Sent from my mobile

On Aug 14, 2013, at 2:23 AM, Jakob Hilden [email protected] wrote:

Hey @eprothro https://github.com/eprothro,
yes this = dependency is intentional to make sure that the 2 gems work
correctly together. You should only put jquery-ui-sass-rails in your
Gemfile, since that will already pull in jquery-ui-rails in the correct
version.

I tried to adjust the README accordingly:
4ec306bhttps://github.com/jhilden/jquery-ui-sass-rails/commit/4ec306be7c7762f3a20ca3e3d2743bda29c888c8Please
let me know (or make a PR) if I can make it even clearer.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/4#issuecomment-22618979
.

from jquery-ui-sass-rails.

I'm having a dependency conflict between this and Activeadmin, which requires jquery-ui-rails 4.1.0. I'd second the request to get a more flexible dependency if possible.

from jquery-ui-sass-rails.

+1
i'm also having a dependency conflict with rails_admin.

from jquery-ui-sass-rails.

@jhilden if you reconsider, I'm happy to submit a PR.

Personally, if you're very concerned about version alignment, I think a post-bundle or on-init warning might be more appropriate than the explicit version constraint.

from jquery-ui-sass-rails.

does that already help? 13eabf0

can you describe the exact depency conflict (with all version numbers)

I would be very open to a PR, how would you solve the issue?

from jquery-ui-sass-rails.

That is better and would have fixed my case, yes.

I assumed that unless we explicitly know a future version breaks something, that >= is the best practice. However, @jhilden you know more about what the potential risks are here than I do, so I defer.

@mattsjohnston can you provide more specifics about your conflict?

from jquery-ui-sass-rails.

I am getting this error since jquery-ui-rails is on 4.1 and this package is on 4.0.2. Is there an easy fix?

from jquery-ui-sass-rails.

This gem will need to be updated. I can work on it as soon as I have some time, but any help/PR in the meantime would be highly appreciated.

from jquery-ui-sass-rails.

Have there been any updates on this? I am having trouble installing ActiveAdmin

from jquery-ui-sass-rails.

Am also still seeing this issue with rails_admin (>= 0)

from jquery-ui-sass-rails.

I'm sorry, but I'm not actively maintaining this gem anymore. But PRs and potential new maintainers are very welcome.

from jquery-ui-sass-rails.

@stephenjlovell I can't help you with rails admin but I played with the gem spec on both this gem and activeadmin and got them to play nice. If you are interested check out the forks here

from jquery-ui-sass-rails.

As I said, PRs are always welcome.

from jquery-ui-sass-rails.

@cantonyselim thanks for the link, will check it out. I'm building a survey automation app and experimenting with a few options for the back end.

from jquery-ui-sass-rails.