We should rename the accesstoken get to util accesstoken get for the command to be consistent with all other commands in the CLI.
Rationale:
At this moment, commands in the CLI are organized in such a way, that the first word depicts the name of the service on which the command operates, eg. aad, flow, outlook, etc. This naming convention is used for clarity but also implicitly for lazy loading commands. The accesstoken get command deviates from this naming as accesstoken is not a Microsoft 365 service.
Since it's a utility command, we should move it to util namespace which will allow us to introduce other helper command in the future in a meaningful and consistent way.
Renaming a command is a breaking change and we should do it in the next major version. For the time being, we can introduce an alias and communicate that the current name will be deprecated in the next version.
We should rename the
accesstoken gettoutil accesstoken getfor the command to be consistent with all other commands in the CLI.Rationale:
At this moment, commands in the CLI are organized in such a way, that the first word depicts the name of the service on which the command operates, eg.
aad,flow,outlook, etc. This naming convention is used for clarity but also implicitly for lazy loading commands. Theaccesstoken getcommand deviates from this naming asaccesstokenis not a Microsoft 365 service.Since it's a utility command, we should move it to
utilnamespace which will allow us to introduce other helper command in the future in a meaningful and consistent way.Renaming a command is a breaking change and we should do it in the next major version. For the time being, we can introduce an alias and communicate that the current name will be deprecated in the next version.