Skip to content
This repository has been archived by the owner on Jul 14, 2023. It is now read-only.

--debug Flag added swagger details in help. --debug Flag should not change behavior of code generation. #846

Open
KalpeshChavan12 opened this issue May 18, 2021 · 1 comment
Labels
priority_p1_important important but not blocking

Comments

@KalpeshChavan12
Copy link

Issue: --debug Flag added swagger details in help. --debug Flag should not change behavior of code generation.
--debug flag should display details log on console. It should change behavior of code generation.

E.g. command help after code generated using --debug flag

helps['maintenance applyupdate show'] = """
    type: command
    short-summary: "Track maintenance updates to resource"
    short-summary: "Track maintenance updates to resource Command group swagger name=ApplyUpdates, Command swagger \
name=Get."
    examples:
      - name: ApplyUpdates_Get
        text: |-

Example code generated with --debug and without --debug flag

Azure/azure-cli-extensions@2843d77

Recommendation: use separate flag to detail help(which include swagger details).

Code Reference to fix:

' Swagger name=' + methodParameterHandler.MethodParameter_CliKey;

@kairu-ms kairu-ms added the priority_p1_important important but not blocking label May 20, 2021
@kairu-ms
Copy link
Contributor

I think another way is writing the swagger details in code comments.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority_p1_important important but not blocking
Projects
None yet
Development

No branches or pull requests

2 participants