Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / alexis/fact_checker issues and pull requests

#15 - License missing from gemspec

Issue - State: closed - Opened by bf4 almost 11 years ago - 2 comments

#14 - Usage of valid? as a public API feels unsafe

Issue - State: closed - Opened by ipoval almost 11 years ago

#13 - run specs in random order and fix failing coupling of the spec

Pull Request - State: closed - Opened by ipoval almost 12 years ago

#12 - refactor the lambda syntax behaviour for fact defenitions

Pull Request - State: closed - Opened by ipoval about 12 years ago

#11 - Internal adjustments

Issue - State: open - Opened by alexis about 12 years ago - 2 comments

#10 - added support for string fact names

Pull Request - State: closed - Opened by ipoval about 12 years ago - 1 comment

#9 - updated rspec 2.10.0

Pull Request - State: closed - Opened by ipoval about 12 years ago

#8 - added 2 test cases for private fact implementation

Pull Request - State: closed - Opened by ipoval about 12 years ago - 2 comments

#7 - PRIVATE FACTS: start

Pull Request - State: closed - Opened by ipoval about 12 years ago

#5 - update README to have all of the public api of the gem mentioned

Issue - State: closed - Opened by ipoval about 12 years ago - 1 comment

#4 - support for private facts

Issue - State: closed - Opened by ipoval about 12 years ago

#3 - if :fact_name .ends_with('?') when we dont need to add '?' to (:fact_name)? predicate

Issue - State: closed - Opened by ipoval almost 13 years ago - 8 comments

#2 - maybe to give a warning if (:fact)? method happens to override existing method in the class

Issue - State: closed - Opened by ipoval almost 13 years ago - 3 comments
Labels: compatibility

#1 - indifferent access for facts using strings and symbols as arguments

Issue - State: closed - Opened by ipoval almost 13 years ago - 3 comments
Labels: feature request