[App Search] Detail Page for Automated Curations#113550
[App Search] Detail Page for Automated Curations#113550byronhulcher merged 24 commits intoelastic:masterfrom
Conversation
…uration is automated
e0711cb to
1d29af1
Compare
|
retest |
| "xpack.enterpriseSearch.appSearch.engine.curations.manageQueryButtonLabel": "クエリを管理", | ||
| "xpack.enterpriseSearch.appSearch.engine.curations.manageQueryDescription": "このキュレーションのクエリを編集、追加、削除します。", | ||
| "xpack.enterpriseSearch.appSearch.engine.curations.manageQueryTitle": "クエリを管理", | ||
| "xpack.enterpriseSearch.appSearch.engine.curations.organicDocuments.emptyDescription": "表示するオーガニック結果はありません。上記のアクティブなクエリを追加または変更します。", |
There was a problem hiding this comment.
I'm pretty sure you don't have to prune these old labels, and that they will be pruned automatically by the i18n process. This is something @constancecchen mentioned before (if I recall correctly), though I'm not sure I'd be able to find the PR where she talks about that or any documentation to back that up.
There was a problem hiding this comment.
I got CI failures from these unpruned ones, I'll reach out to you next time I see that happen.
There was a problem hiding this comment.
Re: i18n failures - if you run node scripts/i18n_check --fix it'll handle removing stuff for you automatically without having to open the file!
More reading: https://github.com/elastic/kibana-team/blob/master/localization.md (their diagram is neat and worth expanding, + the info around how and when they manage scheduling for i18n)
There was a problem hiding this comment.
Re: i18n failures - if you run node scripts/i18n_check --fix it'll handle removing stuff for you automatically without having to open the file!
👍 I used that to remove these, just highlighting that they're not pruned automatically.
JasonStoltz
left a comment
There was a problem hiding this comment.
This code all looks great. I just left a couple of comments. Full disclosure, it takes forever for me to pull down a new branch and rebuild to test, so I did not test this locally.
| import { PromotedDocuments, OrganicDocuments } from './documents'; | ||
|
|
||
| export const AutomatedCuration: React.FC = () => { | ||
| const { curationId } = useParams() as { curationId: string }; |
There was a problem hiding this comment.
I suspect you can do something like this instead to avoid casting.
const { curationId } = useParams<{ curationId: string }>();
| const { convertToManual } = useActions(CurationLogic({ curationId })); | ||
| const { activeQuery, dataLoading, queries } = useValues(CurationLogic({ curationId })); |
There was a problem hiding this comment.
Purely out of curiosity, do you know if there is any functional difference between what you have and the following? The later avoids instantiating the logic twice, but I don't know if it matters or not.
| const { convertToManual } = useActions(CurationLogic({ curationId })); | |
| const { activeQuery, dataLoading, queries } = useValues(CurationLogic({ curationId })); | |
| const logic = CurationLogic({ curationId }); | |
| const { convertToManual } = useActions(logic); | |
| const { activeQuery, dataLoading, queries } = useValues(logic); |
There was a problem hiding this comment.
No reason! I'll go with yours
There was a problem hiding this comment.
I've done this in 9930246. I think its effectively the same, but I think instantiating it once is a better practice, in casse we use a lot of props in other logic files.
| }); | ||
|
|
||
| describe('draggging', () => { | ||
| describe('dragging', () => { |
💚 Build SucceededMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: |
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
This reverts commit 4d2a9c5.
|
Apologies @byronhulcher, this needed to be reverted. It was causing type checks to fail, see here: https://buildkite.com/elastic/kibana-hourly/builds/906#ccd9944c-5587-4b24-8502-a73bd37d4145 It likely conflicted with something else that was merged in since the last time you merged upstream |
Summary
The
Curationview has now split into theManualCurationandAutomatedCurationviews.ManualCurationis unchanged from the oldCurationwhileAutomatedCurationis new, with the differences being:AutomatedBadgeScreenshots
Checklist