impuri 0.12.4 → 0.12.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: aab104dee6358b2a2b622ff7dbc2ab1c475efcfe16292c697267291cc9f18864
-  data.tar.gz: 17bc26c213a267651ece96bf4d6c381695736a18e87f8dd1fbcf74f7d537e3e6
+  metadata.gz: 81f27b4bc9314c8199dc35463499f0e114bf12f8713a9c6097c1aa4dde873829
+  data.tar.gz: ac6b31604e0f7fdc879c8ff1da25bfe4bd72b32128647f16803e884e110cb0e2
 SHA512:
-  metadata.gz: b4a25caaf3a3094446d53d6f92806588ee30dbe231fca48990d2ecfbeca8946b23520b244c4201f5d22f72c27610db7c6e1502816e1b846fe32babb2e49a4a85
-  data.tar.gz: 5fbbfb0301df0e1e44f20e3cf76bea7a840789a4f2c7c6be7a9e2b02d46ef8ace0462db03eef59586b94f48ecc04db7fdc4485a4017c85624d08710404eb5572
+  metadata.gz: ba84c2be5bb8acbfca23f1f6c3ca4a09b063adb6957cfb193301d10c93e0e80a36197e2b05b844d00448c90ccc068c948d900f868d7295035b1cd0ec7a2bc456
+  data.tar.gz: f70dd55d179733932c5c134dcd6971cb5e7906f24a656a0c09a80a826a0af34d1ecd5282bdce042ffcf3569ac64821ce76e4479c698f778558e1eaae33a48c04

data/CHANGELOG

@@ -2,6 +2,14 @@
 
 ## 20260819
 
+0.12.5: + ROADMAP.md, for the two TODO items which are questions rather than work.
+
+1. + ROADMAP.md: encoding before breaking the string down, and whether the path separator should be settable. Neither is a job. The first names a cost in the present design and proposes a different one which might avoid it, so nothing can be done until the trade is judged worth making. The second ends "Any other uses?", which asks whether to do it at all rather than planning to.
+2. ~ TODO.txt: - those two, renumbered, leaving the funkier URIs and the parameter separator, which are work and can be done without anything first being decided. It stays a plain numbered list in a .txt: a list of jobs wants no headings and no markdown, and the two questions were the only things in it which did.
+3. + ROADMAP.md: under the path separator question, that 0.12.0's #to_ssh already serves the one use ever named for it, choosing the separator from what was parsed rather than from the caller. That is the argument for leaving it a question: the case which motivated it is met, and no second case has appeared.
+4. ~ impuri.gemspec: + 'ROADMAP.md' to spec.files, TODO.txt having shipped since 0.9.0. The two are the same kind of document and there is no reason for one to ship and not the other. switches keeps its ROADMAP.md out of its gem, which is the other consistent answer; this one follows what impuri already did.
+5. ~ ImpURI::VERSION: /0.12.4/0.12.5/
+
 0.12.4: + LICENSE, which the gemspec had claimed since 0.8.0 without one being present.
 
 1. + LICENSE: the MIT text, copyright 2011-2026, the repository's first commit being from 2011. spec.license = 'MIT' has been declared since the gemspec was written, so rubygems has shown a licence for this gem that the repository did not carry and the built gem did not contain. Anyone taking the gem at its word had nothing to read.

data/ROADMAP.md

@@ -0,0 +1,29 @@
+# ImpURI Roadmap
+
+Date: 20260819
+
+Jobs are in TODO.txt. What is here is undecided: questions to be answered rather
+than work to be done, which is why they are prose and the jobs are a list.
+
+## Open questions
+
+### Encoding before breaking the string down
+
+Consider encoding everything in the URI before breaking the string into parts, so
+as to avoid the kind of complexity introduced in `ImpURI.has_userinfo?`.
+
+This is a change of approach rather than a job. It names a cost in the present
+design and proposes a different design which might avoid it, and nothing can be
+done about it until somebody decides whether the trade is worth making.
+
+### Whether the path separator should be settable
+
+Be able to change the colon path separator for an ImpURI instance, say if
+converting from ssh-form to the URI-form of an ssh resource. Any other uses?
+
+The question is that last clause, and it was there from the start. One use was
+named, and 0.12.0 met it from the other side: `#to_ssh` renders the ssh/scp form,
+choosing the separator by what the resource was parsed from rather than letting the
+caller set it. So the one motivating case is served without the separator being
+settable at all. Whether anything else wants it remains open, and until something
+does, this stays a question rather than becoming work.

data/TODO.txt

@@ -1,6 +1,4 @@
 1. Handle port numbers.  Done as of 0.1.0.
 2. Create strict and non-strict parsing modes, which will either accept or reject non-URI ssh/scp formatted strings if they are supplied.  Done as of 0.2.0.
 3. Doesn't handle some of the funkier URI's like: ssh:// with keys in the userinfo section, mailto: (no ://, but merely :), and ldap://.
-4. Consider encoding everything in the URI before breaking down the strings, so as to avoid the kind of complexity introduced in ImpURI.has_userinfo?().
-5. Be able to change the semicolon parameter separator for an ImpURI instance.
-6. Be able to change the colon path separator for an ImpURI instance, say if converting from ssh-form to the URI-form of an ssh resource for instance.  Any other uses?
+4. Be able to change the semicolon parameter separator for an ImpURI instance.

data/impuri.gemspec

@@ -39,6 +39,7 @@ Gem::Specification.new do |spec|
     'LICENSE',
     'Rakefile',
     'README.md',
+    'ROADMAP.md',
     'TODO.txt',
   ].flatten
 

data/lib/ImpURI/VERSION.rb

@@ -2,5 +2,5 @@
 # ImpURI::VERSION
 
 class ImpURI
-  VERSION = '0.12.4'
+  VERSION = '0.12.5'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: impuri
 version: !ruby/object:Gem::Version
-  version: 0.12.4
+  version: 0.12.5
 platform: ruby
 authors:
 - thoran
@@ -49,6 +49,7 @@ files:
 - Gemfile
 - LICENSE
 - README.md
+- ROADMAP.md
 - Rakefile
 - TODO.txt
 - impuri.gemspec