
Security News
CISA’s 2025 SBOM Guidance Adds Hashes, Licenses, Tool Metadata, and Context
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
Simple and agile Ruby data validation tool inspired by refinement types and functional approach
# Write your "types" as simple as...
class Email < ::BC::Refined
REGEX = /\A[\w+\-.]+@[a-z\d\-]+(\.[a-z\d\-]+)*\.[a-z]+\z/i
def match
return if (context[:email] = value.to_s) =~ REGEX
failure(:invalid_email)
end
end
class Phone < ::BC::Refined
REGEX = /\A(\+7|8)(9|8)\d{9}\z/i
def match
return if (context[:phone] = value.to_s) =~ REGEX
failure(:invalid_phone)
end
end
# ... compose them...
Login = Email.or_a(Phone)
# ... and match!
case match = Login.match("not-a-login")
when Phone, Email
match # use as you wish, you exactly know what kind of login you received
when BC::ContractFailure # translate error message
match.messages # => [:no_matches, :invalid_phone, :invalid_email]
else raise # to make sure you covered all scenarios (Functional Way)
end
# And then in
# config/initializers/contracts.rb
module Contracts
class YabedaInstrument
def call(session)
valid_marker = session.valid? ? "V" : "I"
result = "[#{valid_marker}] #{session.result_type_name}"
Yabeda.api_contract_matches.increment(result: result)
end
end
end
BloodContracts::Instrumentation.configure do |cfg|
# Attach to every BC::Refined ancestor with Login in the name
cfg.instrument "Login", Contracts::YabedaInstrument.new
end
Add this line to your application's Gemfile:
gem 'blood_contracts'
And then execute:
$ bundle
Or install it yourself as:
$ gem install blood_contracts
This gem is just facade for the whole data validation and monitoring toolset.
For deeper understanding see BloodContracts::Core, BloodContracts::Ext and BloodContracts::Instrumentation
After checking out the repo, run bin/setup
to install dependencies. Then, run rake spec
to run the tests. You can also run bin/console
for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install
. To release a new version, update the version number in version.rb
, and then run bundle exec rake release
, which will create a git tag for the version, push git commits and tags, and push the .gem
file to rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/sclinede/blood_contracts. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
The gem is available as open source under the terms of the MIT License.
Everyone interacting in the BloodContracts project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.
FAQs
Unknown package
We found that blood_contracts demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
Security News
A clarification on our recent research investigating 60 malicious Ruby gems.
Security News
ESLint now supports parallel linting with a new --concurrency flag, delivering major speed gains and closing a 10-year-old feature request.