gleek/fluxpocket

Drupal module for pocket integration for fluxkraft

fluxpocket's Issues

Event for deletion of Url

Triggered everytime a url is deleted from pocket

'since' element not respected in the events

Every time a pocket event is triggered, maximum allowed entries(3) are fetched even those which are already fetched.
this is handled in PocketTaskEntryHandler.php getRequestArguments() but does not seem to work

Split "Modify/Delete Url from Pocket" in different actions

Follow up of #1

Currently the Rules Action "Modify/Delete Url from Pocket" contains of 5 different actions. These 5 Actions should be provided as separate actions.

• Archive
• Unarchive (re-add, I'd change the wording to unarchive, as it is more clear)
• Favorite
• Unfavorite
• Delete

Current Status and Future Task

The Project Broadly consists of two parts :

• Action
• Events

The Action Part is fully functional as of now.

Events/Triggers(Future Tasks):

• Requires the Server to Poll the getpocket server after specified time interval
  • Will be added by adding the form entry in the service endpoints.
• Tasks will be added extending RepetitiveTaskHandlerBase class
• Events will be added along with rule extending CronEventHandlerBase class

making events work for established services

The events of established services such as fluxtwitter don't seem to respond when the events take place. There might be some configuration errors. This is critical to understand before making the events for gleek/fluxpocket.

Event for Addition of Item in Pocket

An event should be triggered when an url is added to the Pocket.
The Event in turn should create variables specifying the:
url, tags, status(favorite/archive), resolved_url, etc.

Event for new favorite item

Event for new item tagged

The rule should also give the list of tags

Create Entities providing entity classes

Add support for Tagging Actions

As stated in the API docs, Modifying tags for items can be possible. For making that work, we might need to get or to retrieve the item_id for a given URL.

So for solving this issue, we have to deal with retrieving data from Pocket first.

Event for archiving of Url

Event - Fluxpocket Repeating Evaluation of a same entry which was already addressed earlier

The bug can be reproduced considering the following scenario

1. Add a rule to trigger every time a favorite URL is added (action being anything such as creation of entity)
2. Add a URL to pocket and add it to favorites
3. Run Cron to Execute the rule
   • The URL is evaluated (as expected)
   • since_id is updated to the time_updated of the URL
4. Add the same URL to Archive (or do any other edits to the URL)
   • time_updated is changed for the URL
5. Run Cron to Execute the rule
   • The URL is re-evaluated (not expected)

This bug holds for any other event such as a new archived entry.

Causes
Since the Updation time of URL is changed when there are any changes in Pocket corresponding that URL (such as adding it to archive or editing the tags),
there is no way for fluxpocket to know that the entries have been evaluated previously.

Possible Solution
Storing the id's of all the processed items and matching them every time with all the entries of pocket.
This is highly inefficient and also the existing fluxservice infrastructure may not have this extent of flexibility.

Other options such as considering the time_created instead of time_updated also provide wrong results.

Creating Task Handler for fluxpocket

Task Handlers are classes that dispatch rule events.
Provides a repetitive task that is repetitively run by Rules Scheduler depending on the configured polling interval.
The classes are created extending the RepetetiveTaskHandlerBase class

Raw documentation

The major classes and there functions should be written in a form of raw documentation