solal / stackoverflow-instant-answers Goto Github PK

Thanks for the extension! I think it has a lot of potential.

First impressions:

• Move the answer box below the google snippet, or, even better:
  • Ability to show the question
• Telemetry should be opt-in
• Animation is distracting. Actually the whole left panel with the checkmark and vote count is a bit useless.
• Add light mode

• Add a "top bar" to results.
• Bar needs to contain: username (as link to profile), photo, and reputation of the poster.

Based on feedback from @dalmo3, look into removing the left sidebar that contains only the upvote count (see here: #2)

Feature request from @dalmo3

Hi there, just installed the extension on Brave/Win10 but the buttons don't work.

When google loads this error shows up in the console.

Failed to load resource: the server responded with a status of 400 (Bad Request) 

// and this is the bad request:
https://api.stackexchange.com/2.2/questions/60251889;tagged;tagged;tagged;tagged;tagged;tagged;6884313;tagged;tagged/answers?order=desc&sort=activity&site=stackoverflow&filter=!b6Aub*uCt1FjWD

Clicking a button throws another error:

base.js:151 Uncaught TypeError: Cannot read property 'body' of undefined
    at addAnswerContent (base.js:151)
    at HTMLButtonElement.<anonymous> (base.js:111)
    at HTMLButtonElement.dispatch (jquery-2.2.4.min.js:3)
    at HTMLButtonElement.r.handle (jquery-2.2.4.min.js:3)

• Only cache about 1k results
• If ceiling is reached, purge results not accessed recently (individual results need recency timestamp for when they were last accessed).
• If result is older than 6 months, purge it to retrieve a newer version of the result.

Based on feedback from both @dalmo3 and @jobwat we need a light mode closer to ST styles.

Consider giving options for both light and dark modes.

This feature requires access to more real estate. Consider moving the answers to the sidebar instead of underneath the link.

Feedback from @jobwat

jQuery is being used for some (not all) DOM access and manipulation.
Remove it entirely in favor of vanilla JS.

• Use Chrome's storage API to store the values locally.
• Retain about 2k "seen" statuses to be mindful of the user's storage.
• If 2k limit reached, purge "seen" statuses not accessed recently (needs timestamp on the status to store latest access).

• Move all styles to SCSS.
• Cleanup the mess that is the current stylesheet to make it easier to maintain.

• Introduce support for other Stackechange domains.
• Retrieve and store locally the list of other Stackexchange domains.
• Change API query behavior to take other domains into account.