k_type 0.0.3 → 0.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d66f0d61fe53fe8c595df611b7581323c24ed589ad520cfd3cbbe77aa91c4d39
-  data.tar.gz: 8ca31c3c74b48018bb824d20599a05a93b265c74e6e21edee483e51d3ac8fb9e
+  metadata.gz: d1d217b81cbbd73eb5cb8e0916a062660344861f556a044a91e4dc4b2b778c38
+  data.tar.gz: 3bdb9e6ee51865d2c281b14ea7e7e7ae9c6a6b4acad940e943a902b1a7eb0d1e
 SHA512:
-  metadata.gz: de645c9b8d6298e938b0e5c4d5534f02fd5a9bcc62fa4da2f360769aa8436ba8ebd9c47a0195ff72908de96f68b309e1bdc6e9704fe41f3c4c1a0c1567663d01
-  data.tar.gz: e7b85f1b1c32117e0ef0d23973663b417792aac8f11e13916fe9b998bef8387b51c86b1202335c9697f9d3bbeb29034b2e47ba95622aa3a8b922688f9951e231
+  metadata.gz: 625144659197463b7c541d261888efd8de724adf4989381976c6281a5ab363c3317769009bf55d316877f3d34b017edaf4b0f324e2bfaf79020030fc5cfed546
+  data.tar.gz: c494e56f03d0a0e536db931c980b0c8e4a44ebf6964220bc35da64643db687697226c16aa42ff7e29f9dacda5de6d1d849f0bcc5e53e90b2ac791acbe6d2d81e

data/lib/k_type.rb

@@ -10,3 +10,10 @@ module KType
 
   # Your code goes here...
 end
+
+if ENV['KLUE_DEBUG']&.to_s&.downcase == 'true'
+  namespace = 'KType::Version'
+  file_path = $LOADED_FEATURES.find { |f| f.include?('k_type/version') }
+  version   = KType::VERSION.ljust(9)
+  puts "#{namespace.ljust(35)} : #{version.ljust(9)} : #{file_path}"
+end

data/lib/k_type/layered_folders.rb

@@ -1,17 +1,6 @@
 # frozen_string_literal: true
 
 module KType
-  #
-  # Named folders makes sense for generated/output folders because you may want
-  # more than one type of location to generate output.
-  #
-  # Don't confuse multiple named output folders with sub-paths, when you want to
-  # build up a file name in a child folder, you can do that as part of building
-  # the filename.
-  #
-  # The idea behind named folders is for when you have two or more totally different
-  # outputs that (may live in the a similar location) or live in different locations.
-
   # Layered folders allow files to be found in any of the searchable folders
   #
   # They derive from and thus work just like named folders in that they allow folders
@@ -71,8 +60,13 @@ module KType
     def add(folder_key, *folder_parts)
       folder = super(folder_key, *folder_parts)
 
-      ordered_keys.prepend(folder_key)
-      ordered_folders.prepend(folder)
+      index = ordered_keys.find_index(folder_key)
+      if index
+        ordered_folders[index] = folder
+      else
+        ordered_keys.prepend(folder_key)
+        ordered_folders.prepend(folder)
+      end
 
       folder
     end

data/lib/k_type/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module KType
-  VERSION = '0.0.3'
+  VERSION = '0.0.4'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: k_type
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - David Cruwys
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-04-05 00:00:00.000000000 Z
+date: 2021-05-02 00:00:00.000000000 Z
 dependencies: []
 description: "    K Type provides base types for KlueLess code generation\n"
 email: