elastic/kibana

[Fleet] Integration page console errors

Open

#169,067 opened on Oct 17, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)TypeScript (8,021 forks)batch import
Team:Fleetbuggood first issue

Repository metrics

Stars
 (19,065 stars)
PR merge metrics
 (Avg merge 1d 16h) (999 merged PRs in 30d)

Description

Kibana version: main branch

Describe the bug:

While opening the Integrations page I see the following errors in browser DevTools console:

Warning: React does not recognize the `packageName` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `packagename` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

...

Warning: React does not recognize the `integrationName` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `integrationname` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

Steps to reproduce:

  1. Load Kibana with DevTools open
  2. Click add integrations
  3. Refresh the page or
  4. Search for the Sample data and click on the Sample data integration.
  • Now click on the Integrations breadcrumb

Expected behavior:

No errors/warnings.

Screenshots (if relevant):

integrations_errors

Contributor guide

Research direction
Locate the React components in the Integrations page that pass `packageName` or `integrationName` props to DOM elements. Ensure these props are not forwarded to the underlying HTML elements by using proper React conventions like destructuring or removing them before spreading.
Tech stack
typescriptreact
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75