url2png-plus 0.1.0 → 1.0.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 70cdf6fac663ba200ddda8f663a2ce5cadc300ed
4
- data.tar.gz: e93e7477081d0fb7e1de9894fd772e4a4d3529a1
3
+ metadata.gz: 22f2742c6fdb60121eddf50d334ab79fe4fb2d8f
4
+ data.tar.gz: 2dd852deb64530049f7fe75c99998a6ade735621
5
5
  SHA512:
6
- metadata.gz: 1a14a5f01b6080be1cb53c898d354387f1a21e3d3b4bb3294521727666b46d5c228a4fd00be540ca23ab8a5aaf1a41dcfaa3dac6a6a8825b664ede3f97c270ac
7
- data.tar.gz: 0dea22d55f5119baf11661860f7e481b34352ed249a1bc81c9c084d1b65f745887856adc95868937f91e30fa0e5906463355ef955d9dc2b8c37089ebf56adf95
6
+ metadata.gz: b7153e75d07a418efaaf918d24b5a07ec96d74a4f0453181c3517584059c87a9276de8625db62fccd80e90b6d7e26996eb4563ee4cd30b792bb5c5705a43516e
7
+ data.tar.gz: ad3cde2f07e82bbe16fb2f8de20c8bdebd29498c6a1bd3cbca61a9a60a8e96b7e1f6e633405755e7b1523d20beae19fb29f9851af1791abd0de3337f4517f81d
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- url2png-plus (0.1.0)
4
+ url2png-plus (1.0.0)
5
5
 
6
6
  GEM
7
7
  remote: https://rubygems.org/
data/README.md CHANGED
@@ -1,8 +1,18 @@
1
1
  # Url2png::Plus
2
2
 
3
- The `url2png` gem is madness. It tries to be compatible with a bunch of different versions of the url2png APIs, which a client doesn't need to worry about. Its also insecure out of the box by using the `http` protocol, and makes configuring the protocol to `https` very difficult.
3
+ Generates URL2PNG urls for Ruby projects and integrations with popular web frameworks, like Rails, Sinatra, etc.
4
4
 
5
- This gem only attempts to integrate with the most recent version of URL2PNG, which is v6 at the time of this writing, and otherwise stay out of the way.
5
+ ## Why `url2png-plus` and not `url2png`?
6
+
7
+ The `url2png` gem is way more complicated than it needs to be:
8
+
9
+ 1. It tries to be compatible with a bunch of different versions of the url2png HTTP APIs. The client shouldn't worry about this, at least I can't rationalize it.
10
+
11
+ 2. Its insecure out of the box by using the `http` protocol. Configuring the protocol is difficult because the base URL is a "magic string" inside the gem.
12
+
13
+ 3. The project has roughly 1,000 LOC. This project has 40 LOC. That doesn't mean much, but it is less stuff that can break.
14
+
15
+ This gem only attempts to integrate with the most recent version of URL2PNG, which is v6 at the time of this writing. If URL2PNG upgrades their APIs, this client will be updated to use the new API without any attempt to remain compatible with the old APIs. That burden will be put on using an older version of the gem.
6
16
 
7
17
  ## Installation
8
18
 
@@ -1,5 +1,5 @@
1
1
  module Url2png
2
2
  module Plus
3
- VERSION = "0.1.0"
3
+ VERSION = "1.0.0"
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: url2png-plus
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.0
4
+ version: 1.0.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Brad Gessler