-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[APM] Migrate Kibana plugins (that depend on APM) to TS project references #81003
Comments
Pinging @elastic/apm-ui (Team:apm) |
Also add missing pieces to kibana_react, as a follow-up to elastic#80992. References elastic#80508 References elastic#81003
Also add missing pieces to kibana_react, as a follow-up to elastic#80992. References elastic#80508 References elastic#81003 # Conflicts: # tsconfig.json
data plugin and others have now been updated in #87294 so we can make some more progress on this now. |
References elastic#80508. References elastic#81003.
References elastic#80508. References elastic#81003.
References elastic#80508. References elastic#81003.
References elastic#80508. References elastic#81003.
About the infra <> apm circular dependency:
It looks like the
Seems like it would be ok go move |
Thanks, @smith, that sounds like a good short-term solution to break the cycle. If you move that function we can try to projectify |
References elastic#80508. References elastic#81003. # Conflicts: # x-pack/tsconfig.refs.json
Like #80508, but for APM-specific plugins and their transitive dependencies.
Implementation instructions.
This list is based on looking at APM's optional and required plugins in its kibana.json and manually walking the transitive dependencies. Other dependencies may also exist and can be added here when found.
It is not complete at this time.
circular dependency here) (#80995)The text was updated successfully, but these errors were encountered: