isosphere / logseq-journals-nextprev

Provides buttons to jump to the next or previous journal entry

I'm a software developer that aims to create reliable and efficient software.

As a software developer I have:

• built a data collection, reporting, and analysis backend for the financial trading side of an expert in the meat and livestock industry
• built a responsive WASM application that tracks power outages in Nova Scotia
• architected a custom CRM for a client's physical meat business
• built monitoring software polling a campus of environmental monitoring devices for Sanofi Pasteur in Toronto, Canada
• enabled software compatiblity with closed, proprietary protocols

I think these public issues are a good example of my work ethic and process:

• isosphere/mastodon#1
• PyO3/pyo3#1476
• erdogant/distfit#12
• arviz-devs/arviz#1756
• arviz-devs/arviz#1755

Contact

You can find my Linked In profile here, you should also see my e-mail in the panel on the left.

I run a Mastodon instance for Atlantic Canada.

New Clients

I am available for contract work; my customers are small businesses that rely on Excel and manual data manipulation/entry. I automate their processes to ensure that their data is serving them - too many serve their data.

I operate under Data Heck.

logseq-journals-nextprev's Issues

Doesn't work with journals

Currently, It only works on single page. It is possible to make the back button function assuming today's date, on journals. I can make a pull request.

The first time, two buttons on the toolbar are hidden by Logseq

The README needs an explanation.

An expensive query is run on every click

Running these queries fresh on every click is unnecessarily expensive:

logseq-journals-nextprev/src/App.vue

Lines 23 to 59 in a7fb8c5

	async _getNewerJournals(currentJournalDate) {
	let ret
	try {
	ret = await logseq.DB.datascriptQuery(`
	[:find (pull ?p [*])
	:where
	[?b :block/page ?p]
	[?p :block/journal? true]
	[?p :block/journal-day ?d]
	[(> ?d ${currentJournalDate})]]
	`)
	} catch (e) {
	console.error(e)
	}
	return this._cleanJournalQueryReturn(ret)
	},
	async _getOlderJournals(currentJournalDate) {
	let ret
	try {
	ret = await logseq.DB.datascriptQuery(`
	[:find (pull ?p [*])
	:where
	[?b :block/page ?p]
	[?p :block/journal? true]
	[?p :block/journal-day ?d]
	[(< ?d ${currentJournalDate})]]
	`)
	} catch (e) {
	console.error(e)
	}
	return this._cleanJournalQueryReturn(ret)
	},

We need only to cache the result and, if the appropriate hooks are available, hook into new journal creation or existing journal deletion to update the cache.

Hide the button in conditions where it doesn't work

There's no point in pushing buttons that don't work. Use CSS to hide buttons when non-journal page is open. I can make a pull request.

Shift does not open items in the sidebar

I've examined the code for logseq-journal-calendar and I don't understand how that plugin accomplishes this feature. The event that is checked is always just {} 🤔