content_scripts/content.js
// initialize onClick to set date time start to todays date and the current time and the date range end to one day from today
initialize onClick to set date time start to todays date and the current time and the date range end to one day from today
initialize onClick to set date time start to todays date and the current time and the date range end to one day from today
function onClick() {
		let urlPathName = this.id.split(" ")[0];
		let startTime = this.id.split(" ")[1];
		chrome.storage.local.set({
			dateRangeStart: startTime - 14400000,
			dateRangeEnd: startTime - 14100000,
			urlPathName: urlPathName
		});
		chrome.runtime.sendMessage(
			{
				action: "meetupRequest"
			},
			response => console.log(response)
		);
	}
function onClick ( ) { let urlPathName = this . id . split ( " " ) [ 0 ] ; let startTime = this . id . split ( " " ) [ 1 ] ; chrome . storage . local . set ( { dateRangeStart : startTime - 14400000 , dateRangeEnd : startTime - 14100000 , urlPathName : urlPathName } ) ; chrome . runtime . sendMessage ( { action : "meetupRequest" } , response => console . log ( response ) ) ; }
initialize onClick to set date time start to todays date and the current time and the date range end to one day from today
initialize onClick to set date time start to todays date and the current time and the date range end to one day from today
// set start range to the utc milliseconds formatted and pulled from the dom node, and the date range end to the date range start plus one day // the tool will query local storage when the api call is made to get the daterangestart and daterangeend time // eslint-disable-next-line no-console // normally the loading screen would initialize if this was fired from the react app, but the injected app doesn't know that the meetup request was initiated. The message is sent directly to the background script so a relay needs to be configured that will fire a message to the content script when the background script is pinged with the meetup request.