acts_as_having_string_id 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +0 -1
- data/lib/acts_as_having_string_id/version.rb +1 -1
- data/lib/acts_as_having_string_id.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: f43c892374317d146c876e67c401c593b8952d67
|
|
4
|
+
data.tar.gz: f1cc6403a64f7acbd3d277258dec4c586a3ef5d0
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 08203d900592ad6e794160dd783cc045d6eef36f01bfcf661a74907c6377543f28b971ce7653f8692e4e473bc063fc8311593439984bde026fb2133dce70d7a0
|
|
7
|
+
data.tar.gz: ec12e978b89176162d108a785117de213da31ce975cbe3635fdc51e7500cb62f15ea37bd8722d07cc381e70206eee3bc5f8898bc86468381b8223e461695887a
|
data/README.md
CHANGED
|
@@ -81,7 +81,6 @@ Then, for exposing your string ID, use the `id_string` method. For example, if y
|
|
|
81
81
|
And that's just about it!
|
|
82
82
|
|
|
83
83
|
## TODO
|
|
84
|
-
* Publish on rubygems
|
|
85
84
|
* Since the `MyModel.find("7EajpSfdWIf")` functionality depends on the argument now being a string, `MyModel.find("5")` will no longer mean `MyModel.find(5)`, but rather `MyModel.find(4387534)` or something. Is that a problem?
|
|
86
85
|
* It's a potential security problem that we don't force strings from controllers (integer id coming from JSON postdata will make it find by original id)
|
|
87
86
|
* Although TEA handles (and outputs) 64-bit ids, we currently limit the input to 32-bit
|