-
Notifications
You must be signed in to change notification settings - Fork 123
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
The Next Version #58
Comments
Hey! I think we should make it as easy to use as possible and try to remove any kind of redundancy. Also, we can use only the Gmail style search so we don't have to implement many things. What do you think of something like this? https://gist.github.com/gabrielengel/201e9661b4f92b8f543d |
@myobie I'm a user/maintaner of gmailgem/gmail (formerly nu7hatch/gmail which was originally forked from this repo.) We'd be very keen to join efforts on the gmailgem fork as our goals are the same, i.e. more usable API, better testing, etc. |
@johnnyshields awesome. I'd like to get some tests started so we can all get it going soon. I've added you as a collaborator. |
@gabrielengel regarding your gist I do have this feedback: I don't think we need to manage any state, instead we can just return objects from every call. An example of what this would look like from your gist would be: Gmail.new(username, password) do |gmail|
gmail.in('inbox').count # => 100
gmail.search('is:unread').count # => 60
gmail.search('is:read').count # => 40
gmail.search('before:2010-02-20 after:2010-03-20')
gmail.search('on:2010-04-15')
gmail.search('from:[email protected]')
gmail.search('to:[email protected]')
gmail.search('is:read from:[email protected] "you are a great employee"')
gmail.peek do |peek|
peek.in('Urgent').count
end
end |
@myobie, I've added you to the gmailgem organization. Come over to our side--we have an awesome team and a reliable approach to test the gem on Travis CI with specs now green. Your suggested improvements are most welcome. |
I think it would be useful in the new version to abandon username/password auth and using Gmail's API.
|
I'm closing this since it's so old. |
Shortly, I want to begin the next version of ruby-gmail.
This gem should live up to this description:
To get there I think these steps need to be taken:
These are very generic todos, but I think they are the path forward. Labels are super important. Also being able to peak and not mark as read will be huge.
If anyone is interested in helping or has comments on the direction please feel free to comment here.
The work for 2.0 will take place on my fork.
The text was updated successfully, but these errors were encountered: