-
Notifications
You must be signed in to change notification settings - Fork 139
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
Report business platform ID instead of partner ID when relevant #5120
base: main
Are you sure you want to change the base?
Conversation
Coverage report
Show files with reduced coverage 🔻
Test suite run success1994 tests passing in 900 suites. Report generated by 🧪jest coverage report action from 39bfdc6 |
6a6802a
to
a152cf6
Compare
We detected some changes at packages/*/src and there are no updates in the .changeset. |
a152cf6
to
e51c6c6
Compare
c2c710a
to
39bfdc6
Compare
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Differences in type declarationsWe detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:
New type declarationsWe found no new type declarations in this PR Existing type declarationspackages/cli-kit/dist/public/node/monorail.d.ts@@ -16,6 +16,7 @@ export interface Schemas {
env_plugin_installed_all?: Optional<string>;
};
public: {
+ business_platform_id?: Optional<number>;
partner_id?: Optional<number>;
command: string;
project_type?: Optional<string>;
packages/cli-kit/dist/public/node/plugins.d.ts@@ -16,7 +16,7 @@ import { Config, Interfaces } from '@oclif/core';
* @returns A dictionary of plug-in names to the response from the hook.
*/
export declare function fanoutHooks<TPluginMap extends HookReturnsPerPlugin, TEvent extends string & keyof TPluginMap>(config: Interfaces.Config, event: TEvent, options: TPluginMap[typeof event]['options'], timeout?: number): Promise<Partial<TPluginMap[typeof event]['pluginReturns']>>;
-type AppSpecificMonorailFields = PickByPrefix<MonorailEventPublic, 'app_', 'project_type' | 'api_key' | 'partner_id'> & PickByPrefix<MonorailEventPublic, 'cmd_extensions_'> & PickByPrefix<MonorailEventPublic, 'cmd_scaffold_'>;
+type AppSpecificMonorailFields = PickByPrefix<MonorailEventPublic, 'app_', 'project_type' | 'api_key' | 'partner_id' | 'business_platform_id'> & PickByPrefix<MonorailEventPublic, 'cmd_extensions_'> & PickByPrefix<MonorailEventPublic, 'cmd_scaffold_'>;
type AppSpecificSensitiveMonorailFields = PickByPrefix<MonorailEventSensitive, 'app_'>;
export interface HookReturnsPerPlugin extends HookReturnPerTunnelPlugin {
public_command_metadata: {
|
WHY are these changes introduced?
To ensure we are tracking BP orgs and Partner orgs separately.
WHAT is this pull request doing?
Introduces a new
business_platform_id
field in analytics tracking to differentiate between Partner and Business Platform organizations. When working with a Business Platform organization, the system now logs thebusiness_platform_id
instead of thepartner_id
.How to test your changes?
Check that when working with App Management, the correct field is reported in analytics (see verbose logs)
Measuring impact
How do we know this change was effective? Please choose one:
Checklist