timeularex v0.1.0 Timeularex

API wrapper for the Timeular public API

http://developers.timeular.com/public-api/

Link to this section Summary

Link to this section Functions

Link to this function activate_device(device_serial)
Link to this function archive_activity(activity_id)
Link to this function archived_activities()
Link to this function assign_side_activity(device_side, activity_id)
Link to this function create_activity(activity)
Link to this function deactivate_device(device_serial)
Link to this function disable_device(device_serial)
Link to this function edit_tracking_note(activity_id, note)
Link to this function enable_device(device_serial)
Link to this function remove_device(device_serial)
Link to this function reports(start_timestamp, stop_timestamp)
Link to this function start(type, args)

Called when an application is started.

This function is called when an application is started using Application.start/2 (and functions on top of that, such as Application.ensure_started/2). This function should start the top-level process of the application (which should be the top supervisor of the application’s supervision tree if the application follows the OTP design principles around supervision).

start_type defines how the application is started:

  • :normal - used if the startup is a normal startup or if the application is distributed and is started on the current node because of a failover from another node and the application specification key :start_phases is :undefined.
  • {:takeover, node} - used if the application is distributed and is started on the current node because of a failover on the node node.
  • {:failover, node} - used if the application is distributed and is started on the current node because of a failover on node node, and the application specification key :start_phases is not :undefined.

start_args are the arguments passed to the application in the :mod specification key (e.g., mod: {MyApp, [:my_args]}).

This function should either return {:ok, pid} or {:ok, pid, state} if startup is successful. pid should be the PID of the top supervisor. state can be an arbitrary term, and if omitted will default to []; if the application is later stopped, state is passed to the stop/1 callback (see the documentation for the c:stop/1 callback for more information).

use Application provides no default implementation for the start/2 callback.

Callback implementation for Application.start/2.

Link to this function start_tracking(activity_id)
Link to this function stop_tracking(activity_id)
Link to this function tags_and_mentions()
Link to this function time_entries(stopped_after, started_before)
Link to this function time_entry(entry_id)
Link to this function unassign_side_activity(device_side, activity_id)
Link to this function update_activity(activity)
Link to this function update_device_name(device_serial, name)