Ondřej Synáček ae700330b9 fix: do not attempt to parse non-existent FB pages ... When user enters something invalid (like number 123), it wuold still hit FB webpage and return HTML. I do simple detection by looking at title when it attempts to parse the DOM directly. When it contains "Content Not Found", it is skipped. Non-existent web pages cannot be parsed by using LDJSON parser and looking at null data.		2020-12-26 21:03:03 +01:00
..
app	feature: add endpoint for logging instrumentation	2020-12-12 13:19:34 +01:00
frontend	fix: error due to inability to parse invalid unicode sequences	2020-12-26 20:57:19 +01:00
routes	feature: add endpoint for logging instrumentation	2020-12-12 13:19:34 +01:00
services	fix: do not attempt to parse non-existent FB pages	2020-12-26 21:03:03 +01:00
static	fix: build process to support Svelte and service worker	2020-12-23 22:05:30 +01:00
views	add webpack for front end builds and serve the assets from backend	2020-07-19 08:14:35 +02:00
cli.js	remove URL requirement for DOM parser	2020-07-19 08:14:34 +02:00
index.js	fix issues with deployment due to winston logging getting in the way	2020-11-15 15:13:49 +01:00
log-utils.js	separate utilities for logs	2020-07-19 08:14:35 +02:00
middlewares.js	separate utilities for logs	2020-07-19 08:14:35 +02:00
parser-utils.js	add fallback parser when LD/JSON not found, use DOM parser	2019-10-23 22:08:49 +02:00
utils.js	separate utilities for logs	2020-07-19 08:14:35 +02:00