Skip to content
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

Support "Local Deploy" in the VSCode Deployment Pane #14234

Merged
merged 2 commits into from
Jun 10, 2024
Merged

Conversation

anthony-c-martin
Copy link
Member

@anthony-c-martin anthony-c-martin commented Jun 4, 2024

Screen.Recording.2024-01-08.at.11.40.02.AM.mov
Microsoft Reviewers: Open in CodeFlow

@anthony-c-martin anthony-c-martin force-pushed the localdeploy branch 2 times, most recently from a50bb9b to b08a37a Compare June 4, 2024 15:57
Copy link
Contributor

github-actions bot commented Jun 4, 2024

Test this change out locally with the following install scripts (Action run 9452446344)

VSCode
  • Mac/Linux
    bash <(curl -Ls https://aka.ms/bicep/nightly-vsix.sh) --run-id 9452446344
  • Windows
    iex "& { $(irm https://aka.ms/bicep/nightly-vsix.ps1) } -RunId 9452446344"
Azure CLI
  • Mac/Linux
    bash <(curl -Ls https://aka.ms/bicep/nightly-cli.sh) --run-id 9452446344
  • Windows
    iex "& { $(irm https://aka.ms/bicep/nightly-cli.ps1) } -RunId 9452446344"

@anthony-c-martin anthony-c-martin force-pushed the localdeploy branch 10 times, most recently from 33296a1 to d75d073 Compare June 7, 2024 15:49
Copy link
Contributor

github-actions bot commented Jun 7, 2024

Dotnet Test Results

    72 files   -     36      72 suites   - 36   22m 57s ⏱️ - 9m 10s
10 878 tests  -     20  10 877 ✅  -     20  1 💤 ±0  0 ❌ ±0 
25 652 runs   - 12 822  25 650 ✅  - 12 821  2 💤  - 1  0 ❌ ±0 

Results for commit 07bf808. ± Comparison against base commit 91b64d4.

♻️ This comment has been updated with latest results.

@anthony-c-martin anthony-c-martin changed the title [WIP] Local Bicep prototype Support "Local Deploy" in the VSCode Deployment Pane Jun 7, 2024
@anthony-c-martin anthony-c-martin marked this pull request as ready for review June 7, 2024 19:23
);
}

export function getLocalDeployOutputs(result: LocalDeployResponse) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be worth changing these functions into components as a best practice to avoid unnecessary rendering.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pushed a change - is that what you were thinking?

Copy link
Contributor

@shenglol shenglol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@alex-frankel
Copy link
Collaborator

alex-frankel commented Jun 10, 2024

So excited to use this one personally :) What is the procedure (as a user) going to be for enabling this?

@anthony-c-martin anthony-c-martin enabled auto-merge (squash) June 10, 2024 16:51
@anthony-c-martin anthony-c-martin merged commit 67b96eb into main Jun 10, 2024
45 of 46 checks passed
@anthony-c-martin anthony-c-martin deleted the localdeploy branch June 10, 2024 16:56
}


export const LocalDeployOutputs: FC<{ result: LocalDeployResponse }> = ({ result }) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using FC was not recommended because it implicitly includes the children prop type, but it seems React 18 fixed the problem, so we should be fine: https://www.totaltypescript.com/you-can-stop-hating-react-fc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants