zernio-sdk 0.0.794 → 0.0.795
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/docs/ValidateApi.md +1 -1
- data/lib/zernio-sdk/api/validate_api.rb +2 -2
- data/lib/zernio-sdk/version.rb +1 -1
- data/openapi.yaml +4 -0
- data/spec/api/validate_api_spec.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 3f64bf96248f653717c5eada91f33c9ecb869645ea68e874073ac8c491d60d1d
|
|
4
|
+
data.tar.gz: 767f67db5f09a94bdeeabfd406ff9022125be75ff3e72d42f2a7841f85c0a7a3
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 84b9078c87d3e073be46bd2996e8c3a6664ab396059946849dcaa756dc5fc65eedf9a352736aa8f2a6eeb9155e19d795ddb2b1d95990339f0a3d241563dd7bb4
|
|
7
|
+
data.tar.gz: fe6a13ebdf18f1c5577992b142929a6d8f62dafd660d253c0e3efb56c6e627a6bd9ee6e6bf95c653677d0d1e09e7eed9fd0a7f093c0d09a5630d2ef7649750f5
|
data/docs/ValidateApi.md
CHANGED
|
@@ -154,7 +154,7 @@ end
|
|
|
154
154
|
|
|
155
155
|
Validate character count
|
|
156
156
|
|
|
157
|
-
Check weighted character count per platform and whether the text is within each platform's limit. Twitter/X uses weighted counting (URLs = 23 chars via t.co, emojis = 2 chars). All other platforms use plain character length. Returns counts and limits for all 15 supported platform variants.
|
|
157
|
+
Check weighted character count per platform and whether the text is within each platform's limit. Twitter/X uses weighted counting (URLs = 23 chars via t.co, emojis = 2 chars). All other platforms use plain character length. Returns counts and limits for all 15 supported platform variants. X (Twitter) returns two rows and this endpoint cannot tell you which one applies to you: it takes only `text`, so it never resolves an account. `twitter` (280) is the free tier limit. `twitterPremium` (25000) applies only when the target X account has a paid X subscription, and publishing enforces 280 instead for any post carrying a poll (this endpoint has no poll input, so the `twitterPremium` row always shows 25000). A free account trusting the `twitterPremium` row can pass validation here and still fail at publish time, where the account's real limit is enforced. To validate against the per-account limit, use `POST /v1/tools/validate/post` instead: it accepts an `accountId` per platform entry, resolves X Premium status, and checks the text against the limit publishing enforces, including the poll cap. A missing, foreign, or invalid `accountId` falls back to the conservative 280.
|
|
158
158
|
|
|
159
159
|
### Examples
|
|
160
160
|
|
|
@@ -156,7 +156,7 @@ module Zernio
|
|
|
156
156
|
end
|
|
157
157
|
|
|
158
158
|
# Validate character count
|
|
159
|
-
# Check weighted character count per platform and whether the text is within each platform's limit. Twitter/X uses weighted counting (URLs = 23 chars via t.co, emojis = 2 chars). All other platforms use plain character length. Returns counts and limits for all 15 supported platform variants.
|
|
159
|
+
# Check weighted character count per platform and whether the text is within each platform's limit. Twitter/X uses weighted counting (URLs = 23 chars via t.co, emojis = 2 chars). All other platforms use plain character length. Returns counts and limits for all 15 supported platform variants. X (Twitter) returns two rows and this endpoint cannot tell you which one applies to you: it takes only `text`, so it never resolves an account. `twitter` (280) is the free tier limit. `twitterPremium` (25000) applies only when the target X account has a paid X subscription, and publishing enforces 280 instead for any post carrying a poll (this endpoint has no poll input, so the `twitterPremium` row always shows 25000). A free account trusting the `twitterPremium` row can pass validation here and still fail at publish time, where the account's real limit is enforced. To validate against the per-account limit, use `POST /v1/tools/validate/post` instead: it accepts an `accountId` per platform entry, resolves X Premium status, and checks the text against the limit publishing enforces, including the poll cap. A missing, foreign, or invalid `accountId` falls back to the conservative 280.
|
|
160
160
|
# @param validate_post_length_request [ValidatePostLengthRequest]
|
|
161
161
|
# @param [Hash] opts the optional parameters
|
|
162
162
|
# @return [ValidatePostLength200Response]
|
|
@@ -166,7 +166,7 @@ module Zernio
|
|
|
166
166
|
end
|
|
167
167
|
|
|
168
168
|
# Validate character count
|
|
169
|
-
# Check weighted character count per platform and whether the text is within each platform's limit. Twitter/X uses weighted counting (URLs = 23 chars via t.co, emojis = 2 chars). All other platforms use plain character length. Returns counts and limits for all 15 supported platform variants.
|
|
169
|
+
# Check weighted character count per platform and whether the text is within each platform's limit. Twitter/X uses weighted counting (URLs = 23 chars via t.co, emojis = 2 chars). All other platforms use plain character length. Returns counts and limits for all 15 supported platform variants. X (Twitter) returns two rows and this endpoint cannot tell you which one applies to you: it takes only `text`, so it never resolves an account. `twitter` (280) is the free tier limit. `twitterPremium` (25000) applies only when the target X account has a paid X subscription, and publishing enforces 280 instead for any post carrying a poll (this endpoint has no poll input, so the `twitterPremium` row always shows 25000). A free account trusting the `twitterPremium` row can pass validation here and still fail at publish time, where the account's real limit is enforced. To validate against the per-account limit, use `POST /v1/tools/validate/post` instead: it accepts an `accountId` per platform entry, resolves X Premium status, and checks the text against the limit publishing enforces, including the poll cap. A missing, foreign, or invalid `accountId` falls back to the conservative 280.
|
|
170
170
|
# @param validate_post_length_request [ValidatePostLengthRequest]
|
|
171
171
|
# @param [Hash] opts the optional parameters
|
|
172
172
|
# @return [Array<(ValidatePostLength200Response, Integer, Hash)>] ValidatePostLength200Response data, response status code and response headers
|
data/lib/zernio-sdk/version.rb
CHANGED
data/openapi.yaml
CHANGED
|
@@ -10322,6 +10322,10 @@ paths:
|
|
|
10322
10322
|
Twitter/X uses weighted counting (URLs = 23 chars via t.co, emojis = 2 chars). All other platforms use plain character length.
|
|
10323
10323
|
|
|
10324
10324
|
Returns counts and limits for all 15 supported platform variants.
|
|
10325
|
+
|
|
10326
|
+
X (Twitter) returns two rows and this endpoint cannot tell you which one applies to you: it takes only `text`, so it never resolves an account. `twitter` (280) is the free tier limit. `twitterPremium` (25000) applies only when the target X account has a paid X subscription, and publishing enforces 280 instead for any post carrying a poll (this endpoint has no poll input, so the `twitterPremium` row always shows 25000). A free account trusting the `twitterPremium` row can pass validation here and still fail at publish time, where the account's real limit is enforced.
|
|
10327
|
+
|
|
10328
|
+
To validate against the per-account limit, use `POST /v1/tools/validate/post` instead: it accepts an `accountId` per platform entry, resolves X Premium status, and checks the text against the limit publishing enforces, including the poll cap. A missing, foreign, or invalid `accountId` falls back to the conservative 280.
|
|
10325
10329
|
security:
|
|
10326
10330
|
- bearerAuth: []
|
|
10327
10331
|
requestBody:
|
|
@@ -58,7 +58,7 @@ describe 'ValidateApi' do
|
|
|
58
58
|
|
|
59
59
|
# unit tests for validate_post_length
|
|
60
60
|
# Validate character count
|
|
61
|
-
# Check weighted character count per platform and whether the text is within each platform's limit. Twitter/X uses weighted counting (URLs = 23 chars via t.co, emojis = 2 chars). All other platforms use plain character length. Returns counts and limits for all 15 supported platform variants.
|
|
61
|
+
# Check weighted character count per platform and whether the text is within each platform's limit. Twitter/X uses weighted counting (URLs = 23 chars via t.co, emojis = 2 chars). All other platforms use plain character length. Returns counts and limits for all 15 supported platform variants. X (Twitter) returns two rows and this endpoint cannot tell you which one applies to you: it takes only `text`, so it never resolves an account. `twitter` (280) is the free tier limit. `twitterPremium` (25000) applies only when the target X account has a paid X subscription, and publishing enforces 280 instead for any post carrying a poll (this endpoint has no poll input, so the `twitterPremium` row always shows 25000). A free account trusting the `twitterPremium` row can pass validation here and still fail at publish time, where the account's real limit is enforced. To validate against the per-account limit, use `POST /v1/tools/validate/post` instead: it accepts an `accountId` per platform entry, resolves X Premium status, and checks the text against the limit publishing enforces, including the poll cap. A missing, foreign, or invalid `accountId` falls back to the conservative 280.
|
|
62
62
|
# @param validate_post_length_request
|
|
63
63
|
# @param [Hash] opts the optional parameters
|
|
64
64
|
# @return [ValidatePostLength200Response]
|