armitage35 / facebook-event-tracker Goto Github PK

View Code? Open in Web Editor NEW

4.0 4.0 1.0 877 KB

A CLI tool that lets non Facebook users keep track of FB Page's events

License: MIT License

JavaScript 100.00%

cli facebook nodejs pupeteer

facebook-event-tracker's People

Contributors

Stargazers

Watchers

Forkers

lgtm-migrator

facebook-event-tracker's Issues

Package the app and distribute it

Make links work on windows

Worth taking into account the fact that terminal-link doesn't work on Windows (at least, not in ConEmu or derivatives). It actually outputs nothing.

To solve that, you could try checking whether or not the terminal of the user supports links, or detect the platform (using os.type()).

Originally posted by @nospoone in https://github.com/Armitage35/facebook-event-tracker/diffs

Improve error handling and reporting

Expected behaviour

Ensure the app reports carshes and usage to different services

Ensure the app is properly initialized

Expected behaviour

Ensure we have a nice behaviour to welcome the user when he arrives the first time the app is launched.

Steps

Create an empty pages file
Display a nice message when this arrives
Disable the crawling feature if there is not at least one page to be crawled

Properly format the urls

Current behaviour

If the user input the page's URL without the /event the parsing won't work

Expected behaviour

add the /event to the page's url if that's not done alerady

display every dates for this event. Not just the first one

facebook-event-tracker/recurring.js

Lines 21 to 26 in e704069

    
           // todo: display every dates for this event. Not just the first one 
        
           const eventDates = await page.evaluate( 
        
           	() => [...document.querySelectorAll('._5x8v')].map(elem => elem.innerText.replace(/\n/g, '')) 
        
           ); 
        
           const eventLink = await page.evaluate(

This issue was generated by todo based on a `todo` comment in `e704069` when #4 was merged. cc @Armitage35.

display every dates for this event. Not just the first one

facebook-event-tracker/recurring.js

Lines 21 to 26 in a2cb892

    
           // todo: display every dates for this event. Not just the first one 
        
           const eventDates = await page.evaluate( 
        
           	() => [...document.querySelectorAll('._5x8v')].map(elem => elem.innerText.replace(/\n/g, '')) 
        
           ); 
        
           const eventLink = await page.evaluate(

This issue was generated by todo based on a `todo` comment in `a2cb892`. It's been assigned to @Armitage35 because they committed the code.

As a user, I want my terminal inputs to be saved in a file within the project in order for them

Expected behaviour

The assignee will enable a user to:

Be asked about an input
Type his input
The app should confirm that the input is actually a Facebook URL, if not, ask for a re-input
Get his answer be displayed to him

These answers should be kept within a file in the project

Add integration testing

Expected behaviour

We already have unit testings (#43 ) so now, time for unit testing baby!

Add unit testing

Add testing to the app and run testing on a CI

Create ical files for events

Check that the user inputs is actually a fb page!

Current behaviour

The user can add anything and we won't know why shit hits the fan until we go and parse it, which is sad.

Expected behaviour

When the user inputs a page, check that it's actually a page.

Strategy

Review regex to only check against Facebook pages
Quickly check the page online to verify it is in fact a page

As a developer, I need to write a POC to make sure I can actually pull data from a FB page using Puppeteer

Current behaviour

We believe we should be able to pull out a page's event using Puppeteer but we have not proven it.

Expected behaviour

The assignee will parse a page to pull a page's event. We want to show we can pull:

An event name
An event date
An event except
An event's location

Annexes

Documentation

Documentation available here: https://github.com/Armitage35/facebook-event-tracker/wiki/Facebook-events-page-architecture

As a developer, I want to understand the ins and out of this project in order to be able to contribute

Current behaviour

The repo does not currently have any documentation, thus, preventing anyone to understand what it does and preventing anyone from contributing.

Expected behaviour

The assignee will:

Set up a readme
Set up the wiki to explain what the project does

Modularize code

Current behaviour

Code is monolithic and huge

Expected behaviour

Split the code into multiple files

	// todo: display every dates for this event. Not just the first one
	const eventDates = await page.evaluate(
	() => [...document.querySelectorAll('._5x8v')].map(elem => elem.innerText.replace(/\n/g, ''))
	);

	const eventLink = await page.evaluate(

armitage35 / facebook-event-tracker Goto Github PK

facebook-event-tracker's People

Contributors

Stargazers

Watchers

Forkers

facebook-event-tracker's Issues

Expected behaviour

Expected behaviour

Steps

Current behaviour

Expected behaviour

This issue was generated by todo based on a todo comment in e704069 when #4 was merged. cc @Armitage35.

This issue was generated by todo based on a todo comment in a2cb892. It's been assigned to @Armitage35 because they committed the code.

Expected behaviour

Expected behaviour

Current behaviour

Expected behaviour

Strategy

Current behaviour

Expected behaviour

Annexes

Documentation

Current behaviour

Expected behaviour

Current behaviour

Expected behaviour

Recommend Projects

Recommend Topics

Recommend Org

This issue was generated by todo based on a `todo` comment in `e704069` when #4 was merged. cc @Armitage35.

This issue was generated by todo based on a `todo` comment in `a2cb892`. It's been assigned to @Armitage35 because they committed the code.