-
Notifications
You must be signed in to change notification settings - Fork 301
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
plugin(analytics-provider-segment): migration of analytics-provider-segment plugin to backstage/community-plugins workspace #1896
plugin(analytics-provider-segment): migration of analytics-provider-segment plugin to backstage/community-plugins workspace #1896
Conversation
Missing ChangesetsThe following package(s) are changed by this PR but do not have a changeset:
See CONTRIBUTING.md for more information about how to add changesets. Changed Packages
|
cc: @04kash / @nickboldt |
workspaces/analytics-provider-segment/plugins/analytics-provider-segment/.prettierrc.js
Outdated
Show resolved
Hide resolved
workspaces/analytics-provider-segment/plugins/analytics-provider-segment/CONTRIBUTING.md
Outdated
Show resolved
Hide resolved
workspaces/analytics-provider-segment/plugins/analytics-provider-segment/README.md
Outdated
Show resolved
Hide resolved
workspaces/analytics-provider-segment/plugins/analytics-provider-segment/README.md
Outdated
Show resolved
Hide resolved
workspaces/analytics-provider-segment/plugins/analytics-provider-segment/catalog-info.yaml
Outdated
Show resolved
Hide resolved
workspaces/analytics-provider-segment/plugins/analytics-provider-segment/catalog-info.yaml
Outdated
Show resolved
Hide resolved
workspaces/analytics-provider-segment/plugins/analytics-provider-segment/catalog-info.yaml
Outdated
Show resolved
Hide resolved
workspaces/analytics-provider-segment/plugins/analytics-provider-segment/catalog-info.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this live in the analytics workspace? https://github.com/backstage/community-plugins/tree/main/workspaces/analytics
Hmm yeah I think so too, WDYT @Fortune-Ndlovu ? |
Agreed, moving... |
Thanks for the contribution! |
Looks good! Just need to add a changeset |
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
…i-reports Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: MT Lewis <mtlewis@users.noreply.github.com> Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: MT Lewis <mtlewis@users.noreply.github.com> Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: MT Lewis <mtlewis@users.noreply.github.com> Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
…rsion Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
workspaces/analytics/plugins/analytics-provider-segment/catalog-info.yaml
Show resolved
Hide resolved
Needs an update to CODEOWNERS. See example in https://github.com/backstage/community-plugins/pull/1912/files |
workspaces/analytics/plugins/analytics-provider-segment/catalog-info.yaml
Outdated
Show resolved
Hide resolved
workspaces/analytics/plugins/analytics-provider-segment/package.json
Outdated
Show resolved
Hide resolved
workspaces/analytics/plugins/analytics-provider-segment/catalog-info.yaml
Outdated
Show resolved
Hide resolved
workspaces/analytics/plugins/analytics-provider-segment/catalog-info.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Fortune-Ndlovu <ndlovufortune97@gmail.com>
I see some unrelated commits as a part of this PR eg: d89bfc2, not sure how they got here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good with merging after this comment is addressed: #1896 (comment)
{ | ||
"extends": ["//"], | ||
"tasks": { | ||
"tsc": { | ||
"outputs": ["../../dist-types/plugins/analytics-provider-segment/**"] | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't use turbo here, you can just remove that config.
"@backstage/theme": "^0.6.0", | ||
"@material-ui/core": "^4.9.13", | ||
"@material-ui/icons": "^4.11.3", | ||
"@material-ui/lab": "4.0.0-alpha.61", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would surprise me if we need this dependency. But there was also in the old code base. We can remove them also in a follow-up PR!
importOrder: [ | ||
'^react(.*)$', | ||
'', | ||
'^@backstage/(.*)$', | ||
'', | ||
'<THIRD_PARTY_MODULES>', | ||
'', | ||
'^@backstage-community/(.*)$', | ||
'', | ||
'<BUILTIN_MODULES>', | ||
'', | ||
'^[.]', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
import { createDevApp } from '@backstage/dev-utils'; | ||
import React from 'react'; | ||
import { GoogleAnalytics } from '../src'; | ||
import { Playground } from './Playground'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -11,7 +11,7 @@ yarn.lock @backstage/community-plugins | |||
/workspaces/3scale @backstage/community-plugins-maintainers @04kash @AndrienkoAleksandr | |||
/workspaces/acr @backstage/community-plugins-maintainers @christoph-jerolimov @invincibleJai | |||
/workspaces/adr @backstage/community-plugins-maintainers @kuangp | |||
/workspaces/analytics @backstage/community-plugins-maintainers @jmezach | |||
/workspaces/analytics @backstage/community-plugins-maintainers @jmezach @schultzp2020 @christoph-jerolimov |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding @schultzp2020 and me, but are we hi-jacking another workspace here?
@jmezach, is it fine for you if we just take care of the extra modules here, or are you fine if we also approve code changes to your modules?
Or, @awanlin @BethGriggs @04kash, should we consider adding additional lines here just for the module(s) we added? It's this PR for Google Analytics and #1906 for Matomo.
I just want to be a kindful and transparent citizen of this repo. ☮️ ✌️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added this as a topic for the next Community SIG, but my thinking is to have paths to each plugin in the CODEOWNERS
file. @jmezach contributed the New Relic analytics plugin, the GA ones are from Spotify from what I can remember.
Hey, I just made a Pull Request!
The
analytics-provider-segment
plugin from the janus-idp/backstage-plugins repository was migrated to the community plugins. The migration was performed by following the manual migration steps outlined in the Community Plugins CONTRIBUTING guide✔️ Checklist
Signed-off-by
line in the message. (more info)