uk-hs_code 0.1.1 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0afc982cf397f38b6c446ed385719496cae73dcc525c0c5c69d2ebf4a321377e
-  data.tar.gz: 60dc6714013f2b3aa242f1f9b3e95da10575a936170059fc6904cc4004872efc
+  metadata.gz: 3da63080141113f6a0de5d28178905c9534f4a6994e0ef27b644e9ffc91acc9e
+  data.tar.gz: 6c38e1ce4e3fe9a578b38346e3db3590d8ca86eafce9cc06d6533c1835a611a5
 SHA512:
-  metadata.gz: afc85b9843f375c506388963f642753d40f07ae3643ce7e40186d269774f11496a0ff32068898fa9afea9a43067bbc034c8dead28e145850aa44980de9619e31
-  data.tar.gz: 4ebdab36483084f291b75ca74f8268f71daa3aba5b6706d57069b96234a3c9c046627f565d66bf3931678155818e2618936233e0a9fb4aeb66c06227f6bcaffd
+  metadata.gz: bac45bb5c7d8f54c061da3c6278b75f2543e1d99865672860c14963ec2250ed49bb1ad27772c14405c4e7b8dab6c7a0fa2233ccd2f6f2297924d3379d6e65d85
+  data.tar.gz: 1135dcf855bf24a2a6df4d2c56e40ae54c783bbe97b681182e9db9e89d176035af73c3e2758ef8871614409f5ba511a6fd3edf096d6828564051272ee9c1c4f9

data/CONTRIBUTING.md

@@ -0,0 +1,19 @@
+# UK/Hs_code Contributing Guidelines
+
+Thank you for your interest in contributing to our open source project! We appreciate your effort and to ensure that your contributions align with the goals of this project and are integrated smoothly, we ask that you follow these guidelines.
+
+1. **Commit Small, Commit Regularly:** Regular and smaller commits are preferred over large, infrequent commits. This makes the changes easier to review and troubleshoot.
+
+2. **Use Imperative Commands:** Your commit titles should succinctly describe the changes you've made. Prefix your commit titles with imperative commands such as: fix, refactor, add, and remove. This is because you should be able to suffix a commit message to the phrase: "If applied, this code will...".
+
+A good practice is to structure your commit title like this: "[GitHub issue number] Add fields to hs record".
+
+Keep It Brief - You're not writing a monologue, so keep it brief. As a general rule, a commit message should not exceed 50 characters.
+
+3. **Use Draft PRs for Ongoing Work:** If your pull request is not ready for review, please mark it as a draft. This indicates to the team that the changes are still in progress.
+
+4. **Request Reviews Before Merging:** When your pull request is ready, request a review from your team members. Reviews ensure that your changes are validated by others.
+
+5. **Address Review Feedback:** If a reviewer asks for changes or provides feedback, please respond promptly and incorporate necessary changes.
+
+6. **Merge Cautiously:** Once your pull request is reviewed and approved, ensure that it's merging into the correct branch and that it's up-to-date with the latest changes in that branch before merging.

data/Gemfile.lock

@@ -1,9 +1,7 @@
 PATH
   remote: .
   specs:
-    uk-hs_code (0.1.0)
-      rake (~> 13.0)
-      rspec (~> 3.0)
+    uk-hs_code (0.1.3)
 
 GEM
   remote: https://rubygems.org/
@@ -22,7 +20,7 @@ GEM
     rainbow (3.1.1)
     rake (13.0.6)
     regexp_parser (2.7.0)
-    rexml (3.2.5)
+    rexml (3.4.1)
     rspec (3.12.0)
       rspec-core (~> 3.12.0)
       rspec-expectations (~> 3.12.0)
@@ -52,10 +50,13 @@ GEM
     unicode-display_width (2.4.2)
 
 PLATFORMS
+  arm64-darwin-23
   x86_64-linux
 
 DEPENDENCIES
   pry
+  rake (~> 13.0)
+  rspec (~> 3.0)
   rubocop
   uk-hs_code!
 

data/README.md

@@ -34,6 +34,8 @@ And:
 
 > refs = Uk::HsCode.search_hs_codes('carpet')
 
+> refs.inspect
+
  # => [#<Uk::HsCode::Record code="8451808000", title="carpet cleaning machines liquid injection">,
  #<Uk::HsCode::Record code="4008000000", title="carpet underlay, rubber">,
  #<Uk::HsCode::Record code="5402000000", title="carpet yarn, of man-made filaments">]
@@ -42,13 +44,13 @@ And:
 
 ## Development
 
-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.
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. To test with static code analyzer, run `rake rubocop`. 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 the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
 
 ## Contributing
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/uk-hs_code.
+Bug reports and pull requests are welcome on GitHub at https://github.com/enigmatt-pl/uk-hs_code.
 
 ## License
 

data/lib/uk/hs_code/version.rb

@@ -2,6 +2,6 @@
 
 module Uk
   module HsCode
-    VERSION = "0.1.1"
+    VERSION = "0.1.3"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: uk-hs_code
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.3
 platform: ruby
 authors:
 - Mateusz Michalski
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2023-04-24 00:00:00.000000000 Z
+date: 2025-05-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: pry
@@ -75,6 +75,7 @@ extra_rdoc_files: []
 files:
 - ".rspec"
 - ".rubocop.yml"
+- CONTRIBUTING.md
 - Gemfile
 - Gemfile.lock
 - LICENSE.txt
@@ -107,7 +108,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.7
+rubygems_version: 3.0.3.1
 signing_key: 
 specification_version: 4
 summary: Enables communication with Trade Tariff Public API V2.