8e00e036e1
* FEATURE: Make emotion /filter ordering match the dashboard table This change makes the /filter endpoint use the same criteria we use in the dashboard table for emotion, so it is not confusing for users. It means that only posts made in the period with the emotion shall be shown in the /filter, and the order is simply a count of posts that match the emotion in the period. It also uses a trick to extract the filter period, and apply it to the CTE clause that calculates post emotion count on the period, making it a bit more efficient. Downside is that /filter filters are evaluated from left to right, so it will only get the speed-up if the emotion order is last. As we do this on the dashboard table, it should cover most uses of the ordering, kicking the need for materialized views down the road. * Remove zero score in filter * add table tooltip * lint |
||
|---|---|---|
| .github/workflows | ||
| admin/assets/javascripts/discourse | ||
| app | ||
| assets | ||
| config | ||
| db | ||
| discourse_automation | ||
| lib | ||
| public/ai-share | ||
| spec | ||
| svg-icons | ||
| test/javascripts | ||
| tokenizers | ||
| .discourse-compatibility | ||
| .gitignore | ||
| .npmrc | ||
| .prettierignore | ||
| .prettierrc.cjs | ||
| .rubocop.yml | ||
| .streerc | ||
| .template-lintrc.cjs | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| README.md | ||
| eslint.config.mjs | ||
| package.json | ||
| plugin.rb | ||
| pnpm-lock.yaml | ||
| translator.yml | ||
README.md
Discourse AI Plugin
Plugin Summary
For more information, please see: https://meta.discourse.org/t/discourse-ai/259214?u=falco