hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
d9b3293dc52e7afdac89373dc0d2e1e74a2fdcf5 | 20,354 | md | Markdown | articles/active-directory/hybrid/how-to-connect-fed-group-claims.md | jobailla/azure-docs.fr-fr | 8c7734bc0d6ffaa8f9f2a39982929b8d9fc8235e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/hybrid/how-to-connect-fed-group-claims.md | jobailla/azure-docs.fr-fr | 8c7734bc0d6ffaa8f9f2a39982929b8d9fc8235e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/hybrid/how-to-connect-fed-group-claims.md | jobailla/azure-docs.fr-fr | 8c7734bc0d6ffaa8f9f2a39982929b8d9fc8235e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Configurer des revendications de groupe pour des applications avec Azure Active Directory | Microsoft Docs
description: Informations sur la façon de configurer des revendications de groupe utilisables avec Azure AD.
services: active-directory
documentationcenter: ''
ms.reviewer: paulgarn
manager: daveba
ms.subservice: hybrid
ms.service: active-directory
ms.workload: identity
ms.topic: how-to
ms.date: 02/27/2019
ms.author: billmath
author: billmath
ms.openlocfilehash: ce438ad0725aff677f897a635a0cd32d92bbbdbe
ms.sourcegitcommit: 32c521a2ef396d121e71ba682e098092ac673b30
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 09/25/2020
ms.locfileid: "91265467"
---
# <a name="configure-group-claims-for-applications-with-azure-active-directory"></a>Configurer des revendications de groupe pour des applications avec Azure Active Directory
Azure Active Directory peut fournir une information d’appartenance de groupe d’utilisateurs dans des jetons utilisables au sein d’applications. Deux modèles principaux sont pris en charge :
- Groupes identifiés par leur attribut d’identificateur d’objet Azure Active Directory
- Groupes identifiés par les attributs sAMAccountName ou GroupSID pour les groupes et utilisateurs synchronisés Active Directory (AD)
> [!IMPORTANT]
> Il existe plusieurs mises en garde concernant cette fonctionnalité :
>
>- La prise en charge de l’utilisation d’attributs sAMAccountName et d’identificateur de sécurité synchronisés localement est conçue pour permettre le déplacement d’applications existantes à partir d’AD FS et d’autres fournisseurs d’identité. Les groupes gérés dans Azure AD ne contiennent pas les attributs nécessaires pour émettre ces revendications.
>- Dans les grandes entreprises, le nombre de groupes dont un utilisateur est un membre peut dépasser la limite qu’Azure Active Directory ajoute à un jeton. 150 groupes pour un jeton SAML, et 200 pour un jeton JWT. Cela peut entraîner des résultats imprévisibles. Si vos utilisateurs ont un grand nombre d’appartenances à des groupes, nous vous recommandons d’utiliser l’option permettant de limiter les groupes émis dans les revendications aux groupes appropriés pour l’application.
>- Pour un nouveau développement d’application, dans les cas où l’application peut être configurée pour celui-ci, et où une prise en charge de groupe imbriqué n’est pas obligatoire, il est recommandé que l’autorisation dans l’application soit basée sur les rôles d’application plutôt que sur des groupes. Cela a pour effet de limiter la quantité d’informations qui doivent figurer dans le jeton, de sécuriser davantage et de séparer l’affectation d’utilisateurs de la configuration de l’application.
## <a name="group-claims-for-applications-migrating-from-ad-fs-and-other-identity-providers"></a>Revendications de groupe pour les applications migrant à partir d’AD FS et d’autres fournisseurs d’identité
De nombreuses applications configurées pour s’authentifier auprès d’AD FS s’appuient sur des informations d’appartenance de groupe sous la forme d’attributs de groupe Windows Active Directory. Ces attributs sont le groupe sAMAccountName qui peut être qualifié par un nom de domaine ou l’identificateur de sécurité du groupe Windows (GroupSID). Lorsque l’application est fédérée avec AD FS, AD FS utilise la fonction de TokenGroups pour récupérer les appartenances de groupe pour l’utilisateur.
Une application qui a été déplacée d’AD FS a besoin de revendications au même format. Des revendications de groupe et de rôle peuvent être émises à partir d’Azure Active Directory, qui contiennent le domaine qualifié sAMAccountName ou GroupSID synchronisé à partir d’Active Directory au lieu de l’attribut objectID Azure Active Directory du groupe.
Les formats pris en charge pour les revendications de groupe sont les suivants :
- **ObjectId de groupe Azure Active Directory** (disponible pour tous les groupes)
- **sAMAccountName** (disponible pour les groupes synchronisés à partir d’Active Directory)
- **NetbiosDomain\sAMAccountName** (disponible pour les groupes synchronisés à partir d’Active Directory)
- **DNSDomainName\sAMAccountName** (disponible pour les groupes synchronisés à partir d’Active Directory)
- **Identificateur de sécurité de groupe local** (disponible pour les groupes synchronisés à partir d’Active Directory)
> [!NOTE]
> Les attributs sAMAccountName et de SID de groupe local sont disponibles uniquement sur des objets de groupe synchronisés à partir d’Active Directory. Ils ne sont pas disponibles sur des groupes créés dans Azure Active Directory ou Office 365. Les applications configurées dans Azure Active Directory pour obtenir des attributs de groupe local synchronisés obtiennent ceux-ci uniquement pour des groupes synchronisés.
## <a name="options-for-applications-to-consume-group-information"></a>Options pour l’utilisation d’informations de groupe par les applications
Les applications peuvent appeler le point de terminaison de groupes MS Graph pour obtenir des informations de groupe pour l’utilisateur authentifié. Cet appel garantit que tous les groupes dont un utilisateur est membre sont disponibles même s’il existe un grand nombre de groupes impliqués. L’énumération de groupes est alors indépendante des limitations de taille de jeton.
Toutefois, si une application existante attend de commencer les informations de groupe via des revendications, Azure Active Directory peut être configuré avec un certain nombre de formats de revendications différents. Considérez les options suivantes :
- Lors de l’utilisation de l’appartenance de groupe à des fins d’autorisation dans l’application, il est préférable d’utiliser l’attribut ObjectID du groupe. L’attribut ObjectID du groupe est immuable et unique dans Azure Active Directory et disponible pour tous les groupes.
- Si vous utilisez l’attribut sAMAccountName du groupe local pour l’autorisation, utilisez les noms de domaines complets afin de réduire la probabilité de situations de conflits de noms. L’attribut sAMAccountName peut être unique au sein d’un domaine Active Directory mais, si plusieurs domaines Active Directory sont synchronisés avec un locataire Azure Active Directory, il est possible que plusieurs groupes aient le même nom.
- Envisagez d’utiliser des [rôles d’application](../../active-directory/develop/howto-add-app-roles-in-azure-ad-apps.md) pour fournir une couche d’indirection entre l’appartenance de groupe et l’application. L’application prend alors des décisions d’autorisation interne basées sur les revendications de rôle dans le jeton.
- Si l’application est configurée pour obtenir des attributs de groupe qui ont été synchronisés à partir d’Active Directory et qu’un groupe ne contient pas ces attributs, celui-ci n’est pas inclus dans les revendications.
- Les revendications de groupe dans les jetons incluent des groupes imbriqués, sauf lors de l’utilisation de l’option permettant de restreindre les revendications de groupe aux groupes affectés à l’application. Si un utilisateur est membre du GroupeB et que celui-ci est membre de GroupeA, les revendications de groupe pour l’utilisateur contiennent le GroupeA et le GroupeB. Quand les utilisateurs d’une organisation disposent d’un nombre important d’appartenances de groupe, le nombre de groupes listés dans le jeton peut faire augmenter la taille du jeton. Azure Active Directory limite le nombre de groupes qu’il émet dans un jeton à 150 pour les assertions SAML, et à 200 pour JWT. Si un utilisateur est membre d’un plus grand nombre de groupes, les groupes sont omis et un lien vers le point de terminaison Graph est inclus à la place, pour obtenir les informations des groupes.
## <a name="prerequisites-for-using-group-attributes-synchronized-from-active-directory"></a>Conditions préalables à l’utilisation d’attributs de groupe synchronisés à partir d’Active Directory
Les revendications d’appartenance de groupe peuvent être émises dans les jetons pour n’importe quel groupe si vous utilisez le format ObjectId. Pour utiliser des revendications de groupe dans des formats autres que l’attribut ObjectId de groupe, les groupes doivent être synchronisés à partir d’Active Directory à l’aide d’Azure AD Connect.
Il existe deux étapes pour configurer Azure Active Directory afin qu’il émette des noms de groupe pour les groupes Active Directory.
1. **Synchronisation des noms de groupe à partir d’Active Directory** Avant qu’Azure Active Directory puisse émettre les noms de groupes ou un identificateur de sécurité (SID) de groupe local dans des revendications de groupe ou de rôle, les attributs requis doivent être synchronisés à partir d’Active Directory. Vous devez exécuter Azure AD Connect version 1.2.70 ou ultérieure. Les version d’Azure AD Connect antérieures à la version 1.2.70 synchronisent les objets de groupe à partir d’Active Directory, mais n’incluent pas les attributs de nom de groupe requis. Effectuez une mise à niveau vers la version actuelle.
2. **Configuration de l’inscription d’application dans Azure Active Directory afin d’inclure les revendications de groupe dans les jetons** Les revendications de groupe peuvent être configurées dans la section Applications d’entreprise du portail ou à l’aide du manifeste de l’application dans la section Inscriptions d’applications. Pour configurer les revendications de groupe dans le manifeste de l’application, voir « Configuration de l’inscription d’application Azure Active Directory pour les attributs de groupe » ci-dessous.
## <a name="add-group-claims-to-tokens-for-saml-applications-using-sso-configuration"></a>Ajouter des revendications de groupe aux jetons pour les applications SAML en configurant l’authentification unique
Pour configurer les revendications de groupe pour une application SAML de galerie ou hors galerie, ouvrez **Applications d’entreprise**, cliquez sur l’application dans la liste, sélectionnez **Configuration de l’authentification unique**, puis sélectionnez **Attributs et revendications de l’utilisateur**.
Cliquez sur **Ajouter une revendication de groupe**.
Utilisez les cases d’option pour sélectionner les groupes à inclure dans le jeton
| Sélection | Description |
|----------|-------------|
| **Tous les groupes** | Émet des groupes de sécurité, ainsi que des rôles et des listes de distribution. |
| **Groupes de sécurité** | Émet les groupes de sécurité dont l’utilisateur est membre dans la revendication de groupe |
| **Rôles d’annuaire** | Si l’utilisateur se voit affecter des rôles d’annuaire, ceux-ci sont émis en tant que revendication « wids » (aucune revendication de groupe n’est émise) |
| **Groupes affectés à l’application** | Émet uniquement les groupes qui sont explicitement affectés à l’application et dont l’utilisateur est membre |
Par exemple, pour émettre tous les groupes de sécurité dont l’utilisateur est membre, sélectionnez Groupes de sécurité
Pour émettre des groupes à l’aide d’attributs Active Directory synchronisés à partir d’Active Directory au lieu d’ObjectID Azure AD, sélectionnez le format requis dans la liste déroulante. Seuls les groupes synchronisés à partir d’Active Directory sont inclus dans les revendications.
Pour émettre uniquement les groupes attribués à l’application, sélectionnez **Groupes attribués à l’application**
Les groupes attribués à l’application sont inclus dans le jeton. Les autres groupes dont l’utilisateur est membre sont omis. Avec cette option, les groupes imbriqués ne sont pas inclus et l’utilisateur doit être un membre direct du groupe attribué à l’application.
Pour changer les groupes attribués à l’application, sélectionnez l’application dans la liste **Applications d’entreprise** puis cliquez sur **Utilisateurs et groupes** dans le menu de navigation de gauche de l’application.
Pour plus d’informations sur la gestion de l’attribution de groupe aux applications, consultez le document [Attribuer un utilisateur ou un groupe à des applications](../../active-directory/manage-apps/assign-user-or-group-access-portal.md).
### <a name="advanced-options"></a>Options avancées
La manière sont les revendications de groupe sont émises peut être modifiée par les paramètres disponibles sous Options avancées
Personnaliser le nom de la revendication de groupe : Si cette option est sélectionnée, un type de revendication différent peut être spécifié pour les revendications de groupe. Entrez le type de revendication dans le champ Nom, et l’espace de noms facultatif pour la revendication dans le champ Espace de noms.
Certaines applications requièrent que les informations d’appartenance de groupe apparaissent dans la revendication « rôle ». Vous pouvez éventuellement émettre les groupes de l’utilisateur en tant que rôles en cochant la case « Émettre les groupes en tant que revendications de rôle ».
> [!NOTE]
> Si l’option pour émettre des données de groupe en tant que rôles est utilisée, seuls les groupes s’affichent dans la revendication de rôle. Les rôles d’application auxquels l’utilisateur est affecté n’apparaissent pas dans la revendication de rôle.
### <a name="edit-the-group-claims-configuration"></a>Modifier la configuration des revendications de groupe
Une fois qu’une configuration de revendication de groupe a été ajoutée à la configuration Attributs et revendications de l’utilisateur, l’option permettant d’ajouter une revendication de groupe est grisée. Pour changer la configuration de revendication de groupe, cliquez sur la revendication de groupe dans la liste **Revendications supplémentaires**.
## <a name="configure-the-azure-ad-application-registration-for-group-attributes"></a>Configurer l’inscription d’application Azure AD pour les attributs de groupe
Les revendications de groupe peuvent également être configurées dans la section [Revendications facultatives](../../active-directory/develop/active-directory-optional-claims.md) du [manifeste de l’application](../../active-directory/develop/reference-app-manifest.md).
1. Dans le portail -> Azure Active Directory -> Inscriptions d’applications, sélectionnez Application -> Manifeste
2. Activer les revendications d’appartenance de groupe en modifiant la revendication groupMembershipClaim
Les valeurs autorisées sont :
| Sélection | Description |
|----------|-------------|
| **"All"** | Émet des groupes de sécurité, ainsi que des rôles et des listes de distribution |
| **"SecurityGroup"** | Émet les groupes de sécurité dont l’utilisateur est membre dans la revendication de groupe |
| **"DirectoryRole"** | Si l’utilisateur se voit affecter des rôles d’annuaire, ceux-ci sont émis en tant que revendication « wids » (aucune revendication de groupe n’est émise) |
| **"ApplicationGroup"** | Émet uniquement les groupes qui sont explicitement affectés à l’application et dont l’utilisateur est membre |
Par exemple :
```json
"groupMembershipClaims": "SecurityGroup"
```
Par défaut, les ObjectId de groupe sont émis dans la valeur de revendication de groupe. Pour modifier la valeur de revendication afin qu’elle contienne des attributs de groupe local, ou pour modifier le type de revendication en rôle, utilisez une configuration OptionalClaims comme suit :
3. Définissez des revendications facultatives de configuration de nom de groupe.
Si vous souhaitez que les groupes dans le jeton contiennent les attributs de groupe AD local, spécifiez la revendication facultative de type de jeton à laquelle appliquer la configuration dans la section des revendications facultatives. Plusieurs types de jetons peuvent être répertoriés :
- idToken pour le jeton d’ID d’OIDC ;
- accessToken pour le jeton d’accès OAuth/OIDC ;
- Saml2Token pour les jetons SAML.
> [!NOTE]
> Le type de jeton Saml2Token s’applique aux jetons de format SAML1.1 et SAML2.0
Pour chaque type de jeton pertinent, modifiez la revendication de groupe pour utiliser la section OptionalClaims dans le manifeste. Le schéma d’OptionalClaims est le suivant :
```json
{
"name": "groups",
"source": null,
"essential": false,
"additionalProperties": []
}
```
| Schéma de revendications facultatives | Valeur |
|----------|-------------|
| **name:** | Doit être « groupes » |
| **source:** | Non utilisé. Omettez ou spécifiez la valeur null |
| **essential:** | Non utilisé. Omettez ou spécifiez la valeur false |
| **additionalProperties:** | Liste de propriétés supplémentaires. Les options valides sont « sam_account_name », « dns_domain_and_sam_account_name », « netbios_domain_and_sam_account_name » et « emit_as_roles » |
Dans additionalProperties une seule des options « sam_account_name », « dns_domain_and_sam_account_name » ou « netbios_domain_and_sam_account_name » est requise. Si plusieurs options sont présentes, la première est utilisée et les autres ignorées.
Certaines applications requièrent des informations de groupe sur l’utilisateur dans la revendication de rôle. Pour modifier le type de revendication de revendication de groupe en revendication de rôle, ajoutez « emit_as_roles » aux propriétés supplémentaires. Les valeurs de groupe sont émises dans la revendication de rôle.
> [!NOTE]
> Si l’option « emit_as_roles » est utilisée, les rôles d’application configurés auxquels l’utilisateur est affecté n’apparaissent pas dans la revendication de rôle
### <a name="examples"></a>Exemples
Émettre des groupes en tant que noms de groupes dans des jetons d’accès OAuth au format dnsDomainName\SAMAccountName
```json
"optionalClaims": {
"accessToken": [{
"name": "groups",
"additionalProperties": ["dns_domain_and_sam_account_name"]
}]
}
```
Pour émettre des noms de groupes à retourner au format netbiosDomain\samAccountName en tant que revendication de rôles dans des jetons d’ID SAML et OIDC :
```json
"optionalClaims": {
"saml2Token": [{
"name": "groups",
"additionalProperties": ["netbios_name_and_sam_account_name", "emit_as_roles"]
}],
"idToken": [{
"name": "groups",
"additionalProperties": ["netbios_name_and_sam_account_name", "emit_as_roles"]
}]
}
```
## <a name="next-steps"></a>Étapes suivantes
- [Ajouter une autorisation à une application web ASP.NET Core à l’aide de groupes et revendications de groupe (exemple de code)](https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/blob/master/5-WebApp-AuthZ/5-2-Groups/README.md)
- [Affecter un utilisateur ou un groupe à une application d’entreprise](../../active-directory/manage-apps/assign-user-or-group-access-portal.md)
- [Configurer des revendications de rôle](../../active-directory/develop/active-directory-enterprise-app-role-management.md)
| 89.27193 | 887 | 0.790655 | fra_Latn | 0.987832 |
d9b329f4ec4c2b4c358a3b47fd918504a765fd81 | 1,776 | md | Markdown | zh/api/Phalcon_Mvc_Collection_Behavior_Timestampable.md | phatnt93/docs | 5746e5a4a5acea76c38bb26466d6da807fb00b05 | [
"BSD-3-Clause"
] | null | null | null | zh/api/Phalcon_Mvc_Collection_Behavior_Timestampable.md | phatnt93/docs | 5746e5a4a5acea76c38bb26466d6da807fb00b05 | [
"BSD-3-Clause"
] | null | null | null | zh/api/Phalcon_Mvc_Collection_Behavior_Timestampable.md | phatnt93/docs | 5746e5a4a5acea76c38bb26466d6da807fb00b05 | [
"BSD-3-Clause"
] | null | null | null | # Class **Phalcon\\Mvc\\Collection\\Behavior\\Timestampable**
*extends* abstract class [Phalcon\Mvc\Collection\Behavior](/[[language]]/[[version]]/api/Phalcon_Mvc_Collection_Behavior)
*implements* [Phalcon\Mvc\Collection\BehaviorInterface](/[[language]]/[[version]]/api/Phalcon_Mvc_Collection_BehaviorInterface)
<a href="https://github.com/phalcon/cphalcon/blob/master/phalcon/mvc/collection/behavior/timestampable.zep" class="btn btn-default btn-sm">Source on GitHub</a>
Allows to automatically update a model’s attribute saving the datetime when a record is created or updated
## Methods
public **notify** (*mixed* $type, [Phalcon\Mvc\CollectionInterface](/[[language]]/[[version]]/api/Phalcon_Mvc_CollectionInterface) $model)
Listens for notifications from the models manager
public **__construct** ([*array* $options]) inherited from [Phalcon\Mvc\Collection\Behavior](/[[language]]/[[version]]/api/Phalcon_Mvc_Collection_Behavior)
Phalcon\\Mvc\\Collection\\Behavior
protected **mustTakeAction** (*mixed* $eventName) inherited from [Phalcon\Mvc\Collection\Behavior](/[[language]]/[[version]]/api/Phalcon_Mvc_Collection_Behavior)
Checks whether the behavior must take action on certain event
protected *array* **getOptions** ([*string* $eventName]) inherited from [Phalcon\Mvc\Collection\Behavior](/[[language]]/[[version]]/api/Phalcon_Mvc_Collection_Behavior)
Returns the behavior options related to an event
public **missingMethod** ([Phalcon\Mvc\CollectionInterface](/[[language]]/[[version]]/api/Phalcon_Mvc_CollectionInterface) $model, *mixed* $method, [*mixed* $arguments]) inherited from [Phalcon\Mvc\Collection\Behavior](/[[language]]/[[version]]/api/Phalcon_Mvc_Collection_Behavior)
Acts as fallbacks when a missing method is called on the collection | 57.290323 | 281 | 0.780405 | yue_Hant | 0.627103 |
d9b3e370caf3f6c3aca175eb9d7b395e610770aa | 2,545 | md | Markdown | docs/slides/03_02.md | planetoftheweb/slides_gitchallenge | dfb1f2be30d7bcdaaa9ddc0e0375ce457936499f | [
"MIT"
] | 3 | 2021-04-16T06:26:07.000Z | 2021-07-03T20:36:48.000Z | docs/slides/03_02.md | planetoftheweb/slides_gitchallenge | dfb1f2be30d7bcdaaa9ddc0e0375ce457936499f | [
"MIT"
] | 1 | 2021-06-04T19:37:01.000Z | 2021-06-04T19:37:01.000Z | docs/slides/03_02.md | planetoftheweb/slides_gitchallenge | dfb1f2be30d7bcdaaa9ddc0e0375ce457936499f | [
"MIT"
] | 5 | 2021-05-09T12:49:22.000Z | 2022-03-07T21:04:17.000Z | ---
title: Typography Modifications
slide: '<!-- .slide: data-visibility="hidden"-->'
---
<!-- .slide: data-state="layout-title" class="bg-dark"-->
# Typography Modifications
<div class="slide-link"><a href="https://go.raybo.org/49sw"><i class="fab fa-slideshare"></i> go.raybo.org/49sw</a></div>
> > Speaker Notes:
There's some typography styles that are more related to the way fonts and text look on your layouts. Let's take a look at those.
---
<!-- .slide: data-state="layout-code-list" -->
# Text Wrapping/Breaking
- `text-{TYP}`
- TYP: `wrap` `nowrap` `break`
<a href="https://codepen.io/planetoftheweb/pen/wvgqMEV?editors=1000" target="_blank"><code class="code-royal">Try it</code></a>
> >
There are different ways to control how text wraps controlling wether spaces wrap or not and also if very long words should break.
---
<!-- .slide: data-state="layout-code-list" -->
# Text Transform
- `text-{TYP}`
- TYP: `lowercase` `uppercase` `capitalize`
<a href="https://codepen.io/planetoftheweb/pen/VwPzegG?editors=1000" target="_blank"><code class="code-royal">Try it</code></a>
> >
Just like in CSS, you can capitalize text using these different classes. It's always better to use these instead of manually capitalizing things since they're more flexible. The interesting one and probably less useful is `text-capitalize`, which only changes the letter of each word.
---
<!-- .slide: data-state="layout-code-list" -->
# Vertical Alignment
- `align-{TYP}`
- `baseline` `top` `middle` `bottom` `text-top` `text-bottom`
<a href="https://codepen.io/planetoftheweb/pen/xxgLVzm?editors=1000" target="_blank"><code class="code-royal">Try it</code></a>
> >
This is one of the lesser useful set of classes, but it sometimes helps you align items to elements within the same line.
---
<!-- .slide: data-state="layout-code-list" -->
# Misc
- ## RTL
```
<html lang="ar" dir="rtl">
```
`font-monospace` `text-reset`
<a href="https://codepen.io/planetoftheweb/pen/LYxjNPB?editors=1000" target="_blank"><code class="code-royal">Try it</code></a>
> >
There are some other text related classes that are important, but not very complicated, so let's talk about them.
First, is RTL or Right To Left. This new version of bootstrap supports languages that are written from right to left like arabic.
All you need to do is specify the language and the direction in your HTML tag.
There's a couple of other small tags, text-monospace changes the font to mono-spaced type
Text reset is prety interesting. It lets you
| 28.920455 | 284 | 0.709234 | eng_Latn | 0.968696 |
d9b4aa5c193d60b9fcb90bb41cb777aff48f7463 | 3,193 | md | Markdown | docs/t-sql/language-elements/close-transact-sql.md | L3onard80/sql-docs.it-it | f73e3d20b5b2f15f839ff784096254478c045bbb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/t-sql/language-elements/close-transact-sql.md | L3onard80/sql-docs.it-it | f73e3d20b5b2f15f839ff784096254478c045bbb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/t-sql/language-elements/close-transact-sql.md | L3onard80/sql-docs.it-it | f73e3d20b5b2f15f839ff784096254478c045bbb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: CLOSE (Transact-SQL) | Microsoft Docs
ms.custom: ''
ms.date: 03/06/2017
ms.prod: sql
ms.prod_service: database-engine, sql-database
ms.reviewer: ''
ms.technology: t-sql
ms.topic: language-reference
f1_keywords:
- CLOSE_TSQL
- CLOSE
dev_langs:
- TSQL
helpviewer_keywords:
- closing cursors
- cursors [SQL Server], closing
- CLOSE statement
ms.assetid: 21546874-97e3-4b93-970f-87c27f6b78c7
author: rothja
ms.author: jroth
ms.openlocfilehash: 63234f9f337bd6427c4c5ed33c146e2ed3a714c9
ms.sourcegitcommit: 58158eda0aa0d7f87f9d958ae349a14c0ba8a209
ms.translationtype: HT
ms.contentlocale: it-IT
ms.lasthandoff: 03/30/2020
ms.locfileid: "67950321"
---
# <a name="close-transact-sql"></a>CLOSE (Transact-SQL)
[!INCLUDE[tsql-appliesto-ss2008-asdb-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-asdb-xxxx-xxx-md.md)]
Chiude un cursore aperto rilasciando il set di risultati corrente e liberando i blocchi dei cursori mantenuti attivi sulle righe in cui è posizionato il cursore. `CLOSE` mantiene le strutture dei dati disponibili per successive operazioni di apertura. Le operazioni di recupero e di aggiornamento posizionato, tuttavia, sono consentite solo dopo la riapertura del cursore. È necessario eseguire l'istruzione `CLOSE` su un cursore aperto. L'esecuzione non è consentita su cursori solo dichiarati o già chiusi.
 [Convenzioni della sintassi Transact-SQL](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
## <a name="syntax"></a>Sintassi
```
CLOSE { { [ GLOBAL ] cursor_name } | cursor_variable_name }
```
## <a name="arguments"></a>Argomenti
GLOBAL
Specifica che *cursor_name* fa riferimento a un cursore globale.
*cursor_name*
Nome di un cursore aperto. Se esistono sia un cursore globale che un cursore locale con il nome *cursor_name*, *cursor_name* fa riferimento al cursore globale quando viene specificato l'argomento GLOBAL. In caso contrario, *cursor_name* fa riferimento al cursore locale.
*cursor_variable_name*
Nome di una variabile di cursore associata a un cursore aperto.
## <a name="examples"></a>Esempi
Nell'esempio seguente viene illustrata la posizione corretta dell'istruzione `CLOSE` in un processo basato su cursori.
```sql
DECLARE Employee_Cursor CURSOR FOR
SELECT EmployeeID, Title FROM AdventureWorks2012.HumanResources.Employee;
OPEN Employee_Cursor;
FETCH NEXT FROM Employee_Cursor;
WHILE @@FETCH_STATUS = 0
BEGIN
FETCH NEXT FROM Employee_Cursor;
END;
CLOSE Employee_Cursor;
DEALLOCATE Employee_Cursor;
GO
```
## <a name="see-also"></a>Vedere anche
[Cursori](../../relational-databases/cursors.md)
[Cursori (Transact-SQL)](../../t-sql/language-elements/cursors-transact-sql.md)
[DEALLOCATE (Transact-SQL)](../../t-sql/language-elements/deallocate-transact-sql.md)
[FETCH (Transact-SQL)](../../t-sql/language-elements/fetch-transact-sql.md)
[OPEN (Transact-SQL)](../../t-sql/language-elements/open-transact-sql.md)
| 41.467532 | 512 | 0.74632 | ita_Latn | 0.648324 |
d9b5c3163f8cd5012c3e40a1acde3ae2d8f9be48 | 2,012 | md | Markdown | articles/data-factory/samples-powershell.md | georgeOsdDev/azure-docs.ja-jp | 2a180fb94381b1f17e50b24e85626240a3e7fa72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/samples-powershell.md | georgeOsdDev/azure-docs.ja-jp | 2a180fb94381b1f17e50b24e85626240a3e7fa72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/samples-powershell.md | georgeOsdDev/azure-docs.ja-jp | 2a180fb94381b1f17e50b24e85626240a3e7fa72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Data Factory の Azure PowerShell サンプル
description: Azure PowerShell サンプル - データ ファクトリの作成と管理で役立つスクリプト。
ms.service: data-factory
author: dcstwh
ms.author: weetok
ms.reviewer: jburchel
ms.topic: conceptual
ms.date: 03/16/2021
ms.openlocfilehash: 21ab661dd19d76526cd97b75660b9749e1342e09
ms.sourcegitcommit: f611b3f57027a21f7b229edf8a5b4f4c75f76331
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 03/22/2021
ms.locfileid: "104783236"
---
# <a name="azure-powershell-samples-for-azure-data-factory"></a>Azure Data Factory の Azure PowerShell サンプル
[!INCLUDE[appliesto-adf-xxx-md](includes/appliesto-adf-xxx-md.md)]
次の表には、Azure Data Factory の Azure PowerShell スクリプトのサンプルへのリンクが含まれています。
| スクリプト | 説明 |
|---|---|
|**データをコピーする**||
|[Azure Blob Storage で BLOB をフォルダーから別のフォルダーにコピーする](scripts/copy-azure-blob-powershell.md?toc=%2fpowershell%2fmodule%2ftoc.json)| この PowerShell スクリプトは、Azure Blob Storage 内のフォルダーから同じ Blob Storage 内の別のフォルダーにデータをコピーします。 |
|[SQL Server から Azure Blob Storage へのデータのコピー](scripts/hybrid-copy-powershell.md?toc=%2fpowershell%2fmodule%2ftoc.json)| この PowerShell スクリプトは、SQL Server データベースから Azure Blob Storage にデータをコピーします。 |
|[一括コピー](scripts/bulk-copy-powershell.md?toc=%2fpowershell%2fmodule%2ftoc.json)| このサンプルの PowerShell スクリプトでは、Azure SQL Database のデータベースの複数のテーブルから Azure Synapse Analytics にデータをコピーします。 |
|[増分コピー](scripts/incremental-copy-powershell.md?toc=%2fpowershell%2fmodule%2ftoc.json)| このサンプルの PowerShell スクリプトは、最初にソース データ ストアからシンク データ ストアにデータをすべてコピーした後で、新しいレコードまたは更新されたレコードだけをソースからシンクに読み込みます。 |
|**データの変換**||
|[Spark クラスターを使用してデータを変換する](scripts/transform-data-spark-powershell.md?toc=%2fpowershell%2fmodule%2ftoc.json)| この PowerShell スクリプトは、Spark クラスターでプログラムを実行することでデータを変換します。 |
|**SSIS パッケージを Azure にリフトしてシフトする**||
|[Azure-SSIS 統合ランタイムを作成する](scripts/deploy-azure-ssis-integration-runtime-powershell.md?toc=%2fpowershell%2fmodule%2ftoc.json)| この PowerShell スクリプトは、Azure で SQL Server Integration Services (SSIS) パッケージを実行する Azure-SSIS 統合ランタイムをプロビジョニングします。 |
| 54.378378 | 239 | 0.809642 | yue_Hant | 0.56007 |
d9b5c8176322cdd065da759975e279cfae181f3e | 325 | md | Markdown | README.md | Somsubhra1/Digitalocean-Kubernetes-Challenge | 131f1e907ee17c68709d3dd2b4c87a62a47b2b0f | [
"MIT"
] | null | null | null | README.md | Somsubhra1/Digitalocean-Kubernetes-Challenge | 131f1e907ee17c68709d3dd2b4c87a62a47b2b0f | [
"MIT"
] | null | null | null | README.md | Somsubhra1/Digitalocean-Kubernetes-Challenge | 131f1e907ee17c68709d3dd2b4c87a62a47b2b0f | [
"MIT"
] | 1 | 2022-03-09T09:16:21.000Z | 2022-03-09T09:16:21.000Z | # Digitalocean-Kubernetes-Challenge
My Submission for DigitalOcean Kubernetes Challenge - Deploy scalable NoSQL database (MongoDB) cluster
## Blog Write-Up
Check out my detailed blog on how to spin up your K8s Cluster on DOKS [here](https://dev.to/somsubhra1/digitalocean-kubernetes-challenge-mongodb-on-kubernetes-367k).
| 40.625 | 165 | 0.806154 | kor_Hang | 0.413129 |
d9b5f47c5042d427d49beb4beba3b9e9bed483d5 | 19,835 | md | Markdown | README_es.md | YYvanYang/saga | d0beabefaf8567888356f8925dcdcdccf2b62d37 | [
"CC0-1.0",
"MIT"
] | null | null | null | README_es.md | YYvanYang/saga | d0beabefaf8567888356f8925dcdcdccf2b62d37 | [
"CC0-1.0",
"MIT"
] | null | null | null | README_es.md | YYvanYang/saga | d0beabefaf8567888356f8925dcdcdccf2b62d37 | [
"CC0-1.0",
"MIT"
] | null | null | null | <img src='https://redux-saga.js.org/logo/0800/Redux-Saga-Logo-Landscape.png' alt='Logo de Redux saga en panorama' width='800px'>
# redux-saga
[](https://www.npmjs.com/package/redux-saga)
[](https://cdnjs.com/libraries/redux-saga)
[](https://www.npmjs.com/package/redux-saga)
[](https://travis-ci.org/redux-saga/redux-saga)
[](https://gitter.im/yelouafi/redux-saga?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
[](#backers)
[](#sponsors)
`redux-saga` es una librería hecha con la intención de facilitar el manejo de _efectos secundarios (side effects)_ (ej. operaciones asíncronas como la _obtención de datos (data fetching)_ y cosas impuras como el acceso al cache del navegador), de manera más eficiente, más simple de probar, y para mejorar el manejo de fallas.
El modelo mental es que una saga represente (a manera de simulación) un hilo diferente en la aplicación y que únicamente sea responsable de los efectos secundarios. `redux-saga` es un _middleware (capa intermedia)_ de redux, lo que significa que este _"hilo"_ puede ser iniciado, suspendido, y cancelado desde la aplicación principal con una acción cualquiera de redux, tiene acceso a todo el _estado (state)_ de la aplicación en redux y también puede _ejecutar (dispatch)_ acciones en redux.
Usa una de las caracteristicas de ES6 llamada _Generadores (Generators)_ para que procedimientos o operaciones asíncronas sean fáciles de leer, escribir y probar. *(Sí no estás familirizado con generadores [aquí hay algúnos enlaces introductorios en inglés](https://redux-saga.js.org/docs/ExternalResources.html))* Al usar estos generadores, estas opreaciones asíncronas se asemejan a código común y corriente síncrono en JavaScript. (Algo así como `async`/`await`, pero los generadores tienen algúnas ventajas adicionales excelentes que necesitamos)
Es posible que ya hayas usado `redux-thunk` para manejar la obtención de datos en tu aplicación. Contrario a `redux-thunk`, aquí no necesitarás llenar tu aplicación de [_callback hells_](http://callbackhell.com/), también podrás probar tus operaciones asíncronas de manera sencilla y tus acciones en redux se mantendrán _puras(pure actions)_.
# Getting started
## Instalación
```sh
$ npm install --save redux-saga
```
o
```sh
$ yarn add redux-saga
```
También puedes usar los builds UMD que se encuentran directamente en el tag `<script>` de una página HTML. Ve [esta sección](#usando-umd-en-el-navegador).
## Ejemplo de uso
Imagina que tienes un UI que necesita solicitar datos de un servidor cuando un botón en pantalla es presionado. (Por simplicidad solo te mostraremos la acción que ejecutará el código)
```javascript
class UserComponent extends React.Component {
...
onSomeButtonClicked() {
const { userId, dispatch } = this.props
dispatch({type: 'USER_FETCH_REQUESTED', payload: {userId}})
}
...
}
```
El Componente _envía (dispatches)_ un objeto de una acción hacia el _Store (almacén de datos)_. Crearemos una Saga que observe todas las acciones de tipo `USER_FETCH_REQUESTED` y que ejecute una llamada de API para solicitar los datos del usuario.
#### `sagas.js`
```javascript
import { call, put, takeEvery, takeLatest } from 'redux-saga/effects'
import Api from '...'
// Saga: será ejecutada cuando la acción USER_FETCH_REQUESTED sea envíada/ejecutada
function* fetchUser(action) {
try {
const user = yield call(Api.fetchUser, action.payload.userId);
yield put({type: "USER_FETCH_SUCCEEDED", user: user});
} catch (e) {
yield put({type: "USER_FETCH_FAILED", message: e.message});
}
}
/*
Llama a fetchUser cada vez que la acción `USER_FETCH_REQUESTED` es enviada/ejecutada.
`takeEvery` permite que las peticiones se ejecuten de manera concurrente.
*/
function* mySaga() {
yield takeEvery("USER_FETCH_REQUESTED", fetchUser);
}
/*
Igualmente podrías usar `takeLatest`.
No permite solicitudes concurrentes del mismo tipo de accion. Si una accion de tipo `USER_FETCH_REQUESTED`
se envía mientras otra está está siendo ejecutada en ese preciso momento, la acción que está siendo ejecutada será cancelada y sólo la última en recibirse será ejecutada.
*/
function* mySaga() {
yield takeLatest("USER_FETCH_REQUESTED", fetchUser);
}
export default mySaga;
```
Para ejecutar una Saga, necesitamos conectarla a un _Redux Store (almacén de datos Redux)_ usando `redux-saga` como un _middleware_.
#### `main.js`
```javascript
import { createStore, applyMiddleware } from 'redux'
import createSagaMiddleware from 'redux-saga'
import reducer from './reducers'
import mySaga from './sagas'
// creamos el saga middleware
const sagaMiddleware = createSagaMiddleware()
// lo montamos en la Redux Store
const store = createStore(
reducer,
applyMiddleware(sagaMiddleware)
)
// y se inicia la saga
sagaMiddleware.run(mySaga)
// por último se muestra la aplicación
```
# Documentación
- [Introducción](https://redux-saga.js.org/docs/introduction/BeginnerTutorial.html)
- [Conceptos Básicos](https://redux-saga.js.org/docs/basics/index.html)
- [Conceptos avanzados](https://redux-saga.js.org/docs/advanced/index.html)
- [Recetas (_Recipes_)](https://redux-saga.js.org/docs/recipes/index.html)
- [Referencias externas](https://redux-saga.js.org/docs/ExternalResources.html)
- [Como solucionar problemas comúnes](https://redux-saga.js.org/docs/Troubleshooting.html)
- [Golsario](https://redux-saga.js.org/docs/Glossary.html)
- [Documentación del API](https://redux-saga.js.org/docs/api/index.html)
# Traducciones
- [Chino](https://github.com/superRaytin/redux-saga-in-chinese)
- [Chino tradicional](https://github.com/neighborhood999/redux-saga)
- [Japonés](https://github.com/redux-saga/redux-saga/blob/master/README_ja.md)
- [Koreano](https://github.com/mskims/redux-saga-in-korean)
- [Portugués](https://github.com/joelbarbosa/redux-saga-pt_BR)
- [Ruso](https://github.com/redux-saga/redux-saga/blob/master/README_ru.md)
# Usando umd en el navegador
Además de `npm` y `yarn`, existe una distribución **umd** de `redux-saga` y se encuentra disponible en la carpeta `dist/`. Cuando se utilice un _build_ umd de `redux-saga` este estará disponible como `ReduxSaga` en el objeto `window`. Esto permite que se pueda create un Saga middleware sin necesidad de usar un `import` de ES6, esto funciona de la siguiente manera:
```javascript
var sagaMiddleware = ReduxSaga.default()
```
La versión umd es útil si no se utiliza Webpack o Browserify. Se puede encontrar directamente en [unpkg](https://unpkg.com/).
Los siguientes _builds_ están disponibles:
- [https://unpkg.com/redux-saga/dist/redux-saga.js](https://unpkg.com/redux-saga/dist/redux-saga.js)
- [https://unpkg.com/redux-saga/dist/redux-saga.min.js](https://unpkg.com/redux-saga/dist/redux-saga.min.js)
**¡Importante!** Si el navegador que utilizara la aplicación no tiene soporte para generadores de ES2015, se deberá transpilarlos (ej. con el [plugin babel](https://github.com/facebook/regenerator/tree/master/packages/regenerator-transform)) y proveer un _runtime_ válido, como [este](https://unpkg.com/regenerator-runtime/runtime.js). Este _runtime_ debe ser importado antes de importar **redux-saga**:
```javascript
import 'regenerator-runtime/runtime'
// después
import sagaMiddleware from 'redux-saga'
```
# Compilado desde el código fuente
```sh
$ git clone https://github.com/redux-saga/redux-saga.git
$ cd redux-saga
$ npm install
$ npm test
```
Más abajo podrás encontrar ejemplos portados (hasta el momento) de los _repos_ de Redux.
### Ejemplos de contadores
Hay tres ejemplos de contadores.
#### contador-vainilla (vanilla JavaScript)
Demo usando vanilla JavaScript y builds UMD. Todo el código fuente está escrito directamente en `index.html`.
Para ejecuta el ejemplo, solo abre `index.html` en tu navegador.
> Importante: tu navegador debe contar con soporte para generadores. Las últimas versiones de Chrome/Firefox/Edge tienen el soporte necesario.
#### counter
Demo usando `webpack` y el API de alto nivel `takeEvery`.
```sh
$ npm run counter
# probar el generador de ejemplo
$ npm run test-counter
```
#### cancellable-counter
Demo usando un API de bajo nivel que demuestra como cancelar una tarea.
```sh
$ npm run cancellable-counter
```
### Ejemplo de un carrito de compras
```sh
$ npm run shop
# probar el generador de ejemplo
$ npm run test-shop
```
### Ejemplo asíncrono
```sh
$ npm run async
# probar el ejemplo de generadores
$ npm run test-async
```
### Ejemplo de una situación real (con webpack y _hot reloading_)
```sh
$ npm run real-world
# lo siento, aún no se implementan las pruebas
```
### TypeScript
Redux-Saga con TypeScript requieren de `DOM.Iterable` o `ES2015.Iterable`. Si tu `target` es `ES6`, es posible que estés listo, sin embargo, si pleaneas ejecutarlo en una ambiente `ES5` necesitarás añadirlo por tu cuenta.
Revisa tu archivo `tsconfig.json`, y la documentación oficial para las <a href="https://www.typescriptlang.org/docs/handbook/compiler-options.html">opciones del compilador</a>.
### Logo
El logo oficial de Redux-Saga en diferentes estilos lo puedes encontrar en el [directorio de logos](https://github.com/redux-saga/redux-saga/tree/master/logo).
### Backers
Por favor, apoyanos con una donación mensual para seguir seguir con nuestras actividades. \[[Convertirme en backer](https://opencollective.com/redux-saga#backer)\]
<a href="https://opencollective.com/redux-saga/backer/0/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/0/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/1/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/1/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/2/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/2/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/3/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/3/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/4/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/4/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/5/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/5/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/6/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/6/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/7/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/7/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/8/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/8/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/9/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/9/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/10/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/10/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/11/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/11/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/12/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/12/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/13/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/13/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/14/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/14/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/15/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/15/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/16/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/16/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/17/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/17/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/18/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/18/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/19/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/19/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/20/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/20/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/21/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/21/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/22/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/22/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/23/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/23/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/24/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/24/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/25/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/25/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/26/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/26/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/27/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/27/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/28/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/28/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/backer/29/website" target="_blank"><img src="https://opencollective.com/redux-saga/backer/29/avatar.svg"></a>
### Patrocinadores
Conviertete en patrocinador y pon tu logo en nuestro README en Github con un enlace a tu sitio. \[[Convertirme en patrocinador](https://opencollective.com/redux-saga#sponsor)\]
<a href="https://opencollective.com/redux-saga/sponsor/0/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/0/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/1/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/1/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/2/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/2/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/3/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/3/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/4/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/4/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/5/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/5/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/6/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/6/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/7/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/7/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/8/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/8/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/9/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/9/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/10/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/10/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/11/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/11/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/12/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/12/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/13/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/13/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/14/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/14/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/15/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/15/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/16/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/16/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/17/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/17/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/18/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/18/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/19/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/19/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/20/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/20/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/21/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/21/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/22/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/22/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/23/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/23/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/24/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/24/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/25/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/25/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/26/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/26/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/27/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/27/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/28/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/28/avatar.svg"></a>
<a href="https://opencollective.com/redux-saga/sponsor/29/website" target="_blank"><img src="https://opencollective.com/redux-saga/sponsor/29/avatar.svg"></a>
| 65.246711 | 551 | 0.744442 | spa_Latn | 0.323405 |
d9b63ca706ec766b082e39fd9a8967ad2fb586f5 | 217 | md | Markdown | _includes/04-lists.md | tushar1999-coder/markdown-portfolio | 8e53955b14d080131663a9957410975c605d0bb2 | [
"MIT"
] | null | null | null | _includes/04-lists.md | tushar1999-coder/markdown-portfolio | 8e53955b14d080131663a9957410975c605d0bb2 | [
"MIT"
] | 5 | 2020-08-01T11:52:58.000Z | 2020-08-01T17:37:36.000Z | _includes/04-lists.md | tushar1999-coder/markdown-portfolio | 8e53955b14d080131663a9957410975c605d0bb2 | [
"MIT"
] | null | null | null | * My faourite food
1. Chole-bhature :heart:
2. Pizza :pizza:
3. Ice-cream :candy:
- Oreo cornetto
- Tooty fruity
- Therefor only upto 1 level nesting is allowed
* My fav places
- Goa
- Mars
| 18.083333 | 51 | 0.626728 | eng_Latn | 0.944844 |
d9b65e70a564f7c958d20809944fb40e6e57653b | 995 | md | Markdown | docs/vs-2015/code-quality/c28246.md | lex111/visualstudio-docs.ru-ru | bbf4a6de3190a41d58a8a18697fc8985198145c9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/code-quality/c28246.md | lex111/visualstudio-docs.ru-ru | bbf4a6de3190a41d58a8a18697fc8985198145c9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/code-quality/c28246.md | lex111/visualstudio-docs.ru-ru | bbf4a6de3190a41d58a8a18697fc8985198145c9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: C28246 | Документация Майкрософт
ms.custom: ''
ms.date: 2018-06-30
ms.prod: visual-studio-dev14
ms.reviewer: ''
ms.suite: ''
ms.technology:
- vs-devops-test
ms.tgt_pltfrm: ''
ms.topic: article
f1_keywords:
- C28246
helpviewer_keywords:
- C28246
ms.assetid: 66a297ab-19fc-4985-8738-0a92f8d1d5cc
caps.latest.revision: 4
author: corob-msft
ms.author: gewarren
manager: ghogen
ms.openlocfilehash: 98ad8fb2d6363b91c9caecb4a659799933d913a1
ms.sourcegitcommit: 55f7ce2d5d2e458e35c45787f1935b237ee5c9f8
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 08/22/2018
ms.locfileid: "47559283"
---
# <a name="c28246"></a>C28246
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
Последнюю версию этого раздела можно найти в [C28246](https://docs.microsoft.com/visualstudio/code-quality/c28246).
Предупреждение C28246: аннотация для функции "\<имя >"-параметр "\<параметр >" не соответствует типу параметра
Оператор __deref был применен к типу, при создании заметки.
| 25.512821 | 117 | 0.774874 | rus_Cyrl | 0.081346 |
d9b6a85718061be488b6dbd4261ae4cd7fd16f27 | 1,307 | md | Markdown | site/themes/biztrox-hugo/exampleSite/content/blog/Finance-My-Business.md | Zyxil/hugo-cms-test | 7d3bc9011d39790be698364fac4df2f31d422f40 | [
"MIT"
] | null | null | null | site/themes/biztrox-hugo/exampleSite/content/blog/Finance-My-Business.md | Zyxil/hugo-cms-test | 7d3bc9011d39790be698364fac4df2f31d422f40 | [
"MIT"
] | null | null | null | site/themes/biztrox-hugo/exampleSite/content/blog/Finance-My-Business.md | Zyxil/hugo-cms-test | 7d3bc9011d39790be698364fac4df2f31d422f40 | [
"MIT"
] | null | null | null | ---
title: "Finance My Business"
bgImage: images/background/page-title.jpg
date: 2018-09-24T11:10:07+06:00
author: John Lincon
type: post
image: images/blog/blog-5.jpg
categories:
- "Profit & Growth"
tags:
- "Consultancy"
- "Market Analysis"
- "Revenue"
---
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex. Commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt.
>Excepteur sint occaecat cupidatat non proident sunt culpa officia deserunt mollit anim id est laborum.Sed ut perspiciatis unde omnis.
1. Business Services
2. Audit & Assurance
3. IT Control Solutions
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex. Commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt. | 54.458333 | 417 | 0.79648 | kor_Hang | 0.317877 |
d9b6b93346d12506dbc2337197894d539cdf1d25 | 281 | md | Markdown | .github/ISSUE_TEMPLATE.md | HiteshMah-Jan/UserManager | d59993c47ae239f6cb9ae9ee52a09dd66ce1d252 | [
"MIT"
] | 16 | 2017-12-13T16:19:58.000Z | 2020-12-09T00:26:42.000Z | .github/ISSUE_TEMPLATE.md | HiteshMah-Jan/UserManager | d59993c47ae239f6cb9ae9ee52a09dd66ce1d252 | [
"MIT"
] | 6 | 2017-12-14T11:39:06.000Z | 2018-01-23T20:40:19.000Z | .github/ISSUE_TEMPLATE.md | HiteshMah-Jan/UserManager | d59993c47ae239f6cb9ae9ee52a09dd66ce1d252 | [
"MIT"
] | 251 | 2017-12-12T20:36:25.000Z | 2021-05-04T11:03:40.000Z | #### Do you want to request a feature or report a bug?
#### What is the current behavior?
#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via [repl](https://repl.it).
#### What is the expected behavior?
| 35.125 | 151 | 0.711744 | eng_Latn | 0.999694 |
d9b70ab9776d1e50ef0a746c93693cc81e6edabb | 86 | md | Markdown | README.md | ninadkgaikwad/ReinforcementLearning_Tutorial | 2ea881d1248bf8e6771715e89541ef147926a3d1 | [
"MIT"
] | null | null | null | README.md | ninadkgaikwad/ReinforcementLearning_Tutorial | 2ea881d1248bf8e6771715e89541ef147926a3d1 | [
"MIT"
] | null | null | null | README.md | ninadkgaikwad/ReinforcementLearning_Tutorial | 2ea881d1248bf8e6771715e89541ef147926a3d1 | [
"MIT"
] | null | null | null | # ReinforcementLearning_Tutorial
A tutorial on Reinforcement Learning for biginners.
| 28.666667 | 52 | 0.860465 | eng_Latn | 0.774955 |
d9b7201800d7afda7d04a9008d9f0a0dbb5bc834 | 29 | md | Markdown | README.md | nukulsharma/validatelog | 2225450018c7a08fe6cbc1162c96dd30def27388 | [
"Apache-2.0"
] | null | null | null | README.md | nukulsharma/validatelog | 2225450018c7a08fe6cbc1162c96dd30def27388 | [
"Apache-2.0"
] | null | null | null | README.md | nukulsharma/validatelog | 2225450018c7a08fe6cbc1162c96dd30def27388 | [
"Apache-2.0"
] | null | null | null | # validatelog
Validate logs
| 9.666667 | 14 | 0.793103 | kor_Hang | 0.338234 |
d9b729021b86aa5341752160b940f7a1d359af1f | 2,263 | md | Markdown | docs/Technical-motivations.md | adamsitnik/command-line-api | c2a46546b69c1c988c69b5db44574e5980c415ee | [
"MIT"
] | 2,653 | 2018-12-19T00:40:52.000Z | 2022-03-31T01:50:54.000Z | docs/Technical-motivations.md | adamsitnik/command-line-api | c2a46546b69c1c988c69b5db44574e5980c415ee | [
"MIT"
] | 996 | 2018-12-19T02:46:03.000Z | 2022-03-31T15:34:59.000Z | docs/Technical-motivations.md | adamsitnik/command-line-api | c2a46546b69c1c988c69b5db44574e5980c415ee | [
"MIT"
] | 389 | 2018-12-19T00:44:42.000Z | 2022-03-25T00:06:18.000Z | # Technical motivations
* Provide a parser that's independent of binding and invocation.
* You can create your own conventions and your own API surface.
* Parsing can easily be tested independently from other application logic.
* The syntax abstraction opens up use cases such as an extensible completions model.
* Features such as syntax validation can be customized independent of your API.
* Grammars can be serialized for interpretation by other tools.
* Different APIs using this base layer can interoperate easily.
* Don't always assume a console app entry point: provide `Main(string[])`-equivalent string splitting.
* Make the end user command line experience consistent and inclusive.
* Support both POSIX and Windows syntax conventions.
* Make help easy to find by defaulting into all common conventions (`-h`, `--help`, `/h` `/?`, `-?`).
* Make completions work by default, so that they become the norm.
* Make it possible to write completion providers for non-.NET command line applications.
* Localization support for all messages that the library emits.
* Parse diagramming, to help people understand a program's syntax without invoking it, is available by default.
* A composable chain of responsibility for subcommand routing, middleware, directives, etc.
* An invocation model that allows for short-circuiting and interception, with access to the parser, meaning cross-cutting behaviors can be composed into your app via NuGet packages.
* Simplify debugging by providing an interception hook in the middleware pipeline.
* Support for handling process cancellation.
* Directive syntax provides a consistent extensibility point that does not interfere with your app's syntax.
* Supports command line API versioning via directives.
* Rich, adapative output rendering
* Write output code once and render it correctly based on the presence or absence of a terminal as well as terminal capabilities.
* Support for higher-level layouts, tables, event-based re-rendering, and animation.
* Support for standard render mode hints via directives.
* Other things:
* Support arbitrarily deep nesting of subcommands.
* Support response files.
* Restore console state after application exit.
| 53.880952 | 183 | 0.772868 | eng_Latn | 0.99819 |
d9b7cff45d47164f419f1a1e56938eb946da4ff1 | 93 | md | Markdown | Existing Projects/Tutorial Screen/readme.md | NichiketPatil/Android-Projects-2 | a603cd343674b24338c5cf0b4491e9c38d4f91f9 | [
"MIT"
] | null | null | null | Existing Projects/Tutorial Screen/readme.md | NichiketPatil/Android-Projects-2 | a603cd343674b24338c5cf0b4491e9c38d4f91f9 | [
"MIT"
] | 4 | 2020-09-18T12:42:22.000Z | 2020-09-30T17:41:25.000Z | Existing Projects/Tutorial Screen/readme.md | NichiketPatil/Android-Projects-2 | a603cd343674b24338c5cf0b4491e9c38d4f91f9 | [
"MIT"
] | 3 | 2020-09-18T12:55:23.000Z | 2020-10-15T13:55:26.000Z | <h2>TUTORIAL SCREEN</h2>
This is a tutorial screen project. To test simply clone and run it.
| 31 | 67 | 0.763441 | eng_Latn | 0.949195 |
d9b81689bba7352bdea8b21f2aefd397b6ae605f | 1,645 | md | Markdown | README-en.md | lynconEBB/babelJS-example | 121fb00d1c088536451258e6b316b2a613bf6904 | [
"MIT"
] | null | null | null | README-en.md | lynconEBB/babelJS-example | 121fb00d1c088536451258e6b316b2a613bf6904 | [
"MIT"
] | null | null | null | README-en.md | lynconEBB/babelJS-example | 121fb00d1c088536451258e6b316b2a613bf6904 | [
"MIT"
] | null | null | null | ## Babel Js Environment Example
This repository aims to provide a JavaScript development environment capable of using the latest features while still being compatible with older browsers
### Prerequisites
- Node
- NPM
- Git
### Installation
First clone this repository in the location you find most appropriate using the following command:
```bash
git clone https://github.com/lynconEBB/babelJS-example.git
```
After that install the dependencies used with the following command:
```bash
npm install --dev
```
### Usage
This structure was created to be as simple as possible to use, just put your codes in the [src](https://github.com/lynconEBB/babelJS-example/tree/master/src) folder and the converted code will be included in the [out](https://github.com/lynconEBB/babelJS-example/tree/master/out) folder.
If you want to transform your codes just once, use the command:
```bash
npm run build
```
Or if you want to write your codes and automatically convert them every time you save, use the command:
```bash
npm run watch
```
### Configuration
Any changes to the Babel settings can be made in the [babel.config.json](https://github.com/lynconEBB/babelJS-example/blob/master/babel.config.json) file.
To change the browsers that you want to guarantee compatibility, just change the _targets_ parameter. This parameter can be a JSON object containing the name of the browsers and their versions or a query in the [browserslist format](https://github.com/browserslist/browserslist#queries).
```JSON
{
"presets":
[
[
"@babel/env",{
"targets": {
"chrome": "58",
"ie": "11"
}
}
]
]
}
``` | 29.375 | 288 | 0.734347 | eng_Latn | 0.994534 |
d9b8be21815c8ed1dfe1b93e101ea1ef3a5c40ba | 7,566 | md | Markdown | docs/guides/infinite-queries.md | voxivoid/vue-query | 727bf1d47567e9e5c45c9c9ae00a0a4036673c5c | [
"MIT"
] | null | null | null | docs/guides/infinite-queries.md | voxivoid/vue-query | 727bf1d47567e9e5c45c9c9ae00a0a4036673c5c | [
"MIT"
] | null | null | null | docs/guides/infinite-queries.md | voxivoid/vue-query | 727bf1d47567e9e5c45c9c9ae00a0a4036673c5c | [
"MIT"
] | null | null | null | Rendering lists that can additively "load more" data onto an existing set of data or "infinite scroll" is also a very common UI pattern.
Vue Query supports a useful version of `useQuery` called `useInfiniteQuery` for querying these types of lists.
When using `useInfiniteQuery`, you'll notice a few things are different:
- `data` is now an object containing infinite query data:
- `data.pages` array containing the fetched pages
- `data.pageParams` array containing the page params used to fetch the pages
- The `fetchNextPage` and `fetchPreviousPage` functions are now available
- The `getNextPageParam` and `getPreviousPageParam` options are available for both determining if there is more data to load and the information to fetch it. This information is supplied as an additional parameter in the query - function (which can optionally be overridden when calling the `fetchNextPage` or `fetchPreviousPage` functions)
- A `hasNextPage` boolean is now available and is `true` if `getNextPageParam` returns a value other than `undefined`
- A `hasPreviousPage` boolean is now available and is `true` if `getPreviousPageParam` returns a value other than `undefined`
- The `isFetchingNextPage` and `isFetchingPreviousPage` booleans are now available to distinguish between a background refresh state and a loading more state
?> Note: When using options like `initialData` or `select` in your query, make sure that when you restructure your data that it still includes `data.pages` and `data.pageParams` properties, otherwise your changes will be overwritten by the query in its return!
## Example
Let's assume we have an API that returns pages of `projects` 3 at a time based on a `cursor` index along with a cursor that can be used to fetch the next group of projects:
```js
fetch("/api/projects?cursor=0");
// { data: [...], nextCursor: 3}
fetch("/api/projects?cursor=3");
// { data: [...], nextCursor: 6}
fetch("/api/projects?cursor=6");
// { data: [...], nextCursor: 9}
fetch("/api/projects?cursor=9");
// { data: [...] }
```
With this information, we can create a "Load More" UI by:
- Waiting for `useInfiniteQuery` to request the first group of data by default
- Returning the information for the next query in `getNextPageParam`
- Calling `fetchNextPage` function
?> Note: It's very important you do not call `fetchNextPage` with arguments unless you want them to override the `pageParam` data returned from the `getNextPageParam` function.
Do not do this: `<button @click={fetchNextPage} />` as this would send the onClick event to the `fetchNextPage` function.
```vue
<script setup>
import { defineComponent } from "vue";
import { useInfiniteQuery } from "vue-query";
const fetchProjects = ({ pageParam = 0 }) =>
fetch("/api/projects?cursor=" + pageParam);
function useProjectsInfiniteQuery() {
return useInfiniteQuery("projects", fetchProjects, {
getNextPageParam: (lastPage, pages) => lastPage.nextCursor,
});
}
const {
data,
error,
fetchNextPage,
hasNextPage,
isFetching,
isFetchingNextPage,
isLoading,
isError,
} = useProjectsInfiniteQuery();
</script>
<template>
<span v-if="isLoading">Loading...</span>
<span v-else-if="isError">Error: {{ error.message }}</span>
<div v-else>
<span v-if="isFetching && !isFetchingNextPage">Fetching...</span>
<ul v-for="(group, index) in data.pages" :key="index">
<li v-for="project in group.projects" :key="project.id">
{{ project.name }}
</li>
</ul>
<button
@click="() => fetchNextPage()"
:disabled="!hasNextPage || isFetchingNextPage"
>
<span v-if="isFetchingNextPage">Loading more...</span>
<span v-else-if="hasNextPage">Load More</span>
<span v-else>Nothing more to load</span>
</button>
</div>
</template>
```
## What happens when an infinite query needs to be refetched?
When an infinite query becomes `stale` and needs to be refetched, each group is fetched `sequentially`, starting from the first one.
This ensures that even if the underlying data is mutated, we're not using stale cursors and potentially getting duplicates or skipping records.
If an infinite query's results are ever removed from the `queryCache`, the pagination restarts at the initial state with only the initial group being requested.
### refetchPage
If you only want to actively refetch a subset of all pages, you can pass the `refetchPage` function to `refetch` returned from `useInfiniteQuery`.
```js
function useProjectsInfiniteQuery() {
return useInfiniteQuery("projects", fetchProjects, {
getNextPageParam: (lastPage, pages) => lastPage.nextCursor,
});
}
const { refetch } = useProjectsInfiniteQuery();
// only refetch the first page
refetch({ refetchPage: (page, index) => index === 0 });
```
You can also pass this function as part of the 2nd argument (`queryFilters`) to [queryClient.refetchQueries](https://react-query.tanstack.com/reference/QueryClient#queryclientrefetchqueries), [queryClient.invalidateQueries](https://react-query.tanstack.com/reference/QueryClient#queryclientinvalidatequeries) or [queryClient.resetQueries](https://react-query.tanstack.com/reference/QueryClient#queryclientresetqueries).
**Signature**
`refetchPage: (page: TData, index: number, allPages: TData[]) => boolean`
The function is executed for each page, and only pages where this function returns `true` will be refetched.
## What if I need to pass custom information to my query function?
By default, the variable returned from `getNextPageParam` will be supplied to the query function, but in some cases, you may want to override this.
You can pass custom variables to the `fetchNextPage` function which will override the default variable like so:
```js
const fetchProjects = ({ pageParam = 0 }) =>
fetch("/api/projects?cursor=" + pageParam);
function useProjectsInfiniteQuery() {
return useInfiniteQuery("projects", fetchProjects, {
getNextPageParam: (lastPage, pages) => lastPage.nextCursor,
});
}
const { fetchNextPage } = useProjectsInfiniteQuery();
// Pass your own page param
const skipToCursor50 = () => fetchNextPage({ pageParam: 50 });
```
## What if I want to implement a bi-directional infinite list?
Bi-directional lists can be implemented by using the `getPreviousPageParam`, `fetchPreviousPage`, `hasPreviousPage` and `isFetchingPreviousPage` properties and functions.
```js
useInfiniteQuery("projects", fetchProjects, {
getNextPageParam: (lastPage, pages) => lastPage.nextCursor,
getPreviousPageParam: (firstPage, pages) => firstPage.prevCursor,
});
```
## What if I want to show the pages in reversed order?
Sometimes you may want to show the pages in reversed order. If this is case, you can use the `select` option:
```js
function useProjectsInfiniteQuery() {
return useInfiniteQuery("projects", fetchProjects, {
select: (data) => ({
pages: [...data.pages].reverse(),
pageParams: [...data.pageParams].reverse(),
}),
});
}
```
## What if I want to manually update the infinite query?
Manually removing first page:
```js
queryClient.setQueryData("projects", (data) => ({
pages: data.pages.slice(1),
pageParams: data.pageParams.slice(1),
}));
```
Manually removing a single value from an individual page:
```js
const newPagesArray =
oldPagesArray?.pages.map((page) =>
page.filter((val) => val.id !== updatedId)
) ?? [];
queryClient.setQueryData("projects", (data) => ({
pages: newPagesArray,
pageParams: data.pageParams,
}));
```
!> Make sure to keep the same data structure of `pages` and `pageParams`!
| 39.202073 | 419 | 0.73143 | eng_Latn | 0.95236 |
d9ba7817c42c0d093601702381a05bdd61ed8ecf | 2,314 | md | Markdown | docs/profiling/how-to-pause-and-resume-performance-data-collection.md | Simran-B/visualstudio-docs.de-de | 0e81681be8dbccb2346866f432f541b97d819dac | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/profiling/how-to-pause-and-resume-performance-data-collection.md | Simran-B/visualstudio-docs.de-de | 0e81681be8dbccb2346866f432f541b97d819dac | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/profiling/how-to-pause-and-resume-performance-data-collection.md | Simran-B/visualstudio-docs.de-de | 0e81681be8dbccb2346866f432f541b97d819dac | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Vorgehensweise: Anhalten und Fortsetzen der Sammlung von Leistungsdaten | Microsoft-Dokumentation'
ms.date: 11/04/2016
ms.topic: conceptual
helpviewer_keywords:
- profiling tools, remote profiling
ms.assetid: b8e76363-65cd-424d-8173-3e2b5f54203b
author: mikejo5000
ms.author: mikejo
manager: jillfra
monikerRange: vs-2017
ms.workload:
- multiple
ms.openlocfilehash: 3b6190dbc4545836e5fa7ea1b1ff6c5bfc3b2403
ms.sourcegitcommit: 00b71889bd72b6a566586885bdb982cfe807cf54
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 12/03/2019
ms.locfileid: "74778790"
---
# <a name="how-to-pause-and-resume-performance-data-collection"></a>Vorgehensweise: Anhalten und Fortsetzen der Sammlung von Leistungsdaten
Im Fenster der Profilerstellungs-Sitzungsseite können Sie die Erfassung der Profilerstellungsdaten interaktiv steuern.
Durch Steuerung der Datensammlung können Sie die Größe der Profildatendatei reduzieren sowie Daten nur für relevante Vorgänge sammeln. Sie können die Profilerstellung in einer Leistungssitzung mehrmals anhalten und fortsetzen.
> [!NOTE]
> Sie können die Leistungssitzung auch mit angehaltener Profilerstellung starten und die Profilaustellung zu einem späteren Zeitpunkt in der Programmausführung fortsetzen. Wählen Sie zum Starten der Leistungssitzung bei angehaltener Profilerstellung im Menü **Debuggen** den Befehl **Leistungsanalyse mit angehaltener Profilerstellung starten** aus.
### <a name="to-pause--resume-or-stop-profiling"></a>So können Sie die Profilerstellung anhalten, fortsetzen oder beenden
- Gehen Sie auf der Profilerstellungs-Sitzungsseite folgendermaßen vor:
- Wählen Sie **Auflistung anhalten** aus, um die Datensammlung anzuhalten.
- Wählen Sie **Auflistung wiederaufnehmen** aus, um die Datensammlung neu zu starten, nachdem sie angehalten wurde.
- Wählen Sie **Profilerstellung beenden** aus, um die Profilerstellungssitzung zu beenden und Berichte zu generieren.
## <a name="see-also"></a>Siehe auch
- [Steuerung der Datensammlung](../profiling/controlling-data-collection.md)
- [Vorgehensweise: Starten und Beenden der Sammlung von Leistungsdaten](../profiling/how-to-start-and-end-performance-data-collection.md)
| 52.590909 | 349 | 0.816335 | deu_Latn | 0.977677 |
d9bad1618b5c99fa8230d2a4a571036f4381fbe8 | 753 | md | Markdown | content/landing-page.dummy.md | eztzez/editorsite-test | 31737cd680cad01016d28dea96e945e79006ca16 | [
"MIT"
] | 5 | 2021-02-03T21:03:13.000Z | 2021-08-23T22:27:45.000Z | content/landing-page.dummy.md | eztzez/editorsite-test | 31737cd680cad01016d28dea96e945e79006ca16 | [
"MIT"
] | null | null | null | content/landing-page.dummy.md | eztzez/editorsite-test | 31737cd680cad01016d28dea96e945e79006ca16 | [
"MIT"
] | 3 | 2021-01-08T10:52:51.000Z | 2021-03-26T15:37:20.000Z | ---
title: Landing Page Interface
carousel:
- image: /uploads/images/carousel-1.jpg
subtitle: one
title: One
sections:
- description: ""
image: /uploads/images/carousel-2.jpg
title: About
type: about
- accordion_image: /uploads/images/human_eye_-_blue.jpg
collapsibles:
- body: ""
header: Lorem Ipsum 1
title: Bullet Points
type: accordion
- paragraph: two
title: one
type: paragraph
- gallery:
- image: /uploads/images/carousel-1.jpg
- testimonials:
- author: ""
testimonial: ""
- promotions:
- promotion: ""
title: ""
---
<!--This serves as dummy data for gatsby incase any of these fields don't exist in the real page, so it won't throw an error-->
| 23.53125 | 127 | 0.632138 | eng_Latn | 0.830844 |
d9baedd703d4c8c0ad6afef33eb58117124d8b59 | 2,631 | md | Markdown | README.md | jiripudil/nettrine-dbal | 7282a01e754348ac78d031c99d827aeac8ab551e | [
"MIT"
] | null | null | null | README.md | jiripudil/nettrine-dbal | 7282a01e754348ac78d031c99d827aeac8ab551e | [
"MIT"
] | null | null | null | README.md | jiripudil/nettrine-dbal | 7282a01e754348ac78d031c99d827aeac8ab551e | [
"MIT"
] | null | null | null | # Doctrine DBAL
Doctrine DBAL for Nette Framework.
-----
[](https://travis-ci.org/nettrine/dbal)
[](https://coveralls.io/r/nettrine/dbal)
[](https://packagist.org/packages/nettrine/dbal)
[](https://packagist.org/packages/nettrine/dbal)
[](https://packagist.org/packages/nettrine/dbal)
[](https://packagist.org/packages/nettrine/dbal)
[](https://packagist.org/packages/nettrine/dbal)
## Discussion / Help
[](http://bit.ly/nettrine)
## Install
```sh
composer require nettrine/dbal
```
## Versions
| State | Version | Branch | PHP |
|-------------|-------------|----------|----------|
| development | dev-master | `master` | `>= 7.1` |
| stable | `^0.2` | `master` | `>= 7.1` |
## Overview
- [Installation - how to install](https://github.com/nettrine/dbal/blob/master/.docs/#installation)
- [Configuration - basic setup](https://github.com/nettrine/dbal/blob/master/.docs/#configuration)
- [Usage](https://github.com/nettrine/dbal/blob/master/.docs/#usage)
- [Events](https://github.com/nettrine/dbal/blob/master/.docs/#events)
- [Bridges](https://github.com/nettrine/dbal/blob/master/.docs/#bridges)
- [Symfony\Console](https://github.com/nettrine/dbal/blob/master/.docs/#symfony-console)
## Maintainers
<table>
<tbody>
<tr>
<td align="center">
<a href="https://github.com/f3l1x">
<img width="150" height="150" src="https://avatars2.githubusercontent.com/u/538058?v=3&s=150">
</a>
</br>
<a href="https://github.com/f3l1x">Milan Felix Šulc</a>
</td>
<td align="center">
<a href="https://github.com/benijo">
<img width="150" height="150" src="https://avatars3.githubusercontent.com/u/6731626?v=3&s=150">
</a>
</br>
<a href="https://github.com/benijo">Josef Benjač</a>
</td>
</tr>
<tbody>
</table>
---
Thank you for testing, reporting and contributing.
| 38.691176 | 144 | 0.662486 | yue_Hant | 0.272453 |
d9bbaae782da5054f59a754a3ee0f1c27493bccc | 132 | md | Markdown | README.md | pokeshun/ElectricalSystems | da880d876deffba841ca33a9c0d987e85f7bfd93 | [
"CC0-1.0"
] | null | null | null | README.md | pokeshun/ElectricalSystems | da880d876deffba841ca33a9c0d987e85f7bfd93 | [
"CC0-1.0"
] | null | null | null | README.md | pokeshun/ElectricalSystems | da880d876deffba841ca33a9c0d987e85f7bfd93 | [
"CC0-1.0"
] | 1 | 2021-03-06T02:13:17.000Z | 2021-03-06T02:13:17.000Z | # ElectricalSystems
This repository is a place where you can find my personal ideas and review guideline about Electrical Systems.
| 33 | 110 | 0.825758 | eng_Latn | 0.999238 |
d9bbb51fe5f78df5436b8dd392e1edb741ce6571 | 3,020 | md | Markdown | node_modules/ghost-editor/README.md | feibaliang/blog | 39b97dd796796b3762874ab28bc0be3e19a033b0 | [
"MIT"
] | null | null | null | node_modules/ghost-editor/README.md | feibaliang/blog | 39b97dd796796b3762874ab28bc0be3e19a033b0 | [
"MIT"
] | null | null | null | node_modules/ghost-editor/README.md | feibaliang/blog | 39b97dd796796b3762874ab28bc0be3e19a033b0 | [
"MIT"
] | null | null | null | # Ghost-editor
This is the new mobiledoc editor for Ghost-Admin. It's still a work in progress but we're very excited about it.
Here are a few of our goals:
- To make the best ghosh darn writing experience on the interwebs.
- To build a tool that works just as well for non technical content creators as power users.
- To support rich content as easily as dealing with an image. Want a poll mid article? You got it. Want to paste a complete NG application in raw HTML? You got it.
When embarking on this project the last thing we wanted was to use one of those WYSIWYG editors with the million options and incomprehensible and inconsistent markup (you know who I'm talking about), to that end we chose to build our editor on top of [mobiledoc-kit](https://github.com/bustlelabs/mobiledoc-kit), you can read more about our decision [here](https://github.com/TryGhost/Ghost/issues/7429).
## So why mobiledoc?
Mobiledoc is a new format for storing rich content, it's platform independent and isn't tied specifically to HTML (we can render a plain text version for a search index for instance). It allows for the embedding of rich applications inside your content using the cards paradigm. It's also a standard so content written in and for Ghost is compatible with any other mobiledoc system, and vice versa.
To us it seemed like the best compromise between a feature rich WYSIWYG editor and the markdown that we so love.
Like Ghost, Mobiledoc-kit is still moving towards its 1.0 release - it still has some bugs, but we're working together to make something really fun.
## To try it out:
- clone this repo
- `cd Ghost-Editor`
- `npm install && bower install`
- `ember serve`
- Visit `http://localhost:4200`
- Click in the middle to activate the editor
## If you want to help out:
- Create an issue on the main Ghost repository [https://github.com/TryGhost/Ghost/issues](https://github.com/TryGhost/Ghost/issues).
- Clone the repo and create a branch.
- Submit a PR.
A fantastic guide on the Ghost workflow is here: https://github.com/TryGhost/Ghost/wiki/Git-workflow, it's well worth a read.
## Some features of the editor.
Ghost-Editor is very much a WYSIWYG editor but it supports a subset of markdown as content shortcuts for those of us who are mouse adverse, specifically:
\# H1
\## H2
\## H3
1. Ordered Lists
\* Unordered Lists
\- Unordered Lists
\> Block Quote
\*italic*
\_italic_
\*\*bold\*\*
\_\_bold\_\_
\~~strikethrough~~
\[link](http://www.ghost.org)
\!\[image](https://ghost.org/assets/logos-f93942864f8c9f4a0a9b0ecd6f7f055c.png)
\`\`\` code blocks (generates a new markdown card) \`\`\`
There's also has an inline menu that you can access by pressing the **/** key within the editor.
Right now we only have three built in "cards", a markdown card, an HTML card, and an Image card. But we plan to add the ability to install custom cards in the near future and have some big and exciting plans (and we're even more excited about what the community will do with it.), so watch this space.
| 49.508197 | 404 | 0.75596 | eng_Latn | 0.997466 |
d9bde3dafd243bb58622c93a658f33abba385fc4 | 3,985 | md | Markdown | README.md | danielb2/anime-downloader | 0bebd6f9e8a7ea6264fcc6c4436570596f299213 | [
"Unlicense"
] | null | null | null | README.md | danielb2/anime-downloader | 0bebd6f9e8a7ea6264fcc6c4436570596f299213 | [
"Unlicense"
] | null | null | null | README.md | danielb2/anime-downloader | 0bebd6f9e8a7ea6264fcc6c4436570596f299213 | [
"Unlicense"
] | null | null | null | <div align="center">
<img src="https://cdn.discordapp.com/attachments/484717445538643979/564476620401016862/Banner.png">
<br>
<strong><i>A simple yet powerful tool for downloading anime.</i></strong>
<br>
<br>
<a href="https://travis-ci.com/vn-ki/anime-downloader">
<img src="https://img.shields.io/travis/com/vn-ki/anime-downloader.svg?style=for-the-badge&logo=Travis%20CI">
</a>
<a href="https://codecov.io/gh/vn-ki/anime-downloader">
<img src="https://img.shields.io/codecov/c/github/vn-ki/anime-downloader.svg?logo=codecov&style=for-the-badge">
</a>
<a href="https://pypi.org/project/anime-downloader/">
<img src="https://img.shields.io/pypi/v/anime-downloader.svg?logo=python&style=for-the-badge">
</a>
<a href="https://discord.gg/Qn2nWGm">
<img src="https://img.shields.io/discord/483008720167632929.svg?color=%237289DA&label=Discord&logo=Discord&style=for-the-badge">
</a>
<a href="https://anime-downlader.rtfd.io">
<img src="https://img.shields.io/readthedocs/anime-downlader.svg?logo=read%20the%20docs&style=for-the-badge">
</a>
</div>
---
# Anime Downloader
Ever dreamt about watching anime for free effortlessly without all those unbearable ads? Ever dreamt of downloading your favourite anime for that long trip?
Yeah. Me too! That's why this tool exists.
## Features
- Download or stream any episode or episode range of any anime.
- Specify the quality you want to stream or download.
- Search and download.
- Save yourselves from those malicious ads.
- Add any anime to your watch list using `anime watch` and let anime downloader take care of everything for you.
- Download using external downloader ([aria2](https://aria2.github.io/) recommended).
- Configurable using `config.json`. See [documentation](https://anime-downlader.readthedocs.io/en/latest/usage/config.html).
## Supported Sites
- twist.moe
- Animepahe
- Anistream
- Animeflix
- Animefreak
- Gogoanime
- Dubbedanime
- a2zanime
- animeout
- itsaturday
- Animeflv
- Kickassanime
- DreamAnime
- RyuAnime
- Erai-Raws
- Animesimple
- Animerush
- Watchmovie
- Kissanime - requires Node.js
- Kisscartoon - requires Node.js
## Installation
[**Installation instructions***](https://anime-downlader.readthedocs.io/en/latest/usage/installation.html)
If you have trouble installing, see extended installation instructions [here](https://anime-downlader.readthedocs.io/en/latest/usage/installation.html) or join the [discord server](https://discord.gg/Qn2nWGm) for help.
**Note**:
- For cloudflare scraping [cfscrape](https://github.com/Anorov/cloudflare-scrape) is used. It depends on [`node-js`](https://nodejs.org/en/). So if you want to use cloudflare, make sure you have [node-js](https://nodejs.org/en/) installed.
- You might have to use pip3 depending on your system
## Usage
See [docs](https://anime-downlader.readthedocs.io/en/latest/usage/dl.html).
Anime downloader has two sub commands, `dl` and `watch`.
- [dl](https://anime-downlader.readthedocs.io/en/latest/usage/dl.html): `dl` can download anime.
- [watch](https://anime-downlader.readthedocs.io/en/latest/usage/watch.html): `watch` can manage your anime watch list. Needs [mpv](https://mpv.io). Deprecated in favour of [adl](https://github.com/RaitaroH/adl)
**To use `anime_downloader` in your package:**
This tool can be used as a library. This means you can import it into your own application and search for anime and do many other wonderful things.
See [documentation](https://anime-downlader.readthedocs.io/en/latest/usage/api.html).
**Development Instructions:**
See [development instructions](https://anime-downlader.readthedocs.io/en/latest/advanced/custom_site.html).
## Related Projects
- [adl](https://github.com/RaitaroH/adl) - a command-line tool for watching anime that makes use of anime-downloader.
---
*Please don't judge me for not paying for anime. I want to support the anime industry, but being a college student, I can't.*
| 38.68932 | 239 | 0.754329 | eng_Latn | 0.516522 |
End of preview. Expand
in Dataset Viewer.
A copy of the deduplicated the stack Markdown files, annotated with fastText to include language labels (lid column) and probabilities (lid_prob). This was done using the NLLB fastText model facebook/fasttext-language-identification.
The following languages were detected:
- abk_Cyrl
- ace_Arab
- ace_Latn
- ady_Cyrl
- afr_Latn
- aka_Latn
- als_Latn
- amh_Ethi
- arb_Arab
- arb_Latn
- arn_Latn
- asm_Beng
- ast_Latn
- ayr_Latn
- azb_Arab
- azj_Latn
- bak_Cyrl
- bam_Latn
- ban_Latn
- bel_Cyrl
- bem_Latn
- ben_Beng
- bho_Deva
- bis_Latn
- bjn_Arab
- bjn_Latn
- bod_Tibt
- bos_Latn
- bug_Latn
- bul_Cyrl
- bxr_Cyrl
- cat_Latn
- ceb_Latn
- ces_Latn
- che_Cyrl
- chv_Cyrl
- cjk_Latn
- ckb_Arab
- crh_Latn
- cym_Latn
- dan_Latn
- deu_Latn
- dik_Latn
- diq_Latn
- dyu_Latn
- dzo_Tibt
- ell_Grek
- eng_Latn
- epo_Latn
- est_Latn
- eus_Latn
- ewe_Latn
- ewo_Latn
- fao_Latn
- fij_Latn
- fin_Latn
- fon_Latn
- fra_Latn
- fur_Latn
- fuv_Latn
- gaz_Latn
- gla_Latn
- gle_Latn
- glg_Latn
- gom_Deva
- grn_Latn
- guj_Gujr
- hat_Latn
- hau_Latn
- heb_Hebr
- hin_Deva
- hrv_Latn
- hun_Latn
- hye_Armn
- ibo_Latn
- ilo_Latn
- ind_Latn
- isl_Latn
- ita_Latn
- jav_Latn
- jpn_Jpan
- kab_Latn
- kac_Latn
- kal_Latn
- kam_Latn
- kan_Knda
- kas_Deva
- kat_Geor
- kaz_Cyrl
- kbp_Latn
- kea_Latn
- khk_Cyrl
- khm_Khmr
- kik_Latn
- kin_Latn
- kir_Cyrl
- kmb_Latn
- kmr_Latn
- knc_Arab
- knc_Latn
- kon_Latn
- kor_Hang
- krc_Cyrl
- lao_Laoo
- lij_Latn
- lim_Latn
- lin_Latn
- lit_Latn
- lmo_Latn
- ltg_Latn
- ltz_Latn
- lua_Latn
- lug_Latn
- luo_Latn
- lus_Latn
- lvs_Latn
- mag_Deva
- mai_Deva
- mal_Mlym
- mar_Deva
- min_Latn
- mkd_Cyrl
- mlt_Latn
- mni_Beng
- mos_Latn
- mri_Latn
- mya_Mymr
- nav_Latn
- nia_Latn
- nld_Latn
- nno_Latn
- nob_Latn
- npi_Deva
- nso_Latn
- nus_Latn
- nya_Latn
- oci_Latn
- ory_Orya
- oss_Cyrl
- pag_Latn
- pan_Guru
- pap_Latn
- pbt_Arab
- pcm_Latn
- pes_Arab
- plt_Latn
- pol_Latn
- por_Latn
- prs_Arab
- quy_Latn
- roh_Latn
- ron_Latn
- run_Latn
- rus_Cyrl
- sag_Latn
- san_Deva
- scn_Latn
- sin_Sinh
- slk_Latn
- slv_Latn
- smo_Latn
- sna_Latn
- snd_Arab
- som_Latn
- sot_Latn
- spa_Latn
- srd_Latn
- srp_Cyrl
- ssw_Latn
- sun_Latn
- swe_Latn
- swh_Latn
- szl_Latn
- tah_Latn
- tam_Taml
- taq_Latn
- tat_Cyrl
- tel_Telu
- tgk_Cyrl
- tgl_Latn
- tha_Thai
- tir_Ethi
- ton_Latn
- tpi_Latn
- tsn_Latn
- tso_Latn
- tuk_Latn
- tum_Latn
- tur_Latn
- twi_Latn
- udm_Cyrl
- uig_Arab
- ukr_Cyrl
- umb_Latn
- urd_Arab
- uzn_Latn
- vec_Latn
- vie_Latn
- war_Latn
- wes_Latn
- wol_Latn
- xho_Latn
- ydd_Hebr
- yor_Latn
- yue_Hant
- zho_Hans
- zho_Hant
- zsm_Latn
- zul_Latn
- Downloads last month
- 38