Releases: Cretezy/dSock
Releases · Cretezy/dSock
v0.4.1
v0.4.0
- Add direct API to worker messaging
- Add
redis_max_retries
option - Add
redis_tls
option - Added request ID to error responses
- Added more logging (including on error responses), and change multiple debug logging to info
- Parallelized parsing of messages received from Redis (should increase throughput)
- Deprecating
address
option: Useport
instead - Fix bug where creating a claim with ID left ID blank
v0.3.3
v0.3.2
v0.3.1
- Improve query binding
- Add locking for concurrent state (thanks a lot @abdullah-aghayan!)
- Change logger to Zap (include request logger)
- Added logging to all requests
- Change unsubscribe type from 2 to 1 (internal type)
- Fix debug mode never being active
- Add log request (
log_requests
) option
v0.3.0
- Breaking
- Change
MISSING_CONNECTION_OR_USER
toMISSING_TARGET
(and changed message)
- Change
- Added channels:
- Added
channel
target option to sending, getting info, disconnect - Added
channels
JWT claim (array of strings) - Added
channels
to claim creation (comma-delimited string) - Added
channels
to info response for connections - Added channel subscribing and unsubscribing
- Added
default_channels
config options (comma-delimited string)
- Added
- Replace
scripts
directory with Task
v0.2.0
-
Breaking
- Changed response format for creating claims
-
All claim data is now inside the
claim
key, and more data is present. Example:Before:
{ "success": true, "id": "XXX", "expiration": 1588473164 }
After:
{ "success": true, "claim": { "id": "XXX", "expiration": 1588473164, "user": "a", "session": "b" } }
-
- Changed response format for creating claims
-
Added tests (E2E, unit) and CI
-
Added past expiration validation (doesn't allow expiration dates in the past) during claim creation
v0.1.2
v0.1.1
- Fixed bug with missing
errorCode
when duration is negative during claim creation - Fix bug with incorrect
errorCode
when error is trigger during checking if a claim exists - Added documentation on errors
Version code during application startup is wrongly reported as v0.1.0