Sha256: 2374953634e67f36ebecaf5a4a1c2954a55f44965821d2ec2990443e7cffd682
Contents?: true
Size: 1.89 KB
Versions: 0
Compression: gzip
Compressed size: 874 Bytes
Stored size: 874 Bytes
Contents
--- !ruby/object:Gem::Specification name: uid_attribute version: !ruby/object:Gem::Version version: 0.2.7 platform: ruby authors: - Paul Belt autorequire: bindir: bin cert_chain: [] date: 2010-05-06 00:00:00 -04:00 default_executable: dependencies: - !ruby/object:Gem::Dependency name: uuidtools type: :runtime version_requirement: version_requirements: !ruby/object:Gem::Requirement requirements: - - ">=" - !ruby/object:Gem::Version version: 2.1.1 version: description: |- Some projects are confined by regulations (or requirements) that demand data can not be used to identify individuals. In such cases data must be scrubbed i.e. identifiable object names must be removed before unauthorized users can see said data. For example, when a developer needs to recreate a bug on their own system that was reported by a customer using customer-specific data. One method to do this is to use globally unique identifiers within the system to identify any given object. email: Paul Belt executables: [] extensions: [] extra_rdoc_files: - README.rdoc files: - .gitignore - LICENSE - README.rdoc - Rakefile - VERSION.yml - lib/uid_attribute.rb - test/uid_attribute_test.rb - uid_attribute.gemspec has_rdoc: true homepage: http://github.com/belt/uid_attribute licenses: [] post_install_message: rdoc_options: - --charset=UTF-8 require_paths: - lib required_ruby_version: !ruby/object:Gem::Requirement requirements: - - ">=" - !ruby/object:Gem::Version version: "0" version: required_rubygems_version: !ruby/object:Gem::Requirement requirements: - - ">=" - !ruby/object:Gem::Version version: "0" version: requirements: [] rubyforge_project: uid_attribute rubygems_version: 1.3.5 signing_key: specification_version: 3 summary: machina to automatically generate UUIDs upon object instantiation. test_files: - test/uid_attribute_test.rb