2c5ff66c9e
Merge branch 'master' into bugfix/stripper
2023-06-29 00:07:27 +02:00
fd80dde802
Dub
...
- Updated homepage
2023-06-29 00:05:34 +02:00
2619577cad
Merge branch 'master' into bugfix/stripper
2023-06-28 23:53:34 +02:00
f20c078fc3
Client
...
- `user(string, string, string, string)` now checks for illegal characters
2023-06-28 23:53:08 +02:00
d2b4ccfeda
Client
...
- Pass in custom error messages for clarity
2023-06-28 23:42:39 +02:00
4fbe10adca
Merge branch 'master' into bugfix/stripper
2023-06-28 08:33:41 +02:00
3aa14492e2
Client
...
- Removed now-completed TODOs
2023-06-28 08:32:44 +02:00
84785529df
Client
...
- `leaveChannel(string)` now ensures that only valid characters are present in the provided channel's name, else throws a `BirchwoodException`
2023-06-28 08:31:41 +02:00
7848e892b7
Merge pull request #34 from deavmi/bugfix/improve_snoosy
...
Bugfix/improve snoosy
2023-06-26 19:05:53 +02:00
466337ec75
Merge branch 'master' into bugfix/improve_snoosy
2023-06-25 17:37:08 +02:00
9b81573eb7
Client
...
- Added or improved `Throws` documentation on many methods
2023-06-25 17:36:46 +02:00
b79a3ad8ee
Client
...
- Now catches `SnoozeError` if a the libsnooze `Event`'s failed to have their `ensure()` call succeed
ErrorType
- Updated description for enum member `INTERNAL_FAILURE`
Sender
- Removed now-completed TODO
Receiver
- Removed now-completed TODO
2023-06-25 17:30:53 +02:00
fe9bf31ad5
Client
...
- Removed now-completed comments and commented-out-code
2023-06-25 17:13:45 +02:00
ed39b950c3
Merge branch 'master' into bugfix/improve_snoosy
2023-06-25 17:13:00 +02:00
42f63b9e0e
Client
...
- We now catch `EventyException` when calling `initEvents()` from within `connect()` and throw a `BirchwoodException`
2023-06-25 17:12:24 +02:00
9d0a2bc3ce
Client
...
- Documented that `initEvents()` may throw an `EventyException`
ErrorType
- Added new member `INTERNAL_FAILURE` which could occur from errors with `Eventy` when setting up the signal handlers and event types
2023-06-25 17:11:59 +02:00
46e8518b6b
Merge branch 'master' into bugfix/improve_snoosy
2023-06-25 17:06:15 +02:00
5488e7902c
Receiver
...
- Removed irrelevant TODO
Sender
- Removed irrelevant TODO
2023-06-25 17:05:36 +02:00
ab09852fa2
README
...
- Upgraded required libsnooze version
- Typo fixes
2023-06-25 17:03:23 +02:00
125bb613a7
Receiver
...
- Removed `hasEnsured` (commented-out already)
- Call `ensure(this)` in constructor
- Removed TODOs relating to ensurance
Sender
- Removed `hasEnsured` (commented-out already)
- Call `ensure(this)` in constructor
- Removed TODOs relating to ensurance
2023-06-25 17:01:52 +02:00
2481ef88db
Dub
...
- Upgraded `libsnooze` to version `1.2.0-beta`
2023-06-25 17:00:32 +02:00
4655584fa5
Client
...
- Let unit test for client call `quit()` eventually
2023-06-21 14:39:23 +02:00
229a137e34
Messages
...
- Added unit test for `hasIllegalCharacters(string)`
2023-06-21 14:39:05 +02:00
80a6baf0f9
Client
...
- `sendMessage(Message)` now uses the new `Message(this).encode(ChecksMode)`
2023-06-21 14:23:12 +02:00
67520c2574
Messages
...
- Implemented `hasIllegalCharacters(string)` which checks whether the provided input string contains any invalid characters
- Updated `encode()` to `encode(ChecksMode)`
2023-06-21 14:22:48 +02:00
06efa23c85
Messages
...
- Implemented `stripIllegalCharacters(string)` which provided an input string this will strip any illegal characters present within it
2023-06-21 14:09:32 +02:00
e833cf7a93
ConnectionInfo
...
- Added `getMode()` and `setMode(ChecksMode)`
2023-06-21 13:49:36 +02:00
5bcbdf72cd
ChecksMode
...
- Defined as the mode describes how birchwood will act when encounterin invalid characters that were provided BY the user TO birchwood
ConnectionInfo
- Use `ChecksMode.EASY` by default
2023-06-21 13:49:22 +02:00
f54e6d9d9b
Events
...
- Documented enum `IRCEventType` and its memers
2023-06-21 13:34:38 +02:00
156af08974
Events
...
- Documented `PongEvent` and `IRCEvent`
2023-06-21 13:34:02 +02:00
e399b0d504
Messages
...
- Documented module
2023-06-21 11:28:45 +02:00
4be1e2e1e2
ControlCode
...
- Removed completed TODO
2023-06-21 11:28:16 +02:00
9a82f9e703
Constants
...
- Documented module
2023-06-21 11:27:26 +02:00
79981897ff
Client
...
- Cleaned up whitespace
2023-06-21 11:23:41 +02:00
6ea7f0c421
Client
...
- Fixed documentation of `connect()` method
2023-06-21 11:22:40 +02:00
dfe2110efc
Client
...
- Documented module
- Removed comment for destructor
2023-06-21 11:21:35 +02:00
992808ca5c
Events
...
- Documented module
- Removed now-completed TODO
2023-06-21 11:20:18 +02:00
385e5856c2
Client
...
- Removed irrelevant TODO
2023-06-21 11:18:42 +02:00
7e44231295
- Updated dependency information
2023-06-21 11:15:43 +02:00
8866895355
- FIxed layout from not rendering on dub
2023-06-21 11:13:53 +02:00
ef532f23f5
- Added shields
2023-06-21 11:11:01 +02:00
d5da8f8f68
Merge pull request #18 from deavmi/ircv3
...
ircv3 support
2023-06-21 11:03:52 +02:00
d924a91d21
Sender
...
- Removed completed TODO
2023-06-21 11:02:45 +02:00
dc5d0f9f4a
Receiver
...
- Catch more specific exception, `FatalException` rather than `SnoozeError`
- Adjusted error message printed out in unittest-builds on occurence of such an exception
Sender
- Catch more specific exception, `FatalException` rather than `SnoozeError`
- Adjusted error message printed out in unittest-builds on occurence of such an exception
2023-06-13 20:30:10 +02:00
f6069ed254
Sender
...
- When `wait()` has an `InterruptedException` then go back to the loop again (retry the `wait()`)
- On `SnoozeError` (for now) we also do the same even though we should stop the loop
Receiver
- When `wait()` has an `InterruptedException` then go back to the loop again (retry the `wait()`)
- On `SnoozeError` (for now) we also do the same even though we should stop the loop
Dub
- Upgraded to `libsnooze` version `1.0.0-beta`
2023-06-12 17:52:42 +02:00
68a8fc74ae
Sender
...
- Added a TODO to catch the `InterruptedException` here
2023-06-12 08:23:36 +02:00
27704617a7
Receiver
...
- Added a TODO to catch the `InterruptedException` here
2023-06-12 08:23:22 +02:00
8199b8b2a4
Client
...
- When the remote host closes the connection and we are in `unittest` build then purposefully crash
2023-06-05 21:04:44 +02:00
2b5da1eb9a
Client
...
- In the `loop()` (the read loop) if built in `unittest` mode then log the read count/status and the current data after the PEEK'd read
2023-06-02 19:29:53 +02:00
cf23797f99
Unit test
...
- Hang for testing ping-pong
2023-06-01 15:59:38 +02:00
