-
Notifications
You must be signed in to change notification settings - Fork 3
Start checking gems with ataru. #56
Comments
PadawansMoon - works |
Great 👍 Can I help with the anima chaos? 😄 |
@moonglum anima worked today for me, meaning I could use it with ataru, and now I'm getting again crazy 'You may have encountered a bug in the Ruby interpreter or extension libraries.' |
@madziaf Ok, that's sad 😒 Let's look at this on Monday, ok? |
More ideas for gems:
|
gem "ataru", :git => "git://github.com/CodePadawans/ataru.git", :branch => "master" |
Even more:
??
|
More ideas for gems:
|
Talking about "scrivener" I know soveran likes building minimal libraries with no dependencies. Very What can be done?. Remembering telling to him in Montevideo that his projects remained me of We do have a *.gemspec file. Maybe we can cover the case when the project doesn't have a gemfile but Can the setup command extract the files defined in the |
and then? i don't get it. when you have Gemfile, then you add ataru there, so the project knows about ataru. do you want to require .rb files of the project, add ataru additionally and give all that to bundle, or how? |
Sorry, my text was confusing. I am was not giving any solution, just pointing out The user can do the following to check the project with ataru:
|
Question: At this point the following gems can be checked, if the user manually installs ataru and sets it up with the correct requires?
|
hej I can install ataru, but have problems with requiring files. Have tried different ways of writing the path, but wasn't sucessful. And there is 2 Ruby versions
|
Well seen! On the ruby version inside other ruby version: I've checked on my installation and the same happens: Can't explain exactly now, will ask Florian about it tomorrow. For the path problem, can you paste the failing setup requires? |
The cases without a Gemfile: coercible: procto: rep: UserRep.shared(user: User.first).to_hash # => { name: "Nathan Herald:, ... I think that could even be a case that is quite common. It could be handled, but it is a biiiig task. We could add it to the #52. ribimaybe: Just do |x|
x * x
end.apply(Nothing) # => Nothing This is one of the cases where we run into limitations with using RegExps instead of a Parser. This has to be handled in the future – we can't do anything about it now. equalizer: |
👍 Neat project. |
In order to excercice the functionality, let's try it out with some gems. We will surely find many exceptional cases, that will give us more information on how the people write their documentation code. I'll propose a short list of problematic tested gems as output of this issue, with comments on how ataru performed on them.
The text was updated successfully, but these errors were encountered: