* 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>
77 lines
2.6 KiB
Markdown
77 lines
2.6 KiB
Markdown
---
|
|
id: 587d7fb9367417b2b2512c12
|
|
title: Encadear auxiliares de consulta para restringir resultados de pesquisa
|
|
challengeType: 2
|
|
forumTopicId: 301533
|
|
dashedName: chain-search-query-helpers-to-narrow-search-results
|
|
---
|
|
|
|
# --description--
|
|
|
|
Se você não passar o callback como o último argumento para `Model.find()` (ou para outros métodos de pesquisa), a consulta não é executada. Você pode armazenar a consulta em uma variável para uso posterior. Esse tipo de objeto permite que você crie uma consulta usando a sintaxe de encadeamento. A pesquisa real do banco de dados é executada quando você finalmente encadear o método `.exec()`. Você sempre precisa passar seu callback para este último método. Existem muitos auxiliares de consulta. Aqui, usaremos os mais comuns.
|
|
|
|
# --instructions--
|
|
|
|
Modifique a função `queryChain` para que encontre pessoas que gostam do alimento especificado pela variável `foodToSearch`. Classifique-os por `name`, limite os resultados a dois documentos e oculte idade deles. Encadeie `.find()`, `.sort()`, `.limit()`, `.select()`e, então, `.exec()`. Passe a callback `done(err, data)` para `exec()`.
|
|
|
|
# --hints--
|
|
|
|
Você deve ter sucesso em encadear auxiliares de consulta
|
|
|
|
```js
|
|
(getUserInput) =>
|
|
$.ajax({
|
|
url: getUserInput('url') + '/_api/query-tools',
|
|
type: 'POST',
|
|
contentType: 'application/json',
|
|
data: JSON.stringify([
|
|
{ name: 'Pablo', age: 26, favoriteFoods: ['burrito', 'hot-dog'] },
|
|
{ name: 'Bob', age: 23, favoriteFoods: ['pizza', 'nachos'] },
|
|
{ name: 'Ashley', age: 32, favoriteFoods: ['steak', 'burrito'] },
|
|
{ name: 'Mario', age: 51, favoriteFoods: ['burrito', 'prosciutto'] }
|
|
])
|
|
}).then(
|
|
(data) => {
|
|
assert.isArray(data, 'the response should be an Array');
|
|
assert.equal(
|
|
data.length,
|
|
2,
|
|
'the data array length is not what expected'
|
|
);
|
|
assert.notProperty(
|
|
data[0],
|
|
'age',
|
|
'The returned first item has too many properties'
|
|
);
|
|
assert.equal(
|
|
data[0].name,
|
|
'Ashley',
|
|
'The returned first item name is not what expected'
|
|
);
|
|
assert.notProperty(
|
|
data[1],
|
|
'age',
|
|
'The returned second item has too many properties'
|
|
);
|
|
assert.equal(
|
|
data[1].name,
|
|
'Mario',
|
|
'The returned second item name is not what expected'
|
|
);
|
|
},
|
|
(xhr) => {
|
|
throw new Error(xhr.responseText);
|
|
}
|
|
);
|
|
```
|
|
|
|
# --solutions--
|
|
|
|
```js
|
|
/**
|
|
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.
|
|
*/
|
|
```
|