You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- content: "How do you customize the route endpoint for a function in an Azure Functions project?"
18
-
choices:
19
-
- content: "Rename *index.js* file to the name of the endpoint you desire."
20
-
isCorrect: false
21
-
explanation: "Incorrect. The name of the API endpoint isn't related to the filename of the function."
22
-
- content: "Inside the function's *function.json* file, add a `route` property and set it to your desired endpoint path name."
23
-
isCorrect: true
24
-
explanation: "Correct. The route endpoint has the same name as the folder that contains the function, by convention. You can customize the path to the endpoint using the `route` property in the *function.json* file"
25
-
- content: "Endpoint paths can't be customized."
26
-
isCorrect: false
27
-
explanation: "The route endpoint has the same name as the folder that contains the function, by convention. However, they can be customized in the *function.json* file."
28
-
- content: "Name the function's symbol in the code to your desired name."
29
-
isCorrect: false
30
-
explanation: "Incorrect. The name of the API endpoint isn't related to the name of any variable in the code."
31
-
- content: "How do you deploy changes to your web app without affecting your production web site?"
32
-
choices:
33
-
- content: "Go to the production URL of your app."
34
-
isCorrect: false
35
-
explanation: "Incorrect. The production URL of your Azure Static Web Apps instance displays your web app, not your build progress."
36
-
- content: "Go to your resource in the Azure portal and view the configuration."
37
-
isCorrect: false
38
-
explanation: "Incorrect. The configuration for your resource in the Azure portal allows you to view or modify the configuration of the resource. It doesn't show the progress of your build and redeployment of your web app."
39
-
- content: "Push your commits to your watched branched of your git repository."
40
-
isCorrect: false
41
-
explanation: "Incorrect. Pushing your commits doesn't show your progress, but it triggers a GitHub Actions workflow."
42
-
- content: "Create a preview URL by creating a pull request against the branch that your GitHub Action is watching."
43
-
isCorrect: true
44
-
explanation: "Correct. Sometimes you want to see your changes in a staging site before publishing to the live web site. Azure Static Web Apps lets you see preview your changes through preview URLs. "
45
-
- content: "How do you tell Azure Static Web Apps that you changed where your API is located?"
46
-
choices:
47
-
- content: "In the package.json file."
48
-
isCorrect: false
49
-
explanation: "Incorrect. The configuration for your app's locations are defined in the GitHub Actions workflow file."
50
-
- content: "Add an entry in *staticwebapp.config.json* for the location."
51
-
isCorrect: false
52
-
explanation: "Incorrect. The *staticwebapp.config.json* file is where you define routing rules, not the location of your API."
53
-
- content: "Azure Static Web Apps automatically knows where your code and API are located, without any configuration."
54
-
isCorrect: false
55
-
explanation: "Incorrect. You can configure the location of your code, artifacts, and API in the GitHub Actions workflow file. If you don't specify these locations, default values are used."
56
-
- content: "In the GitHub Actions workflow file, located in your *.github/workflows* folder."
57
-
isCorrect: true
58
-
explanation: "Correct. You can configure the locations for your app code, app artifact, and API in the GitHub Actions workflow file. This file is located in your *.github/workflows* folder."
- content: "How do you customize the route endpoint for a function in an Azure Functions project?"
18
+
choices:
19
+
- content: "Rename *index.js* file to the name of the endpoint you desire."
20
+
isCorrect: false
21
+
explanation: "Incorrect. The name of the API endpoint isn't related to the filename of the function."
22
+
- content: "Inside the function's *function.json* file, add a `route` property and set it to your desired endpoint path name."
23
+
isCorrect: true
24
+
explanation: "Correct. The route endpoint has the same name as the folder that contains the function, by convention. You can customize the path to the endpoint using the `route` property in the *function.json* file"
25
+
- content: "Endpoint paths can't be customized."
26
+
isCorrect: false
27
+
explanation: "The route endpoint has the same name as the folder that contains the function, by convention. However, they can be customized in the *function.json* file."
28
+
- content: "Name the function's symbol in the code to your desired name."
29
+
isCorrect: false
30
+
explanation: "Incorrect. The name of the API endpoint isn't related to the name of any variable in the code."
31
+
- content: "How do you deploy changes to your web app without affecting your production web site?"
32
+
choices:
33
+
- content: "Go to the production URL of your app."
34
+
isCorrect: false
35
+
explanation: "Incorrect. The production URL of your Azure Static Web Apps instance displays your web app, not your build progress."
36
+
- content: "Go to your resource in the Azure portal and view the configuration."
37
+
isCorrect: false
38
+
explanation: "Incorrect. The configuration for your resource in the Azure portal allows you to view or modify the configuration of the resource. It doesn't show the progress of your build and redeployment of your web app."
39
+
- content: "Push your commits to your watched branched of your git repository."
40
+
isCorrect: false
41
+
explanation: "Incorrect. Pushing your commits doesn't show your progress, but it triggers a GitHub Actions workflow."
42
+
- content: "Create a preview URL by creating a pull request against the branch that your GitHub Action is watching."
43
+
isCorrect: true
44
+
explanation: "Correct. Sometimes you want to see your changes in a staging site before publishing to the live web site. Azure Static Web Apps lets you see preview your changes through preview URLs. "
45
+
- content: "How do you tell Azure Static Web Apps that you changed where your API is located?"
46
+
choices:
47
+
- content: "In the package.json file."
48
+
isCorrect: false
49
+
explanation: "Incorrect. The locations of your apps are defined and configured in the GitHub Actions workflow file."
50
+
- content: "Add an entry in *staticwebapp.config.json* for the location."
51
+
isCorrect: false
52
+
explanation: "Incorrect. The *staticwebapp.config.json* file is where you define routing rules, not the location of your API."
53
+
- content: "Azure Static Web Apps automatically knows where your code and API are located, without any configuration."
54
+
isCorrect: false
55
+
explanation: "Incorrect. You can configure the location of your code, artifacts, and API in the GitHub Actions workflow file. If you don't specify these locations, default values are used."
56
+
- content: "In the GitHub Actions workflow file, located in your *.github/workflows* folder."
57
+
isCorrect: true
58
+
explanation: "Correct. You can configure the locations for your app code, app artifact, and API in the GitHub Actions workflow file. This file is located in your *.github/workflows* folder."
Copy file name to clipboardExpand all lines: learn-pr/azure/publish-static-web-app-api-preview-url/includes/2-exercise-get-started.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ This module uses resources made available to you via the sandbox, which provides
6
6
7
7
To begin, create a repository by using a GitHub template. A series of repository templates are available, which contain a starter app implemented in various front end frameworks.
8
8
9
-
1. Go to the GitHub [create from template page](https://github.com/login?return_to=/MicrosoftDocs/mslearn-staticwebapp-api/generate?azure-portal=true) to open the template repository.
9
+
1. Go to the GitHub [create from template page](https://github.com/login?return_to=/MicrosoftDocs/mslearn-staticwebapp-api/generate?azure-portal=true).
10
10
11
-
1. If prompted for _Owner_, select one of your GitHub accounts.
11
+
1. If prompted for *Owner*, select one of your GitHub accounts.
12
12
13
-
1. For _repository name_, enter **my-static-web-app-and-api**.
13
+
1. For *Repository name*, enter **my-static-web-app-and-api**.
14
14
15
-
1. Select **Create repository from template**.
15
+
1. Select **Create repository**.
16
16
17
17
As you create the project from a template, GitHub builds your repository in the background.
18
18
@@ -29,11 +29,11 @@ Now you have a GitHub repository named **my-static-web-app-and-api** in your Git
29
29
Make sure to replace `<YOUR_GITHUB_USERNAME>` with your GitHub username.
> If you have trouble copying into the command prompt terminal, right-click the icon in the title bar, and in the **Properties** tab, ensure that **Use Ctrl+Shift+C/V as Copy/Paste** is checked.
36
+
> If you have trouble copying into the command prompt terminal, right-click the icon in the title bar, and in the **Properties** tab, ensure **Use Ctrl+Shift+C/V as Copy/Paste** is checked.
37
37
38
38
1. Change to the directory for the source code you cloned.
39
39
@@ -291,7 +291,7 @@ Current Azure and GitHub authenticated sessions are required to create a static
291
291
::: zone-end
292
292
293
293
> [!NOTE]
294
-
> This repository differs from other projects you may have used in the past. This project contains four different apps in four different folders. Each folder contains an app created in a different JavaScript framework. Typically, you'd have only one app in the root of your repository and thus the default `/` for the app path location. This is a great example of how Azure Static Web Apps lets you configure locations in the first place - you have full control over how the app is built.
294
+
> This repository differs from other projects you might be used to. This project contains four different apps in four different folders. Each folder contains an app created in a different JavaScript framework. Typically, you'd have only one app in the root of your repository and thus the default `/` for the app path location. This structure is a great example of how Azure Static Web Apps lets you configure locations in the first place - you have full control over how the app is built.
295
295
296
296
3. Once the app is created, a confirmation notification is shown in Visual Studio Code.
297
297
@@ -316,7 +316,7 @@ Current Azure and GitHub authenticated sessions are required to create a static
316
316
Congratulations! Your app is deployed to Azure Static Web Apps!
317
317
318
318
> [!NOTE]
319
-
> Don't worry if you see a web page that states the app hasn't been built and deployed yet. Try refreshing the browser in a minute. The GitHub Action service runs automatically when the Azure Static Web App is created. So if you see the splash page, the app is still being deployed.
319
+
> Don't worry if you see a web page that states the app isn't built and deployed yet. Try refreshing the browser in a minute. The GitHub Action service runs automatically when the Azure Static Web App is created. So if you see the splash page, the app is still being deployed.
Copy file name to clipboardExpand all lines: learn-pr/azure/publish-static-web-app-api-preview-url/includes/3-build-api.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ You don't need a full server for your front-end or back-end to configure and mai
10
10
11
11
Azure Functions serves your route endpoints, doesn't require a full back-end server to configure or maintain, and provides automatic scaling out and scaling in based on demand. These features make Azure Functions a great API partner for your shopping list web app that serves static assets.
12
12
13
-
Azure Static Web Apps generates a unique URL for your site, which you can find on the *Overview* tab in the portal. The API is available through this same URL by appending */api* to the URL.
13
+
Azure Static Web Apps generates a unique URL for your site, which you can find on the **Overview** tab in the portal. The API is available through this same URL by appending `/api` to the URL.
14
14
15
15
### Your shopping list API
16
16
@@ -25,7 +25,7 @@ Here are the four endpoints that you create:
25
25
| PUT |`products/:id`|`api/products/:id`|
26
26
| DELETE |`products/:id`|`api/products/:id`|
27
27
28
-
Notice that your HTTP GET requests route to `api/products`. The *api* prefix is reserved for your API endpoints in the app. You can define any other routes to fit the needs of your site, but *api* always points to the Azure Functions app.
28
+
Notice that your HTTP GET requests route to `api/products`. The `api` prefix is reserved for your API endpoints in the app. You can define any other routes to fit the needs of your site, but `api` always points to the Azure Functions app.
0 commit comments