vucalur / nemtu Goto Github PK

• Scroll to new articles link inside toastr

Flag ignoreChanges for each of engine.customFields deciding if changes to a field should cause an article to be treated as new.

For fixed fields behaviour is non-configurable:

• title, imgUrl, url - changes ignored
• listingId - change always yields a new article.
• scrapDate - void for new posts

Spike/Thinking: where does the latency happen? network? parsing? → Performance benchmark!

From eBay search:

Use similar, more user-friendly approach. Nobody wants to write see crazy XPath selectors :)

Can be applied in 2 places:

1. When copying public engine, user could select a subset of fields she wants to use.
   View can be switched to more advanced form with selectors edit option.
2. Scrap and store all fields defined by engine. When browsing articles of a channel, user can choose which ones to display with a similar UI

angular.js?3437:13920 Error: Firebase.child failed: First argument was an invalid path: "undefined". Paths must be non-empty strings and can't contain ".", "#", "$", "[", or "]"

Caused by invoking firebase.database.Reference.child() with undefined path somewhere in the code.

Bug causes channels view not to be rendered properly: