* chore: rename APIs and Microservices to include "Backend" (#42515) * fix typo * fix typo * undo change * Corrected grammar mistake Corrected a grammar mistake by removing a comma. * change APIs and Microservices cert title * update title * Change APIs and Microservices certi title * Update translations.json * update title * feat(curriculum): rename apis and microservices cert * rename folder structure * rename certificate * rename learn Markdown * apis-and-microservices -> back-end-development-and-apis * update backend meta * update i18n langs and cypress test Co-authored-by: Shaun Hamilton <shauhami020@gmail.com> * fix: add development to front-end libraries (#42512) * fix: added-the-word-Development-to-front-end-libraries * fix/added-the-word-Development-to-front-end-libraries * fix/added-word-development-to-front-end-libraries-in-other-related-files * fix/added-the-word-Development-to-front-end-and-all-related-files * fix/removed-typos-from-last-commit-in-index.md * fix/reverted-changes-that-i-made-to-dependecies * fix/removed xvfg * fix/reverted changes that i made to package.json * remove unwanted changes * front-end-development-libraries changes * rename backend certSlug and README * update i18n folder names and keys * test: add legacy path redirect tests This uses serve.json from the client-config repo, since we currently use that in production * fix: create public dir before moving serve.json * fix: add missing script * refactor: collect redirect tests * test: convert to cy.location for stricter tests * rename certificate folder to 00-certificates * change crowdin config to recognise new certificates location * allow translations to be used Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com> * add forwards slashes to path redirects * fix cypress path tests again * plese cypress * fix: test different challenge Okay so I literally have no idea why this one particular challenge fails in Cypress Firefox ONLY. Tom and I paired and spun a full build instance and confirmed in Firefox the page loads and redirects as expected. Changing to another bootstrap challenge passes Cypress firefox locally. Absolutely boggled by this. AAAAAAAAAAAAAAA * fix: separate the test Okay apparently the test does not work unless we separate it into a different `it` statement. >:( >:( >:( >:( Co-authored-by: Sujal Gupta <55016909+heysujal@users.noreply.github.com> Co-authored-by: Noor Fakhry <65724923+NoorFakhry@users.noreply.github.com> Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com> Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
2.5 KiB
2.5 KiB
id, title, challengeType, forumTopicId, dashedName
id | title | challengeType | forumTopicId | dashedName |
---|---|---|---|---|
587d7fb2367417b2b2512bf6 | 從客戶端獲取輸入的查詢參數 | 2 | 301512 | get-query-parameter-input-from-the-client |
--description--
從客戶端獲取輸入的另一種常見方式是使用查詢字符串對路由路徑中的數據進行編碼, 查詢字符串使用標記(?)分隔,並且包含鍵值對 field=value, 每對鍵值使用連字號(&)分隔。 Express 能夠從查詢字符串中解析這些數據,並且把它放到 req.query
對象中。 有些字符(如百分號(%))不能在出現在 URL 中,它們在發送前必須以不同的格式進行編碼。 如果使用 JavaScript 的 API,可以用特定的方法來編碼/解碼這些字符。
路由地址:'/library'
實際請求 URL:'/library?userId=546&bookId=6754'
req.query:{userId: '546', bookId: '6754'}
--instructions--
構建一個 API 接口,使用路由掛載在 GET /name
上, 使用一個 JSON 文件來響應,它的結構是這樣的:{ name: 'firstname lastname'}
, 名字(first name)和姓氏(last name)參數應該編碼在查詢參數中,例如:?first=firstname&last=lastname
。
注意: 在後面的練習中,我們將向相同的路由路徑 /name
發送 POST 請求來接收數據。 如果願意,可以使用app.route(path).get(handler).post(handler)
這中寫法, 這種語法允許在同一路徑路由上鍊式調用不同的請求方法, 可以節省一點打字時間,也可以讓代碼看起來更清晰。
--hints--
測試 1:你的 API 應該用正確的名字來響應
(getUserInput) =>
$.get(getUserInput('url') + '/name?first=Mick&last=Jagger').then(
(data) => {
assert.equal(
data.name,
'Mick Jagger',
'Test 1: "GET /name" route does not behave as expected'
);
},
(xhr) => {
throw new Error(xhr.responseText);
}
);
測試 2:你的 API 應該用正確的名字來響應
(getUserInput) =>
$.get(getUserInput('url') + '/name?last=Richards&first=Keith').then(
(data) => {
assert.equal(
data.name,
'Keith Richards',
'Test 2: "GET /name" route does not behave as expected'
);
},
(xhr) => {
throw new Error(xhr.responseText);
}
);
--solutions--
/**
Backend challenges don't need solutions,
because they would need to be tested against a full working project.
Please check our contributing guidelines to learn more.
*/