-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes for v4 #78
Comments
As long as the original 'building block' base is available at some path, that should be generally agreeable, the subpath doesn't seem troublesome. It makes sense to have a 'reference implementation' of sorts for people wanting somewhat more work done for them. One thing I'd love to see in a new major version is either first-class SASL support, or at least the necessary reworkings to allow hooking the registration flow so we can perform the SASL dance ourselves (#57 (comment)). Not having support for 'properly' logging into servers has been a papercut for my general use client. For prior art—another go client which supports both |
Yep, I plan on leaving Conn, Reader, Writer, Event, and Prefix mostly untouched. SASL would fit in the ircx package. I'll have to check out that implementation and see if I can come up with anything. |
I had a bit of time so I started work on this. Unfortunately, it doesn't look like gopkg.in handles alpha versions, so I'm temporarily moving this library back to the github namespace until it actually gets merged in. At that point, it will most likely go back to gopkg.in. For now the import paths are as follows:
Things that have been done so far:
And this is where I semi-rant about Go package management... I really wish that suffix wasn't required. It's really frustrating needing to add /v4 for v2+ but not for v0 and v1. It's a small, but fairly frustrating thing. I know the problem it's trying to solve... and I get it... but man, I really don't like those import paths. |
Things left to do:
|
I'm actually re-thinking this - I'm in the progress of moving Client back from ircx, and adding Tracker/ISupport under a new release. If/when breaking changes happen (like improved context support) I will do a major version bump. |
I don't have the time to work on improved Context support at the moment, so I'm going to leave that for v5. |
v4.0.0 was merged and tagged! |
Hello all!
I've been looking at releasing v4 of this library, mostly as a slightly simpler version and splitting some utilities I keep having to make out into a separate
ircx
package. I wanted to run all these past people before I just go ahead and do them though.ircx
- the idea is to keep the base package to only protocol-related tools like reading and writing messages, numerics, etc.gopkg.in/go-irc/irc.v4
- this will allow us to also havegopkg.in/go-irc/ircx.v0
rather thangopkg.in/irc.v4
and the longer form forircx
Additional tools meant for ircx:
Does anyone have any thoughts?
The text was updated successfully, but these errors were encountered: