Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
) # Backport This will backport the following commits from `main` to `8.x`: - [[Rules migration] Post merge feedback followups (#202815)](#202815) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-04T16:06:10Z","message":"[Rules migration] Post merge feedback followups (#202815)\n\n## Summary\r\n\r\nThese are the followup updated to address feedback from my previous PRs:\r\n\r\n* Make sure to use descriptive names specific to the `siem_migrations`\r\nsubdomain\r\n([comment](https://github.com/elastic/kibana/pull/200978#pullrequestreview-2454582368)):\r\n\r\n> Make sure you use descriptive names specific to the siem_migrations\r\nsubdomain. Names like RulesPage, RulesTable, useRulesColumns etc are way\r\ntoo generic and conflict with the rule management terminology, which\r\nwould make code search more difficult.\r\n\r\n\r\n* Export the memo component directly everywhere\r\n([comment](https://github.com/elastic/kibana/pull/201597#discussion_r1858069127)):\r\n\r\n> Could we export the memo component directly everywhere? It's shorter\r\nand it makes it easier to find the references in the IDE.\r\n\r\n\r\n* Use one hook to access APIs instead of two\r\n([comment](https://github.com/elastic/kibana/pull/202494#discussion_r1867967135)):\r\n\r\n> I see that for every API request we have to implement 2 separate\r\nhooks. Why don't we add error handling to the same hook that does the\r\nuseQuery? so we have everything in one hook. Or is there a reason to\r\nhave them separate?","sha":"4d8f7111d0f8c330aab2c8347cf6d131570ff665","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:prev-minor"],"title":"[Rules migration] Post merge feedback followups","number":202815,"url":"https://github.com/elastic/kibana/pull/202815","mergeCommit":{"message":"[Rules migration] Post merge feedback followups (#202815)\n\n## Summary\r\n\r\nThese are the followup updated to address feedback from my previous PRs:\r\n\r\n* Make sure to use descriptive names specific to the `siem_migrations`\r\nsubdomain\r\n([comment](https://github.com/elastic/kibana/pull/200978#pullrequestreview-2454582368)):\r\n\r\n> Make sure you use descriptive names specific to the siem_migrations\r\nsubdomain. Names like RulesPage, RulesTable, useRulesColumns etc are way\r\ntoo generic and conflict with the rule management terminology, which\r\nwould make code search more difficult.\r\n\r\n\r\n* Export the memo component directly everywhere\r\n([comment](https://github.com/elastic/kibana/pull/201597#discussion_r1858069127)):\r\n\r\n> Could we export the memo component directly everywhere? It's shorter\r\nand it makes it easier to find the references in the IDE.\r\n\r\n\r\n* Use one hook to access APIs instead of two\r\n([comment](https://github.com/elastic/kibana/pull/202494#discussion_r1867967135)):\r\n\r\n> I see that for every API request we have to implement 2 separate\r\nhooks. Why don't we add error handling to the same hook that does the\r\nuseQuery? so we have everything in one hook. Or is there a reason to\r\nhave them separate?","sha":"4d8f7111d0f8c330aab2c8347cf6d131570ff665"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202815","number":202815,"mergeCommit":{"message":"[Rules migration] Post merge feedback followups (#202815)\n\n## Summary\r\n\r\nThese are the followup updated to address feedback from my previous PRs:\r\n\r\n* Make sure to use descriptive names specific to the `siem_migrations`\r\nsubdomain\r\n([comment](https://github.com/elastic/kibana/pull/200978#pullrequestreview-2454582368)):\r\n\r\n> Make sure you use descriptive names specific to the siem_migrations\r\nsubdomain. Names like RulesPage, RulesTable, useRulesColumns etc are way\r\ntoo generic and conflict with the rule management terminology, which\r\nwould make code search more difficult.\r\n\r\n\r\n* Export the memo component directly everywhere\r\n([comment](https://github.com/elastic/kibana/pull/201597#discussion_r1858069127)):\r\n\r\n> Could we export the memo component directly everywhere? It's shorter\r\nand it makes it easier to find the references in the IDE.\r\n\r\n\r\n* Use one hook to access APIs instead of two\r\n([comment](https://github.com/elastic/kibana/pull/202494#discussion_r1867967135)):\r\n\r\n> I see that for every API request we have to implement 2 separate\r\nhooks. Why don't we add error handling to the same hook that does the\r\nuseQuery? so we have everything in one hook. Or is there a reason to\r\nhave them separate?","sha":"4d8f7111d0f8c330aab2c8347cf6d131570ff665"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <[email protected]>
- Loading branch information