bilbottom / daily-tracker Goto Github PK

An application for keeping track of tasks throughout the day.

Python 100.00%

python

daily-tracker's Introduction

🧙 Howdy, I’m Billiam

I like Maths, coding, and Star Trek – Qapla'!

I'm a Data person, specialising in SQL and Python. A lot of my brain power is spent thinking about automation, optimisation, application structure, and data modelling.

I'm motivated by "how I do" rather than "what I do".

Some of my pet peeves include:

Homonyms
Ted Mosby
Datetime formats that don't follow ISO 8601

🤔 Who is Billiam anyway?

Education and Career 👨‍🎓 👨‍💼

Art & Design Foundation Diploma for 1 year
Brighton University for 3 years to get a Maths BSc
Warwick University for 1 year to get a Pure Maths MSc
Credit Risk Analyst at TSB for 2 years
Analyst at Jaja Finance for 1 year
Data Analyst at Allica Bank for 1 year
Analytics Engineer at Sainsbury's (:avocado:) currently

🤖 Bilbottom as Code	📊 GitHub Stats
class Bilbottom(TypicalNerd): """A man, a myth, a legend.""" name = "Billiam" location = "London, England" languages = ["SQL", "Python"] @property def favourite_language(self) -> str: return random.choice(self.languages)	Powered by https://github.com/anuraghazra/github-readme-stats

🤖 Bilbottom as Code

📊 GitHub Stats

class Bilbottom(TypicalNerd):
    """A man, a myth, a legend."""
    name = "Billiam"
    location = "London, England"
    languages = ["SQL", "Python"]
    
    @property
    def favourite_language(self) -> str:
        return random.choice(self.languages)

Powered by https://github.com/anuraghazra/github-readme-stats

daily-tracker's People

Contributors

Watchers

daily-tracker's Issues

Move the contents of the .env file into the configuration.yaml file

The variables in the .env file aren't actually environment variables, they're credentials -- so a better interface into them is through the yaml file

This will allow us to drop the python-dotenv dependency, too

The security considerations of this will need to be assessed, but it should be easy enough to allow specific environment variables (defined outside of the .env file) to be used where the configuration.yaml file is empty for the corresponding credential

AppleScript doesn't return recurring meetings

With recurring meetings, the AppleScript call to Outlook doesn't return instances of recurring meetings after the first instance

This means that the calendar integration isn't as fully featured on macOS as we would like since the pop-up doesn't recognise that a (recurring) meeting is scheduled

Using AppleScript actually locks this into the "old" Outlook. Does the "new" Outlook have an alternative API that we can use?

Add a `--debug` option which tests the connection to the enabled integrations

Jira: https://community.atlassian.com/t5/Confluence-questions/Health-Check-endpoint/qaq-p/1013647
Slack: ...
Outlook: ...

One more issue

Some stuffs

Test issue

Some sample description

Add functionality for "New Outlook" on macOS

The AppleScript solution only works for the legacy Outlook (as at 2024-03-22) and the legacy Outlook has stopped working for me, so I need to use the new Outlook and need the auto-population from meetings enabled for it

Tidy database backend (and get triggers working)

There are a few places in the backend where quick fixes have been thrown in to fix some small errors and bugs, rather than implementing a proper fix. One such example is the introduction of the v_latest_tasks view to account for the triggers causing errors with the sqlite3 API:

daily-tracker/daily_tracker/core/database.py

Lines 226 to 239 in e1e7a26

    
                   # latest_tasks = """ 
        
                   #     select task, detail 
        
                   #     from v_latest_tasks 
        
                   #     where last_date_time >= datetime('now', :date_modifier) 
        
                   #        or indx = 0  /* Defaults */ 
        
                   #     order by indx, task 
        
                   # """ 
        
                   latest_tasks = """ 
        
                       select task, detail 
        
                       from task_detail_with_defaults 
        
                       where last_date_time >= datetime('now', :date_modifier) 
        
                          or indx = 0  /* Defaults */ 
        
                       order by indx, task 
        
                   """

The backend has ended up being a mess because of these quick-fixes. These need to be aligned and tidied up, with a clear separation between database features (triggers) and Python features

Two alternatives:

Kivy: https://kivy.org/
Qt: https://www.qt.io/qt-for-python

Improve the performance of the unit test workflow

The issue is installing the dependencies every single time

Some potential solutions:

Create a docker image for this application
Add a caching step to the workflow

	# latest_tasks = """
	# select task, detail
	# from v_latest_tasks
	# where last_date_time >= datetime('now', :date_modifier)
	# or indx = 0 /* Defaults */
	# order by indx, task
	# """
	latest_tasks = """
	select task, detail
	from task_detail_with_defaults
	where last_date_time >= datetime('now', :date_modifier)
	or indx = 0 /* Defaults */
	order by indx, task
	"""