User tests: Successful: Unsuccessful:
When running the indexer of Smart Search in the backend, the output is very unsatisfying for debugging. When debugging is enabled, this PR adds a list of all contexts that are being indexed with the total number of items to index and the currently indexed items.
npm i
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_finder JavaScript Repository |
Labels |
Added:
?
|
Unfortunately no. I don't know the best solution for these issues and if you could help me with this, I'd be very gratefull.
Woof is happy.
https://eslint.org/docs/rules/prefer-template (formatting strings
https://eslint.org/docs/rules/guard-for-in (you were missing the hasOwnProperty
on one loop and on the other on a style eslint didn't like)
Finally we're using the airbnb style guide which chooses to disallow for in loops because of the whole prototype thing https://github.com/airbnb/javascript#iterators--nope
To fix that i used Object.entries
which isn't the most efficient ever (Object.keys is probably better looking for 10 seconds at https://hackernoon.com/5-techniques-to-iterate-over-javascript-object-entries-and-their-performance-6602dcb708a8 ). But I wasn't sure exactly what the data structure was as was just doing this from github editor (if we had key => value or just a list)
I have tested this item
I apply this patch and run npm install. Without this patch the indexer runs correctly. With patch applied the indexer don´t run.
I've gone through this again and hopefully fixed it. Can you check again?
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22593.
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
Labels |
Added:
?
|
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-12-11 13:50:44 |
Closed_By | ⇒ | wilsonge |
Can you make the dog here happy?