From 53d553428ffae65cf0cebaed3c96acb1ef18ece6 Mon Sep 17 00:00:00 2001 From: Feiyue Yu Date: Mon, 11 Jan 2021 15:23:27 +0800 Subject: [PATCH 1/3] {Doc} Track 2 Migration Guidance --- doc/track_2_migration_guidance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/track_2_migration_guidance.md b/doc/track_2_migration_guidance.md index b481e09bdc3..29da0f2b78a 100644 --- a/doc/track_2_migration_guidance.md +++ b/doc/track_2_migration_guidance.md @@ -24,7 +24,7 @@ Below is a list of typical issues. ### Long running operation function name change -Long running operations have changed their function names in Track 2 SDK. A `begin_` prefix is added. E.g. `create_or_update` becomes `begin_create_or_update`. `delete` becomes `begin_delete`. It is a naming convention in Track 2 SDK to indicate that an operation is a long running operation. +Long running operations have changed their function names in Track 2 SDK. A `begin_` prefix is added. E.g. `create_or_update` becomes `begin_create_or_update`. `delete` becomes `begin_delete`. It is a naming convention in Track 2 SDK to indicate that an operation is a long running operation. Test cases can uncover most instances. But if a command has no test, it will be missed. A rigorous method is going through all methods to see whether they are long running operations. ### Property name change From 41c64705701c49a3344c941f477192d25782e339 Mon Sep 17 00:00:00 2001 From: Feiyue Yu Date: Tue, 12 Jan 2021 11:08:12 +0800 Subject: [PATCH 2/3] Update doc/track_2_migration_guidance.md Co-authored-by: Jiashuo Li --- doc/track_2_migration_guidance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/track_2_migration_guidance.md b/doc/track_2_migration_guidance.md index 29da0f2b78a..a7ca48a3e38 100644 --- a/doc/track_2_migration_guidance.md +++ b/doc/track_2_migration_guidance.md @@ -24,7 +24,7 @@ Below is a list of typical issues. ### Long running operation function name change -Long running operations have changed their function names in Track 2 SDK. A `begin_` prefix is added. E.g. `create_or_update` becomes `begin_create_or_update`. `delete` becomes `begin_delete`. It is a naming convention in Track 2 SDK to indicate that an operation is a long running operation. Test cases can uncover most instances. But if a command has no test, it will be missed. A rigorous method is going through all methods to see whether they are long running operations. +Long running operations have changed their function names in Track 2 SDK. A `begin_` prefix is added. E.g. `create_or_update` becomes `begin_create_or_update`. `delete` becomes `begin_delete`. It is a naming convention in Track 2 SDK to indicate that an operation is a long running operation. Test cases can reveal most instances, but if a command has no test, it may be missed. A reliable approach is going through all methods to see whether they are long running operations. ### Property name change From 6c95b3c3ef95f26e8fda539b45991897628591c3 Mon Sep 17 00:00:00 2001 From: Feiyue Yu Date: Tue, 12 Jan 2021 11:11:38 +0800 Subject: [PATCH 3/3] Update doc/track_2_migration_guidance.md --- doc/track_2_migration_guidance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/track_2_migration_guidance.md b/doc/track_2_migration_guidance.md index a7ca48a3e38..0f7fd19c732 100644 --- a/doc/track_2_migration_guidance.md +++ b/doc/track_2_migration_guidance.md @@ -24,7 +24,7 @@ Below is a list of typical issues. ### Long running operation function name change -Long running operations have changed their function names in Track 2 SDK. A `begin_` prefix is added. E.g. `create_or_update` becomes `begin_create_or_update`. `delete` becomes `begin_delete`. It is a naming convention in Track 2 SDK to indicate that an operation is a long running operation. Test cases can reveal most instances, but if a command has no test, it may be missed. A reliable approach is going through all methods to see whether they are long running operations. +Long running operations have changed their function names in Track 2 SDK. A `begin_` prefix is added. For example, `create_or_update` becomes `begin_create_or_update`. `delete` becomes `begin_delete`. It is a naming convention in Track 2 SDK to indicate that an operation is a long running operation. Test cases can reveal most instances, but if a command has no test, it may be missed. A reliable approach is going through all methods to see whether they are long running operations. ### Property name change