Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please declare your dependencies in your gemspec #215

Open
zenspider opened this issue May 18, 2016 · 5 comments
Open

Please declare your dependencies in your gemspec #215

zenspider opened this issue May 18, 2016 · 5 comments

Comments

@zenspider
Copy link

You're using sexp_processor and ruby_parser but not declaring dependencies on them. Please do so.

@daniel-rikowski
Copy link

daniel-rikowski commented May 18, 2016

Did you get them to work? Every time I tried to use the authorization rules browser it failed, because of the parsed s-exps, which cannot be processed by decl_auth. (Last time it worked was around 2009, on Ruby 1.9.3. with 1.8 syntax only)

That is probably because the code is tailored to Ruby 1.8 syntax and possibly to an old version of ruby_parser, too

If that is still the case I'd prefer to remove or extract the non-working features, i.e. the app directory, instead of adding the dependencies, considering the "gimmicky" nature of the rules and usages browsers.

@zenspider
Copy link
Author

Welp... this project seems dead. :(

@zeiv
Copy link
Contributor

zeiv commented Jun 15, 2017

@zenspider see Authoreyes 😉

Listed as WIP, last commit 3 months ago, but I'm still using it in several production apps without a hitch. Should be mostly a drop-in replacement

@zenspider
Copy link
Author

@zeiv I'm not a user. I'm a "victim" :)

This project uses one of my gems irresponsibly and I get bugs filed on it as a result. Hopefully others will see your comment and switch over tho.

@zeiv
Copy link
Contributor

zeiv commented Jun 15, 2017

@zenspider Ah, I see. Unfortunate. Yeah, there are a couple pull requests I think to axe the portion that uses sexp_processor and ruby_parser. I don't know if they will ever be merged...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants