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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
d591783be76a9b6b1bfeaa63708821c0ab61516f | 1,303 | md | Markdown | fr/android/logcat.md | reinhart1010/nix | a1803c718ead3b79854b65396c8967bd5ec32874 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | fr/android/logcat.md | reinhart1010/nix | a1803c718ead3b79854b65396c8967bd5ec32874 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | fr/android/logcat.md | reinhart1010/nix | a1803c718ead3b79854b65396c8967bd5ec32874 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
layout: page
title: android/logcat (français)
description: "Exporte une log depuis les messages système."
content_hash: 858bedc81e61fbe1f0b91eab1c9bfd35a235837f
related_topics:
- title: Deutsch version
url: /de/android/logcat.html
icon: bi bi-globe
- title: English version
url: /en/android/logcat.html
icon: bi bi-globe
- title: Indonesia version
url: /id/android/logcat.html
icon: bi bi-globe
- title: português (Brasil) version
url: /pt_BR/android/logcat.html
icon: bi bi-globe
- title: 中文 version
url: /zh/android/logcat.html
icon: bi bi-globe
- title: 中文 (繁體, 台灣) version
url: /zh_TW/android/logcat.html
icon: bi bi-globe
---
# logcat
Exporte une log depuis les messages système.
Plus d'informations : <https://developer.android.com/studio/command-line/logcat>.
- Affiche la journalisation système :
`logcat`
- Écris la journalisation système dans un fichier :
`logcat -f `<span class="tldr-var badge badge-pill bg-dark-lm bg-white-dm text-white-lm text-dark-dm font-weight-bold">chemin/vers/fichier</span>
- Affiche les lignes qui correspondent à une expression régulière :
`logcat --regex `<span class="tldr-var badge badge-pill bg-dark-lm bg-white-dm text-white-lm text-dark-dm font-weight-bold">expression_régulière</span>
| 31.02381 | 151 | 0.729087 | fra_Latn | 0.30051 |
d592d70ef273ca28acd2e5ed660d2037c0db1dcf | 1,975 | md | Markdown | cookbooks-local/finalize/README.md | amfranco/vagrant-drupal | c24e0c61e480c4e282a885bb2b12629685017da8 | [
"Apache-2.0"
] | null | null | null | cookbooks-local/finalize/README.md | amfranco/vagrant-drupal | c24e0c61e480c4e282a885bb2b12629685017da8 | [
"Apache-2.0"
] | null | null | null | cookbooks-local/finalize/README.md | amfranco/vagrant-drupal | c24e0c61e480c4e282a885bb2b12629685017da8 | [
"Apache-2.0"
] | null | null | null | ##Description
Completes environment configuration:
* PHPUnit
* xdebug
* memchache
* Virtual host
* Install Drush
* Download and install drupal
##Requirements
* [apache2](https://github.com/opscode-cookbooks/apache2) - opscode apache2 w/ LWRP
* [php](https://github.com/opscode-cookbooks/php) - php/pear
* [drush](https://github.com/ksorokin/chef-drush.git) - drupal shell
##Attributes
Apache config
default["finalize"]["server_name"] = "drupal-site"
default["finalize"]["apache2"]["docroot"] = "/vagrant/www"
Drupal config
default["finalize"]["drupal"]["pressflow"] = false
default["finalize"]["drupal"]["sites_subdir"] = "default"
default["finalize"]["drupal"]["major_version"] = "7"
default["finalize"]["drupal"]["install_profile"] = "standard"
default["finalize"]["drupal"]["account_name"] = "admin"
default["finalize"]["drupal"]["account_pass"] = "admin"
default["finalize"]["drupal"]["preferred_state"] = "stable"
default["finalize"]["drupal"]["theme"] = "omega"
default["finalize"]["drupal"]["modules_preset"] = %w{entity
features
libraries
devel
token
ctools
pathauto
rules
admin_menu}
##Recipes
### default
Completes apache and php configuration.
### web_server
Creates apache viratual host, nginx config, installs and configures varnish
### iptables
Disables iptables firewall if installed
### drupal
Download drupal sources, default modules preset, theme and installs them
| 32.377049 | 83 | 0.517975 | eng_Latn | 0.222747 |
d592fce4ce5bb749a157dd8307d3d89fe15208b1 | 3,170 | md | Markdown | docs/interfaces/_responses_timeline_feed_response_.timelinefeedresponselocation.md | cuonglnhust/instagram-private-api-tcom | 9ee21e8356b7bfef5ee9ddc2fdf72d53a62d93eb | [
"MIT"
] | 2 | 2020-08-29T14:35:20.000Z | 2020-09-09T13:02:54.000Z | docs/interfaces/_responses_timeline_feed_response_.timelinefeedresponselocation.md | cuonglnhust/instagram-private-api-tcom | 9ee21e8356b7bfef5ee9ddc2fdf72d53a62d93eb | [
"MIT"
] | null | null | null | docs/interfaces/_responses_timeline_feed_response_.timelinefeedresponselocation.md | cuonglnhust/instagram-private-api-tcom | 9ee21e8356b7bfef5ee9ddc2fdf72d53a62d93eb | [
"MIT"
] | null | null | null | > **[instagram-private-api-tcom](../README.md)**
[Globals](../README.md) / ["responses/timeline.feed.response"](../modules/_responses_timeline_feed_response_.md) / [TimelineFeedResponseLocation](_responses_timeline_feed_response_.timelinefeedresponselocation.md) /
# Interface: TimelineFeedResponseLocation
## Hierarchy
* **TimelineFeedResponseLocation**
## Index
### Properties
* [address](_responses_timeline_feed_response_.timelinefeedresponselocation.md#address)
* [city](_responses_timeline_feed_response_.timelinefeedresponselocation.md#city)
* [external_source](_responses_timeline_feed_response_.timelinefeedresponselocation.md#external_source)
* [facebook_places_id](_responses_timeline_feed_response_.timelinefeedresponselocation.md#facebook_places_id)
* [lat](_responses_timeline_feed_response_.timelinefeedresponselocation.md#lat)
* [lng](_responses_timeline_feed_response_.timelinefeedresponselocation.md#lng)
* [name](_responses_timeline_feed_response_.timelinefeedresponselocation.md#name)
* [pk](_responses_timeline_feed_response_.timelinefeedresponselocation.md#pk)
* [short_name](_responses_timeline_feed_response_.timelinefeedresponselocation.md#short_name)
## Properties
### address
• **address**: *string*
*Defined in [responses/timeline.feed.response.ts:194](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/timeline.feed.response.ts#L194)*
___
### city
• **city**: *string*
*Defined in [responses/timeline.feed.response.ts:195](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/timeline.feed.response.ts#L195)*
___
### external_source
• **external_source**: *string*
*Defined in [responses/timeline.feed.response.ts:199](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/timeline.feed.response.ts#L199)*
___
### facebook_places_id
• **facebook_places_id**: *number | string*
*Defined in [responses/timeline.feed.response.ts:200](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/timeline.feed.response.ts#L200)*
___
### lat
• **lat**: *number*
*Defined in [responses/timeline.feed.response.ts:198](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/timeline.feed.response.ts#L198)*
___
### lng
• **lng**: *number*
*Defined in [responses/timeline.feed.response.ts:197](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/timeline.feed.response.ts#L197)*
___
### name
• **name**: *string*
*Defined in [responses/timeline.feed.response.ts:193](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/timeline.feed.response.ts#L193)*
___
### pk
• **pk**: *number | string*
*Defined in [responses/timeline.feed.response.ts:192](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/timeline.feed.response.ts#L192)*
___
### short_name
• **short_name**: *string*
*Defined in [responses/timeline.feed.response.ts:196](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/timeline.feed.response.ts#L196)* | 33.368421 | 215 | 0.788328 | ssw_Latn | 0.179215 |
d59392c2bc302122d3e698a18c9a7b59cf36d264 | 2,853 | md | Markdown | Harder/Permutations.md | sachinkatageri/100-plus-python-coding-problems-with-solutions | f714d4e4bf33270ac96b03ab43d45f814d3acf25 | [
"MIT"
] | null | null | null | Harder/Permutations.md | sachinkatageri/100-plus-python-coding-problems-with-solutions | f714d4e4bf33270ac96b03ab43d45f814d3acf25 | [
"MIT"
] | null | null | null | Harder/Permutations.md | sachinkatageri/100-plus-python-coding-problems-with-solutions | f714d4e4bf33270ac96b03ab43d45f814d3acf25 | [
"MIT"
] | null | null | null | # 12.4: Permutation [Premium]
## The Problem
Find all permutation of a given list.
## Hints
In mathematics, the permutation is the way to find all possible order of elements
For example, you have 1,2,3. Now all possible order is
1,2,3
1,3,2
2,1,3
2,3,1
3,1,2
3,2,1
So, the permutation is a way to find all the possible order or sequence of elements.
```python
lst = [2,3,4,6,11,16,7,8]
before = lst[:4]
after = lst[4+1:]
excluding = before + after
print(excluding)
print('-----------------------')
print(lst[:4] + lst[4+1])
```
**[Try it on Programming Hero](https://play.google.com/store/apps/details?id=com.learnprogramming.codecamp)**
## Solution
```python
def get_permutation(lst):
# For an empty list, there is no permutation
if len(lst) == 0:
return []
# list with one element will have only one
# permutation
if len(lst) == 1:
return [lst]
# Create an empty list to store permutation
perms = []
for i in range(len(lst)):
# Extract current elemnt from the list.
current = lst[i]
# Recursively call permutation for the
# remaining list
rem_list = lst[:i] + lst[i+1:]
rem_perm = get_permutation(rem_list)
# Generate permutations by adding first element
for p in rem_perm:
perms.append([current] + p)
return perms
# now test the function
data = [1,2,3]
for perm in get_permutation(data):
print (perm)
```
**[Try it on Programming Hero](https://play.google.com/store/apps/details?id=com.learnprogramming.codecamp)**
## Explanation
In the code, we are getting the current element by lst[i].
Then we create the remaining list by lst[:i] + lst[i+1:]
We stored it in the remaining list named as rem_list. After that, we recursively call the get_permutation. This will give permutation for the rest elements. We stored that in the rem_perm list.
Finally, we have to join the current element with the rest of the list. To do so, we have added [current] + p
The loop variable p is a list. Whereas the current is an element. You can not add
`3 + [2,1]`
That’s why we put current in a list as well so that it becomes a list as well. In the following example,
`[3] + [2, 1]`
This will create [3, 2, 1]. That’s why we did [current] + p to make the final permutation.
This code is harder. It will take a few practices to become comfortable with it.
[](Generate-Sentences.md)
tags: `programming-hero` `python` `python3` `problem-solving` `programming` `coding-challenge` `interview` `learn-python` `python-tutorial` `programming-exercises` `programming-challenges` `programming-fundamentals` `programming-contest` `python-coding-challenges` `python-problem-solving` | 31.7 | 304 | 0.664914 | eng_Latn | 0.984267 |
d5945e2576ff63e3906613b28be7f8016e4a5029 | 294 | md | Markdown | home-cluster/components/pjon-routers/Serial-SoftwareBitBang_Tx_busB/README.md | Halytskyi/SmartThings | b1d599a7025f57586770bec42db436b1c0c7e244 | [
"Apache-2.0"
] | 10 | 2020-11-09T00:17:45.000Z | 2022-02-15T01:04:09.000Z | home-cluster/components/pjon-routers/Serial-SoftwareBitBang_Tx_busB/README.md | Halytskyi/SmartThings | b1d599a7025f57586770bec42db436b1c0c7e244 | [
"Apache-2.0"
] | null | null | null | home-cluster/components/pjon-routers/Serial-SoftwareBitBang_Tx_busB/README.md | Halytskyi/SmartThings | b1d599a7025f57586770bec42db436b1c0c7e244 | [
"Apache-2.0"
] | null | null | null | # Router Serial-SoftwareBitBang Tx busB
Router for receiving messages from remote devices (connected via SoftwareBitBang) to RPi (through Serial).
[pjon-grpc.cfg](pjon-grpc.cfg) - example of configuration file for [PJON gRPC Server](https://github.com/Halytskyi/PJON-gRPC/tree/master/server)
| 49 | 144 | 0.792517 | eng_Latn | 0.650534 |
d59520f1eb94e3661656643ffb90697ee1eebb16 | 5,573 | md | Markdown | README.md | atmo/marshmallow-jsonschema | 3c579c7d3b9c579e8610f7e698d4589604d4884c | [
"MIT"
] | 1 | 2020-01-15T12:05:49.000Z | 2020-01-15T12:05:49.000Z | README.md | atmo/marshmallow-jsonschema | 3c579c7d3b9c579e8610f7e698d4589604d4884c | [
"MIT"
] | null | null | null | README.md | atmo/marshmallow-jsonschema | 3c579c7d3b9c579e8610f7e698d4589604d4884c | [
"MIT"
] | 1 | 2018-04-18T10:28:20.000Z | 2018-04-18T10:28:20.000Z | ## marshmallow-jsonschema: JSON Schema formatting with marshmallow
[](https://travis-ci.org/fuhrysteve/marshmallow-jsonschema)
[](https://coveralls.io/github/fuhrysteve/marshmallow-jsonschema?branch=master)
[](https://github.com/python/black)
marshmallow-jsonschema translates marshmallow schemas into
JSON Schema Draft v7 compliant jsonschema. See http://json-schema.org/
#### Why would I want my schema translated to JSON?
What are the use cases for this? Let's say you have a
marshmallow schema in python, but you want to render your
schema as a form in another system (for example: a web browser
or mobile device).
#### Installation
```
pip install marshmallow-jsonschema
```
#### Some Client tools can render forms using JSON Schema
* https://github.com/brutusin/json-forms
* https://github.com/mozilla-services/react-jsonschema-form
* https://github.com/jdorn/json-editor
* https://github.com/ulion/jsonform
### Examples
Word of caution: starting with marshmallow 3.0.0b7, `.dump()` now directly returns
`data` instead of `(error, data)`, as noted in [marshmallow's changelog](https://github.com/marshmallow-code/marshmallow/blob/8cf1fb8d95f287d626ed0f38967c90198e28b476/CHANGELOG.rst#300b7-2018-02-03).
marshmallow-jsonschema is directly affected by this and the examples below are
for marshmallow<=3.0.0b7. To upgrade to >=3.0.0b7, remove the `.data` from the code.
#### Simple Example
```python
from marshmallow import Schema, fields
from marshmallow_jsonschema import JSONSchema
class UserSchema(Schema):
username = fields.String()
age = fields.Integer()
birthday = fields.Date()
user_schema = UserSchema()
json_schema = JSONSchema()
json_schema.dump(user_schema).data
```
Yields:
```python
{'properties': {'age': {'format': 'integer',
'title': 'age',
'type': 'number'},
'birthday': {'format': 'date',
'title': 'birthday',
'type': 'string'},
'username': {'title': 'username', 'type': 'string'}},
'required': [],
'type': 'object'}
```
#### Nested Example
```python
from marshmallow import Schema, fields
from marshmallow_jsonschema import JSONSchema
from tests import UserSchema
class Athlete(object):
user_schema = UserSchema()
def __init__(self):
self.name = 'sam'
class AthleteSchema(Schema):
user_schema = fields.Nested(JSONSchema)
name = fields.String()
athlete = Athlete()
athlete_schema = AthleteSchema()
athlete_schema.dump(athlete).data
```
#### Complete example Flask application using brutisin/json-forms
This example renders a form not dissimilar to how [wtforms](https://github.com/wtforms/wtforms) might render a form.
However rather than rendering the form in python, the JSON Schema is rendered using the
javascript library [brutusin/json-forms](https://github.com/brutusin/json-forms).
```python
from flask import Flask, jsonify
from marshmallow import Schema, fields
from marshmallow_jsonschema import JSONSchema
app = Flask(__name__)
class UserSchema(Schema):
name = fields.String()
address = fields.String()
@app.route('/schema')
def schema():
schema = UserSchema()
return jsonify(JSONSchema().dump(schema).data)
@app.route('/')
def home():
return '''<!DOCTYPE html>
<head>
<link rel="stylesheet" href="https://cdn.jsdelivr.net/brutusin.json-forms/1.3.0/css/brutusin-json-forms.css"><Paste>
<script src="https://code.jquery.com/jquery-1.12.1.min.js" integrity="sha256-I1nTg78tSrZev3kjvfdM5A5Ak/blglGzlaZANLPDl3I=" crossorigin="anonymous"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/underscore.string/3.3.4/underscore.string.min.js"></script>
<script src="https://cdn.jsdelivr.net/brutusin.json-forms/1.3.0/js/brutusin-json-forms.min.js"></script>
<script>
$(document).ready(function() {
$.ajax({
url: '/schema'
, success: function(data) {
var container = document.getElementById('myform');
var BrutusinForms = brutusin["json-forms"];
var bf = BrutusinForms.create(data);
bf.render(container);
}
});
});
</script>
</head>
<body>
<div id="myform"></div>
</body>
</html>
'''
if __name__ == '__main__':
app.run(host='0.0.0.0', debug=True)
```
### Advanced usage
#### Custom Type support
Simply add a `_jsonschema_type_mapping` method to your field
so we know how it ought to get serialized to JSON Schema.
A common use case for this is creating a dropdown menu using
enum (see Gender below).
```python
class Colour(fields.Field):
def _jsonschema_type_mapping(self):
return {
'type': 'string',
}
def _serialize(self, value, attr, obj):
r, g, b = value
r = hex(r)[2:]
g = hex(g)[2:]
b = hex(b)[2:]
return '#' + r + g + b
class Gender(fields.String):
def _jsonschema_type_mapping(self):
return {
'type': 'string',
'enum': ['Male', 'Female']
}
class UserSchema(Schema):
name = fields.String(required=True)
favourite_colour = Colour()
gender = Gender()
schema = UserSchema()
json_schema = JSONSchema()
json_schema.dump(schema).data
```
| 28.146465 | 199 | 0.683294 | eng_Latn | 0.509992 |
d5956b9d042f243e20ebe43fac286367523819c4 | 811 | md | Markdown | CONTRIBUTING.md | dhanushkasathurusinghe/issuehub.io | fafca3d8ceaed35966e6ddfedfbdf821335fe537 | [
"MIT"
] | 1 | 2020-06-16T05:29:23.000Z | 2020-06-16T05:29:23.000Z | CONTRIBUTING.md | dhanushkasathurusinghe/issuehub.io | fafca3d8ceaed35966e6ddfedfbdf821335fe537 | [
"MIT"
] | 2 | 2020-07-25T08:52:08.000Z | 2021-09-28T05:06:55.000Z | CONTRIBUTING.md | dhanushkasathurusinghe/issuehub.io | fafca3d8ceaed35966e6ddfedfbdf821335fe537 | [
"MIT"
] | null | null | null | # Contributing to **issuehub.io**
## Quick guide:
1. Fork the repo.
2. Add a test for your change. Only styling, documentation and refactoring changes (that are already covered by tests) don't require any new tests. If you are adding functionality or fixing a bug, you need a test! Also, no need to test rails!
3. Make the test pass.
4. Commit, with a meaningful describing message. This is very important!
5. Push to your fork and submit a pull request.
6. Wait for comments or feedback!
Syntax:
* no trailing whitespace. Blank lines should not have any space.
* my_method(my_arg) or my_method arguments but definitely not my_method( my_arg )
* a = b and not a=b.
* aim for 1.9 hash syntax - `{ dog: "Akira" }` rather than `{ :dog => "Akira" }`
* follow the conventions you see used in the source already.
| 42.684211 | 242 | 0.734895 | eng_Latn | 0.99887 |
d59591c54581ffc1e1ef18b732fc69b8dc997523 | 4,956 | md | Markdown | docs/relational-databases/system-catalog-views/sys-server-resource-stats-azure-sql-database.md | zelanko/sql-docs.es-es | e8de33fb5b7b566192c5fd38f7d922aca7fa3840 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-catalog-views/sys-server-resource-stats-azure-sql-database.md | zelanko/sql-docs.es-es | e8de33fb5b7b566192c5fd38f7d922aca7fa3840 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-catalog-views/sys-server-resource-stats-azure-sql-database.md | zelanko/sql-docs.es-es | e8de33fb5b7b566192c5fd38f7d922aca7fa3840 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: sys.server_resource_stats (Azure SQL Database)
title: sys.server_resource_stats (Azure SQL Database) | Microsoft Docs
ms.custom: ''
ms.date: 06/28/2018
ms.service: sql-database
ms.topic: language-reference
f1_keywords:
- resource_stats
- sys.resource_stats
- sys.resource_stats_TSQL
- resource_stats_TSQL
dev_langs:
- TSQL
helpviewer_keywords:
- sys.resource_stats
- resource_stats
ms.assetid: ''
author: jovanpop-msft
ms.author: jovanpop
monikerRange: =azuresqldb-current
ms.openlocfilehash: 142269f7c3cd8a5a1e764e2e48cf41f83490bd76
ms.sourcegitcommit: 1a544cf4dd2720b124c3697d1e62ae7741db757c
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 12/14/2020
ms.locfileid: "97464606"
---
# <a name="sysserver_resource_stats-azure-sql-database"></a>sys.server_resource_stats (Azure SQL Database)
[!INCLUDE[Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/asdb-asdbmi.md)]
Devuelve los datos de uso de CPU, e/s y almacenamiento de Azure SQL Instancia administrada. Los datos se recopilan y se agregan en intervalos de cinco minutos. Hay una fila por cada 15 segundos de informes. Los datos devueltos incluyen el uso de CPU, el tamaño de almacenamiento, el uso de e/s y la SKU. Los datos históricos se conservan durante 14 días aproximadamente.
La vista **Sys.server_resource_stats** tiene definiciones diferentes en función de la versión de Azure SQL instancia administrada con la que está asociada la base de datos. Tenga en cuenta estas diferencias y cualquier modificación que requiera la aplicación al actualizar a una nueva versión de servidor.
En la tabla siguiente se describen las columnas disponibles en un servidor v12:
|Columnas|Tipo de datos|Descripción|
|----------------------------|---------------|-----------------|
|start_time|**datetime2**|Hora UTC que indica el inicio del intervalo de informes de quince segundos|
|end_time|**datetime**|Hora UTC que indica el final del intervalo de informes de quince segundos|
|resource_type|Nvarchar(128)|Tipo del recurso para el que se proporcionan las métricas|
|resource_name|nvarchar(128)|Nombre del recurso.|
|sku|nvarchar(128)|Instancia administrada nivel de servicio de la instancia. Los posibles valores son los siguientes: <br><ul><li>De uso general</li></ul><ul><li>Crítico para la empresa</li></ul>|
|hardware_generation|nvarchar(128)|Identificador de generación de hardware: como gen 4 o gen 5|
|virtual_core_count|int|Representa el número de núcleos virtuales por instancia (8, 16 o 24 en versión preliminar pública)|
|avg_cpu_percent|decimal (5, 2)|Uso de proceso promedio en porcentaje del límite del nivel de servicio Instancia administrada utilizado por la instancia de. Se calcula como suma del tiempo de CPU de todos los grupos de recursos para todas las bases de datos de la instancia y dividido por el tiempo de CPU disponible para ese nivel en el intervalo especificado.|
|reserved_storage_mb|bigint|Almacenamiento reservado por instancia (cantidad de espacio de almacenamiento que el cliente compró para la instancia administrada)|
|storage_space_used_mb|decimal (18, 2)|Almacenamiento utilizado por todos los archivos de base de datos en una instancia administrada (incluidas las bases de datos de usuario y del sistema)|
|io_request|bigint|Número total de operaciones físicas de e/s dentro del intervalo|
|io_bytes_read|bigint|Número de bytes físicos leídos dentro del intervalo|
|io_bytes_written|bigint|Número de bytes físicos escritos en el intervalo|
> [!TIP]
> Para más información sobre estos límites y los niveles de servicio, consulte los temas [instancia administrada niveles de servicio](/azure/sql-database/sql-database-managed-instance#managed-instance-service-tiers).
## <a name="permissions"></a>Permisos
Esta vista está disponible para todos los roles de usuario con permisos para conectarse a la base de datos **maestra** .
## <a name="remarks"></a>Comentarios
Los datos devueltos por **Sys.server_resource_stats** se expresan como el total que se usa en bytes o megabytes (indicados en nombres de columna) distintos de avg_cpu, que se expresa como un porcentaje de los límites máximos permitidos para el nivel de servicio/nivel de rendimiento que se está ejecutando.
## <a name="examples"></a>Ejemplos
El ejemplo siguiente devuelve todas las bases de datos cuyo promedio de uso de proceso fue al menos del 80 % durante la semana pasada.
```sql
DECLARE @s datetime;
DECLARE @e datetime;
SET @s= DateAdd(d,-7,GetUTCDate());
SET @e= GETUTCDATE();
SELECT resource_name, AVG(avg_cpu_percent) AS Average_Compute_Utilization
FROM sys.server_resource_stats
WHERE start_time BETWEEN @s AND @e
GROUP BY resource_name
HAVING AVG(avg_cpu_percent) >= 80
```
## <a name="see-also"></a>Consulte también
[Instancia administrada niveles de servicio](/azure/sql-database/sql-database-managed-instance#managed-instance-service-tiers) | 61.185185 | 370 | 0.778854 | spa_Latn | 0.944291 |
d595cf557f960efcfa431c846060e515a8c90e70 | 5,571 | md | Markdown | README.md | hyo-choi/javascript-baseball-precourse | 4c2d99acb84c90196d3a30bd9a49db025a46b842 | [
"MIT"
] | null | null | null | README.md | hyo-choi/javascript-baseball-precourse | 4c2d99acb84c90196d3a30bd9a49db025a46b842 | [
"MIT"
] | null | null | null | README.md | hyo-choi/javascript-baseball-precourse | 4c2d99acb84c90196d3a30bd9a49db025a46b842 | [
"MIT"
] | null | null | null | # ⚾ 미션 - 숫자 야구 게임
## 📝 이론 정리
### 모듈화 할 때 유의점
- 참고 1: [모듈화(javascript.info)](https://ko.javascript.info/import-export)
참고 2: [모듈화(MDN)](https://developer.mozilla.org/ko/docs/Web/JavaScript/Guide/Modules)
- 모듈을 포함한 스크립트를 HTML 파일에 포함한 경우, 로컬(예를 들어 file://URL)에서는 JS의 모듈 보안 요구사항으로 인해 CORS 오류가 발생한다. 따라서 모듈이 있는 HTML은 서버를 통해 테스트 해야 한다.
- 그 외 일반 스크립트와 다른 점은 [MDN](https://developer.mozilla.org/ko/docs/Web/JavaScript/Guide/Modules#other_differences_between_modules_and_standard_scripts) 참고.
### 클로저란?
- 참고 1: [클로저](https://hyunseob.github.io/2016/08/30/javascript-closure/)
참고 2: [클로저(MDN)](https://developer.mozilla.org/ko/docs/Web/JavaScript/Closures)
- 클로저는 함수와 함수가 선언된 어휘적 환경의 조합이다.
- 클로저에서 property로 선언된 것은 외부 scope에서도 접근하고 사용할 수 있다.
- 클로저를 이용하면 [private 변수, 메소드를 사용할 수 있다.](https://developer.mozilla.org/ko/docs/Web/JavaScript/Closures#%ED%81%B4%EB%A1%9C%EC%A0%80%EB%A5%BC_%EC%9D%B4%EC%9A%A9%ED%95%B4%EC%84%9C_%ED%94%84%EB%9D%BC%EC%9D%B4%EB%B9%97_%EB%A9%94%EC%86%8C%EB%93%9C_private_method_%ED%9D%89%EB%82%B4%EB%82%B4%EA%B8%B0)
### 콜백이란?
- 참고: [도대체 콜백이 뭔데?](https://medium.com/@oasis9217/%EB%B2%88%EC%97%AD-javascript-%EB%8F%84%EB%8C%80%EC%B2%B4-%EC%BD%9C%EB%B0%B1%EC%9D%B4-%EB%AD%94%EB%8D%B0-65bb82556c56)
- 콜백 함수는 다른 함수에 인자로 넘겨지는 함수이다.
- 기본적으로 콜백 함수의 this는 전역 객체에 바인딩되어 있으나, addEventListener를 통해 등록된 handler 함수의 this는 [event target에 바인딩](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#the_value_of_this_within_the_handler) 되어있다. 따라서 event가 실행되었을 때 this로 event target 대신 객체를 참조하고 싶다면 [bind 함수](https://developer.mozilla.org/ko/docs/Web/JavaScript/Reference/Global_Objects/Function/bind)를 이용해 새로운 함수를 콜백으로 등록해주어야 한다.
### 이 과제에서
- ``function BaseballGame()``은 ``new``를 이용하여 호출하는 경우 [생성자 함수](https://ko.javascript.info/constructor-new#ref-257)로 취급되고 ``this``는 생성자 함수가 암묵적으로 생성한 빈 객체에 바인딩된다. 따라서 ``const game = new BaseballGame(); console.log(game);``을 추가해보면 생성된 BaseballGame 객체의 this 정보를 확인할 수 있다.
- new를 사용하지 않고 ``BaseballGame()`` 함수를 호출하면 ``this``는 [전역 객체에 바인딩](https://poiemaweb.com/js-this#33-%EC%83%9D%EC%84%B1%EC%9E%90-%ED%95%A8%EC%88%98%EC%97%90-new-%EC%97%B0%EC%82%B0%EC%9E%90%EB%A5%BC-%EB%B6%99%EC%9D%B4%EC%A7%80-%EC%95%8A%EA%B3%A0-%ED%98%B8%EC%B6%9C%ED%95%A0-%EA%B2%BD%EC%9A%B0)된다.
그런데 ``function BaseballGame()``의 경우 첫 글자가 영문 대문자이므로 **생성자 함수라고 해석하는 것이 옳다.** 따라서 해당 함수의 내용은 생성자 함수의 맥락에서 작성해야 하고 사용자는 이 함수를 new 없이 호출하지 않아야 한다.
- 이 과제는 함수를 어떻게 구성하였는지, 함수를 어떤 방식으로 호출하는지에 따라 정상적으로 동작할 수도 아닐 수도 있다. 모듈화, 클로저, this 바인딩에 대해 정확히 이해하고 작성해야 한다. 기능을 모두 구현한 후 자세한 내용을 찾아보았더니 고칠 부분이 여럿 보였기 때문에 앞으로는 필요한 개념을 앞서 학습하고 코드를 작성하도록 해야겠다.
<br>
## ✅ 구현할 기능 목록
- 컴퓨터 측 정답 설정
- 1부터 9까지
- 서로 다른 수로 이루어진
- 세 자리 숫자
- click 이벤트 처리
- 유저 측 입력 받기
- 입력값 확인
1. 유효성 검사
- 잘못된 입력에 대한 에러 처리
2. 힌트 생성
- 정답 처리
- 메시지 + button 생성
- button 클릭 시 리셋 이벤트 실행 후 메시지 + button 삭제
<br>
## 🎯 기능 요구사항
- 기본적으로 1부터 9까지 서로 다른 수로 이루어진 3자리의 수를 맞추는 게임이다.
- 같은 수가 같은 자리에 있으면 `스트라이크`, 다른 자리에 있으면 `볼`, 같은 수가 전혀 없으면 `낫싱`이란 힌트를 얻고, 그 힌트를 이용해서 먼저 상대방(컴퓨터)의 수를 맞추면 승리한다.
- 예) 상대방(컴퓨터)의 수가 425일 때
- 123을 제시한 경우 : 1스트라이크
- 456을 제시한 경우 : 1볼 1스트라이크
- 789를 제시한 경우 : 낫싱
- 위 숫자 야구게임에서 상대방의 역할을 컴퓨터가 한다. 컴퓨터는 1에서 9까지 서로 다른 임의의 수 3개를 선택한다. 게임 플레이어는 컴퓨터가 생각하고 있는 3개의 숫자를 입력하고, 컴퓨터는 입력한 숫자에 대한 결과를 출력한다.
- 이 같은 과정을 반복해 컴퓨터가 선택한 3개의 숫자를 모두 맞히면 게임이 종료된다.
- 게임을 종료한 후 게임을 다시 시작할 수 있다.
- 게임을 종료한 후 id가 `game-restart-button`인 버튼을 클릭함으로써 게임을 다시 시작할 수 있다.
- `예) <button id="game-restart-button">재시작</button>`
<br>
## 💻 프로그래밍 실행 결과
<br>
## ✅ 프로그래밍 요구사항
- `play`(컴퓨터의 랜덤 값, 유저의 입력 값) 메서드를 만들어 게임을 진행한다.
- `play`메서드는 `String`으로 결과값을 return 한다.
- `index.js`에서 아래의 function 또는 class 형태를 활용한다.
```javascript
export default function BaseballGame() {
this.play = function (computerInputNumbers, userInputNumbers) {
return "결과 값 String";
};
}
export default class BaseballGame {
play(computerInputNumbers, userInputNumbers) {
return "결과 값 String";
}
}
// 예시
play(123, 456); // '낫싱'
play(123, 345); // '1볼'
play(123, 432); // '2볼'
play(123, 312); // '3볼'
play(123, 145); // '1스트라이크'
play(123, 134); // '1볼 1스트라이크'
play(123, 132); // '2볼 1스트라이크'
play(123, 124); // '2스트라이크'
```
- 스트라이크와 볼이 같이 있는 경우 볼을 먼저쓰고, 스트라이크를 쓴다.
- 사용자가 잘못된 입력 값을 작성한 경우 `alert`을 이용해 메시지를 보여주고, 재입력할 수 있게 한다.
- 외부 라이브러리(jQuery, Lodash 등)를 사용하지 않고, 순수 Vanilla JS로만 구현한다.
- **자바스크립트 코드 컨벤션을 지키면서 프로그래밍** 한다
- [https://google.github.io/styleguide/jsguide.html](https://google.github.io/styleguide/jsguide.html)
- [https://ui.toast.com/fe-guide/ko_CODING-CONVENSION/](https://ui.toast.com/fe-guide/ko_CODING-CONVENTION)
- **indent(인덴트, 들여쓰기) depth를 3이 넘지 않도록 구현한다. 2까지만 허용**한다.
- 예를 들어 while문 안에 if문이 있으면 들여쓰기는 2이다.
- 힌트: indent(인덴트, 들여쓰기) depth를 줄이는 좋은 방법은 함수(또는 메소드)를 분리하면 된다.
- **함수(또는 메소드)가 한 가지 일만 하도록 최대한 작게** 만들어라.
<br>
## 📝 미션 저장소 및 진행 요구사항
- 저장소를 fork/clone해 시작한다.
- **기능을 구현하기 전에 README.md 파일에 구현할 기능 목록**을 정리해 추가한다.
- **git의 commit 단위는 앞 단계에서 README.md 파일에 정리한 기능 목록 단위로 추가**한다.
- [프리코스 과제 제출](https://github.com/woowacourse/woowacourse-docs/tree/master/precourse) 문서 절차를 따라 미션을 제출한다.
<br>
## 🔗 참고 링크
미션 진행이 어렵다면 아래 링크를 참고한다.
- DOM
- [MDN DOM](https://developer.mozilla.org/ko/docs/Web/API/Document_Object_Model/%EC%86%8C%EA%B0%9C)
- alert
- [MDN alert](https://developer.mozilla.org/ko/docs/Web/API/Window/alert)
- javascript module
- [module](https://ko.javascript.info/modules-intro)
- event
- [이벤트](https://ko.javascript.info/introduction-browser-events)
- [이벤트 위임](https://ko.javascript.info/event-delegation)
| 41.887218 | 409 | 0.688745 | kor_Hang | 1 |
d596a293e6b461d4fe43b398aff5eb76694bdaa0 | 807 | md | Markdown | README.md | krux02/variant | dd82569960009467d4b3a42dbea393101b9dec13 | [
"MIT"
] | 40 | 2015-12-25T01:19:50.000Z | 2022-03-14T05:19:15.000Z | README.md | krux02/variant | dd82569960009467d4b3a42dbea393101b9dec13 | [
"MIT"
] | 5 | 2016-01-07T16:38:37.000Z | 2022-02-19T12:54:17.000Z | README.md | krux02/variant | dd82569960009467d4b3a42dbea393101b9dec13 | [
"MIT"
] | 4 | 2016-07-09T15:38:22.000Z | 2020-09-27T09:16:40.000Z | # variant [](https://travis-ci.org/yglukhov/variant) [](https://github.com/yglukhov/nimble-tag)
Variant type and type matching for Nim
```nim
import variant
var v = newVariant(5)
assert v.ofType(int)
assert v.get(int) == 5
v = newVariant(3.0)
assert v.ofType(float)
assert v.get(float) == 3.0
v = newVariant(@[1, 2, 3])
assert v.ofType(seq[int])
assert v.get(seq[int])[1] == 2
```
Matching:
```nim
var v = newVariant(@[1, 2, 3])
assert v.ofType(seq[int])
variantMatch case v as u
of int:
echo "u is int: ", u
of seq[int]:
echo "u is seq[int]: ", u
else:
echo "dont know what v is"
```
Will output:
```
u is seq[int]: @[1, 2, 3]
```
| 22.416667 | 253 | 0.665428 | kor_Hang | 0.126915 |
d596c6a96b4542193e6e4f26c7e2eade3d092522 | 325 | md | Markdown | docs/guides/advanced/README.md | JamesKennewell/OXRS-IO-WEBSITE | baceb791316623412f12c5a03a05a29bac6ea2e5 | [
"BSD-2-Clause"
] | 1 | 2021-09-02T07:16:13.000Z | 2021-09-02T07:16:13.000Z | docs/guides/advanced/README.md | JamesKennewell/OXRS-IO-WEBSITE | baceb791316623412f12c5a03a05a29bac6ea2e5 | [
"BSD-2-Clause"
] | 20 | 2021-09-07T00:19:21.000Z | 2022-03-07T03:40:50.000Z | docs/guides/advanced/README.md | JamesKennewell/OXRS-IO-WEBSITE | baceb791316623412f12c5a03a05a29bac6ea2e5 | [
"BSD-2-Clause"
] | 11 | 2021-09-12T04:45:38.000Z | 2022-02-09T08:55:48.000Z | ---
tags: [""]
---
# Advanced Guide
Includes:
## Software
- [Home Assistant](/guides/advanced/home_assistant.html) Sample automations to work with StateMonitor
- node red
- mqtt
## Building Firmware
- Arduino
- PlatformIO
## Ethernet Cabling
::: tip TODO
Content to be created for this page
:::
| 15.47619 | 103 | 0.652308 | eng_Latn | 0.790171 |
d597873123667f01b53fe46b90251d033d671994 | 5,379 | md | Markdown | published/202112/20210927 Bash Shell Scripting for beginners (Part 1).md | hwlife/TranslateProject | 1f4292dc0f735a54a240f9eb3e1bd10f2cf70424 | [
"Apache-2.0"
] | null | null | null | published/202112/20210927 Bash Shell Scripting for beginners (Part 1).md | hwlife/TranslateProject | 1f4292dc0f735a54a240f9eb3e1bd10f2cf70424 | [
"Apache-2.0"
] | 1 | 2020-02-03T14:45:50.000Z | 2020-02-03T14:45:50.000Z | published/202112/20210927 Bash Shell Scripting for beginners (Part 1).md | CN-QUAN/TranslateProject | 89f982acd224c24de4431ce147aa1dedaa70b206 | [
"Apache-2.0"
] | null | null | null | [#]: subject: "Bash Shell Scripting for beginners (Part 1)"
[#]: via: "https://fedoramagazine.org/bash-shell-scripting-for-beginners-part-1/"
[#]: author: "zexcon https://fedoramagazine.org/author/zexcon/"
[#]: collector: "lujun9972"
[#]: translator: "unigeorge"
[#]: reviewer: "wxy"
[#]: publisher: "wxy"
[#]: url: "https://linux.cn/article-14131-1.html"
Bash Shell 脚本新手指南（一）
======
![][1]
如标题所示，本文将涵盖面向初学者的 Bash Shell 脚本知识。虽然本文没有回顾 Bash 的历史，但是有很多资源能够便于读者了解相关内容，读者也可以直接访问 <https://www.gnu.org/software/bash/> 上的 GNU 项目。我们会从了解一些非常基本的概念开始，然后再将相关知识综合起来。
### 创建脚本文件
首先来创建一个脚本文件。我们要确保当前目录为家目录。
```
cd ~
```
在主目录中创建示例文件。文件名可以是任意名称，本文使用 `learnToScript.sh` 作为文件名。
```
touch learnToScript.sh
```
此时家目录中就生成了一个名为 `learnToScript.sh` 的文件。输入以下命令以检验该文件是否存在，还可以注意到其权限是 `-rw-rw-r–`。
```
[zexcon@trinity ~]$ ls -l
total 7
drwxr-xr-x. 1 zexcon zexcon 90 Aug 30 13:08 Desktop
drwxr-xr-x. 1 zexcon zexcon 80 Sep 16 08:53 Documents
drwxr-xr-x. 1 zexcon zexcon 1222 Sep 16 08:53 Downloads
-rw-rw-r--. 1 zexcon zexcon 70 Sep 17 10:10 learnToScript.sh
drwxr-xr-x. 1 zexcon zexcon 0 Jul 7 16:04 Music
drwxr-xr-x. 1 zexcon zexcon 318 Sep 15 13:53 Pictures
drwxr-xr-x. 1 zexcon zexcon 0 Jul 7 16:04 Public
drwxr-xr-x. 1 zexcon zexcon 0 Jul 7 16:04 Videos
[zexcon@trinity ~]$
```
正式开始之前还有一件事要做。可以试一下在没有写入任何内容的情况下执行脚本，命令行输入以下内容：
```
./learnToScript.sh
```
```
[zexcon ~]$ ./learnToScript.sh
bash: ./learnToScript.sh: Permission denied
```
提示权限被拒绝，因为该文件没有执行权限。所以你需要更改文件的权限才能执行脚本。如果你不熟悉权限相关知识，建议阅读 [Paul W. Frields][4] 写的 Fedora 杂志文章。
- [命令行小知识：权限][5]
- [命令行小知识：深入权限][6]
假定我们已经了解了权限相关知识，回到终端更改 `learnToScript.sh` 文件，增加执行权限。输入以下内容：
```
chmod 755 learnToScript.sh
```
```
[zexcon@trinity ~]$ ls -l
total 7
drwxr-xr-x. 1 zexcon zexcon 90 Aug 30 13:08 Desktop
drwxr-xr-x. 1 zexcon zexcon 80 Sep 16 08:53 Documents
drwxr-xr-x. 1 zexcon zexcon 1222 Sep 16 08:53 Downloads
-rwxr-xr-x. 1 zexcon zexcon 70 Sep 17 10:10 learnToScript.sh
drwxr-xr-x. 1 zexcon zexcon 0 Jul 7 16:04 Music
drwxr-xr-x. 1 zexcon zexcon 318 Sep 15 13:53 Pictures
drwxr-xr-x. 1 zexcon zexcon 0 Jul 7 16:04 Public
drwxr-xr-x. 1 zexcon zexcon 0 Jul 7 16:04 Videos
[zexcon@trinity ~]$
```
好的，现在一切准备就绪，你已经获得了 `learnToScript.sh` 命令的读取、写入和执行权限 （`-rwxr-xr-x`）。
### 编辑脚本文件
下面的内容需要你熟悉 `vim` 或其他类似的文本编辑器，本文选用 `vim`。在命令提示符下输入以下内容：
```
vim learnToScript.sh
```
这会打开一个空的文本文件，里面有一堆波浪号。键盘输入 `i` 将进入插入模式。通过查看终端窗口的左下角，你可以确认它处于该模式。（友情推荐，[nano][7] 编辑器也很不错。）
接下来我们要确保文件被正确的解释器识别。因此，输入 `#!` 和 bash 的目录 `/bin/bash`：
```
#!/bin/bash
```
本文教程步骤的最后一件事是保存文档。按 `Esc` 退出输入模式，然后按 `Shift+:`。在冒号处输入 `wq`，按下回车键，就会写入（`w`）文件并退出（`q`）`vim` 编辑器。
> 使用 `vim` 时要记住，要想写入文档，就需要输入 `i`，此时你会在底部看到 `–INSERT–`。要保存文档，就需要按 `Esc` 退出输入模式，然后按 `Shift+:`，输入 `w` 写入文件；或者按 `Esc`，然后 `Shift+:` 输入 `q`，实现退出而不保存；或者将 `wq` 连在一起，可以实现写入并关闭文件。`Esc` 本身就只是退出插入模式。你可以在其 [官方网站][8] 或 [教程网站][9] 上找到更多关于 `vim` 的信息。
### 开始正式写脚本
#### echo 命令
`echo` 命令用于向终端返回一些信息，可以使用单引号、双引号或不使用引号。那么让我们用一个传统的 Hello World 来试试它！
```
#!/bin/bash
echo Hello World!
echo 'Hello World!'
echo "Hello World!"
```
```
[zexcon ~]$ ./learnToScript.sh
Hello World!
Hello World!
Hello World!
[zexcon ~]$
```
注意，上述三行得到了相同的结果。使用单引号、双引号或不使用引号的结果不是一定相同的，但在这个基本脚本中确实得到了同样的结果。在某些情况下，引号的类型不同会导致结果差异。至此恭喜你编写了第一个 Bash 脚本。当你继续创建更多脚本并放飞你的想法时，可能会需要了解以下更多的知识。
#### 命令替换 $( ) 和 \` \`
命令替换可以实现以下效果：获取在命令行执行命令的结果，并将该结果写入变量。例如，如果在命令提示符下输入 `ls`，可以获得当前工作目录的列表。我们用这个命令来实践一下。命令替换选项有两个，请注意：第一个选项使用键盘左侧 `Tab` 键上方的反引号。它与波浪号 `~` 在一个键位上。第二个选项使用 shell 变量。
```
#!/bin/bash
command1=`ls`
echo $command1
command2=$(ls)
echo $command2
```
```
[zexcon ~]$ ./learnToScript.sh
Desktop Documents Downloads learnToScript.sh Music Pictures Public snap Videos
Desktop Documents Downloads learnToScript.sh Music Pictures Public snap Videos
[zexcon ~]$
```
注意变量、等号和命令开头之间不要有空格。使用这两个选项得到的结果是完全相同的。请注意，变量需要以美元符号开头。如果你忘记了，并且回显了不带美元符号的命令变量，会只输出命令的名称，如下所示：
```
#!/bin/bash
command1=`ls`
echo command1
command2=$(ls)
echo command2
```
```
[zexcon ~]$ ./learnToScript.sh
command1
command2
[zexcon ~]$
```
#### 双括号 (())
那么双括号有什么用呢？ 很简单，双括号用于数学方程式。
```
#!/bin/bash
echo $((5+3))
echo $((5-3))
echo $((5*3))
echo $((5/3))
```
```
[zexcon ~]$ ./learnToScript.sh
8
2
15
1
[zexcon ~]$
```
### 结语
至此，我们已经创建了第一个脚本。我们知道了如何执行多个命令：将它们放在一个脚本中并运行，就可以获得结果。下一篇文章会继续讨论，了解输入和输出的重定向、管道命令、使用双括号或者添加注释等知识。
--------------------------------------------------------------------------------
via: https://fedoramagazine.org/bash-shell-scripting-for-beginners-part-1/
作者：[zexcon][a]
选题：[lujun9972][b]
译者：[unigeorge](https://github.com/unigeorge)
校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://fedoramagazine.org/author/zexcon/
[b]: https://github.com/lujun9972
[1]: https://fedoramagazine.org/wp-content/uploads/2021/09/bash_shell_scripting_pt1-1536x650.jpg
[2]: https://unsplash.com/@nbandana?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText
[3]: https://unsplash.com/s/photos/shell-scripting?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText
[4]: http://pfrields.id.fedoraproject.org/
[5]: https://fedoramagazine.org/command-line-quick-tips-permissions/
[6]: https://fedoramagazine.org/command-line-quick-tips-more-about-permissions/
[7]: https://fedoramagazine.org/gnu-nano-minimalist-console-editor/
[8]: https://www.vim.org/docs.php
[9]: https://linuxhandbook.com/basic-vim-commands/
| 24.788018 | 233 | 0.705521 | yue_Hant | 0.882253 |
d59797bc6826b71189d13c68a650114627a46627 | 1,419 | md | Markdown | README.md | Zhang-Hongda/transform_publisher | d7057cb1ac5d83075ab486ed90dd987cf76af690 | [
"MIT"
] | 1 | 2020-05-13T14:46:00.000Z | 2020-05-13T14:46:00.000Z | README.md | Zhang-Hongda/transform_publisher | d7057cb1ac5d83075ab486ed90dd987cf76af690 | [
"MIT"
] | null | null | null | README.md | Zhang-Hongda/transform_publisher | d7057cb1ac5d83075ab486ed90dd987cf76af690 | [
"MIT"
] | null | null | null | transform_publisher
==============================
****
|Author|Zhang Hongda|
|------|-----------------|
|E-mail|[email protected]|
|Institute|Harbin Institute of Technology|
****
### Description
A tf broadcaster with a graphical user interface.
### Installation
Step 1: clone the repository into your own workspace
```
cd ${PATH_TO YOUR_WORKSPACE_FOLDER}/src
git clone https://github.com/Zhang-Hongda/transform_publisher
```
Step 2: building
```
catkin_make
```
Step 3: activate the workspace
```
source ${PATH_TO YOUR_WORKSPACE_FOLDER}/devel/setup.bash
```
### Strat
To start the program, run:
```
roscore
rosrun transform_publisher transform_publisher
```
### GUI
The interface should look like this:
### Usage
* The "__Ros Master__" panel
* Users can specify the __url__ and __ip__ for connecting the ros master.
* Check "__Use environment variables__" if you want to use the environmental configuration of your computer (recommended).
* Check "__Remember settings on stratup__" to allows the system to load the current configuration during startup next time.
* The "__tf publisher__" panel
* Users can specify the __frame_id__ and __child frame_id__ for the messages publisher.
* Modify the values in __x__,__y__,__z__,__row__,__pitch__,__yaw__ to change the tf messages.
* Click on "__publish__" button to publish tf messages.
| 31.533333 | 127 | 0.729387 | eng_Latn | 0.9238 |
d597dc7f109c7bc1eecbda4dbc4986ccf87cae9c | 1,053 | md | Markdown | data/blog/item_2226.md | VallyPepyako/wsd-jam | daa81b7f253bc585002f339e78dc1b42c537ce63 | [
"MIT"
] | null | null | null | data/blog/item_2226.md | VallyPepyako/wsd-jam | daa81b7f253bc585002f339e78dc1b42c537ce63 | [
"MIT"
] | null | null | null | data/blog/item_2226.md | VallyPepyako/wsd-jam | daa81b7f253bc585002f339e78dc1b42c537ce63 | [
"MIT"
] | null | null | null | ---
path: "/blog/page_2226"
title: "Part 2226"
---
ри раза нас опрокидывали, как карточных солдатиков. Ваши гренадеры были великолепны, ей Богу. Я видел, как их ряды шесть раз смыкались, и как они выступали точно на парад. Чудный народ! Наш Неаполитанский король, который в этих делах собаку съел, кричал им: браво! — Га, га, так вы наш брат солдат! — Тем лучше, тем лучше, господин Пьер. Страшны в сражениях, любезны с красавицами, вот французы, господин Пьер. Не правда ли?
1 — Кстати, скажите пожалуста, правда ли, что все женщины уехали из Москвы? Странная мысль, чего они боялись?
— Разве французские дамы не уехали бы из Парижа, если бы русские вошли в него?
2 Ха — ха — ха!.. А вот сказал штуку.
— Париж?... Но Париж... Париж...
— Париж — столица мира...
3 Ну, если б вы мне не сказали, что вы русский, я бы побился об заклад, что вы парижанин. В вас что-то есть, эта...
369— Oh ça se voit bien. Paris!... Un homme qui ne connait pas Paris, est un sauvage. Un Parisien, ça se sent à deux lieux. Paris, c’est Talma, la Duschénois, Potier, la Sor
| 75.214286 | 424 | 0.730294 | rus_Cyrl | 0.970263 |
d5988b3db1321ab01217a862e5006c5dfa70be79 | 218 | md | Markdown | _watches/M20210317_034344_TLP_8.md | Meteoros-Floripa/meteoros.floripa.br | 7d296fb8d630a4e5fec9ab1a3fb6050420fc0dad | [
"MIT"
] | 5 | 2020-01-22T17:44:06.000Z | 2020-01-26T17:57:58.000Z | _watches/M20210317_034344_TLP_8.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | null | null | null | _watches/M20210317_034344_TLP_8.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | 2 | 2020-05-19T17:06:27.000Z | 2020-09-04T00:00:43.000Z | ---
layout: watch
title: TLP8 - 17/03/2021 - M20210317_034344_TLP_8T.jpg
date: 2021-03-17 03:43:44
permalink: /2021/03/17/watch/M20210317_034344_TLP_8
capture: TLP8/2021/202103/20210316/M20210317_034344_TLP_8T.jpg
---
| 27.25 | 62 | 0.784404 | eng_Latn | 0.03221 |
d5993be45f9c8ce01664c374619e2a10f796ea42 | 7,922 | md | Markdown | blog/en-us/dubboAsync_client.md | wangkezun/dubbo-website | 61526315e8b5d25ce8b9a489c00cfe9dfd3ef50a | [
"Apache-2.0"
] | 1 | 2019-12-20T01:49:05.000Z | 2019-12-20T01:49:05.000Z | blog/en-us/dubboAsync_client.md | wangkezun/dubbo-website | 61526315e8b5d25ce8b9a489c00cfe9dfd3ef50a | [
"Apache-2.0"
] | 1 | 2020-10-19T06:48:29.000Z | 2020-10-19T06:48:29.000Z | blog/en-us/dubboAsync_client.md | wangkezun/dubbo-website | 61526315e8b5d25ce8b9a489c00cfe9dfd3ef50a | [
"Apache-2.0"
] | 1 | 2021-04-06T02:23:37.000Z | 2021-04-06T02:23:37.000Z | ---
title: Implementation background and practice of Dubbo client asynchronous interface
keywords: Dubbo, Asynchronous, Reactive
description: Implementation background and practice of Dubbo client asynchronous interface
---
# Implementation background and practice of Dubbo client asynchronous interface
## Preface
Let's start with a brief introduction about the stages of a complete Dubbo invocation.
1. Biz~ represents business thread, that is, the thread where the business logic is located. Biz~ thread pool may be created and maintained by business itself, most of which may be managed by system framework itself (for example, a web system runs under Tomcat container, Biz~ thread is maintained by Tomcat); IO~ stands for network data processing thread, which is created and maintained by IO framework (such as Netty, Grizzly). Dubbo Remoting's default Netty implementation is NioEventloopLoopGroup. In addition, according to the binding relationship between Channel and IO thread, IO~ can also be regarded as an acceptable Channel for event messages. Asynchronous processing stages such as Biz and IO are abstractly described in JDK8 as completionstages.
2. As we all know, the way of data communication between threads is shared variables. The data communication between Biz and IO is Queue. Specifically to Dubbo, Biz put a task in EventLoop's LinkedBlockingQueue in the client side implementation (i.e. the steps labeled in Figure 1 above), and the corresponding Thread in the EventLoop will keep iteration the Queue to keep on executing the information the task contains. Specific code can refer to SingleThreadEventExecutor (by the way, the default is to use in the Netty is capacity-free LinkedBlockingQueue, when the Biz processing rate higher than the rate of network, there seems to be a Memory Leak risk).
3. As shown in the figure above, a standard RPC call passes through four message (event) transfers of 1,2,3,4, respectively are the client business thread sending requests to the client IO thread, the server business logic thread receiving the server IO thread requests, the server logic thread responding to the server IO thread after processing, and the client IO thread receiving the results feedback to the business logic thread.
## Client Asynchronization
### Background
In the Java language (other languages are not clear), a call of the local interface can be transparently converted into the call of remote RPC through the proxy mechanism. Most business parties prefer this programming method similar to the local interface to do remote service invocation. Therefore, although RPC is naturally asynchronous internally, users using Dubbo mostly use synchronization, while asynchrony becomes a minority use scenario. The advantage of synchronization is that the programming model is more in line with the "traditional" habits of the business side. The cost is that the current Biz~threads need to be blocked after the request event represented by 1 in the figure, and can not be awakened until the response processing represented by 4. In the process of 1,2,3,4, which is short in microsecond level and long in second level, the Biz~ thread will be blocked, which will consume thread resources and increase the overhead of system resources.
Therefore, the motivation of client asynchronization is to save thread resource overhead at the cost of understanding how asynchronization is used. In the synchronous mode, the return type of API interface represents a certain business class, while in the asynchronous case, the response and the request are completely independent events, so it is most suitable for the return type of API interface to be CompletionStage mentioned above, which is the inevitable asynchronization supported by Dubbo on asynchronization. Back to the latest Dubbo release, without changing the interface, you need to register a callback interface to handle the response return event when the service is created.
The example blow is to illustrate it.
### The sample
Refer to the example code for event notification: [https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-notify](https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-notify)
Event notification allows the Consumer to trigger 'oninvoke', 'onreturn' and 'onthrow' events, which respectively represent before the call, after the call returns normally, or when an exception occurs.
You can specify a method for notifying events when configuring the Consumer, such as:
```xml
<bean id="demoCallback" class="com.alibaba.dubbo.samples.notify.impl.NotifyImpl" />
<dubbo:reference id="demoService" check="false" interface="com.alibaba.dubbo.samples.notify.api.DemoService" version="1.0.0" group="cn">
<dubbo:method name="sayHello" onreturn="demoCallback.onreturn" onthrow="demoCallback.onthrow"/>
</dubbo:reference>
```
The code for NotifyImpl is as follows:
```java
public class NotifyImpl implements Notify{
public Map<Integer, String> ret = new HashMap<Integer, String>();
public void onreturn(String name, int id) {
ret.put(id, name);
System.out.println("onreturn: " + name);
}
public void onthrow(Throwable ex, String name, int id) {
System.out.println("onthrow: " + name);
}
}
```
It is important to note that the parameters for the three methods in the custom Notify interface are as follows:
* `oninvoke` The parameters of the method are the same as those of the calling method.
* `onreturn` The first parameter of the method is the return value of the calling method, and the rest is the parameters of the calling method.
* `onthrow` The first parameter to the method is the call exception, and the rest is the parameter to the calling method.
In the above configuration, the `sayHello` method is called synchronously, so the execution of the event notification method is also synchronously executed. `async=true` can be configured to make the method call asynchronous, and the notification event method is also executed asynchronously. In particular, the `oninvoke` method executes synchronously, regardless of whether it is invoked asynchronously or not.
### Practical advice
* <div data-type="alignment" data-value="justify" style="text-align:justify">
<div data-type="p">Logical Non-Strongly dependent results after RPC invocation: Asynchronous callbacks are suitable for client-side asynchronous invocation when the client <strong>is not strongly dependent on the server response</strong>.</div>
</div>
* <div data-type="alignment" data-value="justify" style="text-align:justify">
<div data-type="p">RX scenario: after learning about reactive programming model, I believe that as long as the programming thinking can embrace reactive and the state machine design of business model can be adjusted appropriately, asynchronous solutions can be applied in all scenarios, so as to achieve better terminal response experience. For Dubbo, the current asynchronous interface model needs to be improved like the reactive model interface in order to make the user more naturally apply the asynchronous interface. </div>
</div>
### Conclusions
* The motivation of client asynchronization is that the request sending and response processing are two different independent events, how the response is handled and in which thread is handled are not required to be coupled with the business logic thread of the request sending event.
* The processing logic of response event callbacks in which thread to process is to be selected according to the situation. It is recommended that if the callback logic is relatively simple, it should be directly in the IO thread; if it contains IO type synchronization operations such as remote access or DB access, it is recommended that it be processed in a separate thread pool. | 93.2 | 970 | 0.792224 | eng_Latn | 0.999104 |
d5998909b5ac6e938ac4f217947c761758af086a | 4,524 | md | Markdown | 31. TailwindCSS and Variables/README.md | Edmartt/articles | 93d62086ff141f5646193afb868973e94f33f1e6 | [
"MIT"
] | 31 | 2020-03-01T20:27:03.000Z | 2022-02-15T14:53:09.000Z | 31. TailwindCSS and Variables/README.md | hmajid2301/articles | 27f38cc6c2dd470d879b30d54d1e804a7d76caab | [
"MIT"
] | 24 | 2020-04-04T12:18:25.000Z | 2022-03-29T08:41:57.000Z | 31. TailwindCSS and Variables/README.md | Edmartt/articles | 93d62086ff141f5646193afb868973e94f33f1e6 | [
"MIT"
] | 52 | 2020-02-29T04:01:10.000Z | 2022-03-11T07:54:16.000Z | ---
title: "TailwindCSS with CSS variables"
tags: ["gatsby", "documentation", "tailwindcss", "css"]
license: "public-domain"
slug: "tailwindcss-with-css-variables"
canonical_url: "https://haseebmajid.dev/blog/tailwindcss-with-css-variables"
date: "2020-08-05"
published: true
cover_image: "images/cover.jpg"
---
TailwindCSS allows us to use pre-defined classes instead of defining our CSS styles. In this article, we will go over
how we can use Custom properties (sometimes referred to as CSS variables or cascading variables) with TailwindCSS.
## Setup
First, follow the installation guide found [here](https://tailwindcss.com/docs/installation/#2-add-tailwind-to-your-css).
This will show you how you can add TailwindCSS to your current project. For part 2 I will assume you called your CSS
file `global.css`. This is the file that contains `@tailwind base;` etc.
## Global CSS
First, we need to edit our TailwindCSS file so it looks something like this:
```css:title=global.css
@tailwind base;
@tailwind components;
@tailwind utilities;
.root,
#root,
#docs-root {
--primary: #367ee9;
--secondary: #a0aec0;
--accent: #718096;
--background: #fff;
--main: #0d0106;
--header: #2d3748;
}
```
I wrap my entire body in an element with class `root` or id `root`, so that any of my elements can access it later.
### Gatsby
If you're using Gatsby, you can add the following to your `gatsby-browser.js` file:
```js:title=gatsby-browser.js
export const wrapRootElement = ({ element }) => (
<div className="root overflow-hidden">{element}</div>
);
```
This will wrap all of our pages in the class `root` and `overflow-hidden` CSS class from TailwindCSS.
## tailwind.config.js
Now we've defined some CSS variables how can we use them with Tailwindcss? Simple, we update our tailwind config file
with some of the new CSS variables. Here we simply want to extend the config to add new colour values.
```js:title=tailwind.config.js
module.exports = {
theme: {
extend: {
colors: {
primary: "var(--primary)",
secondary: "var(--secondary)",
main: "var(--main)",
background: "var(--background)",
header: "var(--header)",
accent: "var(--accent)",
},
},
},
};
```
The syntax is very similar to how we would use the variables normally with CSS where it would normally look like:
```css
element {
background-color: var(--primary);
}
```
## Logo
Now how do we use our variable? Again pretty straight forward just like our normal tailwind classes. Let's imagine
we have a React component called `Logo.tsx`, defined like so:
```tsx:title=Logo.tsx
import React from "react";
import tw from "twin.macro";
export interface Props {
/** The size of the main text */
size?: string;
}
const Logo = ({ size = "2xl" }: Props) => (
<LogoContainer className={` md:text-${size}`}>
<Tag><</Tag>
Haseeb
<Tag>/></Tag>
</LogoContainer>
);
const LogoContainer = tw.div`cursor-pointer font-header tracking-wide text-2xl font-bold hover:text-primary`;
const Tag = tw.span`text-accent`;
export default Logo;
```
> INFO: I'm using the `twin.macro` the library so we can use it with CSS-in-JS.
To use our variables we just use them like: `text-primary`. Which will use the value we defined above, `#367ee9`. Now
if we change the value in the `global.css` file, it will automatically change here as well.
## Dark/Light Mode (Optional)
This can be easily extended to add a dark/light mode. Add the following to the `global.css` file like so:
```css:title=global.css
.theme-light {
--background: #fff;
--main: #0d0106;
--header: #2d3748;
}
.theme-dark {
--background: #0e141b;
--main: #ffffff;
--header: #eaeaea;
}
```
We can use a theme context to get the current theme I've written about
[here](https://dev.to/hmajid2301/react-hooks-context-local-storage-3job). We get the current theme then use that to determine which class
to set. This will then change value of the variables. If the theme changes, the variable values will change dark -> light or
light -> dark etc.
```jsx
const { theme } = useContext(ThemeContext);
// ...
return (
<div
className={`${
theme === "light" ? "theme-light" : "theme-dark"
} bg-background`}
>
// ...
</div>
);
```
That's it! We've learnt how to use CSS variables with TailwindCSS.
## Appendix
- [Example Project](https://gitlab.com/hmajid2301/personal-site/-/tree/fa01433eecec728427763e1e2b2cdd9710a9c197)
- [Icons from FlatIcon](https://flaticon.com)
| 27.754601 | 137 | 0.696286 | eng_Latn | 0.954256 |
d599b9ce6257856c7c28eb6486d44eb3b0b0267a | 3,430 | md | Markdown | CIP-1855/CIP-1855.md | kevinhammond/CIPs | 1f12a676c1a2f093fd1da7390074efeac911ce7f | [
"CC-BY-4.0"
] | 305 | 2020-05-05T18:23:04.000Z | 2022-03-31T09:12:34.000Z | CIP-1855/CIP-1855.md | kevinhammond/CIPs | 1f12a676c1a2f093fd1da7390074efeac911ce7f | [
"CC-BY-4.0"
] | 119 | 2020-05-29T06:57:58.000Z | 2022-03-30T13:55:43.000Z | CIP-1855/CIP-1855.md | kevinhammond/CIPs | 1f12a676c1a2f093fd1da7390074efeac911ce7f | [
"CC-BY-4.0"
] | 123 | 2020-05-06T03:36:24.000Z | 2022-03-31T13:37:54.000Z | ---
CIP: 1855
Title: Forging policy keys for HD Wallets
Authors: Samuel Leathers <[email protected]>, John Lotoski <[email protected]>, Michael Bishop <[email protected]>
Comments-Summary: Multi-party transaction signing and key management for HD wallets.
Comments-URI: https://github.com/cardano-foundation/CIPs/wiki/Comments:CIP-1855
Status: Draft
Type: Standards
Created: 2021-06-02
License: CC-BY-4.0
---
# Abstract
This document describes how to derive forging policy keys used for minting/burning tokens.
## Glossary
Term | Definition
--- | ---
HD | Hierarchical Deterministic, refers to wallets as described in [BIP-0032].
# Motivation
## Overview
Forging tokens is derived from a script policy. The script policy includes hashes of keys needed to forge new tokens and must be witnessed by the keys with hashes listed.
# Specification
## HD Derivation
We consider the following HD derivation paths similarly to [CIP-1852]:
```
m / purpose' / coin_type' / policy_ix'
```
To associate policy keys to a wallet, we reserve however `purpose=1855'` to reserve for policy keys for forging tokens. The coin type remains `coin_type=1815'` to identify Ada as registered in [SLIP-0044]. We use a hardened index for each policy key as derivation is not needed.
We can summarize the various paths and their respective domain in the following table:
| `purpose` | `coin_type` | `policy_ix` |
| --- | --- | --- |
| `1855'` | `1815'` | `[2^31 .. 2^32-1]` |
### Rationale
- ERC20 Converter IOHK is developing needs to keep track of policy keys. Rather than having randomly generated policy keys, a policy key can be associated with a mnemonic which is easier to backup.
- A 3rd party may want to have multiple tokens tied to same mnemonic, so we allow an index to specify the token.
- We use a different purpose for mainly two reasons:
- It prevents mixing up standard wallets with policy keys used for forging.
- Using a different purpose also fits well the use-case on hardware wallets who can still rely on a single root seed to manage many types of wallets.
### Examples
- `m/1855’/1815’/0’`
- `m/1855’/1815’/1’`
- `m/1855’/1815’/2’`
# Backwards Compatibility
N/A (no preceding implementation or design).
# Reference Implementation
None yet.
# Related Work
Description | Link
--- | ---
BIP-0032 - HD Wallets | https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki
CIP-5 - Common Bech32 Prefixes | https://github.com/cardano-foundation/CIPs/tree/master/CIP-0005
CIP-1852 - Cardano HD Wallets | https://github.com/cardano-foundation/CIPs/tree/master/CIP-1852
A Formal Specification of the Cardano Ledger | https://hydra.iohk.io/job/Cardano/cardano-ledger-specs/shelleyLedgerSpec/latest/download-by-type/doc-pdf/ledger-spec
# Copyright
CC-BY-4.0
[BIP-0032]: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki
[CIP-5]: https://github.com/cardano-foundation/CIPs/tree/master/CIP5
[CIP-1852]: https://github.com/cardano-foundation/CIPs/blob/master/CIP-1852/CIP-1852.md
[ledger-spec.pdf]: https://hydra.iohk.io/job/Cardano/cardano-ledger-specs/shelleyLedgerSpec/latest/download-by-type/doc-pdf/ledger-spec
[SLIP-0044]: https://github.com/satoshilabs/slips/blob/master/slip-0044.md
| 36.105263 | 278 | 0.710496 | eng_Latn | 0.907654 |
d59a5d6c3a284bcbdfc117db8f28560dbb84e728 | 5,372 | md | Markdown | articles/active-directory/devices/hybrid-azuread-join-control.md | ClosetheWorld/azure-docs.ja-jp | e6c4cee8628ba1bb30a2138f7bb2d12f9b48dc51 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-10-22T22:16:30.000Z | 2019-10-22T22:16:30.000Z | articles/active-directory/devices/hybrid-azuread-join-control.md | ClosetheWorld/azure-docs.ja-jp | e6c4cee8628ba1bb30a2138f7bb2d12f9b48dc51 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/devices/hybrid-azuread-join-control.md | ClosetheWorld/azure-docs.ja-jp | e6c4cee8628ba1bb30a2138f7bb2d12f9b48dc51 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: ハイブリッド Azure AD 参加の制御された検証 - Azure AD
description: ハイブリッド Azure AD 参加を組織全体で同時に有効にする前に、その制御された検証を実行する方法を説明します
services: active-directory
ms.service: active-directory
ms.subservice: devices
ms.topic: conceptual
ms.date: 06/28/2019
ms.author: joflore
author: MicrosoftGuyJFlo
manager: daveba
ms.reviewer: sandeo
ms.collection: M365-identity-device-management
ms.openlocfilehash: c897d52c10efdb8824f676d7640dcc7275915a9e
ms.sourcegitcommit: 670c38d85ef97bf236b45850fd4750e3b98c8899
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 08/08/2019
ms.locfileid: "68851790"
---
# <a name="controlled-validation-of-hybrid-azure-ad-join"></a>ハイブリッド Azure AD 参加の検証を制御する
すべての前提条件がそろったら、Windows デバイスが、Azure AD テナントにデバイスとして自動的に登録されます。 Azure AD でのこれらのデバイス ID の状態は、ハイブリッド Azure AD 参加と呼ばれます。 この記事で説明する概念の詳細については、[Azure Active Directory でのデバイス管理の概要](overview.md)と[Hybrid Azure Active Directory 参加の実装の計画](hybrid-azuread-join-plan.md)に関する記事を参照してください。
組織では、ハイブリッド Azure AD 参加を組織全体で同時に有効にする前に、その制御された検証を実行する必要がある場合があります。 この記事では、ハイブリッド Azure AD 参加の制御された検証を実行する方法について説明します。
## <a name="controlled-validation-of-hybrid-azure-ad-join-on-windows-current-devices"></a>Windows の現在のデバイスでのハイブリッド Azure AD 参加の制御された検証
Windows デスクトップ オペレーティング システムを実行するデバイスの場合、サポートされるバージョンは Windows 10 Anniversary Update (Version 1607) 以降です。 ベスト プラクティスとして、Windows 10 の最新バージョンにアップグレードしてください。
Windows の現在のデバイスでハイブリッド Azure AD 参加の制御された検証を実行するには、次を行う必要があります。
1. サービス接続ポイント (SCP) エントリが存在する場合に、Active Directory (AD) からそれをクリアします
1. グループ ポリシー オブジェクト (GPO) を使用して、ドメインに参加しているコンピューターで SCP のクライアント側レジストリ設定を構成します
1. AD FS を使用している場合、GPO を使用して、AD FS サーバーで SCP のクライアント側レジストリ設定を構成する必要もあります
### <a name="clear-the-scp-from-ad"></a>AD から SCP をクリアする
AD で SCP オブジェクトを変更するには、Active Directory サービス インターフェイス エディター (ADSI Edit) を使用します。
1. **ADSI Edit** デスクトップ アプリケーションは、エンタープライズ管理者として、管理ワークステーションまたはドメイン コントローラーから起動します。
1. ドメインの**構成名前付けコンテキスト**に接続します。
1. **CN=Configuration,DC=contoso,DC=com** > **CN=Services** > **CN=Device Registration Configuration** を参照します
1. **CN=Device Registration Configuration** の下のリーフ オブジェクトを右クリックして、 **[プロパティ]** を選択します
1. **[属性エディター]** ウィンドウから**キーワード**を選択し、 **[編集]** をクリックします
1. **azureADId** と **azureADName** の値を選択し (一度に 1 つずつ)、 **[削除]** をクリックします
1. **[ADSI エディター]** を閉じます
### <a name="configure-client-side-registry-setting-for-scp"></a>SCP のクライアント側レジストリ設定を構成する
次の例を使用して、デバイスのレジストリ内の SCP エントリを構成するレジストリ設定をデプロイするためのグループ ポリシー オブジェクト (GPO) を作成します。
1. グループ ポリシー管理コンソールを開き、ドメインに新しいグループ ポリシー オブジェクトを作成します。
1. 新しく作成した GPO に名前 (ClientSideSCP など) を付けます。
1. GPO を編集し、次のパスを参照します。 **[コンピューターの構成]** > **[基本設定]** > **[Windows 設定]** > **[レジストリ]**
1. [レジストリ] を右クリックして、 **[新規]** > **[レジストリ項目]** を選択します
1. **[全般]** タブで、次を構成します
1. アクション:**Update**
1. Hive:**HKEY_LOCAL_MACHINE**
1. キー パス:**SOFTWARE\Microsoft\Windows\CurrentVersion\CDJ\AAD**
1. 値の名前:**TenantId**
1. 値の型:**REG_SZ**
1. 値のデータ:Azure AD インスタンスの GUID または**ディレクトリ ID** (この値は、**Azure portal** > **[Azure Active Directory]** > **[プロパティ]** > **[ディレクトリ ID]** にあります)
1. **[OK]**
1. [レジストリ] を右クリックして、 **[新規]** > **[レジストリ項目]** を選択します
1. **[全般]** タブで、次を構成します
1. アクション:**Update**
1. Hive:**HKEY_LOCAL_MACHINE**
1. キー パス:**SOFTWARE\Microsoft\Windows\CurrentVersion\CDJ\AAD**
1. 値の名前:**TenantName**
1. 値の型:**REG_SZ**
1. 値のデータ:AD FS などのフェデレーション環境を使用している場合は、確認済みの**ドメイン名**。 マネージド環境を使用している場合は、確認済みの**ドメイン名**または onmicrosoft.com のドメイン名 (たとえば、`contoso.onmicrosoft.com`)。
1. **[OK]**
1. 新しく作成された GPO のエディターを閉じます
1. 制御されたロールアウト群に属している、ドメインに参加しているコンピューターを含む目的の OU に、新しく作成した GPO をリンクします
### <a name="configure-ad-fs-settings"></a>AD FS 設定を構成する
AD FS を使用している場合は、まず、上記の手順を使用して、ただし GPO を AD FS サーバーにリンクして、クライアント側の SCP を構成する必要があります。 SCP オブジェクトで、デバイス オブジェクトの権限のソースを定義します。 オンプレミスまたは Azure AD を指定できます。 これが AD FS 用に構成されている場合、デバイス オブジェクトのソースは Azure AD として確立されます。
> [!NOTE]
> AD FS サーバー上でクライアント側の SCP を構成できなかった場合、デバイス ID のソースはオンプレミスと見なされ、指定された期間の後に、AD FS ではオンプレミスのディレクトリからデバイス オブジェクトの削除が開始されます。
## <a name="controlled-validation-of-hybrid-azure-ad-join-on-windows-down-level-devices"></a>ダウンレベルの Windows デバイスでハイブリッド Azure AD 参加の制御された検証
ダウンレベルの Windows デバイスを登録するには、組織で Microsoft ダウンロード センターから入手可能な [Microsoft Workplace Join for non-Windows 10 computers](https://www.microsoft.com/download/details.aspx?id=53554) をインストールする必要があります。
[System Center Configuration Manager](https://www.microsoft.com/cloud-platform/system-center-configuration-manager) などのソフトウェア ディストリビューション システムを使用して、このパッケージをデプロイできます。 パッケージは、quiet パラメーターを使用する、標準のサイレント インストール オプションをサポートしています。 Configuration Manager の Current Branch には、完了した登録を追跡する機能など、以前のバージョンにはない利点が追加されています。
インストーラーによって、ユーザー コンテキストで実行されるシステムにスケジュール済みタスクが作成されます。 このタスクは、ユーザーが Windows にサインインするとトリガーされます。 Azure AD によって認証が行われた後、ユーザーの資格情報を使ってサイレントにデバイスが Azure AD に登録されます。
デバイスの登録を制御するには、選択したダウンレベルの Windows デバイスのグループに Windows インストーラー パッケージをデプロイする必要があります。
> [!NOTE]
> AD で SCP が構成されていない場合、グループ ポリシー オブジェクト (GPO) を使用してドメインに参加しているコンピューターで、「[SCP のクライアント側レジストリ設定を構成する](#configure-client-side-registry-setting-for-scp)」で説明されている同じアプローチに従います。
すべてが期待どおりに動作していることを確認したら、[Azure AD Connect を使用して SCP を構成し](hybrid-azuread-join-managed-domains.md#configure-hybrid-azure-ad-join)、Windows の現在およびダウンレベルのデバイスの残りの部分を Azure AD に自動的に登録できます。
## <a name="next-steps"></a>次の手順
[ハイブリッド Azure Active Directory 参加の実装の計画](hybrid-azuread-join-plan.md)
| 50.679245 | 307 | 0.77029 | yue_Hant | 0.675505 |
d59b76cf7d6707a51edef687370346f37fa252f4 | 4,296 | md | Markdown | articles/supply-chain/sales-marketing/tasks/enter-sales-agreements.md | DanielLandi/dynamics-365-unified-operations-public | 44a29bd3a3d0b6a916bbb795129ddfa3eecb0f19 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-12-03T17:44:14.000Z | 2020-12-03T17:44:14.000Z | articles/supply-chain/sales-marketing/tasks/enter-sales-agreements.md | DanielLandi/dynamics-365-unified-operations-public | 44a29bd3a3d0b6a916bbb795129ddfa3eecb0f19 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/supply-chain/sales-marketing/tasks/enter-sales-agreements.md | DanielLandi/dynamics-365-unified-operations-public | 44a29bd3a3d0b6a916bbb795129ddfa3eecb0f19 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-07-15T03:37:48.000Z | 2020-07-15T03:37:48.000Z | ---
# required metadata
title: Enter sales agreements
description: This procedure shows you how to create a sales agreement that commits one of your customers to buy a product for an agreed amount over time in exchange for special discounts.
author: omulvad
manager: AnnBe
ms.date: 11/10/2016
ms.topic: business-process
ms.prod:
ms.service: dynamics-ax-applications
ms.technology:
# optional metadata
# ms.search.form:
audience: Application User
# ms.devlang:
ms.reviewer: kfend
ms.search.scope: Operations
# ms.tgt_pltfrm:
# ms.custom:
ms.search.region: Global
ms.search.industry: Service industries
ms.author: omulvad
ms.search.validFrom: 2016-06-30
ms.dyn365.ops.version: AX 7.0.0
---
# Enter sales agreements
[!include[task guide banner](../../includes/task-guide-banner.md)]
This procedure shows you how to create a sales agreement that commits one of your customers to buy a product for an agreed amount over time in exchange for special discounts. You can run this procedure in demo data company USMF or on your own data.
## Set up sales agreement header
1. Go to Sales and marketing > Sales agreements > Sales agreements.
2. Click New.
3. In the Customer account field, click the drop-down button to open the lookup.
4. In the list, find and select the desired record.
5. In the list, click the link in the selected row.
6. In the Sales agreement classification field, click the drop-down button to open the lookup.
7. In the list, click the link in the selected row.
8. Expand the General section.
9. In the Default commitment field, select 'Product value commitment'.
* A commitment type is a mandatory criterion that you must assign to the agreement to define how the agreement contract will be fulfilled. The four predefined types let you set up the customer's commitment target, expressed as a quantity or a value. The quantity commitment type can only be applied to a specific product, but the value-based types are applicable to sales of both specific and non-specific products.
10. In the Expiration date field, set the date to a future date when you want the agreement to expire.
11. Click OK.
## Set up product value commitment lines
1. Click Add line.
2. In the Item number field, click the drop-down button to open the lookup.
3. In the list, find and select the desired record.
4. In the list, click the link in the selected row.
* The type of commitment that you have chosen for the agreement affects the kind of information you can enter for the agreement lines. For example, for a value-based agreement you must specify the total net amount (in the agreed currency) for which the customer commits to buys goods from you. In this example the Quantity and Unit fields on the line are unavailable because you’re creating an agreement for the customer to buy a specific value of a product.
5. In the Net amount field, enter the monetary amount that the customer has committed to buying.
6. In the Discount percent field, enter a percentage value that will apply to the customer's sales order lines that are linked to this agreement.
7. Expand the Line details section.
8. Select Yes in the Max is enforced field.
* Selecting Max is enforced means that the total amount of all the sales order lines that use the commitment's special prices, discounts and/or payment terms must not exceed the amount specified on the commitment.
* The minimum and maximum release amounts specify a range of values that must be sold on each sales order that uses the selected agreement.
9. Expand the Sales agreement header section.
* Unless the status of the agreement is set to Effective, sales orders cannot be associated with the agreement and can therefore not contribute to the fulfilment of that agreement. You can change the status manually at this stage. However, the status would normally be changed when you confirm the agreement for the customer.
10. On the Action Pane, click Sales agreement.
11. Click Confirmation.
* Make sure that the Mark agreement as effective option is set to Yes.
12. Select Yes in the Print report field.
13. Click OK.
14. Close the page.
* The agreement is now effective and you can start linking the customer's orders to the agreement, to offset against the committed target.
| 59.666667 | 465 | 0.774209 | eng_Latn | 0.999195 |
d59bc83de154b31eba9ce38b0bce125b90ebf7dc | 378 | md | Markdown | _posts/2021-05-18-S02E17.md | EdGrimley/edgrimley.github.io | a6b849cb09d8ff9b0afe547533ba04a8383ac7bd | [
"MIT"
] | null | null | null | _posts/2021-05-18-S02E17.md | EdGrimley/edgrimley.github.io | a6b849cb09d8ff9b0afe547533ba04a8383ac7bd | [
"MIT"
] | null | null | null | _posts/2021-05-18-S02E17.md | EdGrimley/edgrimley.github.io | a6b849cb09d8ff9b0afe547533ba04a8383ac7bd | [
"MIT"
] | null | null | null | ---
layout: post
title: "S02E17"
date: 2021-05-18 18:00:15 -0500
categories: radio
---
<audio controls="controls" preload="none">
<source src="https://sparechange.s3.us-east-2.amazonaws.com/SpareChange-S02E17-051821-1600.mp3" type="audio/mpeg">
</audio>
<br>
<a href="https://sparechange.s3.us-east-2.amazonaws.com/SpareChange-S02E17-051821-1600.mp3">Download</a>
<br>
| 27 | 119 | 0.71164 | kor_Hang | 0.090792 |
d59c9b9246f11f8febdd40756785bcbaf6b4a94e | 5,592 | md | Markdown | articles/service-bus-messaging/service-bus-ip-filtering.md | ankitscribbles/azure-docs | 709801ba745c4be0459751d18132fd59822ff602 | [
"CC-BY-4.0"
] | null | null | null | articles/service-bus-messaging/service-bus-ip-filtering.md | ankitscribbles/azure-docs | 709801ba745c4be0459751d18132fd59822ff602 | [
"CC-BY-4.0"
] | null | null | null | articles/service-bus-messaging/service-bus-ip-filtering.md | ankitscribbles/azure-docs | 709801ba745c4be0459751d18132fd59822ff602 | [
"CC-BY-4.0"
] | null | null | null | ---
title: Azure Service Bus Firewall Rules | Microsoft Docs
description: How to use Firewall Rules to allow connections from specific IP addresses to Azure Service Bus.
services: service-bus
documentationcenter: ''
author: clemensv
manager: timlt
ms.service: service-bus
ms.devlang: na
ms.topic: article
ms.date: 09/26/2018
ms.author: clemensv
---
# Use Firewall rules
For scenarios in which Azure Service Bus is only accessible from certain well-known sites, Firewall rules enable you to configure rules for accepting traffic originating from specific IPv4 addresses. For example, these addresses may be those of a corporate NAT gateway.
## When to use
If you are looking to setup Service Bus such that it should receive traffic only from a specified range of IP addresses and reject everything else, then you can leverage a *Firewall* to block Service Bus endpoints from other IP addresses. For example, you are using Service Bus with [Azure Express Route][express-route] to create private connections to your on-premises infrastructure.
## How filter rules are applied
The IP filter rules are applied at the Service Bus namespace level. Therefore, the rules apply to all connections from clients using any supported protocol.
Any connection attempt from an IP address that does not match an allowed IP rule on the Service Bus namespace is rejected as unauthorized. The response does not mention the IP rule.
## Default setting
By default, the **IP Filter** grid in the portal for Service Bus is empty. This default setting means that your namespace accepts connections any IP address. This default setting is equivalent to a rule that accepts the 0.0.0.0/0 IP address range.
## IP filter rule evaluation
IP filter rules are applied in order and the first rule that matches the IP address determines the accept or reject action.
>[!WARNING]
> Implementing Firewall rules can prevent other Azure services from interacting with Service Bus.
>
> Trusted Microsoft services are not supported when IP Filtering (Firewall rules) are implemented, and will be made available soon.
>
> Common Azure scenarios that don't work with IP Filtering (note that the list is **NOT** exhaustive) -
> - Azure Monitor
> - Azure Stream Analytics
> - Integration with Azure Event Grid
> - Azure IoT Hub Routes
> - Azure IoT Device Explorer
> - Azure Data Explorer
>
> The below Microsoft services are required to be on a virtual network
> - Azure App Service
> - Azure Functions
### Creating a virtual network and firewall rule with Azure Resource Manager templates
> [!IMPORTANT]
> Virtual Networks are supported only in the **premium** tier of Service Bus.
The following Resource Manager template enables adding a virtual network rule to an existing Service Bus namespace.
Template parameters:
- **ipMask** is a single IPv4 address or a block of IP addresses in CIDR notation. For example, in CIDR notation 70.37.104.0/24 represents the 256 IPv4 addresses from 70.37.104.0 to 70.37.104.255, with 24 indicating the number of significant prefix bits for the range.
> [!NOTE]
> While there are no deny rules possible, the Azure Resource Manager template has the default action set to **"Allow"** which doesn't restrict connections.
> When making Virtual Network or Firewalls rules, we must change the
> ***"defaultAction"***
>
> from
> ```json
> "defaultAction": "Allow"
> ```
> to
> ```json
> "defaultAction": "Deny"
> ```
>
```json
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"servicebusNamespaceName": {
"type": "string",
"metadata": {
"description": "Name of the Service Bus namespace"
}
},
"location": {
"type": "string",
"metadata": {
"description": "Location for Namespace"
}
}
},
"variables": {
"namespaceNetworkRuleSetName": "[concat(parameters('servicebusNamespaceName'), concat('/', 'default'))]",
},
"resources": [
{
"apiVersion": "2018-01-01-preview",
"name": "[parameters('servicebusNamespaceName')]",
"type": "Microsoft.ServiceBus/namespaces",
"location": "[parameters('location')]",
"sku": {
"name": "Standard",
"tier": "Standard"
},
"properties": { }
},
{
"apiVersion": "2018-01-01-preview",
"name": "[variables('namespaceNetworkRuleSetName')]",
"type": "Microsoft.ServiceBus/namespaces/networkruleset",
"dependsOn": [
"[concat('Microsoft.ServiceBus/namespaces/', parameters('servicebusNamespaceName'))]"
],
"properties": {
"virtualNetworkRules": [<YOUR EXISTING VIRTUAL NETWORK RULES>],
"ipRules":
[
{
"ipMask":"10.1.1.1",
"action":"Allow"
},
{
"ipMask":"11.0.0.0/24",
"action":"Allow"
}
],
"defaultAction": "Deny"
}
}
],
"outputs": { }
}
```
To deploy the template, follow the instructions for [Azure Resource Manager][lnk-deploy].
## Next steps
For constraining access to Service Bus to Azure virtual networks, see the following link:
- [Virtual Network Service Endpoints for Service Bus][lnk-vnet]
<!-- Links -->
[lnk-deploy]: ../azure-resource-manager/resource-group-template-deploy.md
[lnk-vnet]: service-bus-service-endpoints.md
[express-route]: /azure/expressroute/expressroute-faqs#supported-services | 36.077419 | 386 | 0.686159 | eng_Latn | 0.961281 |
d59ccab19a91560bffd63253a8dba63f3250c3d7 | 2,897 | md | Markdown | CHANGELOG.md | ojab/ruby-enum | 66c2b559d807d1b54f2455349691e4f73bdf1140 | [
"MIT"
] | null | null | null | CHANGELOG.md | ojab/ruby-enum | 66c2b559d807d1b54f2455349691e4f73bdf1140 | [
"MIT"
] | null | null | null | CHANGELOG.md | ojab/ruby-enum | 66c2b559d807d1b54f2455349691e4f73bdf1140 | [
"MIT"
] | null | null | null | ### 0.9.1 (Next)
* Your contribution here.
### 0.9.0 (2021/01/21)
* [#34](https://github.com/dblock/ruby-enum/pull/34): Added support for Ruby 3.0 - [@dblock](https://github.com/dblock).
* [#29](https://github.com/dblock/ruby-enum/pull/29): Added superclass values when enumerating with `Ruby::Enum#values` - [@gi](https://github.com/gi).
* [#30](https://github.com/dblock/ruby-enum/pull/30): Default value to key - [@gi](https://github.com/gi).
* [#34](https://github.com/dblock/ruby-enum/pull/34): Replaced Travis-CI with Github Actions, added Danger PR linter - [@dblock](https://github.com/dblock).
* [#37](https://github.com/dblock/ruby-enum/pull/37): Added code coverage - [@dblock](https://github.com/dblock).
### 0.8.0 (2020/03/27)
* [#22](https://github.com/dblock/ruby-enum/pull/22): Added `Ruby::Enum#each_key` and `Ruby::Enum#each_value` - [@dblock](https://github.com/dblock).
* [#22](https://github.com/dblock/ruby-enum/pull/22): Dropped support for Ruby 2.2 - [@dblock](https://github.com/dblock).
* [#22](https://github.com/dblock/ruby-enum/pull/22): Upgraded RuboCop to 0.80.1 - [@dblock](https://github.com/dblock).
### 0.7.2 (2017/03/15)
* [#18](https://github.com/dblock/ruby-enum/pull/18): Added support for non constant definition - [@laertispappas](https://github.com/laertispappas).
### 0.7.1 (2017/02/23)
* [#16](https://github.com/dblock/ruby-enum/pull/16): Replaced `const_missing` with `const_set` - [@laertispappas](https://github.com/laertispappas).
### 0.7.0 (2017/02/21)
* [#3](https://github.com/dblock/ruby-enum/pull/13): Added support for subclassing an Enum - [@laertispappas](https://github.com/laertispappas).
### 0.6.0 (2016/05/12)
* [#12](https://github.com/dblock/ruby-enum/pull/12): A `Ruby::Enum::Errors::DuplicateKeyError` or a `Ruby::Enum::Errors::DuplciateKeyValyeError` will now be raised when duplicate keys / values are defined - [@laertispappas](https://github.com/laertispappas).
### 0.5.0 (2015/11/20)
* [#8](https://github.com/dblock/ruby-enum/pull/8): Added `Ruby::Enum#key`, `Ruby::Enum#value`, `Ruby::Enum#key?`, and `Ruby::Enum#value?` - [@dmolesUC3](https://github.com/dmolesUC3).
### 0.4.0 (2014/06/29)
* [#5](https://github.com/dblock/ruby-enum/pull/5): Mixed in `Enumerable` - [@kgann](https://github.com/kgann).
### 0.3.0 (2014/05/19)
* [#4](https://github.com/dblock/ruby-enum/pull/4): Added `Ruby::Enum#map` - [@ArnaudRinquin](https://github.com/ArnaudRinquin).
### 0.2.1 (2013/05/15)
* Added `Ruby::Enum#values`, `Ruby::Enum#keys` and `Ruby::Enum#to_h` - [@dblock](https://github.com/dblock).
* A `Ruby::Enum::Errors::UninitializedConstantError` will now be raised when referencing an undefined enum - [@dblock](https://github.com/dblock).
### 0.1.0 (2013/05/14)
* Initial public release, live-coded during [May 2013 NYC.rb](http://code.dblock.org/your-first-ruby-gem) - [@dblock](https://github.com/dblock).
| 52.672727 | 259 | 0.682085 | yue_Hant | 0.595049 |
d59d4cd3bca61e85eec5bcd184511bae1a31c05f | 3,772 | md | Markdown | docs/vs-2015/modeling/generate-and-configure-your-app-from-models.md | chitwad36/visualstudio-docs.zh-cn | 7e63608d8c5cb17cdbb9cf510ecff9680e9bad4c | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-06T12:30:55.000Z | 2020-06-06T12:30:55.000Z | docs/vs-2015/modeling/generate-and-configure-your-app-from-models.md | chitwad36/visualstudio-docs.zh-cn | 7e63608d8c5cb17cdbb9cf510ecff9680e9bad4c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/modeling/generate-and-configure-your-app-from-models.md | chitwad36/visualstudio-docs.zh-cn | 7e63608d8c5cb17cdbb9cf510ecff9680e9bad4c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 生成并配置将应用程序模型从 |Microsoft Docs
ms.custom: ''
ms.date: 11/15/2016
ms.prod: visual-studio-tfs-dev14
ms.reviewer: ''
ms.suite: ''
ms.tgt_pltfrm: ''
ms.topic: article
ms.assetid: 4dc8f572-a09e-4d19-a92d-f1df383e728b
caps.latest.revision: 9
author: alexhomer1
ms.author: gewarren
manager: douge
ms.openlocfilehash: 96dc292712a04b7a1049400b908bf5f678b63df3
ms.sourcegitcommit: 240c8b34e80952d00e90c52dcb1a077b9aff47f6
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 10/23/2018
ms.locfileid: "49857446"
---
# <a name="generate-and-configure-your-app-from-models"></a>从模型中生成并配置你的应用程序
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
你可从模型生成或配置你的应用程序的不同部件。 模型可以是 UML 或 DSL。
模型比代码更能直接表示要求。 与更新代码相比，通过直接从模型派生应用程序的行为，你可以更加快速可靠地对更改的需求做出响应。 尽管需要做一些初始工作来设置派生，但如果你预计要求会发生改变，或者你计划生成产品的几个变体，则这种投资是会有回报的。
## <a name="generating-the-code-of-your-application-from-a-model"></a>从模型生成应用程序代码
生成代码的最便捷方法是使用模板。 可以在同一个生成代码[!INCLUDE[vsprvs](../includes/vsprvs-md.md)]解决方案在其中保留的模型。 有关详细信息，请参见:
- [使用 T4 文本模板生成设计时代码](../modeling/design-time-code-generation-by-using-t4-text-templates.md)
- [从 UML 模型生成文件](../modeling/generate-files-from-a-uml-model.md)
- [从域特定语言生成代码](../modeling/generating-code-from-a-domain-specific-language.md)
这种方法易于进行增量应用。 首先使用一个仅适用于特定情况的应用程序，并从模型中选择一些你希望更改的应用程序部分。 重命名这些部分的源文件，以便这些文件成为文本模板 (.tt) 文件。 此时，将自动从模板文件生成 .cs 源文件，该应用程序能像以前一样工作。
然后，你可以取用一部分代码并将其替换为文本模板表达式，该表达式读取模型并生成这部分的源文件。 至少模型的一个值应生成原始源，这样你才能再次运行该应用程序，该应用程序才能像以前一样工作。 在测试过不同的模型值之后，你可以继续在另一部分代码中插入模板表达式。
这种递增方法意味着代码生成通常是一种低风险的方式。 生成的应用程序通常能执行与手写版本几乎一样的操作。
但是，如果是从一个现有应用程序开始，你可能会发现需要进行很多重构才能隔开受模型控制的不同行为，以便这些行为可以独立改变。 建议你在估计项目成本时，将应用程序的这一方面评估在内。
## <a name="configuring-your-application-from-a-model"></a>从模型进配置应用程序
如果你希望在运行时改变应用程序的行为，则无法使用在编译应用程序前生成源代码的代码生成。 相反，你可以将应用程序设计为读取 UML 或 DSL 模型并相应地改变其行为。 有关详细信息，请参见:
- [在程序代码中读取 UML 模型](../modeling/read-a-uml-model-in-program-code.md)
- [如何：在程序代码中从文件打开模型](../modeling/how-to-open-a-model-from-file-in-program-code.md)
也可以以增量方式应用此方法，但一开始会有更多的工作要做。 你需要编写读取模型代码，并设置一个允许可变部分访问其值的框架。 生成泛型的可变部分比代码生成的开销更大。
一个泛型应用程序的执行效果通常没有其特定的对应应用程序好。 如果性能很关键，则你的项目计划应将这种风险评估在内。
## <a name="developing-a-derived-application"></a>开发派生应用程序
你可能会发现以下一般准则会很有帮助。
- **先具体后一般化。** 首先编写一个特定版本的应用程序。 此版本应能在一组条件下工作。 当你认为该应用程序能正常工作时，你可以从模型派生一些部分。 逐渐扩展派生的部分。
例如，设计一个具有一组特定网页的网站，然后设计一个 Web 应用程序来表示在模型中定义的页面。
- **模型的变体方面。** 确定将发生改变的方面，两个不同部署之间的改变，或随着需求变化而改变。 这些方面应从模型派生。
例如，如果一组网页及其之间的链接发生更改，但这些网页的样式和格式始终是相同的，那么模型应描述这些链接，但不必描述网页的格式。
- **分离关注点。** 如果可变方面能分成独立的区域，则为每个区域使用单独的模型。 使用 ModelBus，你可以定义同时影响各模型及其之间的约束的操作。
例如，使用一个模型来定义网页导航，使用另一个模型来定义网页布局。 有关详细信息，请参阅[与其他模型和工具集成 UML 模型](../modeling/integrate-uml-models-with-other-models-and-tools.md)。
- **模型的要求，而不是解决方案。** 设计 DSL 或采用 UML，以便用来描述用户需求。 与此相反，不要根据实现的可变方面设计表示法。
例如，Web 导航模型应表示网页和网页间的超链接。 Web 导航模型不应表示应用程序中的 HTML 或类的片段。
- **生成或解释？** 如果特定部署的需求将很少更改，则从模型生成程序代码。 如果需求可能会频繁更改，或者可能共存于同一部署的多个变体中，则编写应用程序，以便该应用程序可以读取和解释模型。
例如，如果你使用网站模型来开发一系列独立安装的不同网站，则应从模型生成网站代码。 但如果你使用模型来控制一个每天改变的网站，则最好编写一个 Web 服务器来相应地读取模型和表示网站。
- **UML 或 DSL？** 考虑通过使用构造型扩展 UML 来创建你的建模表示法。 如果没有符合目标的 UML 关系图，则定义一个 DSL。 但要避免中断 UML 的标准语义。
例如，UML 类图是框和箭头的集合；有了这种表示法，你在理论上能定义任何内容。 但是，除非你实际需要描述一组类型，否则我们不建议你使用类图。 例如，你可以采用类图来描述不同类型的网页。
## <a name="see-also"></a>请参阅
[从 UML 模型生成文件](../modeling/generate-files-from-a-uml-model.md)
[读取程序代码中的 UML 模型](../modeling/read-a-uml-model-in-program-code.md)
[从域特定语言生成代码](../modeling/generating-code-from-a-domain-specific-language.md)
[如何： 从程序代码中的文件打开模型](../modeling/how-to-open-a-model-from-file-in-program-code.md)
[使用 T4 文本模板生成设计时代码](../modeling/design-time-code-generation-by-using-t4-text-templates.md)
| 40.55914 | 135 | 0.759279 | yue_Hant | 0.836104 |
d59ddda6260c9f715281bf87c0d05bb5b696aed8 | 231 | md | Markdown | site/static/carts/floppy-fish.md | FrankWPA/wasm4 | fbf54e978566ff5a0777d23d980ff3be51daba7f | [
"0BSD"
] | null | null | null | site/static/carts/floppy-fish.md | FrankWPA/wasm4 | fbf54e978566ff5a0777d23d980ff3be51daba7f | [
"0BSD"
] | null | null | null | site/static/carts/floppy-fish.md | FrankWPA/wasm4 | fbf54e978566ff5a0777d23d980ff3be51daba7f | [
"0BSD"
] | null | null | null | ---
author: Chris Breece
github: TheBebopCowboy
date: 2022-05-19 21:00:00 GMT
---
# Floppy Fish
My first WASM-4 game! Written in AssemblyScript; you can check out the source here:
https://gitlab.com/bebopcowboygames/floppy_fish
| 21 | 84 | 0.757576 | eng_Latn | 0.510735 |
d59e234bf920fb197ca7f57ff537a0435a251b88 | 6,578 | md | Markdown | docs/framework/winforms/advanced/walkthrough-assigning-wpf-content-on-windows-forms-at-design-time.md | andreatosato/docs.it-it-1 | 0a50e3e816ac998ddb603eb44b7a8cece7b1e523 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/winforms/advanced/walkthrough-assigning-wpf-content-on-windows-forms-at-design-time.md | andreatosato/docs.it-it-1 | 0a50e3e816ac998ddb603eb44b7a8cece7b1e523 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/winforms/advanced/walkthrough-assigning-wpf-content-on-windows-forms-at-design-time.md | andreatosato/docs.it-it-1 | 0a50e3e816ac998ddb603eb44b7a8cece7b1e523 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Procedura dettagliata: assegnazione del contenuto WPF in Windows Form in fase di progettazione'
ms.date: 03/30/2017
helpviewer_keywords:
- WPF content [Windows Forms], assigning at design time
- ElementHost control [Windows Forms], assigning WPF content at design time
- interoperability [WPF]
- Windows Forms, content assignments
- WPF user control [Windows Forms], hosting in Windows Forms
ms.assetid: b3e9ef93-7e0f-4a2f-8f1e-3437609a1eb7
ms.openlocfilehash: 554153335c08c9c8911a5d4fda3696db1e0abf2a
ms.sourcegitcommit: 586dbdcaef9767642436b1e4efbe88fb15473d6f
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 10/06/2018
ms.locfileid: "48838104"
---
# <a name="walkthrough-assigning-wpf-content-on-windows-forms-at-design-time"></a>Procedura dettagliata: assegnazione del contenuto WPF in Windows Form in fase di progettazione
Questa procedura dettagliata illustra come selezionare i tipi di controllo Windows Presentation Foundation (WPF) da visualizzare nel form. È possibile selezionare qualsiasi tipo di controllo WPF incluso nel progetto.
Questa procedura dettagliata prevede l'esecuzione delle attività seguenti:
- Creare il progetto.
- Creare i tipi di controllo WPF.
- Selezionare i controlli WPF.
> [!NOTE]
> Le finestre di dialogo e i comandi di menu visualizzati potrebbero essere diversi da quelli descritti nella Guida a seconda delle impostazioni attive o dell'edizione del programma. Per modificare le impostazioni, scegliere **Importa/Esporta impostazioni** dal menu **Strumenti** . Per altre informazioni, vedere [Personalizzare l'IDE di Visual Studio](/visualstudio/ide/personalizing-the-visual-studio-ide).
## <a name="prerequisites"></a>Prerequisiti
Per completare la procedura dettagliata, è necessario disporre dei componenti seguenti:
- Visual Studio 2012.
## <a name="creating-the-project"></a>Creazione del progetto
Il primo passaggio consiste nella creazione del progetto Windows Form.
> [!NOTE]
> Con il contenuto WPF sono supportati solo progetti C# e Visual Basic.
#### <a name="to-create-the-project"></a>Per creare il progetto
- Creare un nuovo progetto Windows Forms Application in Visual Basic o Visual c# denominato `SelectingWpfContent`.
## <a name="creating-the-wpf-control-types"></a>Creazione di tipi di controllo WPF
Dopo avere aggiunto i tipi di controllo WPF al progetto, è possibile includerli in controlli <xref:System.Windows.Forms.Integration.ElementHost> diversi.
#### <a name="to-create-wpf-control-types"></a>Per creare i tipi di controllo WPF
1. Aggiungere un nuovo progetto WPF <xref:System.Windows.Controls.UserControl> alla soluzione. Usare il nome predefinito per il tipo di controllo, `UserControl1.xaml`. Per altre informazioni, vedere [procedura dettagliata: creazione di nuovo contenuto WPF in Windows Form in fase di progettazione](../../../../docs/framework/winforms/advanced/walkthrough-creating-new-wpf-content-on-windows-forms-at-design-time.md).
2. In visualizzazione Progettazione verificare che `UserControl1` sia selezionato. Per altre informazioni, vedere [procedura: selezionare e spostare elementi nella finestra di progettazione](https://msdn.microsoft.com/library/54cb70b6-b35b-46e4-a0cc-65189399c474).
3. Nel **le proprietà** finestra, impostare il valore della <xref:System.Windows.FrameworkElement.Width%2A> e <xref:System.Windows.FrameworkElement.Height%2A> le proprietà da `200`.
4. Aggiungere un <xref:System.Windows.Controls.TextBox?displayProperty=nameWithType> il controllo al <xref:System.Windows.Controls.UserControl> e impostare il valore della <xref:System.Windows.Controls.TextBox.Text%2A> proprietà **contenuto ospitato**.
5. Aggiungere un secondo controllo WPF <xref:System.Windows.Controls.UserControl> al progetto. Usare il nome predefinito per il tipo di controllo, `UserControl2.xaml`.
6. Nel **le proprietà** finestra, impostare il valore della <xref:System.Windows.FrameworkElement.Width%2A> e <xref:System.Windows.FrameworkElement.Height%2A> le proprietà da `200`.
7. Aggiungere un <xref:System.Windows.Controls.TextBox?displayProperty=nameWithType> il controllo al <xref:System.Windows.Controls.UserControl> e impostare il valore della <xref:System.Windows.Controls.TextBox.Text%2A> proprietà **Hosted Content 2**.
**Nota** In generale, è opportuno ospitare contenuto WPF più sofisticato. Il controllo <xref:System.Windows.Controls.TextBox?displayProperty=nameWithType> è qui usato a solo a titolo esemplificativo.
1. Compilare il progetto.
## <a name="selecting-wpf-controls"></a>Selezione di controlli WPF
È possibile assegnare contenuto WPF diverso a un controllo <xref:System.Windows.Forms.Integration.ElementHost> che include già contenuto.
#### <a name="to-select-wpf-controls"></a>Per selezionare i controlli WPF
1. Aprire `Form1` in Progettazione Windows Form.
2. Nel **casella degli strumenti**, fare doppio clic su `UserControl1` per creare un'istanza di `UserControl1` nel form.
L'istanza di `UserControl1` viene inclusa in un nuovo controllo <xref:System.Windows.Forms.Integration.ElementHost> denominato `elementHost1`.
3. Nel pannello smart tag per `elementHost1`, aprire il **selezione contenuto ospitato** elenco a discesa.
4. Selezionare **UserControl2** dall'elenco a discesa.
Il controllo `elementHost1` include ora un'istanza del tipo `UserControl2`.
5. Nel **delle proprietà** finestra, verificare che il <xref:System.Windows.Forms.Integration.ElementHost.Child%2A> è impostata su **UserControl2**.
6. Dal **casella degli strumenti**, nella **interoperabilità WPF** gruppo, trascinare un <xref:System.Windows.Forms.Integration.ElementHost> controllo nel form.
Il nome predefinito del nuovo controllo è `elementHost2`.
7. Nel pannello smart tag per `elementHost2`, aprire il **selezione contenuto ospitato** elenco a discesa.
8. Selezionare **UserControl1** nell'elenco a discesa.
9. Il controllo `elementHost2` include ora un'istanza del tipo `UserControl1`.
## <a name="see-also"></a>Vedere anche
<xref:System.Windows.Forms.Integration.ElementHost>
<xref:System.Windows.Forms.Integration.WindowsFormsHost>
[Migrazione e interoperabilità](../../../../docs/framework/wpf/advanced/migration-and-interoperability.md)
[Uso di controlli WPF](../../../../docs/framework/winforms/advanced/using-wpf-controls.md)
[Progettare XAML in Visual Studio](/visualstudio/designers/designing-xaml-in-visual-studio)
| 62.647619 | 419 | 0.768471 | ita_Latn | 0.978829 |
d59e318e45418f93ccebb180080114aab2a2a629 | 570 | md | Markdown | README.md | CkFreak/express-boilerplate | 2d0ee9868a77eda603234ae0e621dbce91bb6175 | [
"MIT"
] | 1 | 2019-01-28T14:31:43.000Z | 2019-01-28T14:31:43.000Z | README.md | CkFreak/express-boilerplate | 2d0ee9868a77eda603234ae0e621dbce91bb6175 | [
"MIT"
] | null | null | null | README.md | CkFreak/express-boilerplate | 2d0ee9868a77eda603234ae0e621dbce91bb6175 | [
"MIT"
] | null | null | null | # express-boilerplate
A quick start nodeJS Server with express and mongoDB
# How to start the boilerplate
In order to start the server you will need an instance of a mongoDB as well as node installed.
You can run the mongoDB in a docker container if you choose to do so.
Aside from this you will need to set some env variables.
### Env Variables to set
* LOG_LEVEL - The log level you want to see (defaults to debug)
* PORT - The port the server will be running on (defaults to 3001)
* MONGO_CONNECTION_STRING - The string to connecto to mongoDB. This has no default.
| 43.846154 | 94 | 0.77193 | eng_Latn | 0.998482 |
d59e3ec3dd3f6af6bd8382feca8e45c101f1e135 | 98 | md | Markdown | README.md | victorluissantos/nav_horizontal | 3f2f751bc10ed7f92c6a2e948b13dc98479b0f06 | [
"MIT"
] | null | null | null | README.md | victorluissantos/nav_horizontal | 3f2f751bc10ed7f92c6a2e948b13dc98479b0f06 | [
"MIT"
] | null | null | null | README.md | victorluissantos/nav_horizontal | 3f2f751bc10ed7f92c6a2e948b13dc98479b0f06 | [
"MIT"
] | null | null | null | # Simple Page
This project is a home page with simple code of game.
 | 19.6 | 54 | 0.734694 | eng_Latn | 0.997918 |
d59f47a56f47a4796dfa1f51819a77b278cb9bde | 63 | md | Markdown | README.md | hacker350/88 | ec3a7245739bd8b47af3e7dc61610d8c60f23648 | [
"Unlicense"
] | null | null | null | README.md | hacker350/88 | ec3a7245739bd8b47af3e7dc61610d8c60f23648 | [
"Unlicense"
] | null | null | null | README.md | hacker350/88 | ec3a7245739bd8b47af3e7dc61610d8c60f23648 | [
"Unlicense"
] | null | null | null | # 88
https://www.facebook.com/deimar.marquez.92?epa=SEARCH_BOX
| 21 | 57 | 0.777778 | yue_Hant | 0.852645 |
d59f6d82e4a39f1ac1af9c9e772c49ed5f5bc3b9 | 136 | md | Markdown | _posts/2021-1-28-cause and effect economics.md | thinktomato/thinktomato.github.io | 69be32b0c442ddc5fc3b50cf3e99790205fbcc72 | [
"MIT"
] | null | null | null | _posts/2021-1-28-cause and effect economics.md | thinktomato/thinktomato.github.io | 69be32b0c442ddc5fc3b50cf3e99790205fbcc72 | [
"MIT"
] | null | null | null | _posts/2021-1-28-cause and effect economics.md | thinktomato/thinktomato.github.io | 69be32b0c442ddc5fc3b50cf3e99790205fbcc72 | [
"MIT"
] | null | null | null | ---
title: 原因与结果的经济学
tag:
- pareto distribution; zipf's law; power law
desc:
layout
---
| 12.363636 | 45 | 0.705882 | eng_Latn | 0.254979 |
d59fbc1f0f1eee1b7c313e8b1d0f24766381283b | 405 | md | Markdown | docs/design/evaluation.md | abe-winter/pg13-py | e647ce1f22f285edeb7daeeacdc1d9569d9c1f55 | [
"MIT"
] | 18 | 2015-01-15T15:19:01.000Z | 2020-08-05T04:26:28.000Z | docs/design/evaluation.md | abe-winter/pg13-py | e647ce1f22f285edeb7daeeacdc1d9569d9c1f55 | [
"MIT"
] | 22 | 2015-04-06T01:44:48.000Z | 2015-08-07T23:16:04.000Z | docs/design/evaluation.md | abe-winter/pg13-py | e647ce1f22f285edeb7daeeacdc1d9569d9c1f55 | [
"MIT"
] | 1 | 2015-04-03T03:13:03.000Z | 2015-04-03T03:13:03.000Z | ## evaluation order
design doc for SQL statement evaluation
### precedence model for doing where-filtering
These actions apply to select, update, delete:
1. CTEs
1. nested select
- can this bind variables from its parent scope? check specs, but easier not to
1. single-table where
1. multi-table where
When the expression is a select, we're also interested in:
1. order & group
2. create output rows
| 25.3125 | 81 | 0.765432 | eng_Latn | 0.999133 |
d5a00b0dad1733d8203c48c6e5c17dfa800231a5 | 52 | md | Markdown | README.md | drsounds/appgen | a134c83db521364dc24b77d4c22b5045fecb4b49 | [
"MIT"
] | null | null | null | README.md | drsounds/appgen | a134c83db521364dc24b77d4c22b5045fecb4b49 | [
"MIT"
] | null | null | null | README.md | drsounds/appgen | a134c83db521364dc24b77d4c22b5045fecb4b49 | [
"MIT"
] | null | null | null | # AppGen
An app bootstraping tool. Work in progress | 17.333333 | 42 | 0.788462 | eng_Latn | 0.542159 |
d5a17a31096f5da77795afe2a4c905ede01d7999 | 80 | md | Markdown | README.md | 329746/GithubTestProject-1 | 991c9de28428ae1744f01652db3690b31896e534 | [
"MIT"
] | null | null | null | README.md | 329746/GithubTestProject-1 | 991c9de28428ae1744f01652db3690b31896e534 | [
"MIT"
] | null | null | null | README.md | 329746/GithubTestProject-1 | 991c9de28428ae1744f01652db3690b31896e534 | [
"MIT"
] | null | null | null | # GithubTestProject-1
# Apex Legends is actually sick
fgfgdhgcfgdbdbfgdb
whynot
| 16 | 31 | 0.8375 | eng_Latn | 0.820016 |
d5a1d5c2bd16e71c702dfb39bed9fa30cc389912 | 6,569 | md | Markdown | articles/site-reliability-engineering/articles/devops.md | IrisClasson/azure-docs.sv-se | a6a2b03ee9a98c9e3708bf0df9f77628db79f1f6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/site-reliability-engineering/articles/devops.md | IrisClasson/azure-docs.sv-se | a6a2b03ee9a98c9e3708bf0df9f77628db79f1f6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/site-reliability-engineering/articles/devops.md | IrisClasson/azure-docs.sv-se | a6a2b03ee9a98c9e3708bf0df9f77628db79f1f6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Vanliga frågor och svar: SRE och DevOps | Microsoft Docs'
titleSuffix: Azure
description: 'Vanliga frågor och svar: förstå relationen mellan SRE och DevOps'
author: dnblankedelman
manager: efreeman
ms.service: site-reliability-engineering
ms.topic: article
ms.date: 04/22/2020
ms.author: dnb
ms.openlocfilehash: e917c609b484b1a58377fea2f6cdd75dde30ca6c
ms.sourcegitcommit: 877491bd46921c11dd478bd25fc718ceee2dcc08
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 07/02/2020
ms.locfileid: "82196418"
---
# <a name="frequently-asked-questions-whats-the-relationship-between-sre-and-devops"></a>Vanliga frågor och svar: Vad är relationen mellan SRE och DevOps?
Det finns en uppsättning vanliga frågor som kommer runt förhållandet mellan platsens Tillförlitlighets teknik och DevOps, inklusive "hur är de samma? Hur skiljer de sig åt? Kan vi ha både i vår organisation? ". Den här artikeln försöker dela några av svaren som har erbjudits av SRE-och DevOps-communities som ger oss närmare förståelse för den här relationen.
## <a name="how-are-they-the-same"></a>Hur är de samma?
SRE och DevOps är både moderna drift metoder som har skapats och utvecklats som svar på utmaningar som ingår:
- en växande komplexitet i våra produktions miljöer och utvecklings processer
- öka affärs beroendet för den kontinuerliga driften av dessa miljöer
- möjligheten att skala personal styrkan linjärt med storleken på dessa miljöer
- behovet av att gå snabbare samtidigt som drifts stabiliteten hålls kvar
Båda drifts metodernas värde riktar sig mot ämnen som är viktiga för att hantera dessa utmaningar som övervakning/undersöknings-, automatiserings-, dokumentations-och samarbets verktyg för program utveckling.
Det finns betydande överlappningar i verktyg och arbets områden mellan SRE och DevOps. När _arbets boken för platsens tillförlitlighet_ försätts, ser SRE ut i samma saker som DevOps men av någon annan anledning. "
## <a name="three-different-ways-to-compare-the-two-operations-practices"></a>Tre olika sätt att jämföra de två drifts metoderna
Likheter mellan SRE och DevOps är tydliga. Var det verkligen är intressant att de två skiljer sig åt eller avviker från varandra. Här erbjuder vi tre sätt att tänka på när det gäller relationen som ett sätt att sätta vissa Nuance i den här frågan. Du kanske inte accepterar svaren, men de ger en bra start plats för diskussion.
### <a name="class-sre-implements-interface-devops"></a>"klass SRE implementerar gränssnittet DevOps"
_Arbets boken för plats tillförlitlighet_ (som nämns i vår [lista över resurs böcker](../resources/books.md)) diskuterar SRE och DevOps i sitt första kapitel. I kapitlet används frasen "Class SRE implementerar gränssnitts DevOps" som dess under rubrik. Detta är avsett att föreslås (med hjälp av en fras som är avsedd för utvecklare) att SRE kan betraktas som en speciell implementering av DevOps-filosofin. Som kapitlet pekar ut är "DevOps relativt tyst med att köra åtgärder på en detaljerad nivå" medan SRE är betydligt mer proskriptiga i dess praxis. Ett möjligt svar på frågan om hur de två relaterarna är SRE kan betraktas som en av många möjliga implementeringar av DevOps.
### <a name="sre-is-to-reliability-as-devops-is-to-delivery"></a>SRE är tillförlitligt eftersom DevOps är till leverans
Den här jämförelsen är en liten muddied eftersom det finns flera definitioner för både SRE och DevOps, men det kan ändå vara användbart. Den börjar med frågan "om du behövde destillera varje åtgärds metod i ett eller två ord som återspeglar dess kärnor, vad skulle det vara?"
Om vi använder den här definitionen av SRE från [platsens Tillförlitlighets tekniks hubb](../index.yml):
> Site Reliability Engineering är ett teknikområde som är avsett att hjälpa en organisation att uppnå lämplig nivå av tillförlitlighet i deras system, produkter och tjänster.
sedan är det enkelt att säga ordet för SRE är "tillförlitlighet". Att ha det i mitten av namnet ger också några utmärkta bevis för detta anspråk.
Om vi använder den här definitionen av DevOps från [Azure DevOps Resource Center](https://docs.microsoft.com/azure/devops/learn/):
> DevOps är en union av människor, processer och produkter för kontinuerlig leverans av värde till våra slutanvändare.
sedan kan en liknande destillation för DevOps bli "Delivery".
Därför är SRE tillförlitligt eftersom DevOps är att leverera.
### <a name="direction-of-attention"></a>Uppmärksamhet riktning
Det här svaret är citerat eller något paraphrased från ett bidrag av Thomas Limoncelli till _SRE_ -adressboken som nämns i [listan över resurs böcker](../resources/books.md). Han noterar att DevOps-teknikerna i stor utsträckning fokuserar på program varu utvecklings livs cykelns pipeline med tillfälliga produktions drifts ansvar samtidigt som SREs fokuserar på produktions åtgärder med tillfälliga SDLC pipeline-ansvar.
Men det är viktigt att han också ritar ett diagram som börjar med program utvecklings processen på en sida och produktions åtgärderna fungerar på den andra. De två är anslutna till den vanliga pipelinen som är byggd för att ta koden från en utvecklare, Shepherd den genom det önskade antalet tester och steg och sedan flytta koden till produktion.
Limoncelli noterar att DevOps-tekniker börjar i utvecklings miljön och automatiserar stegen mot produktion. När du är klar går de tillbaka för att optimera Flask halsar.
SREs, å andra sidan, fokuserar på produktions åtgärder och når djup i pipelinen som ett sätt att förbättra slut resultatet (i princip fungerar i motsatt riktning).
Det är skillnad i SRE-och DevOps-fokus som kan hjälpa dig att skilja dem åt.
## <a name="coexistence-in-the-same-organization"></a>Samexistens i samma organisation
Den slutliga fråga vi vill adressera är "kan du ha både SRE och DevOps i samma organisation?"
Svaret på den här frågan är en Emphatic "Ja!".
Vi hoppas att de tidigare svaren ger någon uppfattning om hur de två drifts metoderna överlappar och, om de inte överlappar, hur de kan komplettera i fokus. Organisationer med en etablerad DevOps-praxis kan experimentera med SRE-praxis på en liten skala (till exempel testa SLIs och SLO: erna) utan att du behöver göra något för att skapa SRE-positioner eller team. Det här är ett ganska vanligt SREt införande mönster.
## <a name="next-steps"></a>Nästa steg
Vill du veta mer om hur du lär dig mer om platsens tillförlitlighet eller DevOps? Kolla på vår [webbplats för Tillförlitlighets teknik](../index.yml) och [Azure DevOps Resource Center](https://docs.microsoft.com/azure/devops/learn/).
| 78.202381 | 680 | 0.803775 | swe_Latn | 1.000007 |
d5a22436838623d7729d6dbf976ae28bcf2527ed | 521 | md | Markdown | src/doc/unstable-book/src/language-features/const-fn.md | ofek/rust | b16c7a235fa0f57fed6b7ec13ffd3cff1bcdd9ad | [
"ECL-2.0",
"Apache-2.0",
"MIT-0",
"MIT"
] | 23 | 2017-11-08T12:00:59.000Z | 2017-11-23T03:06:53.000Z | src/doc/unstable-book/src/language-features/const-fn.md | ofek/rust | b16c7a235fa0f57fed6b7ec13ffd3cff1bcdd9ad | [
"ECL-2.0",
"Apache-2.0",
"MIT-0",
"MIT"
] | 9 | 2017-07-17T20:14:20.000Z | 2017-09-05T20:31:32.000Z | src/doc/unstable-book/src/language-features/const-fn.md | ofek/rust | b16c7a235fa0f57fed6b7ec13ffd3cff1bcdd9ad | [
"ECL-2.0",
"Apache-2.0",
"MIT-0",
"MIT"
] | 3 | 2019-05-09T17:38:24.000Z | 2020-11-22T22:01:16.000Z | # `const_fn`
The tracking issue for this feature is: [#24111]
[#24111]: https://github.com/rust-lang/rust/issues/24111
------------------------
The `const_fn` feature allows marking free functions and inherent methods as
`const`, enabling them to be called in constants contexts, with constant
arguments.
## Examples
```rust
#![feature(const_fn)]
const fn double(x: i32) -> i32 {
x * 2
}
const FIVE: i32 = 5;
const TEN: i32 = double(FIVE);
fn main() {
assert_eq!(5, FIVE);
assert_eq!(10, TEN);
}
```
| 17.366667 | 76 | 0.642994 | eng_Latn | 0.877481 |
d5a30627d42989657358eeaa32b9e96ad64d075c | 12,989 | md | Markdown | docs/analytics-platform-system/configure-infiniband-network-adapters.md | KochertNinja/sql-docs | 04c031f7411aa33e2174be11dfced7feca8fbcda | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-05-24T03:55:49.000Z | 2019-05-24T03:55:49.000Z | docs/analytics-platform-system/configure-infiniband-network-adapters.md | KochertNinja/sql-docs | 04c031f7411aa33e2174be11dfced7feca8fbcda | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/analytics-platform-system/configure-infiniband-network-adapters.md | KochertNinja/sql-docs | 04c031f7411aa33e2174be11dfced7feca8fbcda | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-04-02T15:42:37.000Z | 2019-04-02T15:42:37.000Z | ---
title: Configure InfiniBand - Analytics Platform System | Microsoft Docs
description: Describes how to configure the InfiniBand network adapters on a non-appliance client server to connect to the Control node on Parallel Data Warehouse (PDW). Use these instructions for basic connectivity and for high availability, so that loading, backup, and other processes automatically connect to the active InfiniBand network.
author: mzaman1
manager: craigg
ms.prod: sql
ms.technology: data-warehouse
ms.topic: conceptual
ms.date: 04/17/2018
ms.author: murshedz
ms.reviewer: martinle
---
# Configure InfiniBand network adapters for Analytics Platform System
Describes how to configure the InfiniBand network adapters on a non-appliance client server to connect to the Control node on Parallel Data Warehouse (PDW). Use these instructions for basic connectivity and for high availability, so that loading, backup, and other processes automatically connect to the active InfiniBand network.
## <a name="Basics"></a>Description
These instructions show you how to find and then set the correct InfiniBand IP addresses and subnet masks on your InfiniBand-connected server. They also explain how to set your server to use the APS appliance DNS so that your connection resolves to the active InfiniBand network.
For high availability, APS has two InfiniBand networks, one active and one passive. Each InfiniBand network has a different IP address for the Control node. If the active InfiniBand network goes down, the passive InfiniBand network becomes the active network. When this happens a script or process automatically connects to the active InfiniBand network without changing the script parameters.
Specifically, in this article you:
1. Find the InfiniBand IP addresses of the APS DNS servers (appliance_domain-AD01 and appliance_domain*-AD02). To do this you log into the AD01 and AD02 servers and get the IP addresses for each InfiniBand network. The InfiniBand IP addresses on the AD node are the DNS IP addresses.
2. Configure each network adapter to use an available IP address on the APS InfiniBand networks.
1. If you have two InfiniBand network adapters, you configure one adapter with an available IP address in the first InfiniBand network which is called TeamIB1, and the other adapter with an available IP address in the second InfiniBand network which is called TeamIB2. Use the appliance_domain-AD01 TeamIB1 IP address as the preferred DNS server and appliance_domain-AD02 TeamIB1 IP address as the alternate DNS server for TeamIB1 network adapter. Use the appliance_domain-AD01 TeamIB2 IP address as the preferred DNS server and appliance_domain-AD02 TeamIB2 IP address as the alternate DNS server for TeamIB2 network adapter.
2. If you have only one InfiniBand network adapter, you configure the adapter with an available IP address from one of the InfiniBand networks. Then you configure the preferred and the alternate DNS servers on this adapter using either appliance_domain-AD01 TeamIB1 and appliance_domain-AD02 TeamIB1 or using appliance_domain-AD01 TeamIB2 and appliance_domain-AD02 TeamIB2 whichever is on the same network as the configured adapter as the preferred and the alternate DNS servers respectively.
3. Configure your InfiniBand network adapter to use APS DNS servers to resolve your connection to the active InfiniBand network.
1. To configure this you use the advanced TCP/IP settings to add the appliance domain DNS suffix to the beginning of the list of DNS suffixes on your client server. This only needs to be configured on one of the network adapters; the setting applies to both adapters.
After configuring your InfiniBand network adapters, client processes can connect to the Control node on the InfiniBand network by using `PDW_region-SQLCTL01` for the address of the server. Your server appends the Analytics Platform System DNS suffix, or you can enter the complete address which is `PDW_region-SQLCTL01.appliance_domain.pdw.local`.
For example, if your PDW region name is MyPDW and the appliance name is MyAPS, the dwloader server specification for loading data is one of the following:
- `dwloader -S MYPDW-SQLCTL01.MyAPS.pdw.local`
- `dwloader -S MYPDW-SQLCTL01`
## <a name="BeforeBegin"></a>Before You Begin
### Requirements
You need an APS appliance domain account to log in to the AD01 node. For example, F12345*\Administrator.
You need a Windows account on the client server that has permission to configure the network adapters.
### Prerequisites
These instructions assume the client server is already racked and cabled to the appliance InfiniBand network. For racking and cabling instructions, see [Acquire and Configure a Loading Server](acquire-and-configure-loading-server.md).
### General Remarks
By using SQLCTL01, the Analytics Platform System DNS connects your client server to the Control node by using the active InfiniBand network. This applies only to getting connected; if the InfiniBand network goes down during a load or backup, you need to restart the process.
To meet your own business requirements, you can also join the client server to your own non-appliance workgroup or Windows domain.
## <a name="Sec1"></a>Step 1: Obtain the appliance InfiniBand network settings
*To obtain the appliance InfiniBand network settings*
1. Log in to the appliance AD01 node by using the appliance_domain\Administrator account.
2. On the appliance AD01 node, open the Control Panel, select Network and Internet, select Network and Sharing Center*, and then select Change Adapter Settings.
3. In the Network Connections window, right-click on Team IB1 and select Properties.
4. From the Internet Protocol Version 4 (TCP/IPv4) Properties window, write down the values for the **IP address** and **Subnet mask**. The IP address of the **_appliance\_domain_-AD01** node is the IP address of the Analytics Platform System DNS server.
5. Repeat steps 1-5 above for the TeamIB1 adapter on **_appliance\_domain_-AD02** server.
6. Click Cancel to close the window.
7. Find an unused IP address on the TeamIB1 network, and write it down.
To find an unused IP address, open a command window and try to ping IP addresses within the range of addresses for your appliance. In this example, the IP address of the TeamIB1 network is 172.16.14.30. Find an IP address that starts with 172.16.14 that is not used. For example, from the command-line enter "ping 172.16.14.254". If the ping request is unsuccessful, the IP address is available.
8. Do the same thing for TeamIB2. In the*Network Connections window, right-click on Team IB2 and select Properties.
9. From the Internet Protocol Version 4 (TCP/IPv4) Properties window, write down the values for the IP address and Subnet mask for TeamIB2.
10. Repeat steps 8-9 above for the TeamIB2 adapter on appliance_domain-AD02 server.
11. Find an unused IP address on the **TeamIB2** network, and write it down.
To find an unused IP address, open a command window and try to ping IP addresses within the range of addresses for your appliance. In this example, the IP address of the TeamIB2 network is 172.16.18.30. Find an IP address that starts with 172.16.18 that is not used. For example, from the command-line enter "ping 172.16.18.254". If the ping request is unsuccessful, the IP address is available.
## <a name="Sec2"></a>Step 2: Configure the InfiniBand Network Adapter Settings on Your Client Server
### Notes
- These steps show you how to register your server with the APS DNS servers.
- To meet your own network needs, you can also join the client server to your own non-appliance workgroup or Windows domain.
- The instructions step through configuring two network adapters on each server. If you only have one network adapter, pick one of the networks to configure on the network adapter, and then add the second DNS IP address as an alternate DNS server.
### To configure the InfiniBand network adapter settings on your client server
1. Log in as a Windows administrator to your loading, backup, or other client server on the appliance InfiniBand network.
2. Open the Control Pane*, select Network and Sharing Center, and then select Change Adapter Settings.
### To configure the first network adapter
1. In the Network Connections window, right-click on one of the unidentified network slots for the Mellanox Adapter and select Properties.
2. In the Properties window
1. On the General tab, set the IP address to the IP address that you verified as free in the ping test for TeamIB1. For the example values used in this article, you would enter 172.16.14.254.
2. Set the subnet mask to the subnet mask you wrote down for TeamIB1.
3. Set the Preferred DNS server to the IP address of TeamIB1 that you wrote down earlier from the appliance_domain*-AD01 node.
4. Set the Alternate DNS server to the IP address of TeamIB1 that you wrote down earlier from the appliance_domain*-AD02 node.
5. Click OK to apply the changes.
### To configure the second network adapter
1. Skip this section if you only have one network adapter.
2. In the Network Connections window, right-click on the second unidentified network slot for the Mellanox Adapter and select Properties.
3. In the Properties window
1. On the General tab, set the IP address to the IP address that you verified as free in the ping test for TeamIB2. For the example values used in this article, you would enter 172.16.18.254.
2. Set the subnet mask to the subnet mask you wrote down for TeamIB2.
3. Set the Preferred DNS server to the IP address of TeamIB2 that you wrote down earlier from the appliance_domain*-AD01 node.
4. Set the Alternate DNS server to the IP address of TeamIB2 that you wrote down earlier from the appliance_domain*-AD02 node.
> [!NOTE]
> If you only have one network adapter, configure the preferred and the alternate DNS servers using either the appliance AD01 TeamIB1 and appliance AD02 TeamIB1 as the preferred and the alternate DNS servers respectively, or use the appliance AD01 TeamIB2 and appliance AD02 TeamIB2 as the preferred and the alternate DNS servers depending on if the AD virtual machine has failed over.
5. Click OK to apply the changes.
### To configure the DNS suffix
1. In the Network Connections window, right-click on one of the network slots for the Mellanox Adapter and select Properties.
2. Click on the Advanced... button.
3. In the Advanced TCP/IP Settings window, if the Append these DNS Suffixes (in order) option is not greyed out, check the box called Append these DNS suffixes (in order):, select the appliance domain suffix, and click Add.... The appliance domain suffix is `appliance_domain.local`
4. If the Append these DNS suffixes (in order): option is greyed out, you can add the APS domain to this server by modifying the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient.
5. For faster address resolution, we recommend moving the appliance suffix to the top of the list.
6. Click OK.
7. Now, you can connect to the appliance Infiniband network by using `PDW_region-SQLCTL01.appliance_domain.local`, or simply `appliance_domain-SQLCTL01`. The connection might be established faster if you connect with the full name and DNS suffix.
Examples for an appliance named MyAPS with a MyPDW PDW region:
- MyPDW-SQLCTL01.MyAPS.local
- MyPDW-SQLCTL01
## See Also
[Acquire and Configure a Loading Server](acquire-and-configure-loading-server.md)
| 71.368132 | 634 | 0.755177 | eng_Latn | 0.993948 |
d5a390fee0e3ad96b3bace02aafff19cfdea5978 | 2,448 | md | Markdown | docs_src/src/guide/README.md | gmgalvan/goyave | 7a5f678cdcba05bd6fea30f3c508c7807844dea8 | [
"MIT"
] | 1 | 2020-10-31T00:54:50.000Z | 2020-10-31T00:54:50.000Z | docs_src/src/guide/README.md | gmgalvan/goyave | 7a5f678cdcba05bd6fea30f3c508c7807844dea8 | [
"MIT"
] | null | null | null | docs_src/src/guide/README.md | gmgalvan/goyave | 7a5f678cdcba05bd6fea30f3c508c7807844dea8 | [
"MIT"
] | null | null | null | ---
meta:
- name: "og:title"
content: "Introduction - Goyave"
- name: "twitter:title"
content: "Introduction - Goyave"
- name: "title"
content: "Introduction - Goyave"
---
# Introduction
Welcome to the Goyave documentation!
This documentation is both a guide and a reference for Goyave application building. You will find instructions covering the basics as well as more advanced topics, from project setup to deployment. But first, let's talk about the framework itself.
Goyave is a Golang web API framework aiming at **cleanliness**, **fast development** and **power**. Goyave applications stay clean and concise thanks to minimalist function calls and route handlers. The framework gives you all the tools to create an easily readable and maintainable web applications, which let you concentrate on the business logic. Although Goyave handles many things for you, such as headers or marshaling, this characteristic doesn't compromise on your freedom of code.
Most golang frameworks for web development don't have a strong directory structure nor conventions to make applications have a uniform architecture and limit redundancy. This makes it difficult to work with them on different projects. In companies, having a well-defined and documented architecture helps new developers integrate projects faster, and reduces the time needed for maintaining them. For open source projects, it helps newcomers understanding the project and makes it easier to contribute. With Goyave, expect a full package with minimum setup.
::: tip Note
Please feel free to sudgest changes, ask for more details, report grammar errors, or notice of uncovered scenarios by [creating an issue](https://github.com/System-Glitch/goyave/issues/new/choose) with the proposal template.
:::
## Discord
Come and learn about the framework, stay updated on the progress, be notified when there is a new release, get help, suggest new features or changes, contribute to the project, and more!
<p align="center">
<a href="https://discord.gg/mfemDMc">
<img src="https://discord.com/api/guilds/744264895209537617/widget.png?style=banner2" alt="Discord">
</a>
</p>
## Contributors
A big "Thank you" to the Goyave contributors:
- [Kuinox](https://github.com/Kuinox) (Powershell install script)
- [Alexandre GV.](https://github.com/alexandregv) (Install script MacOS compatibility)
- [jRimbault](https://github.com/jRimbault) (CI and code analysis)
| 58.285714 | 557 | 0.77451 | eng_Latn | 0.991737 |
d5a43fc00d91a4675923d085a9b8bdfdc9bf64b3 | 763 | md | Markdown | docs/義肢/副木/3. 臨床檢查.md | liaoyuju/miniature-octo-fortnight | 0105880960410481b33c9397472e401362ef6974 | [
"MIT"
] | null | null | null | docs/義肢/副木/3. 臨床檢查.md | liaoyuju/miniature-octo-fortnight | 0105880960410481b33c9397472e401362ef6974 | [
"MIT"
] | null | null | null | docs/義肢/副木/3. 臨床檢查.md | liaoyuju/miniature-octo-fortnight | 0105880960410481b33c9397472e401362ef6974 | [
"MIT"
] | null | null | null | ## 臨床檢查
- history：訪談
- observation：關節穩定性
- 0：僵直
- 3：正常
- 6：不穩
- palpation 觸診
- assessments：ROM, MMT, ViAS, VeAS, 2PD, SWMT, functional test
- follow up consideration
- 受壓部位
- 順著手臂的外型輪廓製作
- 在變形的位置施加最小的拉力→慢慢改善，而不是一步到位
- 使用pad增加表面積以分散壓力
- 水腫
- 治療計劃（時間因子）
- 病人順從性compliance
- 護理
## 特別關注
- 符合生理需求
- static splints應間隔性地穿戴，並作為運動計畫的一部份
- 病人需在心理上接受副木的外觀
- 副木的機械性會影響到材料的選擇
- 好的設計
- 保持在自然的arch
- 保留正常的動作維度
- 讓好的肌肉可以發揮功能
- 提供最實用的抓握模式
- 最佳穩定度下能有最大的活動度
- 掌心、指腹要露出來→感覺接收
## 臨床推理
- interactive
- narrative
- pragmatic
- conditional
- procedural
## 大步驟
- client
- referral
- design
- monitor
- adjust | 16.955556 | 64 | 0.559633 | yue_Hant | 0.977818 |
d5a45c425e7eaeaf995ecbb9a3e1e764d0bc7f6b | 3,126 | md | Markdown | articles/marketplace/marketplace-managed-apps.md | BaherAbdullah/azure-docs | 65d82440dd3209697fdb983ef456b0a2293e270a | [
"CC-BY-4.0",
"MIT"
] | 7,073 | 2017-06-27T08:58:22.000Z | 2022-03-30T23:19:23.000Z | articles/marketplace/marketplace-managed-apps.md | BaherAbdullah/azure-docs | 65d82440dd3209697fdb983ef456b0a2293e270a | [
"CC-BY-4.0",
"MIT"
] | 87,608 | 2017-06-26T22:11:41.000Z | 2022-03-31T23:57:29.000Z | articles/marketplace/marketplace-managed-apps.md | BaherAbdullah/azure-docs | 65d82440dd3209697fdb983ef456b0a2293e270a | [
"CC-BY-4.0",
"MIT"
] | 17,093 | 2017-06-27T03:28:18.000Z | 2022-03-31T20:46:38.000Z | ---
title: Azure applications managed application offer publishing guide - Azure Marketplace
description: This article describes the requirements for publishing a managed application in Azure Marketplace.
ms.service: marketplace
ms.subservice: partnercenter-marketplace-publisher
ms.topic: conceptual
author: msjogarrig
ms.author: jogarrig
ms.date: 09/04/2020
---
# Publishing guide for Azure managed applications
An Azure *managed application* offer is one way to publish an Azure application in Azure Marketplace. Managed applications are transact offers that are deployed and billed through Azure Marketplace. The listing option that a user sees is *Get It Now*.
This article explains the requirements for the managed application offer type.
Use the managed application offer type under the following conditions:
- You're deploying a subscription-based solution for your customer by using either a virtual machine (VM) or an entire infrastructure as a service (IaaS)-based solution.
- You or your customer requires the solution to be managed by a partner.
>[!NOTE]
>For example, a partner can be a systems integrator or a managed service provider (MSP).
## Managed application offer requirements
|Requirements |Details |
|---------|---------|
|An Azure subscription | Managed applications must be deployed to a customer's subscription, but they can be managed by a third party. |
|Billing and metering | The resources are provided in a customer's Azure subscription. Azure Resources that use the pay-as-you-go payment model are transacted with the customer via Microsoft and billed via the customer's Azure subscription. <br><br> For bring-your-own-license Azure Resources, Microsoft bills any infrastructure costs that are incurred in the customer subscription, but you transact software licensing fees with the customer directly. |
|An Azure Managed Application package | The configured Azure Resource Manager Template and Create UI Definition that will be used to deploy your application to the customer's subscription.<br><br>For more information about creating a Managed Application, see [Managed Application Overview](../azure-resource-manager/managed-applications/publish-service-catalog-app.md).|
---
> [!NOTE]
> Managed applications must be deployable through Azure Marketplace. If customer communication is a concern, reach out to interested customers after you've enabled lead sharing.
> [!Note]
> A Cloud Solution Provider (CSP) partner channel opt-in is now available. For more information about marketing your offer through the Microsoft CSP partner channels, see [Cloud Solution Providers](./cloud-solution-providers.md).
## Next steps
If you haven't already done so, learn how to [Grow your cloud business with Azure Marketplace](https://azuremarketplace.microsoft.com/sell).
To register for and start working in Partner Center:
- [Sign in to Partner Center](https://partner.microsoft.com/dashboard/account/v3/enrollment/introduction/partnership) to create or complete your offer.
- See [Create an Azure application offer](azure-app-offer-setup.md) for more information.
| 62.52 | 464 | 0.792067 | eng_Latn | 0.993135 |
d5a4c47c7f3ac66da9be89904a0c205c9a658053 | 4,078 | md | Markdown | microservices.md | daveshap/RavenAGI | 71a78f34de752a8ba5c48caf5385b953aa0e1a83 | [
"MIT"
] | 1 | 2021-04-07T04:50:57.000Z | 2021-04-07T04:50:57.000Z | microservices.md | daveshap/RavenAGI | 71a78f34de752a8ba5c48caf5385b953aa0e1a83 | [
"MIT"
] | null | null | null | microservices.md | daveshap/RavenAGI | 71a78f34de752a8ba5c48caf5385b953aa0e1a83 | [
"MIT"
] | null | null | null | # Microservices
## What is a microservice?
A microservice is a standalone component of a larger application. It's like an interchangeable part. It allows for segmented and iterative development of a large application. The biggest tech companies you're familiar with all use a microservices architecture. Microservices allow for smaller teams of experts to work on their part of the larger application without worrying about breaking everything else. This makes programming easier, safer, and more accessible.
## How do I design a microservice?
Microservices have three primary components: input, processing, and output. Raven microservices look for messages in the nexus and then use those messages to perform some kind of processing. In many cases, they feed the input from the messages into a *prompt* that is then fed to a cognitive engine, such as GPT-3, to provide some kind of output. The output is then sent back to the nexus. Put another way:
1. Input
2. Processing
3. Output
Some microservices interact with the outside world. For instance you might have a speech-to-text service that allows Raven to listen to the real world. You might also have a text-to-speech service that allows Raven to speak. Then you might have another service that searches Wikipedia for additional information to add to the nexus. The sky is the limit! If you need ideas, please check out the **Architecture** and **Roadmap** pages.
## Microservice Best Practices
Here are a few guiding principles to follow:
1. Microservices should do only one thing (hence *micro*).
2. Microservices should only query the nexus for what they need, instead of pulling everything. This will save on bandwidth and processing time.
3. Microservices should be responsible for remembering what they have and have not seen.
4. Microservices must keep track of the messages to which they are responding as well as their original context.
5. Microservices for the MVP should start with `svc_` in the name.
6. If a microservice needs a prompt, it should have its own dedicated prompt.
## Advantages of Microservices
The largest tech companies in the world have all migrated to microservices architectures for a few very good reasons!
- **Easier to design.** A microservice is small, and therefore simpler than a larger service or monolithic application.
- **Easier to troubleshoot.** The bigger your application is, the harder it is to understand and diagnose.
- **Easier to specialize.** Let's say you're an expert in speech. You will be more productive if all you have to focus on is speech, rather than security or databases. You can also write your microservice in whatever language you want.
- **Easier to deploy.** Microservices are smaller and inherently more flexible. You can deploy them in containers, such as with Docker or OpenShift.
## Disadvantages of Microservices
While microservices have plenty of advantages, there are some costs.
- **Distributed thinking.** Microservices require you to think about programming in a distributed manner and use APIs.
- **More to keep track of.** Microservices are independent application components, meaning you need to keep track of all of them.
- **Complex interactions.** Microservices are distributed across networks and multiple compute nodes, introducing different bottlenecks and failure points.
## Types of Microservices
Raven will ultimately have quite a few types of microservices. This list is not exhaustive.
- **Sensors.** These are the services that take input from the outside world, such as audio and video.
- **Executive.** These are the services that generate some kind of output (such as audio, video, or robotic action).
- **Cognitive.** These are the thinking services, such as action generation, action iteration, and Core Objective Functions.
- **Metacognition.** These are the services that monitor what Raven is thinking about and modify Raven's priorities. For example, the inhibition microservice halts lines of thought on completed topics. The fact-checking service ensures that Raven doesn't say false things. | 78.423077 | 466 | 0.791074 | eng_Latn | 0.999465 |
d5a6300ed3f64c9ab4f1a77bf19dfe229133e862 | 2,138 | md | Markdown | README.md | rebelloV/ctzn-extended | 932ba35e183a951a136fd0294624a9c6b76cf2e3 | [
"MIT"
] | null | null | null | README.md | rebelloV/ctzn-extended | 932ba35e183a951a136fd0294624a9c6b76cf2e3 | [
"MIT"
] | null | null | null | README.md | rebelloV/ctzn-extended | 932ba35e183a951a136fd0294624a9c6b76cf2e3 | [
"MIT"
] | null | null | null | # CTZN Extended ("CTZN" pronounced "Citizen")
CTZN is a decentralized social network with a strong focus on building communities initally created by Paul Frazee, CTZN Extended is a new fork created by early CTZN user, Joe Harley, to teach himself about JavaScript and improve upon the original CTZN platform (think what C++ is to C!)
**Standard CTZN Features**
- Status feeds with 256 character limits but the ability to post "extended text" with no limit (shows on expand).
- Social following and moderated communities.
- Threaded comments.
- Decentralized hosting (anybody can create a server, and data syncs using the [Hypercore Protocol](https://hypercore-protocol.org)).
Read the [initial design document](./docs/design.md) to learn more about the architecture.
## CTZN Extended - possible features roadmap
- Incorporate private messaging features.
- Create built-in Fediverse bridging software.
- Allow further theme customisation.
- Add the ability for built SSH/Telnet text-mode viewing.
- Create groupware systems based on CTZN.
## ⚠️ Alpha Software
CTZN (and by extestion, CTZN Extended) is still in development! If you decide to run a server or build against the protocol, beware that breaking changes may occur and won't always be communicated ahead of time.
## 📚 Standard CTZN Docs
- **Setup**
- [**How to set up a CTZN server**](./docs/setting-up-a-server.md)
- [**How to work on the CTZN codebase**](./docs/developer-setup.md)
- **Architecture**
- [**Design overview**](./docs/design.md)
- [**Roadmap**](./docs/roadmap.md)
- [**APIs**](./docs/apis.md)
- [**Database schemas overview**](./docs/schemas.md)
- [**Database methods**](./docs/dbmethods.md)
- [**Community roles system**](./docs/community-roles.md)
- [**Community permissions system**](./docs/permissions.md)
### 📺 Videos
Standard CTZN's development has been live-streamed from day 1. You can [watch the archives on YouTube](https://www.youtube.com/channel/UCSkcL4my2wgDRFvjQOJzrlg).
### Attributions
### Default item-class icon
Icon licensed under CC BY 3.0: [icon king 1](https://freeicons.io/profile/3)
----
| 41.921569 | 287 | 0.727783 | eng_Latn | 0.969528 |
d5a653eff0d7fbc498e60ce954120a14cdb55c2b | 1,093 | md | Markdown | Base/usr/share/man/man7/Shell-vars.md | martingms/serenity | f68ed6d25ba0d8327fabcb24cb6b70ef051c7da0 | [
"BSD-2-Clause"
] | 1 | 2021-06-11T19:25:48.000Z | 2021-06-11T19:25:48.000Z | Base/usr/share/man/man7/Shell-vars.md | martingms/serenity | f68ed6d25ba0d8327fabcb24cb6b70ef051c7da0 | [
"BSD-2-Clause"
] | null | null | null | Base/usr/share/man/man7/Shell-vars.md | martingms/serenity | f68ed6d25ba0d8327fabcb24cb6b70ef051c7da0 | [
"BSD-2-Clause"
] | 1 | 2020-06-05T18:55:38.000Z | 2020-06-05T18:55:38.000Z | ## Name
Shell Variables - Special local and environment variables used by the Shell
## Description
The Shell uses various variables to allow for customisations of certain behavioural or visual things.
Such variables can be changed or set by the user to tweak how the shell presents things.
## Behavioural
1. Output interpretations
`IFS` (local)
The value of this variable is used to join lists or split strings into lists, its default value is a newline (`\\n`).
## Visual
2. Prompting
`PROMPT` (environment)
The value of this variable is used to generate a prompt, the following escape sequences can be used literally inside the value, and they would expand to their respective values:
- `\\u` : the current username
- `\\h` : the current hostname
- `\\w` : a collapsed path (relative to home) to the current directory
- `\\p` : the string '$' (or '#' if the user is 'root')
Any other escaped character shall be ignored.
`PROMPT_EOL_MARK` (environment)
The value of this variable is used to denote the ends of partial lines (lines with no newline), its default value is '%'.
| 28.763158 | 177 | 0.743824 | eng_Latn | 0.999409 |
d5a7adb8131fc0887d80a162b072c8cd65c16398 | 33 | md | Markdown | README.md | ridwanzal/edo_mvc | dd0cfacd465a49d203654d3be01fef07d0c9932d | [
"MIT"
] | 1 | 2019-11-12T01:24:16.000Z | 2019-11-12T01:24:16.000Z | README.md | ridwanzal/edo_mvc | dd0cfacd465a49d203654d3be01fef07d0c9932d | [
"MIT"
] | 1 | 2022-02-10T18:16:45.000Z | 2022-02-10T18:16:45.000Z | README.md | ridwanzal/edo_mvc | dd0cfacd465a49d203654d3be01fef07d0c9932d | [
"MIT"
] | null | null | null | # edo_mvc
My Personal Web based
| 11 | 22 | 0.757576 | eng_Latn | 0.989735 |
d5a80e380170e7ed36bb1bfee5a39d83234c7666 | 1,804 | md | Markdown | src/strategies/balance-in-vdfyn-vault/README.md | OccamFi/snapshot-strategies | 375d797855d61794dcca03f0a7c29bee723f891f | [
"MIT"
] | 73 | 2021-08-05T16:03:19.000Z | 2022-03-30T15:13:32.000Z | src/strategies/balance-in-vdfyn-vault/README.md | OccamFi/snapshot-strategies | 375d797855d61794dcca03f0a7c29bee723f891f | [
"MIT"
] | 217 | 2021-08-02T14:41:58.000Z | 2022-03-31T06:29:21.000Z | src/strategies/balance-in-vdfyn-vault/README.md | OccamFi/snapshot-strategies | 375d797855d61794dcca03f0a7c29bee723f891f | [
"MIT"
] | 313 | 2021-08-02T13:29:07.000Z | 2022-03-31T21:23:46.000Z | # vDfyn contract call strategy
This strategy allows users to calculate the total amount of Dfyn staked by the user in the vDfyn vault.
## Example
The space config will look like this:
```JSON
{
"strategies": [
["balance-in-vdfyn-vault", {
// vDfyn vault contract
"contractAddress": "0x75455c3DE45dD32CBE9a5aD5E518D3D50823c976",
// scoreMultiplier can be used to increase users' scores by a certain magnitude
"scoreMultiplier": 2,
// ABI for balanceOf method
"methodABI": [
{
"inputs": [
{
"internalType": "address",
"name": "account",
"type": "address"
}
],
"name": "balanceOf",
"outputs": [
{
"internalType": "uint256",
"name": "",
"type": "uint256"
}
],
"stateMutability": "view",
"type": "function"
},
{
"inputs": [],
"name": "ratio",
"outputs": [
{
"internalType": "uint256",
"name": "dfynAmount_",
"type": "uint256"
}
],
"stateMutability": "view",
"type": "function"
}
]
}],
]
}
```
| 32.214286 | 103 | 0.329268 | eng_Latn | 0.609219 |
d5a841e30d38f7d7bb63e0295b76fe94630bfcde | 1,002 | md | Markdown | content/post/statmodeling-stat-columbia-edu-2020-05-14-so-much-of-academia-is-about-connections-and-reputation-laundering.md | chuxinyuan/daily | dc201b9ddb1e4e8a5ec18cc9f9b618df889b504c | [
"MIT"
] | 8 | 2018-03-27T05:17:56.000Z | 2021-09-11T19:18:07.000Z | content/post/statmodeling-stat-columbia-edu-2020-05-14-so-much-of-academia-is-about-connections-and-reputation-laundering.md | chuxinyuan/daily | dc201b9ddb1e4e8a5ec18cc9f9b618df889b504c | [
"MIT"
] | 16 | 2018-01-31T04:27:06.000Z | 2021-10-03T19:54:50.000Z | content/post/statmodeling-stat-columbia-edu-2020-05-14-so-much-of-academia-is-about-connections-and-reputation-laundering.md | chuxinyuan/daily | dc201b9ddb1e4e8a5ec18cc9f9b618df889b504c | [
"MIT"
] | 12 | 2018-01-27T15:17:26.000Z | 2021-09-07T04:43:12.000Z | ---
title: So much of academia is about connections and reputation laundering
date: '2020-05-14'
linkTitle: https://statmodeling.stat.columbia.edu/2020/05/14/so-much-of-academia-is-about-connections-and-reputation-laundering/
source: Statistical Modeling, Causal Inference, and Social Science
description: 'There are two ways of looking at this: 1. Statistics / numerical analysis
/ data science is a lot harder than you, the reader of this blog, might think. 2.
Academia, like any other working environment, is full of prominent, successful,
well-connected bluffers. Someone sent me this: and this followup: I clicked around
a bit, ...'
disable_comments: true
---
There are two ways of looking at this: 1. Statistics / numerical analysis / data science is a lot harder than you, the reader of this blog, might think. 2. Academia, like any other working environment, is full of prominent, successful, well-connected bluffers. Someone sent me this: and this followup: I clicked around a bit, ... | 77.076923 | 329 | 0.773453 | eng_Latn | 0.997625 |
d5a8e5d2f259ceb7d12eac738edfb4ba6495cfd6 | 94 | md | Markdown | README.md | wiipsp/Matrix | d0060baa0a6c563a9d23ea2e97c9b691e5c6a10f | [
"Apache-2.0"
] | null | null | null | README.md | wiipsp/Matrix | d0060baa0a6c563a9d23ea2e97c9b691e5c6a10f | [
"Apache-2.0"
] | null | null | null | README.md | wiipsp/Matrix | d0060baa0a6c563a9d23ea2e97c9b691e5c6a10f | [
"Apache-2.0"
] | null | null | null | # Matrix
A game used cocos2d-x engine. Can deploy to Android, IOS, Mac, Win32, Linux and WP8.
| 31.333333 | 84 | 0.734043 | eng_Latn | 0.904914 |
d5a8f46d35e3d19b05913fe414db65a128fca485 | 1,228 | md | Markdown | modules/402-ingress-nginx/images/controller-0-26/patches/README.md | p3rd/deckhouse | aad6bf45d58a2b981e0ec05f2cb093d9afb9ae56 | [
"Apache-2.0"
] | 596 | 2020-11-12T12:16:12.000Z | 2022-03-26T23:49:13.000Z | modules/402-ingress-nginx/images/controller-0-26/patches/README.md | p3rd/deckhouse | aad6bf45d58a2b981e0ec05f2cb093d9afb9ae56 | [
"Apache-2.0"
] | 851 | 2021-07-01T06:49:47.000Z | 2022-03-31T18:41:30.000Z | modules/402-ingress-nginx/images/controller-0-26/patches/README.md | aksemats/deckhouse | 253c812a76988948d721e8831d3757906a90cfa5 | [
"Apache-2.0"
] | 32 | 2021-07-04T11:03:17.000Z | 2022-03-23T14:09:18.000Z | ## Patches
### Reason
Properly show the reason in templates.
It was accepted to the upstream.
https://github.com/kubernetes/ingress-nginx/pull/5213
## Omit helm secrets
The problem is that the ingress nginx controller subscribes to all secrets.
If there are a lot of helm secrets in the cluster, kube-apiserver will consume a significant amount of memory.
It was accepted to the upstream.
https://github.com/kubernetes/ingress-nginx/pull/5702
## Nginx TPL
* Enable our metrics collector instead of the default one.
* Enable pcre_jit.
* Add the health check server to provide the way for an external load balancer to check that the ingress controller will be terminated soon.
We do not intend to make a PR to the upstream with these changes, because there are only our custom features.
## Ingress information
There are two patches to fix the problem with ingress names in logs and metrics.
Unfortunately, the PR was declined in the upstream.
https://github.com/kubernetes/ingress-nginx/pull/4367
# Pod IP
This is a small patch to fix the problem with the ingress controller pod listening on 0.0.0.0 in the host network mode.
Our PR was reverted in the upstream.
https://github.com/kubernetes/ingress-nginx/issues/2262
| 35.085714 | 140 | 0.785831 | eng_Latn | 0.994427 |
d5a99ec173c999c364ad42babb41d0624081e612 | 2,924 | md | Markdown | Gathered CTF writeups/2019-11-07--defcamp-dctf-ENISA-Hackfest-2020 (and quals)/hello-nemo.md | mihaid-b/CyberSakura | f60e6b6bfd6898c69b84424b080090ae98f8076c | [
"MIT"
] | 1 | 2022-03-27T06:00:41.000Z | 2022-03-27T06:00:41.000Z | Gathered CTF writeups/2019-11-07--defcamp-dctf-ENISA-Hackfest-2020 (and quals)/hello-nemo.md | mihaid-b/CyberSakura | f60e6b6bfd6898c69b84424b080090ae98f8076c | [
"MIT"
] | null | null | null | Gathered CTF writeups/2019-11-07--defcamp-dctf-ENISA-Hackfest-2020 (and quals)/hello-nemo.md | mihaid-b/CyberSakura | f60e6b6bfd6898c69b84424b080090ae98f8076c | [
"MIT"
] | 1 | 2022-03-27T06:01:42.000Z | 2022-03-27T06:01:42.000Z | ### CHALLENGE PROMPT :
We just managed to intercept Cpt. Nemo of the Nautilus submarine. Something's fishy over here...
Download nemo.pcapng and start the investigation.
----------------------------------------------------------------------------------------------------
We are given a network packet capture , *nemo.pcapng* .
Running
>foremost nemo.pcapng
outputs :
|foundat=flag.txtUT <br/>
foundat=flag.txtUT <br/>
*| <br/>
Foremost seems to have found an interesting file , flag.txt , and it also created a .zip folder located
inside the /output/ directory . The zip folder contains two zip files :*00000061.zip* and *00000062.zip*
Peeking inside *00000061.zip* and *00000062.zip* we find out that they contain the flag.txt found earlier,
however when trying to extract the zip files in order to get to the flag we are met with a prompt asking
us for a password . Let's take a look at the pcap and see if we can find the password .
Looking at the protocol hierarchy statistics , we can get a general overview of the protocols used in the
capture . FTP immediately catches my eye , since protocols like FTP , HTTP , TELNET are unencrypted by
default and can reveal a lot of useful information .
---------------------------------------------------------------------------------------
Here is a small snippet of the FTP traffic , in summary by analyzing some more FTP packets we can tell that
someone logs in as user through FTP , and uploads flag.zip . Then , they download a file called password.txt .
---------------------------------------------------------------------------------------
Continuing forward , lets analyze the TELNET packets . Filtering for TELNET in wireshark , we select whichever
packet , right click it , select follow and then follow TCP stream .
We can tell that someone is poking around in here , running a lot of commands . However , aadysgaugysdihsasdh
doesnt seem to be the password for the .zip files .
----------------------------------------------------------------------------------------
In this snippet bellow we see that " dgyfogfoewyeowyefowouevftowyefg " is being written to password.txt :
" ccaatt dgyfogfoewyeowyefowouevftowyefgdgyfogfoewyeowyefowouevftowyefg >> ppaa
.ssss word.txt "
Now unziping 00000061.zip with " dgyfogfoewyeowyefowouevftowyefg " as the password when prompted , we get the flag.
**DCTF{3907879c7744872694209e3ea9d2697508b7a0a464afddb2660de7ed0052d7a7}**
| 44.984615 | 119 | 0.678865 | eng_Latn | 0.959608 |
d5a9addd4b75e77946c4a69d5d9b9c1452f6a518 | 7,451 | md | Markdown | iis/get-started/planning-for-security/understanding-built-in-user-and-group-accounts-in-iis.md | Rich-Lang/iis-docs | 3fc0423f2c1ca43616e24e7781ae49efc9c66016 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-03-19T18:34:42.000Z | 2020-03-19T18:34:42.000Z | iis/get-started/planning-for-security/understanding-built-in-user-and-group-accounts-in-iis.md | Rich-Lang/iis-docs | 3fc0423f2c1ca43616e24e7781ae49efc9c66016 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | iis/get-started/planning-for-security/understanding-built-in-user-and-group-accounts-in-iis.md | Rich-Lang/iis-docs | 3fc0423f2c1ca43616e24e7781ae49efc9c66016 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Understanding Built-In User and Group Accounts in IIS 7 | Microsoft Docs"
author: rick-anderson
description: "Introduction In earlier versions of IIS, a local account called IUSR_MachineName is created during installation. IIS used the IUSR_MachineName account by def..."
ms.author: iiscontent
manager: soshir
ms.date: 11/22/2007
ms.topic: article
ms.assetid: 08c4f998-bb43-4500-90f8-03e3d495683e
ms.technology: iis
ms.prod: iis
msc.legacyurl: /learn/get-started/planning-for-security/understanding-built-in-user-and-group-accounts-in-iis
msc.type: authoredcontent
---
Understanding Built-In User and Group Accounts in IIS 7
====================
by [Saad Ladki](https://twitter.com/saadladki)
## Introduction
In earlier versions of IIS, a local account called IUSR\_MachineName is created during installation. IIS used the IUSR\_MachineName account by default whenever anonymous authentication was enabled. This was used by both the FTP and HTTP services.
There was also a group called IIS\_WPG, which was used as a container for all the application pool identities. During IIS setup, all the appropriate resources on the system were granted the correct user rights for the IIS\_WPG group so that an administrator only needed to add their identity to that group when they created a new application pool account.
This model worked well, but had its drawbacks: the IUSR\_MachineName account and the IIS\_WPG group were both local to the system that they were created on. Every account and group within Windows is given a unique number called a security identifier (SID) that distinguishes it from other accounts. When an ACL is created only the SID is used. As part of the design in earlier versions of IIS, IUSR\_MachineName was included in the metabase.xml file so that if you tried to copy the metabase.xml from one computer to another, it would not work. The account on the other computer would have a different name.
In addition, you could not 'xcopy /o' ACLs from one computer to another since the SIDs were different from computer to computer. One workaround was to use domain accounts, but that required adding an active directory to the infrastructure. The IIS\_WPG group had similar issues with user rights. If you set ACLs on one computer's file system for IIS\_WPG and tried to 'xcopy /o' those over to another computer, it would fail. This experience has been improved in IIS 7 and above by using a built-in account and group.
A built-in account and group are guaranteed by the operating system to always have a unique SID. IIS 7 and above have taken this further and ensured that the actual names that are used by the new account and group will never be localized. For example, regardless of the language of Windows that you install, the IIS account name will always be IUSR and the group name will be IIS\_IUSRS.
In summary, IIS 7 and above offer the following:
- The IUSR built-in account replaces the IUSR\_MachineName account.
- The IIS\_IUSRS built-in group replaces the IIS\_WPG group.
The IUSR account no longer needs a password because it is a built-in account. Logically, you can think of it as being the same as the NETWORKSERVICE or LOCALSERVICE accounts. Both the new IUSR account and the IIS\_IUSRS group are discussed in greater depth in the sections below.
## Understanding the New IUSR Account
The IUSR account replaces the IUSR\_MachineName account in IIS 7 and above. The IUSR\_MachineName account will still be created and used if you install the FTP 6 compatible server that is included in Windows Server 2008. If you do not install the FTP server that is included with Windows Server 2008, then this account will not be created.
This built-in account does not need a password and will be the default identity that is used when anonymous authentication is enabled. If you look in the applicationHost.config file you will see the following definition:
[!code-xml[Main](understanding-built-in-user-and-group-accounts-in-iis/samples/sample1.xml)]
This tells IIS to use the new built-in account for all anonymous authentication requests. The biggest advantages are that you can:
- Set file system permissions for the IUSR account by using Windows Explorer or any of the many command line tools.
- No longer need to worry about passwords expiring for this account.
- Use xcopy /o to copy files along with their ownership and ACL information to different computers seamlessly.
> [!NOTE]
> The IUSR account is similar to LOCALSERVICE in the manner in which it acts anonymously on the network. The NETWORKSERVICE and LOCALSYSTEM accounts can act as the machine identity, but the IUSR account cannot because it would require an elevation of user rights. If you need the anonymous account to have rights on the network, you must create a new user account and set the user name and password manually, as you did in the past for anonymous authentication.
**To grant an anonymous account rights on the network by using IIS Manager:**
1. Click **Start**, type **INetMgr.exe**, and then click **Enter**. If prompted, click **Continue** to elevate your permissions.
2. In the **Connections** section, click the **+** button next to the name of your computer.
3. In IIS Manager, double-click the site that you want to administer.
4. In the Features View, double-click **Authentication**.
5. Select **Anonymous Authentication**, and then click **Edit** in the **Actions** pane.
6. In the **Edit Anonymous Authentication Credentials** dialog box, click the **Specific user** option, and then click **Set**.
7. In the **Set Credentials** dialog box, input the user name and password desired, and then click **OK**.
## Understanding the New IIS\_IUSRS Group
The IIS\_IUSRS group replaces the IIS\_WPG group. This built-in group has access to all the necessary file and system resources so that an account, when added to this group, can seamlessly act as an application pool identity.
As with the built-in account, this built-in group solves several xcopy deployment obstacles. If you set permissions on your files for the IIS\_WPG group (that was available on IIS 6.0 systems) and tried to copy those files to another Windows computer, the group's SID would be different across the computers and your site's configurations would be broken.
Since the group SID in IIS 7 and above is the same on all systems that are running Windows Server 2008, you can use 'xcopy /o' to preserve the ACL's and ownership information as you move files from computer to computer. This makes xcopy deployments easy.
IIS 7 and above also makes the process of configuring an application pool identity and making all necessary changes easier. When IIS starts a worker process, it needs to create a token that the process will use. When this token is created, IIS automatically adds the IIS\_IUSRS membership to the worker processes token at runtime. The accounts that run as 'application pool identities' no longer need to be an explicit part of the IIS\_IUSRS group. This change helps you to set up your systems with fewer obstacles and makes your overall experience more favorable.
If you want to disable this feature and manually add accounts to the IIS\_IUSRS group, disable this new feature by setting the **manualGroupMembership** value to '**true**'. The following example shows how this can be done to the **defaultAppPool**:
[!code-xml[Main](understanding-built-in-user-and-group-accounts-in-iis/samples/sample2.xml)] | 96.766234 | 607 | 0.790229 | eng_Latn | 0.999179 |
d5aa31d58fe3436f4aebe80213425c0c3e694890 | 5,247 | md | Markdown | docs/api/navigator-config.md | taxfix/native-navigation | aa6bea2d7553a26571f5f363ba87ef86ba1351a8 | [
"MIT"
] | 3 | 2017-11-28T05:31:35.000Z | 2018-01-27T00:57:00.000Z | docs/api/navigator-config.md | taxfix/native-navigation | aa6bea2d7553a26571f5f363ba87ef86ba1351a8 | [
"MIT"
] | 34 | 2017-10-23T17:06:10.000Z | 2021-05-09T01:55:07.000Z | docs/api/navigator-config.md | taxfix/native-navigation | aa6bea2d7553a26571f5f363ba87ef86ba1351a8 | [
"MIT"
] | 1 | 2018-03-03T08:47:27.000Z | 2018-03-03T08:47:27.000Z | # `<Navigator.Config />`
The `Config` component is a a component that is used to configure the current screen and navigation
bar. The component itself does not result in any UI being rendered in the current react view hierarchy,
but instead is used as a declarative interface for the screen.
The `Config` component can be rendered at any point in the react view hierarchy, and multiple instances
of the component can be rendered in the same hierarchy, with the props of each getting merged together
with the preference being given to the instances in the order that they mount.
## Usage
```jsx
import React from 'react';
import Navigator from 'native-navigation';
export default class Screen extends React.Component {
render() {
const {
children,
title,
} = this.props;
return (
<Navigator.Config
title={title}
backgroundColor="#F7F7F7"
elevation={4}
onBackPress={() => console.log('onBackPress')}
onLeftPress={() => console.log('onLeftPress')}
onRightPress={(index) => console.log('onRightPress', index)}
onAppear={() => console.log('onAppear')}
>
{children}
</Navigator.Config>
);
}
}
```
## Props
#### `children: node`
If `children` are passed into the component, the `Config`'s `render` method will return the result of
`React.Children.only(this.props.children)`. Otherwise, `render` will just return `null`.
#### `title: string`
The title of the screen. This shows up in the center of the navigation bar by default.
#### `titleColor: Color`
The text color of the title.
#### `subtitle: string`
The subtitle of the screen. This shows up as a string below the title of the screen.
#### `subtitleColor: Color`
The text color of the subtitle.
#### `alpha: number`
The opacity of the navigation bar. Should be between `0` and `1`.
#### `prefersLargeTitles: boolean`
If true, will use iOS 11 style large titles.
Defaults to `false`.
#### `rightTitle: string`
The
#### `rightImage: Image`
#### `rightButtons: Array<Button>`
-
#### `screenColor: Color`
The background color of the entire screen.
If the color is translucent, the old screen will be kept below this one (to use it like a modal, for instance).
Defaults to `#FFFFFF`.
#### `hidden: boolean`
If true, the navigation bar will not be visible.
Defaults to `false`.
#### `backgroundColor: Color`
#### `foregroundColor: Color`
#### `statusBarHidden: boolean`
If true, the status bar will not be visible.
Defaults to `false`.
#### `statusBarAnimation: 'slide' | 'none' | 'fade'`
Configures how the status bar should animate between configurations.
Defaults to `'fade'`.
#### `statusBarStyle: 'light' | 'default'`
## Events
#### `onAppear: () => void`
#### `onDisappear: () => void`
#### `onEnterTransitionCompleted: () => void`
#### `onBarHeightChanged: ({ height: number, force: boolean }) => void`
#### `onLeftPress: () => void`
#### `onRightPress: (index: number) => void`
## Example Usage
## Related Guides
- [Shared Element Transitions](/docs/guides/shared-element-transitions.md)
## Types
- [`ScreenConfig`](/docs/types/NavigationResult.md)
# Navigator.Config
## Props
```js
type Image = {
uri: string;
width: number;
height: number;
}
type Button = {
// shared
title: string;
image: Image;
// ios-only-but-should-share
enabled: boolean;
tintColor: boolean;
fontName: string;
fontSize: number;
// ios-only
style: 'plain' | 'default';
systemItem: 'done' | 'cancel' | 'edit' | 'save' | 'add' | 'flexibleSpace' | 'compose' | 'reply' | 'action' | 'organize' | 'bookmarks' | 'search' | 'refresh' | 'stop' | 'camera' | 'trash' | 'play' | 'pause' | 'rewind' | 'fastForward' | 'undo' | 'redo' | 'pageCurl';
// android-only
};
type NavigatorConfigProps = {
// shared
title: string;
titleColor: Color;
subtitle: string;
subtitleColor: Color;
alpha: number;
rightTitle: string;
rightImage: Image;
rightButtons: Array<Button>;
screenColor: Color;
hidden: boolean;
backgroundColor: Color;
foregroundColor: Color;
statusBarHidden: boolean;
statusBarAnimation: 'slide' | 'none' | 'fade'; // 'fade' is default
statusBarStyle: 'light' | 'default';
// ios-only-but-should-share
backIndicatorImage: Image;
titleFontName: string;
titleFontSize: number;
subtitleFontName: string;
subtitleFontSize: number;
// android-only-but-should-share
navIcon: Image;
logo: Image;
textAlign: 'left' | 'center' | 'right';
leftButtons: Array<Button>;
// ios-only
prompt: string;
hidesBackButton: boolean;
hidesBarsOnTap: boolean;
hidesBarsOnSwipe: boolean;
hidesBarsWhenKeyboardAppears: boolean;
isToolbarHidden: boolean;
backIndicatorTransitionMaskImage: Image;
translucent: boolean;
prefersLargeTitles: boolean;
// android-only
statusBarColor: Color;
statusBarTranslucent: boolean;
windowTitle: string;
elevation: number;
overflowIcon: Image;
displayHomeAsUp: boolean;
homeButtonEnabled: boolean;
showHome: boolean;
showTitle: boolean;
showCustom: boolean;
useLogo: boolean;
useShowHideAnimation: boolean;
hideOnScroll: boolean;
hideOffset: number;
}
```
| 19.95057 | 266 | 0.675815 | eng_Latn | 0.900074 |
d5ab3858b8045c8e022d631b5513268d3c2411c4 | 4,679 | md | Markdown | _posts/2009-10-13-la-neutralite-pragmatique-des-nouvelles-technologies-de-linformation-et-de-la-communication.md | taniki/cendres.net | 400687b57aa0ab6f61b616752204fa4317e9eb61 | [
"MIT"
] | null | null | null | _posts/2009-10-13-la-neutralite-pragmatique-des-nouvelles-technologies-de-linformation-et-de-la-communication.md | taniki/cendres.net | 400687b57aa0ab6f61b616752204fa4317e9eb61 | [
"MIT"
] | null | null | null | _posts/2009-10-13-la-neutralite-pragmatique-des-nouvelles-technologies-de-linformation-et-de-la-communication.md | taniki/cendres.net | 400687b57aa0ab6f61b616752204fa4317e9eb61 | [
"MIT"
] | null | null | null | ---
layout: post
title: "La neutralité pragmatique des nouvelles technologies de l'information et de la communication"
---
<p>Il n'y a pas encore si longtemps que ça, seulement 5 ans, je soutenais l'idée que le blog en tant qu'objet était neutre sociologiquement et sémiologiquement. Il ne décrit ni société, ni signification particulière. Il les permet toutes. La constitution d'un groupement social utilisant les blogs pour partager des recettes de cuisine n'est un paradoxe que pour ceux qui prêtait une intention à un objet. D'où une guerre de tranchées contre le communautarisme et l'usage répété du terme « blogosphère » ; ce qui parallèlement n'empêche pas de soutenir et de participer à l'amélioration de ce genre d'outils en contribuant et en aidant les artisans de cette disponibilité. Aujourd'hui, je crois encore que ce terme ne fonctionnera jamais comme incantation d'une classe sociale, particularisme parisien mis à part où des marionnetistes avisés rencontrent une offre de personnalités en papier pré-maché. La même analyse peut être conduite à propos de twitter. Notre petit présent ne se privera pas non plus d'ajouter d'autres modulations à la liste des nouveaux outils institués tels des sceptres. Pour l'instant, il s'agit seulement de l'ajout progressif de toutes les notions de paratextualité, contextualité, hypertextualité, infratextualité, etc au texte numérique et son affranchissement de la matière.</p> <p>Fixons l'idée une bonne fois pour toute. <em>Les outils de publication, électroniques ou non, sont neutres dans leur usage car tout leur est permis [Neutralité pragmatique].</em> Ce n'est pas parce qu'ils seront finalement utilisés à fins quelconques, banales, nombrilistes ou qu'ils ont peu été utilisé proportionnellement pour autre chose (l'échange, la révolution, la prise de parole plutôt que l'idiote mobilisation en faveur d'un discours légitimiste, etc) qu'ils n'en seront jamais les supports. Le corrollaire est donc qu'il n'y a aucune impossibilité pragmatique. Par exemple, tout <em>jugement</em> sur les blogs (leur mort comme leur avènement, leur futilité comme la preuve d'un pouvoir) n'est qu'un abandon réactionnaire du débat sur ce qu'il est possible d'en faire au détriment de ce que l'air du temps en a fait ; c'est ainsi se priver de la reconnaissance tacite que ce sont les acteurs qui les manipulent qui détiennent un degré de responsabilité et qui sont ainsi sociologiquement parlant.</p> <p>Dans l'architecture de l'information, le seul rôle de cette catégorie d'outils est d'épargner aucune possibilité d'usage soit actuellement soit par extension future en fonction des besoins.</p> <p>Le contexte prime sur la possibilité technique, non l'inverse. Le champ d'action repose bien plus sur la capacité de mobilisation sociale que la disponibilité technique. Nous sommes justement dans la culture où l'individu peut <em>toujours</em> s'engager à faire coïncider à moindre coup la technique et ses intentions modulo la question primordiale de l'affection de ressources pendant un temps donné (« se donner du temps »). L'usage n'est ainsi que le signe secondaire, non pas de la nature de l'outils technologique, mais de la culture qui les prends en main. Agir politiquement, c'est influencer sur la culture et sa mise en action dans les usages plutôt que de chercher à posséder ou maîtriser des outils.</p> <p>Refuser ou abandonner un mode de parole au nom de la mode, au nom du manque de distinction, au nom du côté <em>mainstream</em> n'est que le désaveu de l'esprit de libération et de critique ainsi qu'assumer un manque de talent flagrant autre que celui de faire partie de la masse mais de le faire bien en tant que « premier ».</p> <p>Peut-on prétendre, autrement que d'un air stupide, que l'information en 140 caractères basés sur des faits à plus de force que l'argumentation ? Ce qui se trame ce n'est ni une question de rapidité ni la défense de l'empirisme, les faits surprenant l'analyse, mais bien plus la mise en valeur de la facilité de moins penser. Contentons nous des faits, divers si possible.</p> <p>La parole publique en tant que mode de représentation issu d'une idéologie particulière à travers l'écriture de la modernité et de ses révolutions a également montré comment les origines sociales d'une pratique peut s'écarter des intentions des acteurs de ceux qui ont forgé la possibilité de cette pratique.</p> <p>Tout cela a beau rester de la tautologie, il reste également perturbant de constater à quel point la confusion peut revenir régulièrement <em>ie</em> à chaque fois que l'on entend parler de blogs, de twitter etc comme des choses et non comme des fragments de personnes.</p>
| 668.428571 | 4,552 | 0.796324 | fra_Latn | 0.99137 |
d5ab4cba64abd08b0267f13d9497062fee6ed2b4 | 37 | md | Markdown | README.md | YunDid/Pumpkin | ca316c9c94a9e89da9fb45c4582d78bd1dfabf64 | [
"Apache-2.0"
] | null | null | null | README.md | YunDid/Pumpkin | ca316c9c94a9e89da9fb45c4582d78bd1dfabf64 | [
"Apache-2.0"
] | null | null | null | README.md | YunDid/Pumpkin | ca316c9c94a9e89da9fb45c4582d78bd1dfabf64 | [
"Apache-2.0"
] | null | null | null | # Pumpkin Engine
Welcome to Pumpkin! | 12.333333 | 19 | 0.783784 | eng_Latn | 0.421216 |
d5ab761ac67d3c337f68a85c29f2874cd88c5e74 | 8,509 | md | Markdown | docs/ide/step-5-add-controls-to-your-form.md | seferciogluecce/visualstudio-docs.tr-tr | 222704fc7d0e32183a44e7e0c94f11ea4cf54a33 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ide/step-5-add-controls-to-your-form.md | seferciogluecce/visualstudio-docs.tr-tr | 222704fc7d0e32183a44e7e0c94f11ea4cf54a33 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ide/step-5-add-controls-to-your-form.md | seferciogluecce/visualstudio-docs.tr-tr | 222704fc7d0e32183a44e7e0c94f11ea4cf54a33 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: '5. adım: formunuza denetimler ekleme'
ms.custom: ''
ms.date: 11/04/2016
ms.prod: visual-studio-dev15
ms.technology: vs-acquisition
ms.topic: conceptual
ms.assetid: dc2746f4-0b5c-4674-9ef7-f40f94150f52
author: TerryGLee
ms.author: tglee
manager: douge
ms.workload:
- multiple
ms.openlocfilehash: a7a0167d4d5af125e706350002ccf8a17e459414
ms.sourcegitcommit: 58052c29fc61c9a1ca55a64a63a7fdcde34668a4
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 06/04/2018
ms.locfileid: "34748562"
---
# <a name="step-5-add-controls-to-your-form"></a>5. adım: formunuza denetimler ekleme
Bu adımda, denetimleri gibi eklediğiniz bir <xref:System.Windows.Forms.PictureBox> denetim ve <xref:System.Windows.Forms.CheckBox> Formunuza denetim. Ardından ekleyin <xref:System.Windows.Forms.Button> formunuza denetimler.
bu konuda video sürümü için bkz: [Öğreticisi 1: Visual Basic'te - Video 2 resim görüntüleyici oluşturma](http://go.microsoft.com/fwlink/?LinkId=205211) veya [Eğitmen 1: Resim Görüntüleyici C# ' - Video 2 oluşturma](http://go.microsoft.com/fwlink/?LinkId=205200). Bazı menü komutları ve diğer kullanıcı arabirimi öğeleri küçük farklar olduklarından bu videolar Visual Studio'nun önceki bir sürümünü kullanın. Ancak, kavramlar ve yordamlar benzer şekilde geçerli sürümünde Visual Studio çalışır.
## <a name="to-add-controls-to-your-form"></a>Formunuza denetimler ekleme
1. Git **araç** (Visual Studio IDE sol tarafta bulunan) sekmesinden ve genişletin **ortak denetimler** grubu. Bu, en yaygın denetimleri formlarında gördüğünüz gösterir.
2. Seçin **TableLayoutPanel** form üzerinde denetim. TableLayoutPanel seçildiğini doğrulamak için adının en üstündeki açılır liste kutusunda gösterildiğinden emin olun **özellikleri** penceresi. En üstte açılır liste kutusunu kullanarak form denetimlerini seçebilirsiniz **özellikleri** penceresi. Bir denetim seçme bu şekilde genellikle fare küçük bir denetimle seçme daha kolay olabilir.
3. Çift **PictureBox** formunuza PictureBox denetimi eklenecek öğe. TableLayoutPanel formunuz doldurmak için yerleşik olduğundan, IDE PictureBox denetimi ilk boş hücreye (sol üst köşesinde) ekler.
4. Yeni seçin **PictureBox** seçmek üzere denetlemek ve ardından aşağıdaki resimde gösterildiği gibi görev listesini görüntülemek için yeni PictureBox denetiminde siyah üçgen seçin.
**PictureBox** görevleri
> [!NOTE]
> TableLayoutPanel denetimi yanlış türde yanlışlıkla eklerseniz, silebilirsiniz. Denetimin sağ tıklayın ve ardından **silmek** bağlam menüsünde. Menü Çubuğu'nu kullanarak formdan denetimleri de kaldırabilirsiniz. Menü çubuğunda seçin **Düzenle** > **geri**, veya **Düzenle** > **silmek**.
5. Seçin **Ana kapsayıcıda yerleştir** bağlantı. Bu otomatik olarak PictureBox ayarlar **yerleştirme** özelliğine **doldurun**. Bu görmek için seçin **PictureBox** gidin seçmek için Denetim **özellikleri** penceresinde ve emin olun, **yerleştirme** özelliği ayarlanmış **doldurun**.
6. Her iki sütuna değiştirerek yayılan PictureBox olun kendi **ColumnSpan** özelliği. Seçin **PictureBox** denetleyin ve ayarlayın, **ColumnSpan** özelliğine **2**. Ayrıca, PictureBox boş olduğunda, boş bir çerçeve göstermek istiyorsunuz. Ayarlama, **kenarlık stili** özelliğine **Fixed3D**.
> [!NOTE]
> Görmüyorsanız, bir **ColumnSpan** , PictureBox, ardından özelliğidir PictureBox TableLayoutPanel yerine formun eklendiğini büyük olasılıkla. Bu sorunu gidermek için tercih **PictureBox**, silmek, seçin **TableLayoutPanel**, ve ardından yeni PictureBox ekleyin.
7. Seçin **TableLayoutPanel** formdaki ve sonra forma bir onay kutusu denetimi ekleyin. Çift **onay kutusunu** öğesi **araç** tablonuz sonraki boş hücreye yeni bir onay kutusu denetimi eklemek için. Bir PictureBox TableLayoutPanel ilk iki hücrelere yukarı aldığından, onay kutusu denetimi için sol alt hücre eklenir. Seçin **metin** özelliği ve Word türü **Esnetme**, aşağıdaki resimde gösterildiği gibi.
**TextBox** ile kontrol **Esnetme** özelliği
8. Seçin **TableLayoutPanel** form ve gidin **kapsayıcıları** grubu **araç** (burada aldığınız TableLayoutPanel denetimi) ve çift tıklatın **FlowLayoutPanel** (sağ alt) PictureBox son hücreye öğesi yeni bir denetim eklemek için. TableLayoutPanel içinde FlowLayoutPanel yerleştirme (seçerek **Ana kapsayıcıda yerleştir** FlowLayoutPanel'ın siyah üçgen görev listesi veya FlowLayoutPanel's ayarlayarak **yerleştirme** özelliğine **doldurun**).
> [!NOTE]
> A <xref:System.Windows.Forms.FlowLayoutPanel> diğer denetimlerini sırayla masaüstünüzdeki satırlardaki düzenler bir kapsayıcıdır. Tüm denetimlerindeki tek bir satırı düzenlemek için yer varsa bir FlowLayoutPanel boyutlandırdığınızda, yapar. Aksi takdirde, bunları birbirinin satırlarındaki düzenler. FlowLayoutPanel dört düğme tutmak için kullanır. Düğmeleri biri üzerinde Yerleştir başka eklendiğinde top, FlowLayoutPanel düğmeleri eklemeden önce seçili olduğundan emin olun. Daha önce her bir hücre yalnızca bir denetim tutabilir belirtmiştik rağmen TableLayoutPanel sağ alt hücrenin dört düğmesi denetimleri vardır. Bir denetim diğer denetimleri tutan bir hücreye koyabilirsiniz olmasıdır. Bu tür denetimi bir kapsayıcı adı verilir ve FlowLayoutPanel bir kapsayıcıdır.
## <a name="to-add-buttons"></a>Düğmeler ekleme
1. Eklediğiniz yeni FlowLayoutPanel seçin. Git **ortak denetimler** içinde **araç** çift tıklayın ve **düğmesini** adlı bir düğme denetim eklemek için öğeyi **button1** için FlowLayoutPanel. Başka bir düğme eklemek için yineleyin. Zaten var olduğu adlı bir düğme IDE belirler **button1** ve bir sonraki çağırır **button2**.
2. Genellikle, kullanarak başka bir düğme ekleme **araç**. Bu saati seçin **button2**ve ardından menü çubuğunda, **Düzenle** > **kopya** (veya basın **Ctrl** + **C**). Menü çubuğunda seçin **Düzenle** > **Yapıştır** (veya basın **Ctrl**+**V**), düğmesinin bir kopyasını yapıştırmak için. Şimdi yeniden yapıştırın. IDE şimdi eklendi **button3** ve **button4** FlowLayoutPanel için.
> [!NOTE]
> Kopyalayın ve hiçbir denetim yapıştırın. IDE adları ve yeni denetimleri mantıksal bir şekilde yerleştirir. Bir kapsayıcıya bir denetim yapıştırırsanız, IDE yerleştirme için sonraki mantıksal alan seçer.
3. İlk düğmesini seçin ve ayarlayın, **metin** özelliğine **resim Göster**. Ardından **metin** sonraki üç düğmelere özelliklerini **resmi temizleyin**, **arka plan rengini ayarlama**, ve **Kapat**.
4. Düğmeleri boyut ve bölmenin sağ tarafındaki hizalamak için bunları düzenlemek için sonraki adım olacaktır. Seçin **FlowLayoutPanel** ve bakmak kendi **FlowDirection** özelliği. Ayarlanmış şekilde değiştirme **RightToLeft**. Bunu hemen düğmeleri kendilerini hücrenin sağ tarafındaki align ve bunların sırası ters şekilde **resim Göster** düğmesi olan sağ taraftaki.
> [!NOTE]
> Düğmeleri hala yanlış sırayla varsa, bunları herhangi bir sırada yeniden düzenlemek için FlowLayoutPanel çevresindeki düğmeler sürükleyebilirsiniz. Bir düğme seçin ve sola veya sağa sürükleyin.
5. Seçin **Kapat** düğmesini seçin. Basılı **Ctrl** anahtarı ve böylece tüm seçilir diğer üç düğme seçin. Tüm düğmeleri seçili durumdayken Git **özellikleri** penceresini açın ve kaydırma kadar **AutoSize** özelliği. Bu özellik otomatik olarak kendisini tüm kendi metnin sığması için yeniden boyutlandırmak için düğmesini söyler. Ayarlamak **doğru**. Düğmeleri şimdi düzgün şekilde boyutlandırılmalıdır ve doğru sırada olmalıdır. (Tüm dört düğmeleri seçili olduğu sürece, tüm dört değiştirebilirsiniz **AutoSize** özellikleri aynı anda.) Aşağıdaki resimde, dört düğme gösterilmektedir.
**resim görüntüleyici** dört düğmeleri
6. Şimdi yeniden kullanıma yeni laid formunuz görmek için programı çalıştırın. Düğmeler ve onay kutusunu seçerek herhangi bir şey henüz yapmaz, ancak en kısa sürede çalışır.
## <a name="to-continue-or-review"></a>Devam etmek veya gözden geçirmek için
- Öğretici bir sonraki adıma dönmek için bkz: [6. adım: düğme denetimlerinizi adlandırma](../ide/step-6-name-your-button-controls.md).
- Eğitmen önceki adıma dönmek için bkz: [4. adım: bir TableLayoutPanel denetimi ile formunuzu düzenleme](../ide/step-4-lay-out-your-form-with-a-tablelayoutpanel-control.md).
| 97.804598 | 778 | 0.787049 | tur_Latn | 0.99986 |
d5abcc22c22099a3beda5c68472fc8eb5b678a6d | 1,354 | md | Markdown | _posts/2020-09-16-cpp6-post.md | happyOBO/happyOBO.github.io | 96e60a67b9b84c26f01312f8ca5ade35803c521f | [
"MIT"
] | 2 | 2020-10-24T03:25:30.000Z | 2021-08-01T05:18:18.000Z | _posts/2020-09-16-cpp6-post.md | happyOBO/happyOBO.github.io | 96e60a67b9b84c26f01312f8ca5ade35803c521f | [
"MIT"
] | 2 | 2020-12-05T14:31:19.000Z | 2020-12-06T05:09:43.000Z | _posts/2020-09-16-cpp6-post.md | happyOBO/happyOBO.github.io | 96e60a67b9b84c26f01312f8ca5ade35803c521f | [
"MIT"
] | 4 | 2020-08-26T10:02:11.000Z | 2020-10-22T05:55:18.000Z | ---
title: "[C++] 챕터 5"
date: 2020-09-16 13:15:28 -0400
categories: C++
---
### 복사 생성자와의 첫만남
---
### C++ 스타일의 초기화
```cpp
// C style
int num = 20;
int &ref = num;
// C++ style
int num(20);
int &ref(num);
```
```cpp
class SoSimple
{
private :
int num1;
int num2;
public :
SoSimple(int n1, int n2) : num(n1), num2(n2)
{}
void ShowSimpleData()
{
cout<<num1<<endl;
cout<<num2<<endl;
}
};
int main(void)
{
SoSimple sim(15,20);
SoSimple sim2 = sim1;
sim2.ShowSimpleData();
return 0;
}
```
### 키워드 explicit
- ``SoSimple sim2 = sim1; `` -> ``SoSimple sim2(sim1)``
- 이러한 묵시적 형변환은 복사 생성자를 explicit 으로 선언하면 막을 수 있다.
### 깊은 복사와 얕은 복사
---
### 디폴트 복사 생성자의 문제점
- 얕은 복사 : 객체 소멸시 문제 발생
- ``Person man2 = man1;``
### 깊은 복사를 위한 복사 생성자의 정의
```cpp
Person(const Person& copy) : age(copy.age)
{
name=new char[strlen(copy.name)+1];
strcpy(name, copy.name);
}
```
### 복사 생성자의 호출 시점
---
### 복사 생성자가 호출되는 시점
1. 기존에 생성된 객체를 이용해서 새로운 객체를 초기화 하는경우
```cpp
Person man("Lee dong woo", 29);
Person man2 = man1;
```
2. Call-by-value 방식의 함수 호출 과정에서 객체를 인자로 전달하는 경우
3. 객체를 반환하되, 참조형으로 반환하지 않는경우
```cpp
SoSimple SimpleFuncObj(SoSimple ob)
{
return ob;
}
int main(void)
{
SoSimple obj;
SimpleFuncObj(obj);
...
}
```
| 10.919355 | 55 | 0.54062 | kor_Hang | 0.999625 |
d5ac365d9eff259cba3b2b442bdb4221a5993f10 | 49,419 | md | Markdown | CHANGELOG.md | Wxh16144/vtils | c6e2659ae8225de437557279ca207efe9cbc94a9 | [
"MIT"
] | null | null | null | CHANGELOG.md | Wxh16144/vtils | c6e2659ae8225de437557279ca207efe9cbc94a9 | [
"MIT"
] | null | null | null | CHANGELOG.md | Wxh16144/vtils | c6e2659ae8225de437557279ca207efe9cbc94a9 | [
"MIT"
] | null | null | null | # Changelog
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
## [4.36.0](https://github.com/fjc0k/vtils/compare/v4.35.1...v4.36.0) (2021-09-15)
### Features
- **utils:** 新增 roundTo 保留 n 位小数下的 x 舍 y 入 ([aeb6886](https://github.com/fjc0k/vtils/commit/aeb6886a95f100380b50d21db963beb690e63376))
### [4.35.1](https://github.com/fjc0k/vtils/compare/v4.35.0...v4.35.1) (2021-09-09)
### Bug Fixes
- 声明 yup.js 有副作用，防止 webpack 将增强代码删除 ([97ab1d3](https://github.com/fjc0k/vtils/commit/97ab1d3167b8b4a1b65a5be0572f939ed6d23842))
## [4.35.0](https://github.com/fjc0k/vtils/compare/v4.34.3...v4.35.0) (2021-09-02)
### Features
- **utils:** 新增 moveUp, moveDown, moveToTop, moveToBottom ([27eaf97](https://github.com/fjc0k/vtils/commit/27eaf9771e97726d55ddf28678027c5fce73e41f))
### [4.34.3](https://github.com/fjc0k/vtils/compare/v4.34.3-beta.0...v4.34.3) (2021-08-14)
### [4.34.3-beta.0](https://github.com/fjc0k/vtils/compare/v4.34.2...v4.34.3-beta.0) (2021-08-11)
### Features
- **loadResource:** 支持 hook ([2473759](https://github.com/fjc0k/vtils/commit/24737596f4c2a1933c3b1d14e9a09d244a151c54))
- **loadResource:** 支持 hook、jsText、cssText ([b39a549](https://github.com/fjc0k/vtils/commit/b39a5494aac128926cb838ce95394418d98f71a7))
- **utils:** 新增 getCurrentScript 返回当前正在运行的脚本所属的 `<script>` 元素 ([d2a93d8](https://github.com/fjc0k/vtils/commit/d2a93d831afacfb353740766d1e1b1c748098703))
- **utils:** 新增 jsonp 发起 jsonp 请求 ([1c2ae89](https://github.com/fjc0k/vtils/commit/1c2ae897b105765861192eefa6d7022bb10a1761))
### Bug Fixes
- **deps:** update dependency antd to v4.16.10 ([a03a0c4](https://github.com/fjc0k/vtils/commit/a03a0c48c022baa471c2397e1642817b23b90865))
- **deps:** update dependency antd to v4.16.11 ([2012ed1](https://github.com/fjc0k/vtils/commit/2012ed1649348c7d14c686a404e45f89a233a4d7))
- **deps:** update dependency antd to v4.16.8 ([c553a02](https://github.com/fjc0k/vtils/commit/c553a026999066346ca2f00f56d2f3851e04140b))
- **deps:** update dependency antd to v4.16.9 ([32541a9](https://github.com/fjc0k/vtils/commit/32541a93c10294c990d5fcf46848a617bb8317b2))
- **loadResource:** 加载 js 默认走 async ([4e944ac](https://github.com/fjc0k/vtils/commit/4e944acbf7a8ab64354b6d644ef96e1a34ab364f))
- yup 内部维护 ([a49dbdd](https://github.com/fjc0k/vtils/commit/a49dbddc01fe8401ac347f83ca0124c85c346794))
### [4.34.2](https://github.com/fjc0k/vtils/compare/v4.34.1...v4.34.2) (2021-07-14)
### Bug Fixes
- **move:** 对空数组移动应返回空数组 ([f93f090](https://github.com/fjc0k/vtils/commit/f93f0902b44566a0eafe3f08915e3f63472f6dbe))
### [4.34.1](https://github.com/fjc0k/vtils/compare/v4.34.1-beta.6...v4.34.1) (2021-07-13)
### Bug Fixes
- **deps:** update dependency antd to v4.16.7 ([4b9e184](https://github.com/fjc0k/vtils/commit/4b9e1842ad8d880bee8dfb58810f7e9a8ecb0a76))
- **TreeData:** fromList 算法优化 ([d911d74](https://github.com/fjc0k/vtils/commit/d911d747a02fdd46a556da5dd4f1949424346c3e))
### [4.34.1-beta.6](https://github.com/fjc0k/vtils/compare/v4.34.1-beta.5...v4.34.1-beta.6) (2021-07-11)
### [4.34.1-beta.5](https://github.com/fjc0k/vtils/compare/v4.34.1-beta.4...v4.34.1-beta.5) (2021-07-10)
### [4.34.1-beta.4](https://github.com/fjc0k/vtils/compare/v4.34.1-beta.3...v4.34.1-beta.4) (2021-07-10)
### [4.34.1-beta.3](https://github.com/fjc0k/vtils/compare/v4.34.1-beta.2...v4.34.1-beta.3) (2021-07-10)
### Features
- **copyTextToClipboard:** 可设置复制容器类名 ([5231b8d](https://github.com/fjc0k/vtils/commit/5231b8dee1df42c9664d29c1a70d454af0ccf7c9))
### [4.34.1-beta.2](https://github.com/fjc0k/vtils/compare/v4.34.1-beta.1...v4.34.1-beta.2) (2021-07-10)
### Bug Fixes
- **TreeData.fromList:** 优化根节点的判定逻辑 ([4222744](https://github.com/fjc0k/vtils/commit/4222744935c655a825c413c9a4348ab05392b291))
### [4.34.1-beta.1](https://github.com/fjc0k/vtils/compare/v4.34.1-beta.0...v4.34.1-beta.1) (2021-07-07)
### [4.34.1-beta.0](https://github.com/fjc0k/vtils/compare/v4.34.0...v4.34.1-beta.0) (2021-07-07)
### Bug Fixes
- **deps:** update dependency antd to v4.14.1 ([0d1d416](https://github.com/fjc0k/vtils/commit/0d1d416eca52a44b7c8dd113389c447ff34e807d))
- **deps:** update dependency antd to v4.15.0 ([7cbbca8](https://github.com/fjc0k/vtils/commit/7cbbca8fcead7b1e5bed7950bef7154e41711fd4))
- **deps:** update dependency antd to v4.15.2 ([f8021cb](https://github.com/fjc0k/vtils/commit/f8021cb0366783a7e0c8307791803d7ec7826d63))
- **deps:** update dependency antd to v4.15.3 ([dbab174](https://github.com/fjc0k/vtils/commit/dbab17459b2adb333def493b158ae16601ed6e05))
- **deps:** update dependency antd to v4.15.4 ([10548f6](https://github.com/fjc0k/vtils/commit/10548f63719a0f0ab1a9d2a0889de5a6f28755c0))
- **deps:** update dependency antd to v4.15.5 ([677cfc5](https://github.com/fjc0k/vtils/commit/677cfc531879f452ea1023f52d065d18b7c74857))
- **deps:** update dependency antd to v4.15.6 ([cbe9040](https://github.com/fjc0k/vtils/commit/cbe904060d64f5280499d42b1eb68955922a9756))
- **deps:** update dependency antd to v4.16.0 ([9e50535](https://github.com/fjc0k/vtils/commit/9e50535eb1271b04474ffa363ca116ac5b47332d))
- **deps:** update dependency antd to v4.16.1 ([901a3ca](https://github.com/fjc0k/vtils/commit/901a3ca1197d73c71d02ed56440a11597ac512f8))
- **deps:** update dependency antd to v4.16.2 ([3b96bc2](https://github.com/fjc0k/vtils/commit/3b96bc2a7b3927216645822e5750181756112a85))
- **deps:** update dependency antd to v4.16.3 ([d20f221](https://github.com/fjc0k/vtils/commit/d20f2218e9a09bfc0b794c53f18f69a12d2448af))
- **deps:** update dependency antd to v4.16.5 ([0a08be1](https://github.com/fjc0k/vtils/commit/0a08be18a352d982cdc961fcb87ead27a482acef))
- **deps:** update dependency antd to v4.16.6 ([fd4e2af](https://github.com/fjc0k/vtils/commit/fd4e2af261d35cdf468e97126ba60dd0d89ac208))
- 更新依赖；使用 yarn 作为包管理工具 ([f8748e7](https://github.com/fjc0k/vtils/commit/f8748e7276db078cdb6ee85c9c91a5c86b7f1e81))
## [4.34.0](https://github.com/fjc0k/vtils/compare/v4.33.0...v4.34.0) (2021-03-18)
### Features
- **createSubmit:** 支持 throw 异常回调 ([2b5e9fb](https://github.com/fjc0k/vtils/commit/2b5e9fba93872c176ba4eb9c60a24935d0d35fb0))
### Bug Fixes
- **deps:** update dependency antd to v4.13.1 ([053b0f7](https://github.com/fjc0k/vtils/commit/053b0f71cc7e7fdfec718250d86a61b6d77ab4d6))
- **deps:** update dependency emotion to v11 ([bad0318](https://github.com/fjc0k/vtils/commit/bad03188bfdeb98b833412b7583c6c48d75c9d74))
## [4.33.0](https://github.com/fjc0k/vtils/compare/v4.32.12...v4.33.0) (2021-03-03)
### Features
- **types:** 导出 UnionToIntersection ([8a17fd6](https://github.com/fjc0k/vtils/commit/8a17fd69092836e31be878441dea980ef1dc4235))
### [4.32.12](https://github.com/fjc0k/vtils/compare/v4.32.11...v4.32.12) (2021-03-03)
### Bug Fixes
- **deps:** update dependency antd to v4.13.0 ([#60](https://github.com/fjc0k/vtils/issues/60)) ([6ed10cb](https://github.com/fjc0k/vtils/commit/6ed10cbd7d61e7f7c0ffcba44c237c6b651fa180))
- **yup:** 中文优化 ([8fa4967](https://github.com/fjc0k/vtils/commit/8fa4967a5b0562f0b53c482d65e312a3dfa1e818))
- **yup:** 类型优化 ([9d145bf](https://github.com/fjc0k/vtils/commit/9d145bf830d08c52500615232c5a4b3e99938c00))
### [4.32.11](https://github.com/fjc0k/vtils/compare/v4.32.10...v4.32.11) (2021-02-22)
### Bug Fixes
- **dev:** 移除 babel plugin import ([dd07a49](https://github.com/fjc0k/vtils/commit/dd07a490cf0163bf7cab82634cb1dc2634b017d0))
### [4.32.10](https://github.com/fjc0k/vtils/compare/v4.32.9...v4.32.10) (2021-02-22)
### [4.32.9](https://github.com/fjc0k/vtils/compare/v4.32.8...v4.32.9) (2021-02-22)
### Bug Fixes
- tweaks ([a799ce7](https://github.com/fjc0k/vtils/commit/a799ce7e60a287ab1a5a024c904add1547c0b71d))
### [4.32.8](https://github.com/fjc0k/vtils/compare/v4.32.7...v4.32.8) (2021-02-22)
### [4.32.7](https://github.com/fjc0k/vtils/compare/v4.32.6...v4.32.7) (2021-02-22)
### [4.32.6](https://github.com/fjc0k/vtils/compare/v4.32.5...v4.32.6) (2021-02-22)
### [4.32.5](https://github.com/fjc0k/vtils/compare/v4.32.4...v4.32.5) (2021-02-22)
### [4.32.4](https://github.com/fjc0k/vtils/compare/v4.32.3...v4.32.4) (2021-02-22)
### [4.32.3](https://github.com/fjc0k/vtils/compare/v4.32.2...v4.32.3) (2021-02-22)
### Bug Fixes
- tweaks ([1e56869](https://github.com/fjc0k/vtils/commit/1e56869998e1929ff746fc8d84237dbb98fde225))
### [4.32.2](https://github.com/fjc0k/vtils/compare/v4.32.1...v4.32.2) (2021-02-22)
### Bug Fixes
- node build ([3624c95](https://github.com/fjc0k/vtils/commit/3624c957419694169e59adde969b7eec8b6e3df7))
### [4.32.1](https://github.com/fjc0k/vtils/compare/v4.32.0...v4.32.1) (2021-02-22)
### Bug Fixes
- **dev:** getBabelPluginImportList ([d9b3848](https://github.com/fjc0k/vtils/commit/d9b3848d217107262e32797b152ef00006b8c86f))
## [4.32.0](https://github.com/fjc0k/vtils/compare/v4.31.0...v4.32.0) (2021-02-22)
### Features
- **dev:** 新增 getBabelPluginImportList ([603843e](https://github.com/fjc0k/vtils/commit/603843e03904575c1017fb16a8f11825e332df47))
## [4.31.0](https://github.com/fjc0k/vtils/compare/v4.30.2...v4.31.0) (2021-02-19)
### Features
- **utils:** 新增 sampleBy, sampleIndex ([7df6ac8](https://github.com/fjc0k/vtils/commit/7df6ac8a75b97f5f78798895a00c6b9e2bfa0ab3))
### Bug Fixes
- **yup:** try catch ([5bfd276](https://github.com/fjc0k/vtils/commit/5bfd276d1151d09c9101710a27936a18be2ca33e))
### [4.30.2](https://github.com/fjc0k/vtils/compare/v4.30.1...v4.30.2) (2021-02-01)
### Bug Fixes
- **DataPacker:** packAsRawType ([97fa9fd](https://github.com/fjc0k/vtils/commit/97fa9fd0d3ac388fe0e626a455413bf7ae65829a))
### [4.30.1](https://github.com/fjc0k/vtils/compare/v4.30.0...v4.30.1) (2021-02-01)
### Bug Fixes
- DataPacker ([c7e39c0](https://github.com/fjc0k/vtils/commit/c7e39c01c6b5d2e11724a5fc4b332cf8c1f14174))
## [4.30.0](https://github.com/fjc0k/vtils/compare/v4.29.0...v4.30.0) (2021-02-01)
### Features
- 使用 DataPacker 替换 ListWrapper ([220c5be](https://github.com/fjc0k/vtils/commit/220c5bec9359db2a06d6ccc0a8e9eaa7518abd35))
## [4.29.0](https://github.com/fjc0k/vtils/compare/v4.28.0...v4.29.0) (2021-01-30)
### Features
- **useLoadMore:** 导出 setData ([4c7546e](https://github.com/fjc0k/vtils/commit/4c7546efa6b616230b5c0d9dc6a4c1346e3985d3))
## [4.28.0](https://github.com/fjc0k/vtils/compare/v4.27.0...v4.28.0) (2021-01-25)
### Features
- **types:** 新增 IsEmptyArray ([7d3bdbd](https://github.com/fjc0k/vtils/commit/7d3bdbdfd03cd6f8b8202e51d45ac550bca6ea61))
- **types:** 新增 IsEmptyObject ([c056fd9](https://github.com/fjc0k/vtils/commit/c056fd9dbf343aea9efed81335b08ca5b15ad4ca))
## [4.27.0](https://github.com/fjc0k/vtils/compare/v4.26.0...v4.27.0) (2021-01-20)
### Features
- **TreeData:** index ([74cebdc](https://github.com/fjc0k/vtils/commit/74cebdce55a6ff4ca3d6c97a7a5b5692e76b0d2a))
## [4.26.0](https://github.com/fjc0k/vtils/compare/v4.25.0...v4.26.0) (2021-01-19)
### Features
- **createGlobalState:** 新增 setStatePartial ([9c76e5a](https://github.com/fjc0k/vtils/commit/9c76e5aa8e7ba3d0da251137bfbd4a42b1169a98))
### Bug Fixes
- **createGlobalState:** 类型重载 ([72e772b](https://github.com/fjc0k/vtils/commit/72e772b25c9afad783c527b2cf1b3d0e89bc637c))
## [4.25.0](https://github.com/fjc0k/vtils/compare/v4.24.0...v4.25.0) (2021-01-18)
### Features
- **utils:** 新增 isType ([dd15ce9](https://github.com/fjc0k/vtils/commit/dd15ce9a6b4e8c37817a4d9db53e9259ed2138c2))
## [4.24.0](https://github.com/fjc0k/vtils/compare/v4.23.0...v4.24.0) (2021-01-15)
### Features
- **utils:** 新增 rot13 ([6450d00](https://github.com/fjc0k/vtils/commit/6450d00389273102e0bfff09b46fed6a344474e0))
## [4.23.0](https://github.com/fjc0k/vtils/compare/v4.22.1...v4.23.0) (2021-01-14)
### Features
- **ListWrapper:** 优化 ([3a25e97](https://github.com/fjc0k/vtils/commit/3a25e97c4d6926df73b4b6498f708c5d5ca3c324))
### [4.22.1](https://github.com/fjc0k/vtils/compare/v4.22.0...v4.22.1) (2021-01-14)
## [4.22.0](https://github.com/fjc0k/vtils/compare/v4.21.0...v4.22.0) (2021-01-14)
### Features
- **utils:** 新增 ListWrapper 列表打包器 ([54644fb](https://github.com/fjc0k/vtils/commit/54644fbe85e342d5ab557ba6d2215bd166718a0d))
## [4.21.0](https://github.com/fjc0k/vtils/compare/v4.20.0...v4.21.0) (2021-01-13)
### Features
- **createGlobalState:** 添加 watchStateImmediate ([5452019](https://github.com/fjc0k/vtils/commit/54520199f3dfe88351aa7702033b8ff88443024f))
## [4.20.0](https://github.com/fjc0k/vtils/compare/v4.19.0...v4.20.0) (2021-01-13)
### Features
- **types:** 新增 NonEmptyArray 非空数组类型 ([cecf602](https://github.com/fjc0k/vtils/commit/cecf6020e906a5499dcb17e7221f0924cc6a30fa))
## [4.19.0](https://github.com/fjc0k/vtils/compare/v4.18.0...v4.19.0) (2021-01-12)
### Features
- **types:** 新增 DotPath ([2417103](https://github.com/fjc0k/vtils/commit/24171035335b3214981f4a5bc571e36e6d37ae72))
## [4.18.0](https://github.com/fjc0k/vtils/compare/v4.17.0...v4.18.0) (2021-01-11)
### Features
- **x:** 新增 nanoid ([c601213](https://github.com/fjc0k/vtils/commit/c6012131268ce5d477a69ed42ee6d438c1d53b21))
## [4.17.0](https://github.com/fjc0k/vtils/compare/v4.16.1...v4.17.0) (2021-01-08)
### Features
- **utils:** 新增 ii 立即调用函数并返回其返回值 ([362ccd3](https://github.com/fjc0k/vtils/commit/362ccd3895d0388e8caf6338b3ce898dce2d4665))
- **utils:** 新增 pMap ([449332d](https://github.com/fjc0k/vtils/commit/449332dfb1392cdf0995677e6dc7719c2444bdca))
### [4.16.1](https://github.com/fjc0k/vtils/compare/v4.16.0...v4.16.1) (2021-01-04)
### Bug Fixes
- **renderComponent:** 修正 key 赋值时机 ([516456e](https://github.com/fjc0k/vtils/commit/516456e8f625d8e174510d687ae0046d5b684aee))
## [4.16.0](https://github.com/fjc0k/vtils/compare/v4.15.0...v4.16.0) (2021-01-04)
### Features
- **useStaged:** 支持 reset 重置暂存状态 ([8edd7e1](https://github.com/fjc0k/vtils/commit/8edd7e10b1388bdc4f6aae5a0bfded466aec16be))
## [4.15.0](https://github.com/fjc0k/vtils/compare/v4.14.1...v4.15.0) (2021-01-04)
### Features
- **react:** 新增 useStaged 暂存状态 ([7fd1181](https://github.com/fjc0k/vtils/commit/7fd1181cf8fd6bf28984fe5b1ba54ed0734f3298))
### [4.14.1](https://github.com/fjc0k/vtils/compare/v4.14.0...v4.14.1) (2021-01-03)
### Bug Fixes
- **TreeData:** 优化类型 ([e454d61](https://github.com/fjc0k/vtils/commit/e454d61beb9607027a47f4e9c6d9948246fef098))
## [4.14.0](https://github.com/fjc0k/vtils/compare/v4.13.2...v4.14.0) (2021-01-03)
### Features
- **cloneDeep,TreeData:** 支持 ignore ([f9bb684](https://github.com/fjc0k/vtils/commit/f9bb684ee2a9777a8d4413ca22de96afd81716fc))
### [4.13.2](https://github.com/fjc0k/vtils/compare/v4.13.1...v4.13.2) (2020-12-31)
### Bug Fixes
- **validator:** mixed 默认 any ([a6c5b71](https://github.com/fjc0k/vtils/commit/a6c5b711b66a3b4dc7fb2401757567ff35468664))
### [4.13.1](https://github.com/fjc0k/vtils/compare/v4.13.0...v4.13.1) (2020-12-30)
### Bug Fixes
- **renderComponent:** 生成默认 key 值 ([ceae5f1](https://github.com/fjc0k/vtils/commit/ceae5f137575aaa21900e720035f566759f29b3f))
## [4.13.0](https://github.com/fjc0k/vtils/compare/v4.12.0...v4.13.0) (2020-12-29)
### Features
- **renderComponent:** 支持设置渲染容器 ([4150947](https://github.com/fjc0k/vtils/commit/4150947808848d6500c47455b8e2feace5bf3cc6))
## [4.12.0](https://github.com/fjc0k/vtils/compare/v4.11.1...v4.12.0) (2020-12-25)
### Features
- **types:** export Class, Asyncify ([739aa6e](https://github.com/fjc0k/vtils/commit/739aa6e932c4f0afb02ed85c1f8e80f1704a2e47))
### [4.11.1](https://github.com/fjc0k/vtils/compare/v4.11.0...v4.11.1) (2020-12-24)
## [4.11.0](https://github.com/fjc0k/vtils/compare/v4.10.1...v4.11.0) (2020-12-24)
### Features
- **validator:** 优化提示文本 ([492c695](https://github.com/fjc0k/vtils/commit/492c6954b1e11139c8fd51bb034ba877a2c33ca3))
- **x:** 新增 sha1 ([d69393a](https://github.com/fjc0k/vtils/commit/d69393ab1097bdef56e045a6f68c20fe93bad60f))
- **x:** 新增 WechatMessageCrypto 微信公众号消息加解密 ([c106915](https://github.com/fjc0k/vtils/commit/c1069152a6ddf4d563df0f16e09bbedd4195481f))
### [4.10.1](https://github.com/fjc0k/vtils/compare/v4.10.0...v4.10.1) (2020-12-22)
## [4.10.0](https://github.com/fjc0k/vtils/compare/v4.9.1...v4.10.0) (2020-12-22)
### Features
- **x:** 新增 RedisCookieJar 使用 Redis 作为 Cookie Jar ([2815e13](https://github.com/fjc0k/vtils/commit/2815e13af3665eaab539da4a23d039edc06dbfc1))
### [4.9.1](https://github.com/fjc0k/vtils/compare/v4.9.0...v4.9.1) (2020-12-21)
### Bug Fixes
- **indent,dedent:** 插入值支持 number 类型 ([926b7cb](https://github.com/fjc0k/vtils/commit/926b7cbe8ca5c8f0582b43b98d1123e52c77f2f5))
## [4.9.0](https://github.com/fjc0k/vtils/compare/v4.8.0...v4.9.0) (2020-12-21)
### Features
- **createXml:** 添加 array 辅助方法 ([c1e0de1](https://github.com/fjc0k/vtils/commit/c1e0de183a3843bd17cf3d6c957e8e7778d7be62))
## [4.8.0](https://github.com/fjc0k/vtils/compare/v4.7.0...v4.8.0) (2020-12-21)
### Features
- **TreeData:** 新增 traverseNode 遍历节点 ([c5dd7b1](https://github.com/fjc0k/vtils/commit/c5dd7b1279093c4fcaa58ea0cbcd43899e3ecb78))
- **x:** 新增 cuid、uuid ([e938c99](https://github.com/fjc0k/vtils/commit/e938c995c455509cccd8734248f17236fd7610ab))
- **x:** 新增 parseXml、createXml ([1ee40c7](https://github.com/fjc0k/vtils/commit/1ee40c7e46108fee79f125b6aeaf79c878cad69d))
## [4.7.0](https://github.com/fjc0k/vtils/compare/v4.6.0...v4.7.0) (2020-12-19)
### Features
- **TreeData:** 遍历优化 ([f432090](https://github.com/fjc0k/vtils/commit/f4320909b5d922a0a4ff03a896ca51c886d33fcd))
- **TreeData:** 遍历算法优化 ([e7a8cf8](https://github.com/fjc0k/vtils/commit/e7a8cf8426c9e470dd74de40ee814e2092cad76f))
- **utils:** 新增 cloneDeepFast 深克隆 ([704704b](https://github.com/fjc0k/vtils/commit/704704b63a35b99ae1f5ba6a4c4da2f4a95297b8))
## [4.6.0](https://github.com/fjc0k/vtils/compare/v4.5.0...v4.6.0) (2020-12-14)
### Features
- **TreeData:** 新增 exportList 方法导出一维列表数据 ([66cf34d](https://github.com/fjc0k/vtils/commit/66cf34d3b84b44da230339a68574842967f85da1))
- **TreeData:** 新增 filter 方法筛选符合条件的节点 ([df07544](https://github.com/fjc0k/vtils/commit/df07544bb5c6f32b84bd6d6c94b092f277367c86))
## [4.5.0](https://github.com/fjc0k/vtils/compare/v4.4.2...v4.5.0) (2020-12-14)
### Features
- **TreeData:** 新增 fromList 方法从列表生成实例 ([5516106](https://github.com/fjc0k/vtils/commit/551610667b537a4fde8458e85f2c9ba2b8fc4f23))
### [4.4.2](https://github.com/fjc0k/vtils/compare/v4.4.1...v4.4.2) (2020-12-12)
### [4.4.1](https://github.com/fjc0k/vtils/compare/v4.4.0...v4.4.1) (2020-12-12)
## [4.4.0](https://github.com/fjc0k/vtils/compare/v4.3.0...v4.4.0) (2020-12-12)
### Features
- **TreeData:** 优化遍历算法 ([954af64](https://github.com/fjc0k/vtils/commit/954af647f0ab5139f1ccc6699495009755b6f1db))
- **TreeData:** 新增 removeNode、removeNodes、count ([7c009f3](https://github.com/fjc0k/vtils/commit/7c009f340dc41b0fe072bab803ac50d18c8be612))
## [4.3.0](https://github.com/fjc0k/vtils/compare/v4.2.1...v4.3.0) (2020-12-12)
### Features
- **TreeData:** 新增 clone 方法克隆实例 ([e08ad66](https://github.com/fjc0k/vtils/commit/e08ad6687d95d76486e23744d09bfecefafadaa7))
### [4.2.1](https://github.com/fjc0k/vtils/compare/v4.2.0...v4.2.1) (2020-12-11)
### Bug Fixes
- **TreeData:** findNodePath、findNodePaths 的结果应包含当前节点 ([53edbb2](https://github.com/fjc0k/vtils/commit/53edbb2e7ada54b3d67404873966615540e8f115))
## [4.2.0](https://github.com/fjc0k/vtils/compare/v4.1.0...v4.2.0) (2020-12-11)
### Features
- **TreeData:** 新增 findNode、findNodes、findNodePath、findNodePaths 方法 ([7217a3a](https://github.com/fjc0k/vtils/commit/7217a3ac713ed579bed04bd442dc6aafab1e7778))
## [4.1.0](https://github.com/fjc0k/vtils/compare/v4.0.0...v4.1.0) (2020-12-08)
### Features
- **utils:** 新增 isBlobUrl 检测传入值是否是 Blob URL ([5654306](https://github.com/fjc0k/vtils/commit/56543061a20fc9cb3b6b36fc73edb97c0b55b877))
- **utils:** 新增 loadCss 加载 CSS 样式 ([70e4727](https://github.com/fjc0k/vtils/commit/70e4727be946fd1ce00881fe0db2eeab854152e2))
### Bug Fixes
- 不打包 validator 的类型定义 ([7d4bd9a](https://github.com/fjc0k/vtils/commit/7d4bd9a6a5c0ec458c3a0b730411d759b19c9372))
## [4.0.0](https://github.com/fjc0k/vtils/compare/v4.0.0-beta.7...v4.0.0) (2020-12-07)
### Features
- **utils:** 新增 TreeData 处理树数据 ([23df907](https://github.com/fjc0k/vtils/commit/23df9070e0bd12a6ba5c41b9f98c23a81254980c))
- **wait:** 支持返回值 ([2d1b63e](https://github.com/fjc0k/vtils/commit/2d1b63e713920e3247262c8623568dc1644deaaa))
- **wait:** 新增 wait.reject ([e9314c8](https://github.com/fjc0k/vtils/commit/e9314c8bd023878cb3063ca94bf494bdd18f4933))
## [4.0.0-beta.7](https://github.com/fjc0k/vtils/compare/v4.0.0-beta.6...v4.0.0-beta.7) (2020-11-27)
### Features
- **createUrlQueryString,parseUrlQueryString:** 支持自定义连接符 ([a7d02bd](https://github.com/fjc0k/vtils/commit/a7d02bd034da0ac3711006e0c7e978d2fad6ab7c))
- **utils:** 新增 isDataUrl ([80b3a0c](https://github.com/fjc0k/vtils/commit/80b3a0c2a938dbf540c14f3b403eeded59ed698d))
- **utils:** 新增 parseDataUrl ([b67d872](https://github.com/fjc0k/vtils/commit/b67d87201f141449ca7397ccb9e92e13d3ea4a4a))
## [4.0.0-beta.6](https://github.com/fjc0k/vtils/compare/v4.0.0-beta.5...v4.0.0-beta.6) (2020-11-26)
### Bug Fixes
- **react:** export types ([dcf584f](https://github.com/fjc0k/vtils/commit/dcf584fa9946c3ece6de10ad5d5c2dfce9ecab91))
## [4.0.0-beta.5](https://github.com/fjc0k/vtils/compare/v4.0.0-beta.4...v4.0.0-beta.5) (2020-11-25)
### Features
- **types:** 新增 CamelCase, SnakeCase, KebabCase, PascalCase, DelimiterCase ([0112b50](https://github.com/fjc0k/vtils/commit/0112b50db1021169220332888b9eb4eb26880908))
## [4.0.0-beta.4](https://github.com/fjc0k/vtils/compare/v4.0.0-beta.3...v4.0.0-beta.4) (2020-11-25)
### Bug Fixes
- **chooseFile:** 返回结果为只读数组 ([d0fbac2](https://github.com/fjc0k/vtils/commit/d0fbac2f3fc7c42364db27c2969fa14fb35c241e))
- **deps:** update dependency yup to ^0.31.0 ([7859da5](https://github.com/fjc0k/vtils/commit/7859da5078625a3ea21715b81debe2434200ab45))
## [4.0.0-beta.3](https://github.com/fjc0k/vtils/compare/v4.0.0-beta.2...v4.0.0-beta.3) (2020-11-23)
### Bug Fixes
- cjs 产物 ([3633d35](https://github.com/fjc0k/vtils/commit/3633d35f7d15157fa7bd1b6da61ca765ca9b5bd7))
## [4.0.0-beta.2](https://github.com/fjc0k/vtils/compare/v4.0.0-beta.1...v4.0.0-beta.2) (2020-11-23)
### Bug Fixes
- 修复 commonjs 配置 ([dc91321](https://github.com/fjc0k/vtils/commit/dc913211d095ae7ba6cb7a3e52f88ec023b16f2b))
## [4.0.0-beta.1](https://github.com/fjc0k/vtils/compare/v4.0.0-beta.0...v4.0.0-beta.1) (2020-11-22)
## [4.0.0-beta.0](https://github.com/fjc0k/vtils/compare/v3.53.0...v4.0.0-beta.0) (2020-11-22)
### Features
- 为 types 工具添加测试 ([26be1f6](https://github.com/fjc0k/vtils/commit/26be1f66cb2a03728165c1a6b71bf86b5e92e725))
- 为其余 types 添加测试 ([c36971e](https://github.com/fjc0k/vtils/commit/c36971ecc9a32e6eb530a1b309089e903c6e2ffc))
- 重构 ([c085c08](https://github.com/fjc0k/vtils/commit/c085c08f3cbb1005c8804e685321ef1e523eee4a))
### Bug Fixes
- **deps:** update dependency yup to ^0.30.0 ([500ad27](https://github.com/fjc0k/vtils/commit/500ad27e3200d6353b4a6bafa4693488cf093b05))
## [3.53.0](https://github.com/fjc0k/vtils/compare/v3.52.0...v3.53.0) (2020-11-18)
### Features
- **utils:** 新增 constantCase, pascalCase ([3f78d8d](https://github.com/fjc0k/vtils/commit/3f78d8d86d7a1a266618b6b5ab1b8ab0a9d7e87e))
## [3.52.0](https://github.com/fjc0k/vtils/compare/v3.51.0...v3.52.0) (2020-11-18)
### Features
- **chooseFile:** 完善单测 ([1d2190f](https://github.com/fjc0k/vtils/commit/1d2190f19082146613fff2c5512f5f73f64d038f))
- **utils:** 新增 copyTextToClipboard 复制文本到剪切板 ([52b437e](https://github.com/fjc0k/vtils/commit/52b437e01f1be88f10647e6f5c231456b7829513))
- **utils:** 新增 formatBytes 格式化字节数 ([699789a](https://github.com/fjc0k/vtils/commit/699789ab5042bc7167baab5034c3f19ef1b51d88))
## [3.51.0](https://github.com/fjc0k/vtils/compare/v3.50.2...v3.51.0) (2020-11-17)
### Features
- **utils:** 新增 chooseFile 选择文件 ([128b650](https://github.com/fjc0k/vtils/commit/128b6503a5c5d7989b56a1b139b92d81cc97f0e5))
### [3.50.2](https://github.com/fjc0k/vtils/compare/v3.50.1...v3.50.2) (2020-11-12)
### [3.50.1](https://github.com/fjc0k/vtils/compare/v3.50.0...v3.50.1) (2020-11-12)
### Bug Fixes
- **types:** 使用 api-extractor 打包类型文件 ([b4c5bbe](https://github.com/fjc0k/vtils/commit/b4c5bbed628008e828c2f1dcf25865524d15ba32))
## [3.50.0](https://github.com/fjc0k/vtils/compare/v3.49.3...v3.50.0) (2020-11-08)
### Features
- **mp:** 新增 getSceneParams、useSceneParams ([0ab6f55](https://github.com/fjc0k/vtils/commit/0ab6f553ff189e0107b9ec638aa704ce74136fef))
### [3.49.3](https://github.com/fjc0k/vtils/compare/v3.49.2...v3.49.3) (2020-10-11)
### Bug Fixes
- 回退 type-fest、文档生成不报错 ([9fe92e1](https://github.com/fjc0k/vtils/commit/9fe92e1e49b6f277d60d65220eecd609644a3d16))
### [3.49.2](https://github.com/fjc0k/vtils/compare/v3.49.0...v3.49.2) (2020-10-11)
## [3.49.0](https://github.com/fjc0k/vtils/compare/v3.48.0...v3.49.0) (2020-10-10)
### Features
- **date:** 新增 formatDistanceAgo ([2715dee](https://github.com/fjc0k/vtils/commit/2715dee7e6b2748745738610550c78aaa0f149d6))
## [3.48.0](https://github.com/fjc0k/vtils/compare/v3.47.0...v3.48.0) (2020-09-26)
### Features
- **Wechat:** 添加 requestPayment 方法 ([3827479](https://github.com/fjc0k/vtils/commit/3827479793ffcf51d87c58344fda0e61249aed7c))
## [3.47.0](https://github.com/fjc0k/vtils/compare/v3.46.0...v3.47.0) (2020-09-19)
### Features
- **useLoadMore:** 返回数据兼容 list 属性代替 data 属性的情况 ([f28212f](https://github.com/fjc0k/vtils/commit/f28212fd6cdd704e5e1690f43e9244add8bfa42b))
## [3.46.0](https://github.com/fjc0k/vtils/compare/v3.45.0...v3.46.0) (2020-09-19)
### Features
- **react:** 新增 useStateWithDeps ([dff9b73](https://github.com/fjc0k/vtils/commit/dff9b73a26196257a6a837b66131be97b40e5e87))
- **types:** 导出 PackageJson, TsConfigJson, JsonValue, JsonArray, JsonObject ([59ecc3d](https://github.com/fjc0k/vtils/commit/59ecc3d07a5e392791ec15fd6de63acc22af7c39))
## [3.45.0](https://github.com/fjc0k/vtils/compare/v3.44.1...v3.45.0) (2020-09-17)
### Features
- **navigatePageTo:** 在页面真正切换后 Promise 才会被 resolve ([35a5721](https://github.com/fjc0k/vtils/commit/35a5721510e992b128aa61bf6071585c399c2623))
### [3.44.1](https://github.com/fjc0k/vtils/compare/v3.44.0...v3.44.1) (2020-08-31)
### Bug Fixes
- **getCurrentPagePath:** 从 utils 引入 last ([6a5ef5f](https://github.com/fjc0k/vtils/commit/6a5ef5f3fd5884286c6c45c1ddc24b30aee369d0))
## [3.44.0](https://github.com/fjc0k/vtils/compare/v3.43.1...v3.44.0) (2020-08-29)
### Features
- **miniProgramBus:** 新增 routeChange ([5981d30](https://github.com/fjc0k/vtils/commit/5981d30292e9b9c3d1fdd6f3838831c5f1b76275))
### [3.43.1](https://github.com/fjc0k/vtils/compare/v3.43.0...v3.43.1) (2020-08-28)
### Bug Fixes
- **getCurrentPageQuery:** 对值执行 decodeURIComponent ([c46cacd](https://github.com/fjc0k/vtils/commit/c46cacdae094b0218e6758c8886724cfdab195d4))
## [3.43.0](https://github.com/fjc0k/vtils/compare/v3.42.0...v3.43.0) (2020-08-28)
### Features
- **mp:** 新增 useShareAppMessage ([b5b39fe](https://github.com/fjc0k/vtils/commit/b5b39fe81957c8af24ccbc6e35bdb8aa2c7034de))
- **mp:** 新增 useTopBarInfo, useSubmit, usePullDownRefresh ([19073ec](https://github.com/fjc0k/vtils/commit/19073ecc43d3f1d272e7823b95330184fcaab74d))
### Bug Fixes
- **patchMiniProgram:** 页面展示时更新当前页面 ID ([033a818](https://github.com/fjc0k/vtils/commit/033a818998858c74eaced1cd69d276201b1d404f))
## [3.42.0](https://github.com/fjc0k/vtils/compare/v3.41.1...v3.42.0) (2020-08-27)
### Features
- **miniProgramBus:** 优化实现，支持返回数据类回调 ([aa9a690](https://github.com/fjc0k/vtils/commit/aa9a690c1c2ed8675726a9fef903acec90066ce8))
### Bug Fixes
- **miniProgramBus:** 页面卸载时移除对当前页面的监听 ([b04d161](https://github.com/fjc0k/vtils/commit/b04d161b00f8fa26fd94859801ccd8da1208c69b))
### [3.41.1](https://github.com/fjc0k/vtils/compare/v3.41.0...v3.41.1) (2020-08-27)
### Bug Fixes
- **miniProgramBus:** toUpperCase ([d50819b](https://github.com/fjc0k/vtils/commit/d50819ba343dbd19063c268de583f7a3d8b575df))
## [3.41.0](https://github.com/fjc0k/vtils/compare/v3.40.0...v3.41.0) (2020-08-26)
### Features
- **EventBus:** 支持 beforeEmit, beforeOn, tag ([ed28ce6](https://github.com/fjc0k/vtils/commit/ed28ce6f1e1750f9528bba146202e303028efb26))
- **mp:** 新增 miniProgramBus ([9538763](https://github.com/fjc0k/vtils/commit/9538763ff6597a8ae93fb48e1f7178e8db7602c8))
## [3.40.0](https://github.com/fjc0k/vtils/compare/v3.39.0...v3.40.0) (2020-08-25)
### Features
- **inMiniProgram:** 添加 \$brand 表示小程序品牌 ([7e84e77](https://github.com/fjc0k/vtils/commit/7e84e77d2494261ba68f6688c57de0681733d098))
- **mp:** 添加 patchMiniProgram ([b6d0669](https://github.com/fjc0k/vtils/commit/b6d0669b11fd9b24596e4545d580341b64c3fc95))
### Bug Fixes
- **getCurrentPagePath:** 兼容字节跳动小程序 ([7c33241](https://github.com/fjc0k/vtils/commit/7c33241ece42811ab71e0158529592d89fb58160))
- **navigatePageTo:** 兼容支付宝小程序 ([f102307](https://github.com/fjc0k/vtils/commit/f102307fbce31084ff3ec092783ba42a96424d79))
## [3.39.0](https://github.com/fjc0k/vtils/compare/v3.38.0...v3.39.0) (2020-08-25)
### Features
- **mp:** navigatePageTo 支持 query ([71b461e](https://github.com/fjc0k/vtils/commit/71b461e45745f68fdec5eaa27131fe6277a35667))
- **mp:** 完善注释 ([f0781f7](https://github.com/fjc0k/vtils/commit/f0781f733831f8d5f59273cbe6f3604179afa8ac))
- **mp:** 新增 getCurrentPagePath, getCurrentPageQuery, getCurrentPageUrl ([9308bec](https://github.com/fjc0k/vtils/commit/9308becbed470145685b7dbdb40175877e76cf14))
## [3.38.0](https://github.com/fjc0k/vtils/compare/v3.37.2...v3.38.0) (2020-08-25)
### Features
- **utils:** 新增 createUrlQueryString, parseUrlQueryString ([7cd3152](https://github.com/fjc0k/vtils/commit/7cd3152766dfbc6441f93336ae49b3d9ca1b8588))
### [3.37.2](https://github.com/fjc0k/vtils/compare/v3.37.1...v3.37.2) (2020-08-25)
### [3.37.1](https://github.com/fjc0k/vtils/compare/v3.37.0...v3.37.1) (2020-08-25)
## [3.37.0](https://github.com/fjc0k/vtils/compare/v3.36.3...v3.37.0) (2020-08-25)
### Features
- **mp:** 新增 getTopBarInfo, submit ([8cfa77d](https://github.com/fjc0k/vtils/commit/8cfa77dc53091aa4aaa5e9d6b3688766cc3541b8))
- **mp:** 新增 navigatePageBack ([0b5224e](https://github.com/fjc0k/vtils/commit/0b5224e2058d17d2784f59b78dd4023ef66737be))
- 新增 mp 系列工具 ([2cf912a](https://github.com/fjc0k/vtils/commit/2cf912a2fb6f669b25a568925cced219afcb5395))
### [3.36.3](https://github.com/fjc0k/vtils/compare/v3.36.2...v3.36.3) (2020-08-23)
### Bug Fixes
- **useSearchParam.taro:** 兼容 taro 3.0.8 ([c797ed2](https://github.com/fjc0k/vtils/commit/c797ed253c569b8bb169ebb1707cede5ee284b48))
- pika -> skypack ([dfa769a](https://github.com/fjc0k/vtils/commit/dfa769a0b9ef2dc5f8ade95136f894a4fadbf109))
### [3.36.2](https://github.com/fjc0k/vtils/compare/v3.36.1...v3.36.2) (2020-08-21)
### Bug Fixes
- 支持 TypeScript 4 ([b0128d6](https://github.com/fjc0k/vtils/commit/b0128d677ff8f52ef2176f072ab06dbce07bd7c1))
### [3.36.1](https://github.com/fjc0k/vtils/compare/v3.36.0...v3.36.1) (2020-08-17)
### Bug Fixes
- **validateInOrder, validateInOrderSync:** 支持未定义的键 ([7296494](https://github.com/fjc0k/vtils/commit/72964947402aba1c3fae665dd02951cd6a750afb))
## [3.36.0](https://github.com/fjc0k/vtils/compare/v3.35.0...v3.36.0) (2020-08-13)
### Features
- **yup:** 添加 validateInOrder, validateInOrderSync 支持按顺序验证对象 ([50a1c42](https://github.com/fjc0k/vtils/commit/50a1c4249d1c354ed258ad81914dd33f219227aa))
- **yup:** 添加 validatePlus, validatePlusSync 方法 ([8dbc288](https://github.com/fjc0k/vtils/commit/8dbc28802e3102aea3c8953de6a67ec2d964cf80))
## [3.35.0](https://github.com/fjc0k/vtils/compare/v3.34.3...v3.35.0) (2020-08-13)
### Features
- **utils:** 新增 createSubmit ([9f07d41](https://github.com/fjc0k/vtils/commit/9f07d41ecc5292807dfa52a13416b76a62427e85))
### [3.34.3](https://github.com/fjc0k/vtils/compare/v3.34.2...v3.34.3) (2020-08-08)
### [3.34.2](https://github.com/fjc0k/vtils/compare/v3.34.1...v3.34.2) (2020-08-07)
### Bug Fixes
- **react:** 将导出加入 prettier-ignore ([6b01d1a](https://github.com/fjc0k/vtils/commit/6b01d1a497d1fbb6a456863638b1f70ffb82abe1))
### [3.34.1](https://github.com/fjc0k/vtils/compare/v3.34.0...v3.34.1) (2020-08-07)
### Bug Fixes
- **react:** 手动导出以解决 cjs 下 Cannot redefine property 的问题 ([11fb15c](https://github.com/fjc0k/vtils/commit/11fb15c1f18b220afffd3fc50f79e9e7bf9fd13b))
## [3.34.0](https://github.com/fjc0k/vtils/compare/v3.33.0...v3.34.0) (2020-08-06)
### Features
- **useControllableValue:** 支持重置值 ([0ffb359](https://github.com/fjc0k/vtils/commit/0ffb35918f3b0dcbb97ad7a34b447c7c385a9ce6))
## [3.33.0](https://github.com/fjc0k/vtils/compare/v3.32.1...v3.33.0) (2020-08-06)
### Features
- **useControllableValue:** 支持 alwaysUpdateValue ([18c0379](https://github.com/fjc0k/vtils/commit/18c0379073d16b1bfecc7a3f2496ff3295450223))
### [3.32.1](https://github.com/fjc0k/vtils/compare/v3.32.0...v3.32.1) (2020-08-06)
### Bug Fixes
- **deps:** update dependency miniprogram-api-typings to v3 ([410ece7](https://github.com/fjc0k/vtils/commit/410ece7010b7c9b6c2240c389ac13b7dfdbcf2d6))
## [3.32.0](https://github.com/fjc0k/vtils/compare/v3.31.1...v3.32.0) (2020-07-27)
### Features
- **useControllableValue:** 支持设置默认值 ([e9fa831](https://github.com/fjc0k/vtils/commit/e9fa831736c720db7da62b1ea86db4de4eaf0cb8))
### [3.31.1](https://github.com/fjc0k/vtils/compare/v3.31.0...v3.31.1) (2020-07-25)
### Bug Fixes
- **defineComponent:** 修复类型定义 ([472aecd](https://github.com/fjc0k/vtils/commit/472aecd2d2cd8bbebcf1680e8ef16893e0c2c9e7))
## [3.31.0](https://github.com/fjc0k/vtils/compare/v3.30.0...v3.31.0) (2020-07-25)
### Features
- **react:** ExtendComponentProps 更名为 DeriveComponentProps ([f7fe455](https://github.com/fjc0k/vtils/commit/f7fe4551fbb4d0d4f6b7b6bc2b2df8b84eed0874))
## [3.30.0](https://github.com/fjc0k/vtils/compare/v3.29.0...v3.30.0) (2020-07-25)
### Features
- **react:** 新增 CommonComponentProps ([edcd28d](https://github.com/fjc0k/vtils/commit/edcd28d0a1a4c46a2d26a909f2702c9e2196db06))
## [3.29.0](https://github.com/fjc0k/vtils/compare/v3.28.0...v3.29.0) (2020-07-24)
### Features
- **react:** 新增 useEnvironment ([7db160e](https://github.com/fjc0k/vtils/commit/7db160e653451366cf8e3e2032fc4e7350477e18))
- **utils:** 新增 getEnvironment ([6e09372](https://github.com/fjc0k/vtils/commit/6e093725a70e1a360ad8ecfe12ceed8aba90d1e2))
### Bug Fixes
- **deps:** update dependency miniprogram-api-typings to ^2.11.0 ([4b31555](https://github.com/fjc0k/vtils/commit/4b31555529f4ec01bca225005ec09efef79dba3a))
## [3.28.0](https://github.com/fjc0k/vtils/compare/v3.27.0...v3.28.0) (2020-07-23)
### Features
- **inAndroid:** 支持在小程序中使用 ([b3db043](https://github.com/fjc0k/vtils/commit/b3db043c15a3dd30fac061876f6a14cbbb194ea7))
- **inIOS:** 支持在小程序中使用 ([e804fb8](https://github.com/fjc0k/vtils/commit/e804fb81c5b2a255ca80e7204c887cc7f370a597))
- **inMiniProgram:** 在小程序中时，现在会返回小程序 API 挂载的全局对象 ([ba90ab8](https://github.com/fjc0k/vtils/commit/ba90ab87af6a19f0007f8f17650a08026a132722))
- **utils:** inWechat 更名为 inWechatWebView ([1d341e4](https://github.com/fjc0k/vtils/commit/1d341e47d41a829bbaea59cbf0eae51f6d87e92b))
## [3.27.0](https://github.com/fjc0k/vtils/compare/v3.26.0...v3.27.0) (2020-07-22)
### Features
- **utils:** 新增 inMiniProgram ([7685872](https://github.com/fjc0k/vtils/commit/76858724e74064f6aac945be0952ae46bc8d16dd))
- **utils:** 新增 inTaro ([19ad7f3](https://github.com/fjc0k/vtils/commit/19ad7f37587a34e337f2c3a3c1061dd0d1302247))
## [3.26.0](https://github.com/fjc0k/vtils/compare/v3.25.4...v3.26.0) (2020-07-22)
### Features
- **react:** 新增 useHover ([59b4e38](https://github.com/fjc0k/vtils/commit/59b4e38cfd7f08727e348aa3be917b27d76b8fa3))
### Bug Fixes
- **useInterval:** 修正测试用例 ([8d45de0](https://github.com/fjc0k/vtils/commit/8d45de0db007baf468ac296a2b5c27059d86a2b2))
### [3.25.4](https://github.com/fjc0k/vtils/compare/v3.25.3...v3.25.4) (2020-07-22)
### Bug Fixes
- **ExtendComponentProps:** 修复 TOverride 的类型定义 ([3051055](https://github.com/fjc0k/vtils/commit/30510553e20198f32bc672478f1c6e61a7b9b07f))
### [3.25.3](https://github.com/fjc0k/vtils/compare/v3.25.2...v3.25.3) (2020-07-21)
### Bug Fixes
- **useInterval:** 修复测试问题 ([7688b13](https://github.com/fjc0k/vtils/commit/7688b139d7909343393603daad34038d6f61fb30))
### [3.25.2](https://github.com/fjc0k/vtils/compare/v3.25.1...v3.25.2) (2020-07-21)
### Bug Fixes
- **defineComponent:** defaultProps 始终可选 ([3c21a39](https://github.com/fjc0k/vtils/commit/3c21a398c28bb7b5b4b01eff5ca9c250ee1fb122))
### [3.25.1](https://github.com/fjc0k/vtils/compare/v3.25.0...v3.25.1) (2020-07-21)
### Bug Fixes
- **defineComponent:** defaultProps 定义优化 ([86cf2ef](https://github.com/fjc0k/vtils/commit/86cf2ef525e729605a4a060e6286daaf0532ce00))
## [3.25.0](https://github.com/fjc0k/vtils/compare/v3.24.1...v3.25.0) (2020-07-20)
### Features
- **react:** 新增 defineComponent ([a9c95d7](https://github.com/fjc0k/vtils/commit/a9c95d7398d98915f852d772f3510e075e4222a0))
- **react:** 新增 ExtendComponentProps ([a1c30c1](https://github.com/fjc0k/vtils/commit/a1c30c1026088d10bbbf7aad18f982c641bea0f0))
- **react:** 新增 isVisibleValue ([a368e51](https://github.com/fjc0k/vtils/commit/a368e51add413de69d60d82787f83d1e0c065c9b))
- **react:** 新增 renderComponent ([ceecb28](https://github.com/fjc0k/vtils/commit/ceecb28913fe66356667de89b9e28bd01acd3beb))
- **react:** 新增 useControllableValue ([da57d15](https://github.com/fjc0k/vtils/commit/da57d15e3f6603d5fd5c1ee45c585371778d6bf1))
### Bug Fixes
- **defineComponent:** 组件的内部属性去除 key 和 ref ([57196ff](https://github.com/fjc0k/vtils/commit/57196ffd707b019bc3d3f42e24c7d9fe9ddd4354))
### [3.24.1](https://github.com/fjc0k/vtils/compare/v3.24.0...v3.24.1) (2020-07-18)
## [3.24.0](https://github.com/fjc0k/vtils/compare/v3.23.0...v3.24.0) (2020-07-18)
### Features
- **utils:** 新增 getWechatPublicAccountQrcodeUrl ([398c886](https://github.com/fjc0k/vtils/commit/398c886d823842e632144419939238d8f257464c))
## [3.23.0](https://github.com/fjc0k/vtils/compare/v3.22.0...v3.23.0) (2020-07-17)
### Features
- **react:** 新增 useWindowSize ([7abcb23](https://github.com/fjc0k/vtils/commit/7abcb23ff8deddaf6bbf9e6b5283adf3e0637161))
## [3.22.0](https://github.com/fjc0k/vtils/compare/v3.21.1...v3.22.0) (2020-07-16)
### Features
- **useInterval:** 支持 duration ([15b7b2c](https://github.com/fjc0k/vtils/commit/15b7b2c24969dd8bfb1b2a78cc1779f10465b974))
### [3.21.1](https://github.com/fjc0k/vtils/compare/v3.21.0...v3.21.1) (2020-07-16)
### Bug Fixes
- **useLocalStorage:** 更新实现 ([1d44804](https://github.com/fjc0k/vtils/commit/1d4480435768080643290fd22ef6ae86ac64424e))
## [3.21.0](https://github.com/fjc0k/vtils/compare/v3.20.0...v3.21.0) (2020-07-16)
### Features
- **react:** 新增 useLocalStorage ([7a415e0](https://github.com/fjc0k/vtils/commit/7a415e0fcd7ce7331ceb3bd786eac10c13b6e8a2))
## [3.20.0](https://github.com/fjc0k/vtils/compare/v3.19.0...v3.20.0) (2020-07-15)
### Features
- **types:** 新增 AnyAsyncFunction ([b6d0602](https://github.com/fjc0k/vtils/commit/b6d06022bc5cca295b1689d742b9f6a55d59aad5))
- **utils:** 新增 onceMeanwhile ([bfa244e](https://github.com/fjc0k/vtils/commit/bfa244e3ea20e38ecc978b0686b556e24afc9a06))
## [3.19.0](https://github.com/fjc0k/vtils/compare/v3.18.3...v3.19.0) (2020-07-15)
### Features
- **utils:** 新增 placeKitten ([b154e21](https://github.com/fjc0k/vtils/commit/b154e21585d1008890760e2c0d4a82461c1c5169))
### [3.18.3](https://github.com/fjc0k/vtils/compare/v3.18.2...v3.18.3) (2020-07-14)
### Bug Fixes
- **indent:** 后行断言部分浏览器暂不支持 ([3262fa0](https://github.com/fjc0k/vtils/commit/3262fa0c6f627369b6dc8a19763d419f8a41cfad))
### [3.18.2](https://github.com/fjc0k/vtils/compare/v3.18.1...v3.18.2) (2020-07-13)
### Bug Fixes
- 锁定 standard-version 版本 ([fc10dd3](https://github.com/fjc0k/vtils/commit/fc10dd3789ae91ffc3461e3d09eddd98165a6e0c))
### [3.18.1](https://github.com/fjc0k/vtils/compare/v3.18.0...v3.18.1) (2020-07-13)
## [3.18.0](https://github.com/fjc0k/vtils/compare/v3.17.0...v3.18.0) (2020-07-13)
### Features
- **taro:** 新增 getTopBarInfo, useTopBarInfo ([72e3f26](https://github.com/fjc0k/vtils/commit/72e3f26a548fbd06f49375e70bae4e6b76d8401d))
## [3.17.0](https://github.com/fjc0k/vtils/compare/v3.16.0...v3.17.0) (2020-07-10)
### Features
- **taro:** 新增 useSubmit ([fbe8d8a](https://github.com/fjc0k/vtils/commit/fbe8d8a72e505db18cf77dca93ca397fc9502993))
## [3.16.0](https://github.com/fjc0k/vtils/compare/v3.15.1...v3.16.0) (2020-07-10)
### Features
- **taro:** 新增 useAutoStopPullDownRefresh ([4338980](https://github.com/fjc0k/vtils/commit/433898027306cd9cc0c07421451c69c5f16eb6df))
### [3.15.1](https://github.com/fjc0k/vtils/compare/v3.15.0...v3.15.1) (2020-07-10)
### Bug Fixes
- **useReachBottom.taro:** 立即触发一次回调有误 ([71323b0](https://github.com/fjc0k/vtils/commit/71323b0bc984dab114920388c590d860ea149059))
## [3.15.0](https://github.com/fjc0k/vtils/compare/v3.14.0...v3.15.0) (2020-07-09)
### Features
- **useInterval:** 支持通过 delay 控制 ([9da9d11](https://github.com/fjc0k/vtils/commit/9da9d11f129ce5d5e811c655d9eeb1591104e5eb))
## [3.14.0](https://github.com/fjc0k/vtils/compare/v3.13.0...v3.14.0) (2020-07-09)
### Features
- **react:** 新增 useSearchParam ([119a864](https://github.com/fjc0k/vtils/commit/119a864eebd1b038a423fea3fc1e4f737973efb5))
## [3.13.0](https://github.com/fjc0k/vtils/compare/v3.12.0...v3.13.0) (2020-07-09)
### Features
- **react:** 新增 useInterval ([d7e942c](https://github.com/fjc0k/vtils/commit/d7e942c7b6a209c293ddf19a7432c3816e063cf1))
## [3.12.0](https://github.com/fjc0k/vtils/compare/v3.11.1...v3.12.0) (2020-07-09)
### Features
- **date:** 新增 intervalToRestrictiveDuration ([cfdcc45](https://github.com/fjc0k/vtils/commit/cfdcc45f0693d34eeb42d2fc2a1ff8cde2dd77bc))
### [3.11.1](https://github.com/fjc0k/vtils/compare/v3.11.0...v3.11.1) (2020-07-09)
### Bug Fixes
- **useLoadMore:** 重新加载应重置 data ([10389c5](https://github.com/fjc0k/vtils/commit/10389c5cc57ac91e10bf8bf8d803587227827660))
## [3.11.0](https://github.com/fjc0k/vtils/compare/v3.10.1...v3.11.0) (2020-07-08)
### Features
- **createGlobalState:** 支持自定义结果 ([e481ce0](https://github.com/fjc0k/vtils/commit/e481ce0c928c421133889a78a273c08f35b370cb))
### Bug Fixes
- **useLoadMore:** 修复 data 的类型定义 ([7cc7972](https://github.com/fjc0k/vtils/commit/7cc7972257821dfc98a17591b460732f8c6222c1))
### [3.10.1](https://github.com/fjc0k/vtils/compare/v3.10.0...v3.10.1) (2020-07-08)
## [3.10.0](https://github.com/fjc0k/vtils/compare/v3.9.0...v3.10.0) (2020-07-08)
### Features
- **date:** 新增 anyToDate ([06d502c](https://github.com/fjc0k/vtils/commit/06d502c53295d02750d632e788d1cbe59fc35111))
## [3.9.0](https://github.com/fjc0k/vtils/compare/v3.8.1...v3.9.0) (2020-06-30)
### Features
- **taro:** 新增 submit ([4f1d662](https://github.com/fjc0k/vtils/commit/4f1d662e4c97722f2b21002daa7ab3caa7d2ed87))
### [3.8.1](https://github.com/fjc0k/vtils/compare/v3.8.0...v3.8.1) (2020-06-30)
### Bug Fixes
- **createGlobalState:** 延后注册的订阅不能获取最新值 ([c4a0062](https://github.com/fjc0k/vtils/commit/c4a0062ae6dbac9416a53775f1dd417452c98b0b))
## [3.8.0](https://github.com/fjc0k/vtils/compare/v3.7.1...v3.8.0) (2020-06-28)
### Features
- **utils:** 新增 traverse ([36d67e9](https://github.com/fjc0k/vtils/commit/36d67e9226aa79e687cbbb36e971a6a511c4291a))
### [3.7.1](https://github.com/fjc0k/vtils/compare/v3.7.0...v3.7.1) (2020-06-28)
### Bug Fixes
- **yup:** 修复 webpack 报警告问题 ([2e03e0c](https://github.com/fjc0k/vtils/commit/2e03e0cdcfe873e57de3ad4fdb800a02d5004910))
## [3.7.0](https://github.com/fjc0k/vtils/compare/v3.6.0...v3.7.0) (2020-06-24)
### Features
- **react:** 新增 useReachBottom.taro ([9afc481](https://github.com/fjc0k/vtils/commit/9afc481bff89fbe7a65fc74d7fe047f73116d174))
## [3.6.0](https://github.com/fjc0k/vtils/compare/v3.5.1...v3.6.0) (2020-06-24)
### Features
- **react:** 新增 useTitle ([9f86c3f](https://github.com/fjc0k/vtils/commit/9f86c3f41d3459f6915abdd45246499abcc0a307))
### [3.5.1](https://github.com/fjc0k/vtils/compare/v3.5.0...v3.5.1) (2020-06-22)
## [3.5.0](https://github.com/fjc0k/vtils/compare/v3.4.0...v3.5.0) (2020-06-22)
### Features
- **utils:** 新增 RichUrl ([c44f488](https://github.com/fjc0k/vtils/commit/c44f48889f35031c987fa60030d4f27c8bd4ee42))
## [3.4.0](https://github.com/fjc0k/vtils/compare/v3.3.1...v3.4.0) (2020-06-19)
### Features
- **createGlobalState:** 支持 watchState ([2412f3a](https://github.com/fjc0k/vtils/commit/2412f3a94076d9d5da368b88e6665c5b0a575bc5))
### [3.3.1](https://github.com/fjc0k/vtils/compare/v3.3.0...v3.3.1) (2020-06-18)
### Bug Fixes
- 设置发布包的 registry 为 https://registry.npmjs.org/ ([bbcf828](https://github.com/fjc0k/vtils/commit/bbcf828b5f814e9ce30c7b15d6e1bec70e38b3ab))
## [3.3.0](https://github.com/fjc0k/vtils/compare/v3.2.0...v3.3.0) (2020-06-18)
### Features
- **react:** 新增 createGlobalState ([037adcc](https://github.com/fjc0k/vtils/commit/037adcc8bb566f988c5e12828e55ca84abf5b98b))
## [3.2.0](https://github.com/fjc0k/vtils/compare/v3.1.2...v3.2.0) (2020-06-15)
### Features
- **utils:** 新增 md5 ([7a23391](https://github.com/fjc0k/vtils/commit/7a23391e3af57eee3fc81e1ef352a4b01959f600))
### [3.1.2](https://github.com/fjc0k/vtils/compare/v3.1.1...v3.1.2) (2020-06-15)
### [3.1.1](https://github.com/fjc0k/vtils/compare/v3.1.0...v3.1.1) (2020-06-14)
## [3.1.0](https://github.com/fjc0k/vtils/compare/v2.59.0...v3.1.0) (2020-06-14)
### Features
- 完成 v3 ([#13](https://github.com/fjc0k/vtils/issues/13)) ([8791ed8](https://github.com/fjc0k/vtils/commit/8791ed819f99267653fc96f6fe4c24a6d4e89142))
### [3.0.1-beta.26](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.25...v3.0.1-beta.26) (2020-06-14)
### [3.0.1-beta.25](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.24...v3.0.1-beta.25) (2020-06-12)
### [3.0.1-beta.24](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.23...v3.0.1-beta.24) (2020-06-11)
### [3.0.1-beta.23](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.22...v3.0.1-beta.23) (2020-06-10)
### [3.0.1-beta.22](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.21...v3.0.1-beta.22) (2020-06-10)
### [3.0.1-beta.21](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.20...v3.0.1-beta.21) (2020-06-10)
### [3.0.1-beta.20](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.19...v3.0.1-beta.20) (2020-06-10)
### [3.0.1-beta.19](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.18...v3.0.1-beta.19) (2020-06-09)
### [3.0.1-beta.18](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.17...v3.0.1-beta.18) (2020-06-08)
### [3.0.1-beta.17](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.16...v3.0.1-beta.17) (2020-06-08)
### [3.0.1-beta.16](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.15...v3.0.1-beta.16) (2020-06-08)
### [3.0.1-beta.15](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.14...v3.0.1-beta.15) (2020-06-08)
### [3.0.1-beta.14](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.13...v3.0.1-beta.14) (2020-06-08)
### [3.0.1-beta.13](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.12...v3.0.1-beta.13) (2020-06-08)
### [3.0.1-beta.12](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.11...v3.0.1-beta.12) (2020-06-08)
### [3.0.1-beta.11](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.10...v3.0.1-beta.11) (2020-06-08)
### [3.0.1-beta.10](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.9...v3.0.1-beta.10) (2020-06-08)
### [3.0.1-beta.9](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.8...v3.0.1-beta.9) (2020-06-07)
### [3.0.1-beta.8](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.7...v3.0.1-beta.8) (2020-06-02)
### [3.0.1-beta.7](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.6...v3.0.1-beta.7) (2020-06-02)
### Features
- add loadResource ([675d7a9](https://github.com/fjc0k/vtils/commit/675d7a94686e9bef0a3340a6d06f63d62e10c6f0))
### [3.0.1-beta.6](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.5...v3.0.1-beta.6) (2020-05-31)
### Features
- add readFile ([8704e3c](https://github.com/fjc0k/vtils/commit/8704e3c32dc87af6019b8d638f683619ef6ab8d0))
### [3.0.1-beta.5](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.4...v3.0.1-beta.5) (2020-05-30)
### Features
- add base64 ([348e8cb](https://github.com/fjc0k/vtils/commit/348e8cb3e275a7f70f79e586958c69d1b54876a4))
### [3.0.1-beta.4](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.3...v3.0.1-beta.4) (2020-05-29)
### [3.0.1-beta.3](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.2...v3.0.1-beta.3) (2020-05-29)
### [3.0.1-beta.2](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.1...v3.0.1-beta.2) (2020-05-29)
### Bug Fixes
- version ([4ee5049](https://github.com/fjc0k/vtils/commit/4ee5049dba693487ce04003e425c615d2b1a6163))
### [3.0.1-beta.1](https://github.com/fjc0k/vtils/compare/v3.0.1-beta.0...v3.0.1-beta.1) (2020-05-29)
### Features
- add isChineseIDCardNumber ([bad0b2b](https://github.com/fjc0k/vtils/commit/bad0b2b3c6bf99ae8d066177770f32b72974b3d1))
- support deno ([9a38de3](https://github.com/fjc0k/vtils/commit/9a38de33686b7f2cdbd250a6d0342c9621b4aaea))
### [3.0.1-beta.0](https://github.com/fjc0k/vtils/compare/v2.59.0...v3.0.1-beta.0) (2020-05-28)
### Features
- 初始化 v3 ([e7d5d0a](https://github.com/fjc0k/vtils/commit/e7d5d0a42d9581256386b891a7685c77a2227e48))
- 新增 dedent ([9ff1e9c](https://github.com/fjc0k/vtils/commit/9ff1e9c3419943cebdf349bbf34950e1da6a6726))
- 新增 indent ([905f8ab](https://github.com/fjc0k/vtils/commit/905f8ab2346a0ee3f33ec8fe282eccf58f0b5edf))
- 新增 wait ([a0f71cf](https://github.com/fjc0k/vtils/commit/a0f71cfa5e63b4239edb80f3c195ab5e2ca12b0c))
- 添加一些工具 ([8e9917a](https://github.com/fjc0k/vtils/commit/8e9917acd71495685b6a5f6da27f12a512c6ec2d))
| 44.401617 | 187 | 0.724782 | yue_Hant | 0.490928 |
d5aca999bbf10b456691a3a6ddebd07042b6b64d | 5,763 | md | Markdown | README.md | truthiswill/frontend | 9719d8ffbf428ccfabcacbad67a12eefe08ecc6d | [
"MIT"
] | 1 | 2020-10-10T08:09:28.000Z | 2020-10-10T08:09:28.000Z | README.md | Antoxa291/frontend | 094f9893f51c20259ffdd4c11f309949f1b385ca | [
"MIT"
] | null | null | null | README.md | Antoxa291/frontend | 094f9893f51c20259ffdd4c11f309949f1b385ca | [
"MIT"
] | 1 | 2019-06-27T10:22:45.000Z | 2019-06-27T10:22:45.000Z | [![Kottans-Frontend][icon-kottans]][kottans-frontend]
[![MIT Licensed][icon-mit]][license]
[![Ideas and useful links][icon-ideas]][ideas]
[![Awesome][icon-awesome]][awesome]
# Front-End Course
The course contains basics of front-end development:
HTML, CSS, JS, and front-end frameworks.
We plan to decrease the amount of lectures in favor of collective discussions,
team projects & collective work. And give all power & responsibility
to students.
You can use these materials for self-education as well.
### Admission
Admission for the main course was open until 13 Jan 2019 and now
is closed as the student's group is full and the course was started.
The only alternative for now - is our p2p course.
Since we would like to support ambitious students who couldn't join the main course,
we providing __peer-to-peer__ learning (hereinafter referred to as __p2p__) based on the online part
([Stage0](https://github.com/kottans/frontend/blob/master/contents.md#stage-0-self-study)) of the main course.
A p2p group has no specific limitations on the number of students and not
so fitted to strict deadlines as the main group is.
The common factor of Peer teaching is that knowledge is shared not by an
instructor or other person of authority.
It’s all about people on the same level teaching each other what they
know. __Learners Teaching Learners__.
As you could understand from the context of p2p meaning - it is a great
possibility to grow up both as a student and teacher. Especially this course,
you will learn how to correctly check the other students job.
If you have any questions you can ask us in one of our chats.
### What you will learn
1. Git, github basics, writing good commit messages
1. Linux, command line basics, network basics
1. HTML, CSS
1. JS basics
1. Build a bunch of test projects
1. Have fun together
<!-- TODO: finish it up -->
<!-- For more information take a look on [syllabus](syllabus.md) -->
### General Requirements
1. __English knowledge:__ a lot of the materials will be in English.
If you do not feel confident enough in your technical English,
take a look at [📚 Словари по фронтенду][frontend-dicts]
1. __Repository on GitHub__ to save your progress.
More about repositories in _Task 0_.
1. __Formatting:__ it's up to you but remember to make it readable.
Using [markdown][markdown] is a good idea.
1. __Reading:__ for each article you are required to read please post
the answers to the following questions in your respective repo.
Don't worry, your answers will not be graded. It's just a way to reflect
on what you have learned.
- name (at least) one thing that was new to you
- name (at least) one thing that surprised you
- name (at least) one thing you intend to use in the future
1. __Online courses:__ finish all tasks, add some reflection
about them into _README_.
1. __Videos:__ same as for the reading; watch the video —
answer three questions.
### Chats
For your comfort we have created several chats in the telegram:
1. [FE Students | Kottans](https://t.me/joinchat/DmX0JBHVkEhV1us2HdMmpA) - chat for students, where you can discuss anything related to the current course
1. [FE Questionarium | Kottans](https://t.me/joinchat/DmX0JAl-mh5W0jrWli8Ycw) - if you need a help of one of the mentors, or maybe from all of them simultaneously, you can ask it there
1. [Kottans Radio](https://t.me/radio_kottans) - our channel with usefull links and awesome articles ;)
### Do you have any questions?
Please see our [FAQ](https://github.com/kottans/frontend/blob/master/faq.md). If you have more questions - we will be happy to answer in our chats.
### Ready?
➡️ __Lets begin!__ Go forward to [Git and GitHub Intro](tasks/git-intro.md)
➡️ Read course plan in [Contents](contents.md)
---
### P.S. You should know
If you are willing to participate in the course, you need to understand that
you’ll spend a lot of time building something big together — a new way
of learning and collaborating. You’ll become part of a small family
and should prepare yourself to find new friends and to invest a lot in this
friendship (as you should in any friendship).
Final task of this course will be to split into groups and create new courses
like that (and we’ll never stop).
#### Our basic rules
* Respect each other.
* [There is no such thing as a stupid question][wiki-stupid-question].
* Each person learns with their own speed, has different background and
personality, please respect this.
* Communicating and understanding people that are different from you
can be beneficial to both parties, provided mutual respect.
* We are against any discriminations by gender, age, the color of skin,
disabilities or any other.
* We respect intellectual property - there is hard work of an author
or a group of authors behind all materials that we use.
[icon-mit]: https://img.shields.io/badge/license-MIT-blue.svg
[icon-ideas]: https://img.shields.io/badge/google--doc-ideas-ff69b4.svg
[icon-awesome]: https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg
[license]: https://github.com/Kottans/web/blob/master/LICENSE.md
[awesome]: https://github.com/sindresorhus/awesome#front-end-development
[ideas]: https://docs.google.com/spreadsheets/d/1bZJhYjK3VHOS2HmQb2Fs4aHfEBt8mp1F09j9nEEDaqE/edit#gid=818017811
[frontend-dicts]: https://github.com/web-standards-ru/dictionary
[markdown]: https://help.github.com/categories/writing-on-github/
[wiki-stupid-question]: https://en.wikipedia.org/wiki/No_such_thing_as_a_stupid_question
[icon-kottans]: https://img.shields.io/badge/%3D(%5E.%5E)%3D-frontend-yellow.svg
[kottans-frontend]: https://github.com/kottans/frontend
| 40.020833 | 184 | 0.76245 | eng_Latn | 0.995949 |
d5ad60bb1d2353231ae5851d1f044273ca61f20a | 2,915 | md | Markdown | README.md | eliasp/provisioning | 8db31a61e76c0af54e34f33d64c0531ad379d292 | [
"MIT"
] | null | null | null | README.md | eliasp/provisioning | 8db31a61e76c0af54e34f33d64c0531ad379d292 | [
"MIT"
] | null | null | null | README.md | eliasp/provisioning | 8db31a61e76c0af54e34f33d64c0531ad379d292 | [
"MIT"
] | null | null | null | # Kubernetes cluster setup automation
> This is part of the Hobby Kube project. Functionality of the modules is described in the [guide](https://github.com/hobby-kube/guide).
Deploy a secure Kubernetes cluster on [Hetzner Cloud](https://www.hetzner.com/cloud), [Scaleway](https://www.scaleway.com/) or [DigitalOcean](https://www.digitalocean.com/) using [Terraform](https://www.terraform.io/).
## Setup
### Requirements
The following packages are required to be installed locally:
```sh
brew install terraform kubectl jq wireguard-tools
```
Modules are using ssh-agent for remote operations. Add your SSH key with `ssh-add -K` if Terraform repeatedly fails to connect to remote hosts.
### Configuration
**Important:** Modify only [main.tf](main.tf) in project root, comment or uncomment sections as needed. All variables in [variables.tf](variables.tf) can be set
either directly or from environment variable.
Export the following environment variables depending on the modules you're using:
#### Set number of hosts (nodes)
```sh
export TF_VAR_node_count=3
```
#### Using Hetzner Cloud as provider
```sh
export TF_VAR_hcloud_token=<token>
export TF_VAR_hcloud_ssh_keys=<keys>
# e.g.
# export TF_VAR_hcloud_ssh_keys='["My Desktop", "My Laptop"]'
# These are the names you give your key after uploading it to the provider.
```
#### Using Scaleway as provider
```sh
export TF_VAR_scaleway_organization=<access_key>
export TF_VAR_scaleway_token=<token>
```
#### Using DigitalOcean as provider
```sh
export TF_VAR_digitalocean_token=<token>
export TF_VAR_digitalocean_ssh_keys=<keys>
# e.g.
# export TF_VAR_digitalocean_ssh_keys='["1234567", "2468013"]'
```
You can get your SSH keys' ID using [the API](https://developers.digitalocean.com/documentation/v2/#list-all-keys).
#### Using Cloudflare for DNS entries
```sh
export TF_VAR_domain=<domain> # e.g. example.org
export TF_VAR_cloudflare_email=<email>
export TF_VAR_cloudflare_token=<token>
```
#### Using Amazon Route 53 for DNS entries
```sh
export TF_VAR_domain=<domain> # e.g. example.org shall be already added to hosted zones.
export TF_VAR_aws_access_key=<ACCESS_KEY>
export TF_VAR_aws_secret_key=<SECRET_KEY>
export TF_VAR_aws_region=<region> # e.g. eu-west-1
```
#### Install additional APT packages
Each provider takes an optional variable to install further packages during provisioning:
```
module "provider" {
# ...
apt_packages = ["ceph-common", "nfs-common"]
}
```
### Execute
From the root of this project...
```sh
# fetch the required modules
$ terraform init
# see what `terraform apply` will do
$ terraform plan
# execute it
$ terraform apply
```
## Using modules independently
Modules in this repository can be used independently:
```hcl
module "kubernetes" {
source = "github.com/hobby-kube/provisioning/service/kubernetes"
}
```
After adding this to your plan, run `terraform get` to fetch the module.
| 25.570175 | 218 | 0.750257 | eng_Latn | 0.871544 |
d5af191934034c6735f8a952a8d6979d0213915f | 3,215 | md | Markdown | stone/daily/love.md | sanyueyuxincao/stone | 8300d41b6c948248dfdc389fa988edf653a0d0ad | [
"MIT"
] | 1 | 2017-01-08T02:57:10.000Z | 2017-01-08T02:57:10.000Z | stone/daily/love.md | sanyueyuxincao/stone | 8300d41b6c948248dfdc389fa988edf653a0d0ad | [
"MIT"
] | null | null | null | stone/daily/love.md | sanyueyuxincao/stone | 8300d41b6c948248dfdc389fa988edf653a0d0ad | [
"MIT"
] | null | null | null | 不知道，从何写起，好久都没用信的形式，和你交流了。你要离开的时候，我哭了，哭的很无助，像个孩子似的，你说，“哭，给老子哭，你知道我为你流过多少次泪嘛”。相处五年，我知道，你为我流过很多的泪，怎会不知道，我也伤心难过过很多次，我或与真不容易流泪，上了高中后，我基本就没哭过了，高考发挥那么差，我也想哭，但是就是哭不出来，只是心里闷的很。很多时候，我也想哭，我很羡慕你，想哭就能哭出来，我有时很伤心，但是就是哭不出来，十一前后，我知道，我们的感情出了问题了，你说要分手，我很懵，15年7月6号，我坐上第一班，武汉到深圳的高铁，在路上，我认定你是我的老婆，是我来深圳奋斗的一切，高铁站外，你拿着饮料等我，我开心坏了，深圳，陌生的城市啊，前途我不知道在哪，以后我也不知道会怎样，但是，我知道你在我身边，我不怕。
究竟，什么是爱，什么是好男友，我对你的是不是爱，我是不是一个好男友，我也不知道。每个人都有自己的看法，知乎上，有人秀男友，微博上，有人发我的好男友。来深圳后，我们都忙着适应自己的工作，第一份工作，第一次进入陌生的环境。不如意，不如意，你过的很不开心，领导让你打杂，工资不高，学不到东西，前途暗淡，有次，你给我打电话，诉说着不开心，我怎么做的呢。。。开导你嘛，领导锻炼新人嘛，刚开始工作，都是这样的，你们的行业还是很有前途的，你们公司还是大的上市公司，一切都将变好的。。。如果这样说，这样做了，你应该还在兆驰，做着你可能慢慢适应了的工作，或与喜欢或与不喜欢，根据现在的结果看，我没这样做，开始还是缓和的劝你，另寻出路，看看能不能转岗，看看能不能晚间时间自学点什么，这些尝试，当然是痛苦的，当然是不愉快的，中间多次的争吵，多次你的哭泣，就这样算在我的身上。
我的心里很乱，有很多话想说，没什么逻辑，毕竟我们，相处5年，我想吐吐槽，想说些，窝火的话。我比较讨厌，你将我们的事情，说给你们寝室的听，我做的在他们眼里不值一文，都是男友该做的，你哭，所有的错，都在我，嗯嗯，给你分析我们可能真的比较适合分手，嗯嗯，从你的角度，给你动力让你不再惧怕我们的分开，毕竟大家都是劝和不劝离的嘛，这样肯定要不是损友，要不就是挚友了，你们关系这么好，当然是挚友了。我有一句，妈卖批，不知当不当讲，别人的事，不要参合，好不好，他们了解我嘛，了解我们嘛。心累，写的心累，我可能是个人渣吧，我可能就对自己好吧，我可能总是自以为是吧。我不高傲，我特么，真的不止一次，承认自己是个失败者了，我敢于面对自己的失败，我敢于承认自己的不足，我不逃避，我敢于面对自己的内心，我一直觉得，人的成长来源于记忆，所以，在我有限的记忆里，我愿意不断从苦难的记忆中，获取人生的经验，学习IC是一个错误的，我愿意承认，我是一个傻逼，当时没好好查资料了解集成电路行业，从而导致3年的时间浪费。爱情，到底是个什么，男友怎样才是好，可能我们之间的问题出在这吧，可能我们的答案不一样，才导致现在的局面。哎，这个问题真的好复杂，我好像给不出具体的答案。说说我眼里，我们的爱情吧。
历史课上，我们因为学号的原因坐在一起上课，我侧面看着你，发现你很漂亮，你好美丽。我开始期待上历史课了，我期待着每周三上午的历史课，为此，我认真打理自己，开始照镜子了（我之前很少照镜子），开始剪头发注意自己的发型了，开始注意自己的衣着了，一次历史课上，我问你要了扣扣号，晚上的时候，我翻着你的空间看，翻着你的照片看，有张你和玩具熊的照片很美，有几张高中毕业在家的照片，我看了一遍又一遍（第一次做我们视频的时候的那几张）。寒假，你主动发消息给我，我知道你失恋了（不知道算不算），你说你很伤心，哭了好久好久，聊天中，我觉得你是很重感情的人，我更加喜欢你了，我们寒假，每天都聊天，我答应带你去看埃菲尔铁塔，我定午夜12点的闹钟，给你发节日快乐，我希望你做我女朋友。后来我们去了仙海湖，后来我们在一起了。我们的脚印，在后山，在龙山，在梧桐大道，在101广场，在排球场，在图书馆树下，在露天电影院，在新区，在老区，在西科大的每一个角落，晚上路黑，我有时看不清楚路，你牵着我的手，我们一级一级的下楼梯。在我表白的地方，你给我一个奖励，打开你的手机定时器，让我快点说，不然就不算了，那晚的月亮好圆，旁边还有虫儿，叽叽喳喳，我心跳好快，宝贝儿，很美，我一把抱过你，我们吻在了一起。我们开始写情书了，我字不好看，先写一遍，然后在抄一遍，我在自习室二楼里，认真的抄写着，我做最后一排，阳光好耀眼，我感觉很温暖。如果，我们一直都在大一，一直都在上大学，一直持续着这样的幸福多好啊，哦，我想起来了，我在九州湖，和你说过：要是世界上，只有我们两个人，那该多好啊，你笑着说我傻逼。那时，我们的爱很纯真，很美好。
时间飞快，该来的会来，以后的出路，以后的工作，好多以后，我们需要考虑了，我去了卓越班，我去了张克非的团队，我去了芯盛，我在不停的寻找着答案，要是我们能无忧无虑，要是我们一直停留在美好的少男少女的岁月里，那该多好，我劝你去卓越班，这里我们也有小矛盾，你是很有主见的女孩，你是较真的女孩。我也是有主见的男孩，有时也是比较死板的男孩。
大学4年，朝夕相处，这里太多的回忆，太多的美好，我们骑单车，我们学游泳，我们出去旅行（都是小地方），我们看电影，我们吃牛排吃自助，我们一起太多太多，要记录，真的是一本小说。彭娟他们可能比我们谈的时间要久，但是我们在一起的时间，是他们的3倍还多吧。
你觉得大街上，随便拉一个人，都比我做的好，我真的很伤心，我敢于承认自己的失败（我不止一次觉得自己一无所有，现在就是）。真的这样嘛，你男人好不好，需要别人来告诉你嘛。
女生希望的纯真恋爱，我们也有过，我是一个爱好出去玩的人，不是一个宅的人，多少男生宅着玩游戏，多少男生不愿运动，我高中毕业后，就不玩游戏了，大一的时候，就报名健身了（去的次数，其实还是可以的，毕竟刚去胸推40kg，后来可以70kg），来深圳后，我们很少出去玩了，真的是因为阶段不同了吧（我也有错，忽视了我们爱情需要的养分），有些道理我真的是这次才明白，真的是第一次，这么清楚的明白，来深圳后，我一门心思的，为我们的未来考虑，所做的你也都知道，其实我们也可以过的很简单的，没必要这么累，你就在兆驰安心的呆着，我就在硅格呆着，周末玩玩深圳大小景点，小长假，去去广州，东莞，清远，惠州，珠海，多么惬意，多么类似大学绵阳周边游。但是，这样做，未来在哪里啊，以后怎么办呢。
我不知道多少男友，可以做到我这样，不知道彭娟男友可不可以，不知道你们宿舍的其他男友，可不可以，为以后长远考虑，为自己女友考虑未来，长大了工作了，不应该这样嘛，我把我们的爱，转换成周末的自学，转换成，一人去图书管的孤独与压力，转换成，无视陌路的恐惧。
每个阶段，爱的形式侧重点，可能真的不同吧，有一点确实始终如一的，我的心里一直都有你，我一直都真心对你，我从未做过对不起你的事，从未犯过原则性的错误，我是这样理解的。但是我们的爱情，我没有细心呵护好，我也真的对不起。我也懂得了，怎样更好的保护它，懂得了好多，你能不能给我个机会呢。没有你陪伴的深圳，我不知道前进的动力，我不知道未来在哪里，我觉得一切都好陌生，夜晚时分，一个人敲打着键盘，好孤单。我最爱看的一部爱情电影，叫做东邪西毒，最感概，张曼玉和张国荣饰演的爱情故事，最向往，洪气的率真自我，我一直都爱着你，方式我觉得需要俩人调节，毕竟我爱的是你，你开心和快乐才是重要的，其他的可能没这么重要，我不想最后和张国荣所代表的角色一样，放不下脸面和高傲，赌气赌时间，恪守沙漠一隅，抱憾终身。缺点是可以改的，改不了的是弱点，我们的事情，逃避不了，我认识到我的问题了，我也下定决心改了，只此一次机会，若还是不行，我无悔放手。 | 169.210526 | 692 | 0.855988 | zho_Hans | 0.467968 |
d5af242a2fa9f0df3137ae68cefaa5b45ab87a03 | 55 | md | Markdown | content/blog/iceland/index.md | josepmartins/xavi-galindo-portfolio | 41464dce8d202c26c65cf8ad76fe8e7ff2b86561 | [
"MIT"
] | null | null | null | content/blog/iceland/index.md | josepmartins/xavi-galindo-portfolio | 41464dce8d202c26c65cf8ad76fe8e7ff2b86561 | [
"MIT"
] | null | null | null | content/blog/iceland/index.md | josepmartins/xavi-galindo-portfolio | 41464dce8d202c26c65cf8ad76fe8e7ff2b86561 | [
"MIT"
] | null | null | null | ---
title: Iceland
date: "2015-05-01T22:12:03.284Z"
--- | 13.75 | 32 | 0.636364 | eng_Latn | 0.132552 |
d5af9b3b62f231438891cf858c430673a83b856c | 262 | md | Markdown | README.md | Rodic/PorterStemmer | b8ef729e452e715c240a7ad4b17919f6c1a4cb2b | [
"Apache-2.0"
] | null | null | null | README.md | Rodic/PorterStemmer | b8ef729e452e715c240a7ad4b17919f6c1a4cb2b | [
"Apache-2.0"
] | null | null | null | README.md | Rodic/PorterStemmer | b8ef729e452e715c240a7ad4b17919f6c1a4cb2b | [
"Apache-2.0"
] | null | null | null | # Scala implementation of the Porter's Stemmer Algorithm
Algo is implemented in functional style (lists, pattern matching and minimal usage of regex)
Full description of the algo can be found [here](http://snowball.tartarus.org/algorithms/porter/stemmer.html) | 52.4 | 109 | 0.805344 | eng_Latn | 0.962669 |
d5afc1d2b51eeb05fd1013b5959cacfc14870fd3 | 1,801 | md | Markdown | easy/18-easy-tuple-length/README.md | Determination-cheng/ts-challenges | 615ba2d1ff00d0c5934e9a353b7d0b4f9c785e03 | [
"MIT"
] | 3 | 2022-01-17T13:14:18.000Z | 2022-02-02T11:10:40.000Z | easy/18-easy-tuple-length/README.md | Determination-cheng/ts-challenges | 615ba2d1ff00d0c5934e9a353b7d0b4f9c785e03 | [
"MIT"
] | 38 | 2022-01-01T11:42:08.000Z | 2022-01-16T13:17:23.000Z | easy/18-easy-tuple-length/README.md | Determination-cheng/ts-challenges | 615ba2d1ff00d0c5934e9a353b7d0b4f9c785e03 | [
"MIT"
] | 1 | 2022-03-26T14:01:42.000Z | 2022-03-26T14:01:42.000Z | <!--info-header-start--><h1>Length of Tuple <img src="https://img.shields.io/badge/-easy-7aad0c" alt="easy"/> <img src="https://img.shields.io/badge/-%23tuple-999" alt="#tuple"/></h1><blockquote><p>by sinoon <a href="https://github.com/sinoon" target="_blank">@sinoon</a></p></blockquote><p><a href="https://tsch.js.org/18/play" target="_blank"><img src="https://img.shields.io/badge/-Take%20the%20Challenge-3178c6?logo=typescript&logoColor=white" alt="Take the Challenge"/></a> <a href="./README.zh-CN.md" target="_blank"><img src="https://img.shields.io/badge/-%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87-gray" alt="简体中文"/></a> <a href="./README.ja.md" target="_blank"><img src="https://img.shields.io/badge/-%E6%97%A5%E6%9C%AC%E8%AA%9E-gray" alt="日本語"/></a> <a href="./README.ko.md" target="_blank"><img src="https://img.shields.io/badge/-%ED%95%9C%EA%B5%AD%EC%96%B4-gray" alt="한국어"/></a> </p><!--info-header-end-->
For given a tuple, you need create a generic `Length`, pick the length of the tuple
For example
```ts
type tesla = ['tesla', 'model 3', 'model X', 'model Y']
type spaceX = ['FALCON 9', 'FALCON HEAVY', 'DRAGON', 'STARSHIP', 'HUMAN SPACEFLIGHT']
type teslaLength = Length<tesla> // expected 4
type spaceXLength = Length<spaceX> // expected 5
```
<!--info-footer-start--><br><a href="../../README.md" target="_blank"><img src="https://img.shields.io/badge/-Back-grey" alt="Back"/></a> <a href="https://tsch.js.org/18/answer" target="_blank"><img src="https://img.shields.io/badge/-Share%20your%20Solutions-teal" alt="Share your Solutions"/></a> <a href="https://tsch.js.org/18/solutions" target="_blank"><img src="https://img.shields.io/badge/-Check%20out%20Solutions-de5a77?logo=awesome-lists&logoColor=white" alt="Check out Solutions"/></a> <!--info-footer-end-->
| 112.5625 | 931 | 0.679622 | yue_Hant | 0.535633 |
d5b031703ac8d319a19cce9915a3f8b7b7a15ea1 | 835 | md | Markdown | _posts/2003-04-20-my-brother-zac.md | kerim/keywords | b16bf75bd1e6347b57e3e3ca62012ec198c110f8 | [
"MIT-0",
"MIT"
] | 1 | 2017-08-10T12:37:13.000Z | 2017-08-10T12:37:13.000Z | _posts/2003-04-20-my-brother-zac.md | kerim/keywords | b16bf75bd1e6347b57e3e3ca62012ec198c110f8 | [
"MIT-0",
"MIT"
] | null | null | null | _posts/2003-04-20-my-brother-zac.md | kerim/keywords | b16bf75bd1e6347b57e3e3ca62012ec198c110f8 | [
"MIT-0",
"MIT"
] | null | null | null | ---
title: My brother Zac
author: Kerim
layout: post
permalink: /archives/2003/04/20/my-brother-zac/
categories:
- Old Blog Import
---
If you haven’t read <a href="http://www.guardian.co.uk/Print/0,3858,4650223,00.html" onclick="_gaq.push(['_trackEvent', 'outbound-article', 'http://www.guardian.co.uk/Print/0,3858,4650223,00.html', 'this excerpt']);" >this excerpt</a> of Abd Samad Moussaoui’s book about his brother yet, you should, it is well written and very revealing:
> Zacarias Moussaoui is the only person to be charged in the US in connection with the September 11 attacks. He has been dubbed the 20th hijacker. Here his brother Abd Samad Moussaoui describes a childhood beset by racism in France and the indoctrination he believes his brother received in London, which drove him into the arms of al-Qaida
| 55.666667 | 350 | 0.758084 | eng_Latn | 0.981546 |
d5b08d827412452c069c68c3564631c3544db9d8 | 9,236 | md | Markdown | docs/README.md | ChrisVilches/Collection-Sync | a3d87a52e62db37f2d5bf58ebfd473099e4000f3 | [
"MIT"
] | 1 | 2021-09-09T01:27:20.000Z | 2021-09-09T01:27:20.000Z | docs/README.md | ChrisVilches/Collection-Sync | a3d87a52e62db37f2d5bf58ebfd473099e4000f3 | [
"MIT"
] | 3 | 2021-09-10T16:14:11.000Z | 2022-01-30T23:53:57.000Z | docs/README.md | ChrisVilches/Collection-Sync | a3d87a52e62db37f2d5bf58ebfd473099e4000f3 | [
"MIT"
] | null | null | null | collection-sync / [Exports](modules.md)
[](https://badge.fury.io/js/collection-sync)
# Collection Sync
Javascript Library for bi-directional database synchronization between multiple devices or servers. Customizable and completely database agnostic.
See [Documentation](/docs/modules.md).
## Use cases
Some examples where this mechanism would be useful:
* Memo app that works offline, and updates remote database when it goes online.
* Multiplatform app (desktop, mobile, web app) which works offline (in mobile and desktop), and updates remote database when going online. When using the app in a different device, the new data is downloaded, making all devices up to date.
## Install
```bash
npm install collection-sync
```
## How to use
Make sure your project is using TypeScript.
Import dependencies:
```ts
import { SyncItem } from "collection-sync";
import { SynchronizableCollection } from "collection-sync";
import { CollectionSyncMetadata } from "collection-sync";
import { SyncOperation, SyncConflictStrategy } from "collection-sync";
import DocId from "collection-sync/dist/types/DocId";
```
Create a class that extends [SyncItem](/docs/classes/SyncItem.md), and populates its data starting from a document from your database. You must customize the way to extract the ID and date it was last updated.
If we use Mongo's `_id`, when synchronizing from one database to another it might be impossible to set it, since some database engines auto generate the `_id` value, hence you must choose how to identify documents using a custom way.
The same applies for `updatedAt`. If your database engine automatically sets `updatedAt` when saving a record, then you'll need to have a custom attribute you can set freely.
Synchronization will fail if you try to set the ID and/or `updatedAt` but your database refuses to leave you set a specific value.
```ts
class CustomItem extends SyncItem {
constructor(doc: any /* e.g. Mongo Document */){
super(doc.documentId, doc, doc.updatedAt);
}
}
```
Then, create a class that extends [SynchronizableCollection](/docs/classes/SynchronizableCollection.md) and implement its abstract methods:
```ts
class LocalCollection extends SynchronizableCollection {
countAll(): number | Promise<number> {
// Count collection documents.
return 100;
}
async initialize(): Promise<void> {
// Executes async logic to initialize collection or datastore (open file, create database connection, etc).
}
findByIds(ids: DocId[]): SyncItem[] | Promise<SyncItem[]> {
const docs = [
{ /* Doc from DB */ },
{ /* Doc from DB */ },
{ /* Doc from DB */ }
];
return docs.map(d => new CustomItem(d)); // Convert to CustomItem.
}
syncBatch(items: SyncItem[]): SyncItem[] | Promise<SyncItem[]> {
// Implement batch upsert/delete of records.
}
itemsNewerThan(date: Date | undefined, limit: number): SyncItem[] | Promise<SyncItem[]> {
// Returns a list of items that have updatedAt greater than argument provided.
// The list MUST be ordered by updatedAt ASC, otherwise an exception will be
// thrown (no syncing will be executed).
}
latestUpdatedItem(): SyncItem | Promise<SyncItem | undefined> | undefined {
// Gets the highest updateAt date in the collection.
}
}
```
Install `npm install --save @types/node` if you get errors related to missing Node types.
You can also implement several lifecycle hooks for granular control over syncing. See [which methods can be overriden from SynchronizableCollection class](/docs/classes/SynchronizableCollection.md) for details.
All methods allow the use of `async/await` if needed.
Next, implement a class that communicates with the remote collection (datastore).
In cases where the local collection is a database in a mobile app, you don't want to connect directly to a remote database, but instead you'd have to prepare a backend API to connect to, which provides the operations needed (syncBatch, findByIds, etc). This class must work as a communication layer between the client and that API.
If both collections are inside a private/secure network, then connecting directly to another database would be fine.
```ts
class RemoteCollection extends SynchronizableCollection {
countAll(): number | Promise<number> {
// Execute some API call to
// https://your_server.com/api/users/count_all
// and return its value here.
}
async initialize(): Promise<void> {
// ...
}
findByIds(ids: DocId[]): SyncItem[] | Promise<SyncItem[]> {
// ...
}
syncBatch(items: SyncItem[]): SyncItem[] | Promise<SyncItem[]> {
// ...
}
itemsNewerThan(date: Date | undefined, limit: number): SyncItem[] | Promise<SyncItem[]> {
// ...
}
latestUpdatedItem(): SyncItem | Promise<SyncItem | undefined> | undefined {
// ...
}
}
```
Finally, implement a mechanism to store and retrieve two dates (last fetch and post dates).
A persistent storage is recommended.
```ts
class MySyncMetadata extends CollectionSyncMetadata{
setLastFetchAt(d: Date): void {
// ...
}
setLastPostAt(d: Date): void {
// ...
}
getLastFetchAt(): Date | Promise<Date | undefined> | undefined {
// ...
}
getLastPostAt(): Date | Promise<Date | undefined> | undefined {
// ...
}
async initialize(): Promise<void> {
// ...
}
}
```
Note that both classes have a `initialize` method. Some storage mechanisms require to open a file, create a DB connection, or do some asynchronous logic before beginning to use them. You can put that logic there.
In this example, however, we'll import and use [BasicSyncMetadata](/docs/classes/BasicSyncMetadata.md), which provides an in-memory storage for synchronization metadata. This is the simplest way to get started.
Add a new import to the top of the file:
```ts
import { BasicSyncMetadata } from "collection-sync";
```
Then, create two synchronization metadata managers:
```ts
const syncMetadataSlave: CollectionSyncMetadata = new BasicSyncMetadata();
const syncMetadataMaster: CollectionSyncMetadata = new BasicSyncMetadata();
```
Now, create two collections:
```ts
const collectionSlave = new LocalCollection(syncMetadataSlave);
const collectionMaster = new RemoteCollection(syncMetadataMaster);
```
Since only the slave keeps track of sync metadata, the master doesn't need a `CollectionSyncMetadata` object. However, since all collections could potentially have a master, it is a required argument.
Attach the parent as master:
```ts
collectionSlave.parent = collectionMaster;
```
Note that both `collectionSlave` and `collectionMaster` simply model how your data stores are arranged. The machine where this code is running doesn't actually need to host `collectionMaster`'s data, but since the way to communicate with it was implemented (i.e. `RemoteCollection`'s methods for API communication), we still can modify its data.
If we assume that some data exists in the datastore `collectionMaster` is pointing at, and the database pointed by `collectionSlave` is empty, then we can perform a fetch to update `collectionSlave`:
```ts
collectionSlave.sync(SyncOperation.Fetch, 100, { conflictStrategy: SyncConflictStrategy.Force });
```
See [sync](/docs/classes/SynchronizableCollection.md#sync) method documentation.
See also [other specifications](sync_specifications.md) related to `sync`.
When syncing, conflicts might occur, and there are a few strategies to overcome them. A conflict occurs when trying to update a record using a record with an older `updatedAt`. In general, when synchronizing data collections, older data should be overwritten by newer data, but sometimes this is not the case, and that's when a conflict is generated. See [SyncConflictStrategy](/docs/enums/SyncConflictStrategy.md) for details.
## Another example
Note: Omitting some steps from the previous example.
```ts
const android = new LocalCollection(new MySyncMetadata());
const pc = new LocalCollection(new MySyncMetadata());
const backend = new LocalCollection(new MySyncMetadata());
android.parent = backend;
pc.parent = backend;
// Data that only exists in Android devide is being pushed...
android.sync(SyncOperation.Post, 1000);
// PC device now has data that previously only the Android device had.
pc.sync(SyncOperation.Fetch, 1000);
```
In practice, you'd want to make your slave collection perform both post and fetch operations during a full sync.
When a conflict is encountered, a suggestion is to ask the user to manually select how to solve them, and then trigger a new synchronization but using a different configuration (e.g. forcing data from the master collection to overwrite slave data).
## Current limitations and future work
### Locking mechanism
Locking mechanism (to prevent multiple devices from synchronizing at the same time) must be implemented by the user. The addition of `acquireLock` and `releaseLock` abstract methods to 'SynchronizableCollection' or `Collection` have been proposed.
### Using it with Vanilla Javascript
Use with vanilla Javascript is not tested. It may not be convenient for development. Typescript is recommended.
## Develop
```bash
npm run test:watch
```
| 39.810345 | 427 | 0.747943 | eng_Latn | 0.970849 |
d5b25a2a73faae765bb7df5bee019e5c9701c4ea | 6,797 | md | Markdown | README.md | blacksmith-net/schema_plus_indexes | 8af6025cd971afae769d34f31c31f520d8cf7d30 | [
"MIT"
] | 8 | 2015-03-11T06:33:12.000Z | 2020-04-08T20:53:19.000Z | README.md | blacksmith-net/schema_plus_indexes | 8af6025cd971afae769d34f31c31f520d8cf7d30 | [
"MIT"
] | 16 | 2015-01-26T15:12:24.000Z | 2018-12-05T19:52:55.000Z | README.md | blacksmith-net/schema_plus_indexes | 8af6025cd971afae769d34f31c31f520d8cf7d30 | [
"MIT"
] | 23 | 2015-01-26T15:01:59.000Z | 2021-01-14T17:50:36.000Z | [](http://badge.fury.io/rb/schema_plus_indexes)
[](http://travis-ci.org/SchemaPlus/schema_plus_indexes)
[](https://coveralls.io/r/SchemaPlus/schema_plus_indexes)
# SchemaPlus::Indexes
SchemaPlus::Indexes adds various convenient capabilities to `ActiveRecord`'s index handling.
SchemaPlus::Indexes is part of the [SchemaPlus](https://github.com/SchemaPlus/) family of Ruby on Rails extension gems.
## Installation
<!-- SCHEMA_DEV: TEMPLATE INSTALLATION - begin -->
<!-- These lines are auto-inserted from a schema_dev template -->
As usual:
```ruby
gem "schema_plus_indexes" # in a Gemfile
gem.add_dependency "schema_plus_indexes" # in a .gemspec
```
<!-- SCHEMA_DEV: TEMPLATE INSTALLATION - end -->
## Features
### Migrations:
#### Shorthand to define a column with an index:
```ruby
t.string :role, index: true # shorthand for index: {}
```
#### Shorthand to define a column with a unique index:
```ruby
t.string :product_code, index: :unique # shorthand for index: { unique: true }
```
#### Create multi-column indexes as part of column definition
Adds an option to include other columns in the index:
```ruby
t.string :first_name
t.string :last_name, index: { with: :first_name }
t.string :country_code
t.string :area_code
t.string :local_number, index: { with: [:country_code, :area_code] }
```
#### Create indexes with `add_column`, `change_table`
ActiveRecord supports the `index:` option to column definitions when creating table. SchemaPlus::Indexes extends that to work also with `add_column` and in `change_table`
```ruby
add_column "tablename", "columnname", index: { ... }
change_table :tablename do |t|
t.integer :column, index: true
end
```
These of course accept the shorthands and `with:` option described above.
#### Remove index :if_exists
```ruby
remove_index "tablename", "columnname", if_exists: true
```
### Models
SchemaPlus::Indexes lets you easily get the indexes of a model:
```ruby
Model.indexes # shorthand for `connection.indexes(Model.table_name)`
```
The value gets cached until the next time `Model.reset_column_information` is called.
### Other things...
* Provides consistent behavior regarding attempted duplicate index
creation: Ignore and log a warning. Different versions of Rails with
different db adapters otherwise behave inconsistently: some ignore the
attempt, some raise an error.
* In the schema dump `schema.rb`, index definitions are included within the
`create_table` statements rather than added afterwards
* When using SQLite3, makes sure that the definitions returned by
`connection.indexes` properly include the column orders (`:asc` or `:desc`)
* For the `ActiveRecord::ConnectionAdapters::IndexDefinition` class (the object that's returned by `connection.indexes`), SchemaPlus::Indexes:
* Provides an `==` operator to compare if two objects refer to an equivalent index
* Allows calling `new` with a signature that matches add_index: `IndexDefinition.new(table_name, column_names, options)`
* Fleshes out the `:orders` attribute, listing `:asc` for a column instead of leaving it undefined.
* Prevents errors from a down :change migration attempting to remove an index that wasn't previously added (this can arise, e.g. with auto-indexing plugins).
## Compatibility
schema_plus_indexes is tested on
<!-- SCHEMA_DEV: MATRIX - begin -->
<!-- These lines are auto-generated by schema_dev based on schema_dev.yml -->
* ruby **2.3.1** with activerecord **4.2**, using **mysql2**, **sqlite3** or **postgresql**
* ruby **2.3.1** with activerecord **5.0**, using **mysql2**, **sqlite3** or **postgresql**
* ruby **2.3.1** with activerecord **5.1**, using **mysql2**, **sqlite3** or **postgresql**
* ruby **2.3.1** with activerecord **5.2**, using **mysql2**, **sqlite3** or **postgresql**
<!-- SCHEMA_DEV: MATRIX - end -->
## Release Notes
### v0.3.1
* Support AR 5.2. Thanks to [@jeremyyap](https://github.com/jeremyyap)
### v0.3.0
* Supports AR 5.1. Thanks to [@iagopiimenta](https://github.com/iagopiimenta)
### v0.2.4
* Supports AR 5.0. Thanks to [@myabc](https://github.com/myabc)
### v0.2.3
* Missing require
### v0.2.2
* Explicit gem dependencies
### v0.2.1
* Upgrade to schema_plus_core 1.0 and conform
### v0.2.0
* Prevent down :change migrations from failing due to trying to remove non-existent indexes
### v0.1.0
* Initial release, extracted from schema_plus 1.x
## Development & Testing
Are you interested in contributing to schema_plus_indexes? Thanks! Please follow
the standard protocol: fork, feature branch, develop, push, and issue pull request.
Some things to know about to help you develop and test:
<!-- SCHEMA_DEV: TEMPLATE USES SCHEMA_DEV - begin -->
<!-- These lines are auto-inserted from a schema_dev template -->
* **schema_dev**: SchemaPlus::Indexes uses [schema_dev](https://github.com/SchemaPlus/schema_dev) to
facilitate running rspec tests on the matrix of ruby, activerecord, and database
versions that the gem supports, both locally and on
[travis-ci](http://travis-ci.org/SchemaPlus/schema_plus_indexes)
To to run rspec locally on the full matrix, do:
$ schema_dev bundle install
$ schema_dev rspec
You can also run on just one configuration at a time; For info, see `schema_dev --help` or the [schema_dev](https://github.com/SchemaPlus/schema_dev) README.
The matrix of configurations is specified in `schema_dev.yml` in
the project root.
<!-- SCHEMA_DEV: TEMPLATE USES SCHEMA_DEV - end -->
<!-- SCHEMA_DEV: TEMPLATE USES SCHEMA_PLUS_CORE - begin -->
<!-- These lines are auto-inserted from a schema_dev template -->
* **schema_plus_core**: SchemaPlus::Indexes uses the SchemaPlus::Core API that
provides middleware callback stacks to make it easy to extend
ActiveRecord's behavior. If that API is missing something you need for
your contribution, please head over to
[schema_plus_core](https://github.com/SchemaPlus/schema_plus_core) and open
an issue or pull request.
<!-- SCHEMA_DEV: TEMPLATE USES SCHEMA_PLUS_CORE - end -->
<!-- SCHEMA_DEV: TEMPLATE USES SCHEMA_MONKEY - begin -->
<!-- These lines are auto-inserted from a schema_dev template -->
* **schema_monkey**: SchemaPlus::Indexes is implemented as a
[schema_monkey](https://github.com/SchemaPlus/schema_monkey) client,
using [schema_monkey](https://github.com/SchemaPlus/schema_monkey)'s
convention-based protocols for extending ActiveRecord and using middleware stacks.
<!-- SCHEMA_DEV: TEMPLATE USES SCHEMA_MONKEY - end -->
| 35.036082 | 171 | 0.729734 | eng_Latn | 0.919771 |
d5b30cc7dedf9b43e50807d1a9afbf38aec8c2d4 | 130 | md | Markdown | README.md | trevalkov/pico-sound-synth | 5886f28e20add03e975f637e8558a3387191067f | [
"MIT"
] | null | null | null | README.md | trevalkov/pico-sound-synth | 5886f28e20add03e975f637e8558a3387191067f | [
"MIT"
] | null | null | null | README.md | trevalkov/pico-sound-synth | 5886f28e20add03e975f637e8558a3387191067f | [
"MIT"
] | null | null | null | # pico-ks-synt
Synthesis of wave tables in embedded systems using the Karplus-Strong algorithm to simulate plucked strings sounds
| 43.333333 | 114 | 0.830769 | eng_Latn | 0.987833 |
d5b38dea512d9aa790b9d6cb05e824b056fd2dcd | 2,055 | md | Markdown | docs/api/store/README.md | 7atp/core | 023c71276613481eec4dcd935fe29b4d8474ca69 | [
"MIT"
] | null | null | null | docs/api/store/README.md | 7atp/core | 023c71276613481eec4dcd935fe29b4d8474ca69 | [
"MIT"
] | null | null | null | docs/api/store/README.md | 7atp/core | 023c71276613481eec4dcd935fe29b4d8474ca69 | [
"MIT"
] | null | null | null | ---
sidebarDepth: 2
---
# Structure of Vuex Store
VueWpJson plugin creates few VueX store modules to store a fetched data.
## wp_config
Simple module which stores config provided by user while registering plugin/Nuxt module. There we inject whole **config object** under "config" key
Example value:
```js
config: {
lang: 'en',
url: 'https://wp.mybackend.com/',
menus: ["info", "contact"]
}
```
Creating this module was essential to make it compatibile with Nuxt.
## wp_lang
There we store website's language under "lang" key. In future, this module will be deleted because we store same data in wp_config
## wp_layouts
If we provide Vuex Store as third argument to registerPlugin - there will be stored under keys post/page:
- In case of Nuxt - "AlternativePost" or "AlternativePage" string
- In case of Vue - Custom Page/Post view component
Creating this module was essential to make it compatibile with Nuxt.
## wp_media
There we have whole response from /media Wordpress' endpoint. It will be used in next versions to provide new functionalities.
Fetched after plugin's registration.
## wp_menu
There we have our menus if we provided any in Config and on our Wordpress we have installed [this plugin](https://wordpress.org/plugins/wp-rest-api-v2-menus/)
We also provide menu component which is placed in **components/Base/BaseMenu.vue**.
It can generate an infinite __ul > li > router-link or a__ structure based on **slug** sent as props. Component will search for slug in VueX store and do the job.
Fetched after plugin's registration.
## wp_meta
Here we store default website's meta data. If page does not have any it will be used as fallback.
Fetched after plugin's registration.
## wp_page
There we store our pages' content. Under __page key__ we have pairs like:
```
"page-slug": <response_from_wp>
```
Fetched after request page's page on frontend
## wp_post
There we store our posts' content. Under __post key__ we have pairs like:
```
"post-slug": <response_from_wp>
```
Fetched after request post's page on frontend
| 32.109375 | 162 | 0.756204 | eng_Latn | 0.989193 |
d5b3dab5b581eb8db270a5ed7fabf26971bc1d3a | 3,790 | md | Markdown | docs/2014/analysis-services/kpi-organizer-kpis-tab-cube-designer-analysis-services-multidimensional-data.md | in4matica/sql-docs.de-de | b5a6c26b66f347686c4943dc8307b3b1deedbe7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/analysis-services/kpi-organizer-kpis-tab-cube-designer-analysis-services-multidimensional-data.md | in4matica/sql-docs.de-de | b5a6c26b66f347686c4943dc8307b3b1deedbe7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/analysis-services/kpi-organizer-kpis-tab-cube-designer-analysis-services-multidimensional-data.md | in4matica/sql-docs.de-de | b5a6c26b66f347686c4943dc8307b3b1deedbe7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: KPI-Planer (Registerkarte ' KPIs ', Cube-Designer) (Analysis Services-Mehrdimensionale Daten) | Microsoft-Dokumentation
ms.custom: ''
ms.date: 06/14/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology: analysis-services
ms.topic: conceptual
f1_keywords:
- sql12.asvs.cubeeditor.kpiorganizerpane.f1
ms.assetid: b0f0388e-3d75-450d-b5fb-8a1d31cf8376
author: minewiskan
ms.author: owend
manager: craigg
ms.openlocfilehash: 85046febbaa348216a48e51860f7dbcf604f9f8c
ms.sourcegitcommit: b87d36c46b39af8b929ad94ec707dee8800950f5
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 02/08/2020
ms.locfileid: "66079394"
---
# <a name="kpi-organizer-kpis-tab-cube-designer-analysis-services---multidimensional-data"></a>KPI-Planer (Registerkarte 'KPIs', Cube-Designer) (Analysis Services – Mehrdimensionale Daten)
Im Bereich **KPI-Planer** der Registerkarte **KPIs** können Sie im Cube-Designer auf die in dem angegebenen Cube enthaltenen Key Performance Indicators (KPIs) zugreifen und diese neu anordnen.
> [!NOTE]
> Der Bereich wird in der Formularansicht nicht angezeigt.
## <a name="options"></a>Tastatur
**List**
Zeigt den Namen des KPI an.
Wählen Sie einen KPI aus, um den KPI-Formular-Editor **** in der Formularansicht anzuzeigen.
## <a name="context-menu"></a>Kontextmenü
Die folgenden Optionen sind im Kontextmenü verfügbar, das angezeigt wird, wenn Sie im Bereich **KPI-Planer** mit der rechten Maustaste auf einen KPI klicken:
|Option|Definition|
|------------|----------------|
|**Neuer KPI**|Wählen Sie einen KPI aus, um den KPI-Formular-Editor **** anzuzeigen und einen neuen KPI zu erstellen. Weitere Informationen zum **** finden Sie unter [ (KPIs Tab, Cube Designer) (Analysis Services - Multidimensional Data)](kpi-form-editor-kpis-tab-cube-designer-analysis-services-multidimensional-data.md).|
|**Nach oben**|Wählen Sie diese Option aus, um den ausgewählten KPI im **KPI-Planer** um eine Position nach oben zu verschieben und die Reihenfolge zu bestimmen, in der die KPIs im **KPI-Browser**angezeigt werden.<br /><br /> Hinweis: Wenn der ausgewählte KPI nicht weiter nach unten verschoben werden kann, ist diese Option deaktiviert.|
|**Nach unten**|Wählen Sie diese Option aus, um den ausgewählten KPI im **KPI-Planer** um eine Position nach unten zu verschieben und die Reihenfolge zu bestimmen, in der die KPIs im **KPI-Browser**angezeigt werden.<br /><br /> Hinweis: Wenn der ausgewählte KPI nicht weiter nach unten verschoben werden kann, ist diese Option deaktiviert.|
|**Löschen**|Wählen Sie diese Option aus, um den ausgewählten KPI zu löschen.|
## <a name="see-also"></a>Weitere Informationen
[Cube-Designer (Analysis Services Mehrdimensionale Daten)](cube-designer-analysis-services-multidimensional-data.md)
[KPIs (Cube-Designer) (Analysis Services Mehrdimensionale Daten)](kpis-cube-designer-analysis-services-multidimensional-data.md)
[Symbolleiste (Registerkarte ' KPIs ', Cube-Designer) (Analysis Services Mehrdimensionale Daten)](toolbar-kpis-tab-cube-designer-analysis-services-multidimensional-data.md)
[Berechnungs Tools (Registerkarte ' KPIs ', Cube-Designer) (Analysis Services Mehrdimensionale Daten)](calculation-tools-kpis-cube-designer-analysis-services-multidimensional-data.md)
[KPI-Formular-Editor (Registerkarte KPIs, Cube-Designer) (Analysis Services-Mehrdimensionale Daten)](kpi-form-editor-kpis-tab-cube-designer-analysis-services-multidimensional-data.md)
[KPI-Browser (Registerkarte KPIs, Cube-Designer) (Analysis Services-Mehrdimensionale Daten)](kpi-browser-kpis-tab-cube-designer-analysis-services-multidimensional-data.md)
| 71.509434 | 342 | 0.759103 | deu_Latn | 0.906834 |
d5b44d8f51d1cbe911744922d37eca75ee1e01de | 302 | md | Markdown | README.md | ohirichi/shopper | 7b100649ea019185f5ececad5f42ba1eb00442c3 | [
"MIT"
] | null | null | null | README.md | ohirichi/shopper | 7b100649ea019185f5ececad5f42ba1eb00442c3 | [
"MIT"
] | null | null | null | README.md | ohirichi/shopper | 7b100649ea019185f5ececad5f42ba1eb00442c3 | [
"MIT"
] | null | null | null | # Shopper
A mock ecommerce site selling sassy comebacks and emotion potions.
Built using NERP stack.
##Screenshots:
| 23.230769 | 79 | 0.754967 | eng_Latn | 0.3502 |
d5b5beb07942f2e21ad450a441ebbea17c248778 | 1,265 | md | Markdown | content/archives/2005/qualified.md | bsag/blog | e5e4ec7456a6b45befaf78dade6f229c4b97a9b7 | [
"BSD-2-Clause-FreeBSD"
] | 1 | 2017-08-24T13:09:17.000Z | 2017-08-24T13:09:17.000Z | content/archives/2005/qualified.md | bsag/blog | e5e4ec7456a6b45befaf78dade6f229c4b97a9b7 | [
"BSD-2-Clause-FreeBSD"
] | null | null | null | content/archives/2005/qualified.md | bsag/blog | e5e4ec7456a6b45befaf78dade6f229c4b97a9b7 | [
"BSD-2-Clause-FreeBSD"
] | null | null | null | -----
kind: article
title: "Qualified"
tags:
- life
created_at: 2005/12/22
permalink: qualified
toc: false
-----
<p>We had the assessment for our <a href="http://www.rousette.org.uk/blog/archives/2005/12/19/first-aid/">First Aid at Work course</a> today, and I passed! So I'm now Licensed To Bandage. I even get to carry a little green card in my wallet to certify that I'm a First Aider. Nothing in the course is particularly hard if you know a little bit about the basic plumbing and wiring of the human body and apply common sense, but it is good to feel confident about the correct way to prioritise treatment and the techniques you need to help someone. I think it's fair to say that in a real emergency, a certain amount of adrenalin and panic would set in, so having a memorised and drummed-in checklist of things to, well, <em>check</em> would be a good anchor to hang on to.</p>
<p>CPR is also an excellent skill to have. I think that everyone should really learn how to do it, because of the vital difference you could make in an emergency situation. Imagine how you'd feel if someone collapsed in front of you and stopped breathing, and you just stood there not knowing what to do? Still, I hope I never have to deal with anything that serious.</p>
| 74.411765 | 774 | 0.762846 | eng_Latn | 0.999392 |
d5b61dc4bf1ad02ee421804a3458d4f09c62723a | 1,528 | md | Markdown | jpa/jpa-eclipselink/README.md | mirostary/thorntail-examples | 0f5d3e0d01af0d77eec357e0a2cdff6dd3bd8807 | [
"Apache-2.0"
] | 259 | 2015-06-10T01:06:40.000Z | 2018-05-17T08:12:06.000Z | jpa/jpa-eclipselink/README.md | mirostary/thorntail-examples | 0f5d3e0d01af0d77eec357e0a2cdff6dd3bd8807 | [
"Apache-2.0"
] | 105 | 2015-06-08T13:47:50.000Z | 2018-04-27T11:25:43.000Z | jpa/jpa-eclipselink/README.md | mirostary/thorntail-examples | 0f5d3e0d01af0d77eec357e0a2cdff6dd3bd8807 | [
"Apache-2.0"
] | 286 | 2015-06-10T07:34:45.000Z | 2018-05-14T16:48:49.000Z | # JPA and Servlet .war Example
This example takes a normal JPA and Servlet build, and wraps it into
a `-thorntail` runnable jar.
> Please raise any issues found with this example in our JIRA:
> https://issues.jboss.org/browse/THORN
## Project `pom.xml`
This project is a traditional JPA project with `war` packaging.
<packaging>war</packaging>
The project adds a `<plugin>` to configure `thorntail-maven-plugin` to
create the runnable `.jar`.
<plugin>
<groupid>io.thorntail</groupId>
<artifactId>thorntail-maven-plugin</artifactId>
<version>${version.thorntail}</version>
<executions>
<execution>
<goals>
<goal>package</goal>
</goals>
</execution>
</executions>
</plugin>
To define the needed parts of Thorntail, a few dependencies are added
<dependency>
<groupid>io.thorntail</groupId>
<artifactId>jpa-eclipselink</artifactId>
<version>${version.thorntail}</version>
</dependency>
<dependency>
<groupid>io.thorntail</groupId>
<artifactId>undertow</artifactId>
<version>${version.thorntail}</version>
</dependency>
The `jpa-eclipselink` dependency provides the JPA APIs with EclipseLink as JPA provider and `undertow` provides the Servlet
APIs.
## Run
You can run it many ways:
* mvn package && java -jar ./target/example-jpa-eclipselink-thorntail.jar
* mvn thorntail:run
* From your IDE, run class `org.wildfly.swarm.Swarm`
## Use
http://localhost:8080/
| 26.344828 | 123 | 0.676702 | eng_Latn | 0.95793 |
d5b64f004800cd3fe7805a9063b221e57d2edee2 | 246 | md | Markdown | README.md | iotfablab/uploader | ce97e5618a90122c2ea2b6e8dbcb0205888395b2 | [
"MIT"
] | null | null | null | README.md | iotfablab/uploader | ce97e5618a90122c2ea2b6e8dbcb0205888395b2 | [
"MIT"
] | null | null | null | README.md | iotfablab/uploader | ce97e5618a90122c2ea2b6e8dbcb0205888395b2 | [
"MIT"
] | null | null | null | # umg-uploader
Python3 based Uploading script for sending information from UMG to InfluxDB on a Server
## Usage
uploader
The configuration file can be change via `CONF_PATH` in `uploader.py`.
The `conf.json` provides a configuration demo. | 24.6 | 87 | 0.772358 | eng_Latn | 0.944465 |
d5b6d5cb1bbf3e365b4e009995ac56c8ff6d6567 | 1,124 | md | Markdown | README.md | OctavioSI/link-share-generator | ec283d9dafd891b9b32284865f8a445c1f1f8253 | [
"MIT"
] | null | null | null | README.md | OctavioSI/link-share-generator | ec283d9dafd891b9b32284865f8a445c1f1f8253 | [
"MIT"
] | null | null | null | README.md | OctavioSI/link-share-generator | ec283d9dafd891b9b32284865f8a445c1f1f8253 | [
"MIT"
] | null | null | null | # SOCIAL LINKS SHARE GENERATOR
Simple link share generator for social media made only with HTML and CSS
## DEMO
You can access the live demo here: https://octaviosi.github.io/link-share-generator/
<br />
## Other Files in this repo
There are some files in the blog-example folder which refer to our blog post at:
🇧🇷 https://br.dev.lawyer/2021/11/entenda-html-css-javascript-basico.html <br />
🇺🇸 https://blog.dev.lawyer/2021/11/learn-basic-html-css-javascript.html
<br />
They are not related to the Social Links Share Generator but we did use them as explanation points which lead to this piece of software.
<hr />
## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
## Thanks to
[@markodenic](https://github.com/markodenic) for putting together this nice list at https://gist.github.com/markodenic/592f4196623690caf83379f2b33a4c9f
## License
[MIT](https://choosealicense.com/licenses/mit/)
| 36.258065 | 151 | 0.770463 | eng_Latn | 0.880153 |
d5b7364cb1b472f0be4a28ab1af6f8827d3a9ff6 | 2,362 | md | Markdown | README.md | PryosCode/Cinyras | 6c54e7496673c0f853a369b6c708e172f7906d5a | [
"Apache-2.0"
] | 3 | 2021-01-14T10:50:58.000Z | 2021-11-08T13:50:48.000Z | README.md | PryosCode/Cinyras | 6c54e7496673c0f853a369b6c708e172f7906d5a | [
"Apache-2.0"
] | null | null | null | README.md | PryosCode/Cinyras | 6c54e7496673c0f853a369b6c708e172f7906d5a | [
"Apache-2.0"
] | null | null | null | <a href="https://github.com/PryosCode/Cinyras/blob/master/examples/HelloWorld.cys"><img align="center" width="100%" alt="Hello World!" src="https://github.com/PryosCode/Cinyras/raw/master/img/hello-world.png"></a>
<p align="center">
<a href="https://github.com/PryosCode/Cinyras/tags"><img alt="Version" src="https://img.shields.io/github/v/release/PryosCode/Cinyras?label=Version"></a>
<a href="https://github.com/PryosCode/Cinyras/actions"><img alt="Linux" src="https://github.com/PryosCode/Cinyras/actions/workflows/linux.yml/badge.svg"></a>
<a href="https://github.com/PryosCode/Cinyras/actions"><img alt="Windows" src="https://github.com/PryosCode/Cinyras/actions/workflows/windows.yml/badge.svg"></a>
<a href="https://github.com/PryosCode/Cinyras/actions"><img alt="MacOS" src="https://github.com/PryosCode/Cinyras/actions/workflows/macos.yml/badge.svg"></a>
<a href="https://github.com/PryosCode/Cinyras/blob/master/LICENSE"><img alt="License" src="https://img.shields.io/github/license/PryosCode/Cinyras?label=License"></a>
</p>
# <a href="https://github.com/PryosCode/Cinyras/blob/master/img/logo.png"><img src="https://github.com/PryosCode/Cinyras/raw/master/img/logo.png" alt="C" width="30" height="auto"></a> Cinyras
Cinyras is a [general purpose programming language](https://en.wikipedia.org/wiki/General-purpose_programming_language).
## Download
[Releases](https://github.com/PryosCode/Cinyras/releases)
## Compile
```bash
$ git clone --recursive https://github.com/PryosCode/Cinyras.git
$ cd Cinyras
$ make
```
## Test
```bash
$ cinyras https://git.io/J336G
Hello World!
```
## Usage
```
USAGE:
cinyras [FLAGS] <FILE> [ARGS]...
FLAGS:
-h, --help Prints help information
-V, --version Prints version information
-v, --verbose Use verbose output
ARGS:
<FILE> Sets the input file to use
<ARGS>... Arguments passed to script
```
## Comparison
### Cinyras
```
void main {
print "Hello World!";
}
```
### C++
```cpp
#include <iostream>
int main(int argc, char *argv[]) {
std::cout << "Hello World!" << std::endl;
return 0;
}
```
### Java
```java
public class Main {
public static void main(String[] args) {
System.out.println("Hello World!");
}
}
```
## License
[Apache License 2.0](https://github.com/PryosCode/Cinyras/blob/master/LICENSE)
| 28.457831 | 213 | 0.684589 | yue_Hant | 0.735612 |
d5b751f1b3f44a66803cfc993cf9d689f35c0ee9 | 3,261 | md | Markdown | README.md | TheHolyWaffle/League-of-Legends-XMPP-Chat-Library | 5e4d87d0c054ff2f6510545b0e9f838338695c70 | [
"MIT"
] | 60 | 2015-01-09T13:37:37.000Z | 2021-09-15T13:55:09.000Z | README.md | TheHolyWaffle/League-of-Legends-XMPP-Chat-Library | 5e4d87d0c054ff2f6510545b0e9f838338695c70 | [
"MIT"
] | 19 | 2015-01-13T12:50:59.000Z | 2017-02-15T23:58:29.000Z | README.md | TheHolyWaffle/League-of-Legends-XMPP-Chat-Library | 5e4d87d0c054ff2f6510545b0e9f838338695c70 | [
"MIT"
] | 38 | 2015-01-09T13:38:00.000Z | 2019-04-23T02:06:59.000Z | League of Legends XMPP Chat Library
===================================
[](https://travis-ci.org/TheHolyWaffle/League-of-Legends-XMPP-Chat-Library) [](https://maven-badges.herokuapp.com/maven-central/com.github.theholywaffle/lolchatapi) [](http://www.versioneye.com/user/projects/5401aa7aeab62acbcb000056)
A Java 7 XMPP library to chat and interact with the League of Legends chatservers. Built upon [Smack](http://www.igniterealtime.org/projects/smack/) and [JDOM](http://www.jdom.org/).
## Features
- [Documented source](http://www.javadoc.io/doc/com.github.theholywaffle/lolchatapi)
- Event-based chat system
- Automatic reconnecting
- Managing of Friends and FriendGroups
- Fetch metadata of friends (level, current division, ...)
- Riot API supported (https://developer.riotgames.com)
## Getting Started
### Download
- **Option 1 (Standalone Jar)**:
Download the <a href="https://search.maven.org/remote_content?g=com.github.theholywaffle&a=lolchatapi&v=LATEST&c=with-dependencies" target="_blank">latest release</a> and add it to the buildpath of your project.
- **Option 2 (Maven)**:
```xml
<dependency>
<groupId>com.github.theholywaffle</groupId>
<artifactId>lolchatapi</artifactId>
<version><!--latest version--></version>
</dependency>
```
### Usage
1. Create a [LolChat](src/main/java/com/github/theholywaffle/lolchatapi/LolChat.java) object with the correct [ChatServer](src/main/java/com/github/theholywaffle/lolchatapi/ChatServer.java) of your region.
2. Add any listeners.
3. Login.
4. ...
### Example
```java
final LolChat api = new LolChat(ChatServer.EUW, FriendRequestPolicy.ACCEPT_ALL, new RiotApiKey("RIOT-API-KEY", RateLimit.DEFAULT));
if (api.login("myusername", "mypassword")) {
// Example 1: Send Chat Message to all your friends
for (Friend f : api.getFriends()) {
f.sendMessage("Hello " + f.getName());
}
// Example 2: Send Chat Message to all your friends and wait for an
// response
for (Friend f : api.getFriends()) {
f.sendMessage("Hello " + f.getName(), new ChatListener() {
@Override
public void onMessage(Friend friend, String message) {
System.out.println("Friend " + friend.getName()
+ " responded to my Hello World!");
}
});
}
// Example3: Send Chat Message to an specific friend
Friend f = api.getFriendByName("Dyrus");
if (f != null && f.isOnline()) {
f.sendMessage("Hi, I'm your biggest fan!");
}
}
```
[more examples](example)
### Javadocs
[here](http://www.javadoc.io/doc/com.github.theholywaffle/lolchatapi)
## Questions or bugs?
Please let me know them [here](../../issues). I'll help you out as soon as I can.
___
*“League of Legends XMPP Chat Library isn't endorsed by Riot Games and doesn't reflect the views or opinions of Riot Games or anyone officially involved in producing or managing League of Legends. League of Legends and Riot Games are trademarks or registered trademarks of Riot Games, Inc. League of Legends © Riot Games, Inc.”*
| 38.364706 | 533 | 0.725851 | eng_Latn | 0.467045 |
d5b7b29eeabf82cad281103d2d1ff9fbe52bc6a6 | 7,933 | md | Markdown | articles/chaos-studio/chaos-studio-overview.md | changeworld/azure-docs.de-de | 26492264ace1ad4cfdf80e5234dfed9a106e8012 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-03-12T23:37:21.000Z | 2021-03-12T23:37:21.000Z | articles/chaos-studio/chaos-studio-overview.md | changeworld/azure-docs.de-de | 26492264ace1ad4cfdf80e5234dfed9a106e8012 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/chaos-studio/chaos-studio-overview.md | changeworld/azure-docs.de-de | 26492264ace1ad4cfdf80e5234dfed9a106e8012 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Was ist Azure Chaos Studio?
description: Hier finden Sie grundlegende Informationen zu Azure Chaos Studio. Dabei handelt es sich um einen Azure-Dienst, mit dem Sie die Resilienz von Anwendungen und Diensten für reale Vorfälle messen, nachvollziehen und gewährleisten können. Zu diesem Zweck werden mittels Chaos Engineering Fehler in Ihren Dienst eingeschleust, um zu ermitteln, wie der Dienst auf Störungen reagiert.
services: chaos-studio
author: johnkemnetz
ms.topic: overview
ms.date: 11/11/2021
ms.author: johnkem
ms.service: chaos-studio
ms.custom: template-overview,ignite-fall-2021
ms.openlocfilehash: 4df530e20733e5f24db930e88bb30894293416a7
ms.sourcegitcommit: e1037fa0082931f3f0039b9a2761861b632e986d
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 11/12/2021
ms.locfileid: "132399331"
---
# <a name="what-is-azure-chaos-studio-preview"></a>Was ist Azure Chaos Studio (Vorschauversion)?
Azure Chaos Studio ist ein verwalteter Dienst zur Verbesserung der Resilienz durch Einschleusung von Fehlern in Ihre Azure-Anwendungen. Die Durchführung kontrollierter Fehlereinschleusungsexperimente (sogenanntes Chaos Engineering) trägt dazu bei, die Resilienz für reale Vorfälle wie etwa Regionsausfälle oder Anwendungsfehler, die auf einem virtuellen Computer eine hohe CPU-Auslastung verursachen, zu messen, nachzuvollziehen und zu verbessern.
> [!VIDEO https://channel9.msdn.com/Shows/Azure-Videos/Azure-Chaos-Studio-Curious-to-control-chaos/player]
## <a name="why-should-i-use-chaos-studio"></a>Gründe für die Verwendung von Chaos Studio
Die Überprüfung und Verbesserung der Resilienz einer Anwendung ist immer ein wichtiger Punkt – ganz gleich, ob Sie eine neue Anwendung entwickeln, die in Azure gehostet wird, eine vorhandene Anwendung zu Azure migrieren oder eine Anwendung verwenden, die bereits in Azure ausgeführt wird. Resilienz ist die Fähigkeit eines Systems, mit Störungen umzugehen und sich von Störungen zu erholen. Eine Beeinträchtigung der Verfügbarkeit Ihrer Anwendung kann zu Fehlern und Ausfällen für Benutzer führen, was wiederum negative Auswirkungen auf Ihr Unternehmen oder Ihre Mission haben kann.
Wenn Sie eine Anwendung in der Cloud ausführen, müssen Sie sich zur Vermeidung dieser negativen Folgen vergewissern, dass Ihre Anwendung effektiv auf Störungen reagiert. Solche Störungen können durch einen Dienst, von dem Sie abhängig sind, durch einen Ausfall des eigentlichen Diensts und sogar durch Tools und Prozesse für die Reaktion auf Vorfälle verursacht werden. Mithilfe von Chaos-Experimenten können Sie die Ausfallsicherheit Ihrer in der Cloud gehosteten Anwendung testen.
## <a name="when-would-i-use-chaos-studio"></a>Wann kann ich Chaos Studio verwenden?
Chaos Engineering kann für eine Vielzahl von Resilienzvalidierungsszenarien verwendet werden. Diese Szenarien decken den gesamten Lebenszyklus der Dienstentwicklung und des Betriebs ab und können entweder als *Shift-Right* (Verlagerung nach rechts) oder als *Shift-Left* (Verlagerung nach links) kategorisiert werden. Bei der Verlagerung nach rechts wird das Szenario am besten in einer Produktions- oder Präproduktionsumgebung überprüft. Bei der Verlagerung nach links kann das Szenario in einer Entwicklungsumgebung oder in einer gemeinsam genutzten Testumgebung überprüft werden. Shift-Right-Szenarien sollten in der Regel mit echtem Kundendatenverkehr oder simulierter Last durchgeführt werden, während bei Shift-Left-Szenarien kein echter Kundendatenverkehr erforderlich ist. Im Anschluss finden Sie einige gängige Szenarien für Chaos Engineering:
* Reproduzieren eines Vorfalls, der Ihre Anwendung beeinträchtigt hat, um den Fehlermodus besser zu verstehen oder sicherzustellen, dass nach dem Vorfall vorgenommene Korrekturen eine Wiederholung des Vorfalls verhindern
* Ausführen von Game Days zur Überprüfung der Auslastung, Skalierung, Leistung und Resilienz eines Diensts zur Vorbereitung auf ein größeres Benutzerereignis oder eine wichtige Phase
* Durchführen von BCDR-Drills (Business Continuity & Disaster Recovery), um sicherzustellen, dass Ihre Anwendung im Falle eines schwerwiegenden Zwischenfalls schnell wiederhergestellt werden kann und wichtige Daten erhalten bleiben
* Durchführen von Hochverfügbarkeitstests, um die Anwendungsresilienz bei bestimmten Fehlern wie Regionsausfällen, Netzwerkkonfigurationsfehlern, Ereignissen mit hoher Auslastung oder Noisy Neighbor-Problemen zu testen
* Entwickeln von Leistungsbenchmarks für Anwendungen
* Planen des Kapazitätsbedarfs für Produktionsumgebungen
* Ausführen von Belastungs- oder Auslastungstests
* Sicherstellen, dass Dienste, die aus einer lokalen Umgebung oder aus einer anderen Cloudumgebung migriert wurden, weiterhin gegenüber bekannten Fehlern resilient sind
* Schaffen von Vertrauen in Dienste, die auf cloudnativen Architekturen basieren
* Vergewissern, dass Livewebsite-Tools, Einblickdaten und Bereitschaftsprozesse unter unerwarteten Bedingungen wie erwartet funktionieren
In vielen dieser Szenarien verwenden Sie zunächst Ad-hoc-Chaos-Experimente, um für Resilienz zu sorgen, und vergewissern sich dann kontinuierlich, dass sich die Resilienz durch neue Bereitstellungen nicht verschlechtert, indem Sie Chaos-Experimente als Bereitstellungsgate in Ihrer CI/CD-Pipeline verwenden.
## <a name="how-does-chaos-studio-work"></a>Funktionsweise von Chaos Studio
Mit Chaos Studio können Sie die Einschleusung von Fehlern in Ihre Azure-Ressourcen sicher und kontrolliert orchestrieren. Das Herzstück von Chaos Studio sind Chaos-Experimente. Ein Chaos-Experiment ist eine Azure-Ressource, die die Fehler beschreibt, die ausgeführt werden sollen, und die Ressourcen, für die diese Fehler ausgeführt werden sollen. Fehler können je nach Ihren Anforderungen parallel oder nacheinander ausgeführt werden. Chaos Studio unterstützt zwei Arten von Fehlern: Fehler vom Typ *Service-direkt* werden direkt für eine Azure-Ressource ausgeführt, ohne dass eine Installation oder Instrumentierung (beispielsweise Neustarten eines Azure Cache for Redis-Clusters oder Hinzufügen von Netzwerklatenz zu AKS-Pods) erforderlich ist. Fehler vom Typ *Agent-basiert* werden dagegen auf virtuellen Computern oder in VM-Skalierungsgruppen ausgeführt, um gastinterne Fehler zu verursachen (beispielsweise durch Auslastung des virtuellen Arbeitsspeichers oder Beenden eines Prozesses). Für jeden Fehler können bestimmte Parameter konfiguriert werden – etwa, welcher Prozess beendet oder wie viel Arbeitsspeicherauslastung generiert werden soll.
Wenn Sie ein Chaos-Experiment erstellen, definieren Sie einen einzelnen Schritt oder mehrere nacheinander ausgeführte *Schritte*. Jeder Schritt enthält mindestens eine *Verzweigung*. Mehrere Verzweigungen werden parallel innerhalb des jeweiligen Schritts ausgeführt, und die einzelnen Verzweigungen enthalten wiederum mindestens eine *Aktion* wie etwa das Einschleusen eines Fehlers oder eine bestimmte Wartedauer. Abschließend strukturieren Sie die Ressourcen (*Ziele*), für die die einzelnen Fehler ausgeführt werden, in Gruppen (sogenannte Selektoren), um in jeder Aktion problemlos auf eine Gruppe von Ressourcen verweisen zu können.
Ein Chaos-Experiment ist eine Azure-Ressource, die sich in einem Abonnement und in einer Ressourcengruppe befindet. Sie können das Azure-Portal oder die Chaos Studio-REST-API verwenden, um ein Experiment zu erstellen, zu aktualisieren, zu starten, abzubrechen und dessen Status anzuzeigen.
## <a name="next-steps"></a>Nächste Schritte
Nutzen Sie die folgenden Links, um mit der Erstellung und Ausführung von Chaos-Experimenten zu beginnen und die Anwendungsresilienz mit Chaos Studio zu verbessern.
- [Erstellen und Ausführen des ersten Experiments](chaos-studio-tutorial-service-direct-portal.md)
- [Grundlegendes zu Chaos Engineering und Resilienz](chaos-studio-chaos-engineering-overview.md)
| 132.216667 | 1,152 | 0.836506 | deu_Latn | 0.999099 |
d5b7d22e0faa38a5357af606ea1ba1e771a4af0b | 780 | md | Markdown | fasttrack/TOC.md | MicrosoftDocs/OfficeDocs-FastTrack-pr.fr-FR | e5b7946ba2935589dbde8b661dfd6074bb051483 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T19:14:12.000Z | 2021-04-21T00:13:50.000Z | fasttrack/TOC.md | MicrosoftDocs/OfficeDocs-FastTrack-pr.fr-FR | e5b7946ba2935589dbde8b661dfd6074bb051483 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-01-26T05:01:40.000Z | 2022-01-26T05:01:50.000Z | fasttrack/TOC.md | MicrosoftDocs/OfficeDocs-FastTrack-pr.fr-FR | e5b7946ba2935589dbde8b661dfd6074bb051483 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-10-11T20:12:49.000Z | 2019-10-11T20:12:49.000Z | # [Avantages du Centre FastTrack pour Microsoft 365](introduction.md)
## [Éligibilité](eligibility.md)
## [Processus et attentes](process-and-expectations.md)
## [Produits et fonctionnalités](products-and-capabilities.md)
### [Soutien aux applications](Win-10-app-assure.md)
### [Assistance proposée](Win-10-app-assure-assistance-offered.md)
### [Nouveau Microsoft Edge](Win-10-microsoft-edge.md)
### [Assistance proposée](Win-10-microsoft-edge-assistance-offered.md)
## [Migration des données](data-migration.md)
## [Annexe A : Accord de partenariat commercial HIPAA pour le service FastTrack](O365-hipaa-business-associate-agreement.md)
## [Annexe B : Présentation des avantages du service FastTrack pour Office 365 pour le gouvernement américain](US-Gov-appendix-overview.md)
| 60 | 139 | 0.773077 | fra_Latn | 0.447887 |
d5b82e745b4c6c05687b3144b8abd73c8fb29d92 | 406 | md | Markdown | Data Structure/Array Or Vector/Minimum Flips To Make Binary Array Same/readMe.md | rajethanm4/Programmers-Community | d16083eb0e84403159d999d4d1a8bbf652ca51f6 | [
"MIT"
] | 8 | 2020-11-07T10:29:21.000Z | 2020-12-26T16:54:13.000Z | Data Structure/Array Or Vector/Minimum Flips To Make Binary Array Same/readMe.md | rajethanm4/Programmers-Community | d16083eb0e84403159d999d4d1a8bbf652ca51f6 | [
"MIT"
] | null | null | null | Data Structure/Array Or Vector/Minimum Flips To Make Binary Array Same/readMe.md | rajethanm4/Programmers-Community | d16083eb0e84403159d999d4d1a8bbf652ca51f6 | [
"MIT"
] | 2 | 2019-12-18T13:06:19.000Z | 2021-01-05T18:47:18.000Z | # Given a binary array, we need to convert this array into an array that either contains all 1s or all 0s. We need to do it using the minimum number of group flips.
# Constraints
- 1 < size Of Array <= 10^6
- 0 < Array Elements <= 10^9
# Input
- Array
- Its Size
# Output
- return the group to be flipped
```
Input : { 0, 0, 1, 1, 0, 0, 1, 1, 0 }
Output : From 2 to 3
From 6 to 7
```
| 20.3 | 166 | 0.625616 | eng_Latn | 0.997325 |
d5b9d85bacd20dc86aa8a91d6ebf68b50af710ae | 502 | md | Markdown | pages/en/lb4/apidocs/rest.routesource.value.md | luisfavila/loopback.io | cb9ac0bd8ca2997d9e0e03089fd1e256f21fe5e8 | [
"MIT"
] | 1 | 2020-03-04T07:37:39.000Z | 2020-03-04T07:37:39.000Z | pages/en/lb4/apidocs/rest.routesource.value.md | saotak/loopback.io | cb9ac0bd8ca2997d9e0e03089fd1e256f21fe5e8 | [
"MIT"
] | 3 | 2021-05-20T12:45:34.000Z | 2022-02-26T06:28:39.000Z | pages/en/lb4/apidocs/rest.routesource.value.md | saotak/loopback.io | cb9ac0bd8ca2997d9e0e03089fd1e256f21fe5e8 | [
"MIT"
] | null | null | null | ---
lang: en
title: 'API docs: rest.routesource.value'
keywords: LoopBack 4.0, LoopBack 4
sidebar: lb4_sidebar
permalink: /doc/en/lb4/apidocs.rest.routesource.value.html
---
<!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [@loopback/rest](./rest.md) > [RouteSource](./rest.routesource.md) > [value](./rest.routesource.value.md)
## RouteSource.value property
<b>Signature:</b>
```typescript
readonly value: RouteEntry;
```
| 23.904762 | 136 | 0.691235 | eng_Latn | 0.250412 |
d5b9f57997f140f822601b0b7b7c35d067da07c7 | 978 | md | Markdown | README.md | 0xc0dec/solo | 381276451767690b5fdb5a50a6b74a92ba78aa15 | [
"Zlib"
] | 31 | 2015-02-20T04:03:43.000Z | 2022-03-07T19:04:02.000Z | README.md | 0xc0dec/solo | 381276451767690b5fdb5a50a6b74a92ba78aa15 | [
"Zlib"
] | 14 | 2015-07-13T09:24:22.000Z | 2016-10-24T10:09:58.000Z | README.md | 0xc0dec/solo | 381276451767690b5fdb5a50a6b74a92ba78aa15 | [
"Zlib"
] | 1 | 2020-02-22T15:09:36.000Z | 2020-02-22T15:09:36.000Z | ## About
"I have no idea how to write game engines"-style game engine. A playground for my gamedev experiments.
## Features
* [Unity](https://unity.com)-inspired component system.
* Loading of several popular mesh and texture formats, also TTF fonts.
* [Bullet](https://github.com/bulletphysics/bullet3) physics.
* Vulkan/OpenGL 4 rendering backend.
* Same API for both Lua and C++.
* [Dear ImGui](https://github.com/ocornut/imgui) UI.
## Building
* Install Python2 (v3 not tested). Needed by some dependencies for building.
* `cd build`.
* `cmake -G "Visual Studio 16 2019" ..` (or other generator de
pending on the OS/IDE).
* Build the generated project.
## Running Lua demos
Using scripts
* `cd build`
* `run-lua-demo1-debug-gl.cmd` or other similar script.
or manually
* `cd build/bin/<Debug|Release>`
* `Solr.exe ../../../src/demos/lua/demo<N>/demo_<gl|vk>.lua` where `N` is the demo number
| 31.548387 | 103 | 0.695297 | eng_Latn | 0.919876 |
d5ba2b423a91742e9212cce9b15be892593f79c2 | 333 | md | Markdown | CHANGELOG.md | 0xdecade/f-datetimerangepicker | 0493eb4c50701a080e033e18a4aefa9278204fa2 | [
"Apache-2.0"
] | 20 | 2019-03-06T04:00:04.000Z | 2022-01-18T16:55:48.000Z | CHANGELOG.md | 0xdecade/f-datetimerangepicker | 0493eb4c50701a080e033e18a4aefa9278204fa2 | [
"Apache-2.0"
] | 9 | 2019-12-26T22:03:19.000Z | 2022-02-22T04:33:50.000Z | CHANGELOG.md | 0xdecade/f-datetimerangepicker | 0493eb4c50701a080e033e18a4aefa9278204fa2 | [
"Apache-2.0"
] | 9 | 2020-01-24T10:07:24.000Z | 2021-12-15T02:34:05.000Z | ## 0.2.0
- Null safety
## 0.1.4
- Support 24hrs format
## 0.1.3
- Config minimum & maximum time cap
## 0.1.2
- Allow minimum & maximum time cap
## 0.1.1
- Support change mode
- Allow change cancel and done text
## 0.1.0
- Use FractionallySizedBox
## 0.0.7
- Added example and CHANGELOG
## 0.0.1
- First stable version | 10.090909 | 35 | 0.645646 | eng_Latn | 0.875194 |
d5bae570b4699a9686a08b3f13138179b7415f1f | 76 | md | Markdown | vault/gabes_work/NCM LISTING/4805.92.90/CARS LOGCOMEX 4805.92.90.md | hox-data/peridot | 42cbc8e6d050642c13d6f64575b945621a905b17 | [
"MIT"
] | null | null | null | vault/gabes_work/NCM LISTING/4805.92.90/CARS LOGCOMEX 4805.92.90.md | hox-data/peridot | 42cbc8e6d050642c13d6f64575b945621a905b17 | [
"MIT"
] | null | null | null | vault/gabes_work/NCM LISTING/4805.92.90/CARS LOGCOMEX 4805.92.90.md | hox-data/peridot | 42cbc8e6d050642c13d6f64575b945621a905b17 | [
"MIT"
] | null | null | null | ![[Pasted image 20220309175103.png]]
![[Pasted image 20220309175118.png]]
| 15.2 | 36 | 0.736842 | eng_Latn | 0.203876 |
d5bb4a8e1546f4046364295b4bc5e658b7ad3bdd | 1,017 | md | Markdown | docs/outlook/mapi/slpstrarray.md | JakubK44/office-developer-client-docs | 7c36a87ab45654d6a9313f3bc4365c08c4a616c6 | [
"CC-BY-4.0",
"MIT"
] | 50 | 2018-11-08T14:51:56.000Z | 2022-03-28T18:56:54.000Z | docs/outlook/mapi/slpstrarray.md | JakubK44/office-developer-client-docs | 7c36a87ab45654d6a9313f3bc4365c08c4a616c6 | [
"CC-BY-4.0",
"MIT"
] | 510 | 2018-05-17T01:01:02.000Z | 2022-03-31T22:20:22.000Z | docs/outlook/mapi/slpstrarray.md | JakubK44/office-developer-client-docs | 7c36a87ab45654d6a9313f3bc4365c08c4a616c6 | [
"CC-BY-4.0",
"MIT"
] | 98 | 2018-05-10T08:39:19.000Z | 2022-03-31T09:41:54.000Z | ---
title: "SLPSTRArray"
manager: soliver
ms.date: 03/09/2015
ms.audience: Developer
ms.topic: reference
ms.prod: office-online-server
ms.localizationpriority: medium
api_name:
- MAPI.SLPSTRArray
api_type:
- COM
ms.assetid: 5f570d9b-eb3d-4fc7-bcbe-348a0b8fe9e9
description: "Last modified: March 09, 2015"
---
# SLPSTRArray
**Applies to**: Outlook 2013 | Outlook 2016
Contains an array of string values that are used to describe a property of type PT_MV_STRING8.
|||
|:-----|:-----|
|Header file: <br/> |Mapidefs.h <br/> |
```cpp
typedef struct _SLPSTRArray
{
ULONG cValues;
LPSTR FAR *lppszA;
} SLPSTRArray;
```
## Members
**cValues**
> Count of values in the array pointed to by the **lppszA** member.
**lppszA**
> Pointer to an array of null-ended 8-bit character strings.
## Remarks
For more information about PT_MV_STRING8, see [List of Property Types](property-types.md).
## See also
[SPropValue](spropvalue.md)
[MAPI Structures](mapi-structures.md)
| 16.142857 | 94 | 0.691249 | eng_Latn | 0.66183 |
d5bc2f986bdfdd030292d758c34a78b6bf40db70 | 181 | md | Markdown | _posts/0000-01-02-aram9321.md | aram9321/github-slideshow | 79f551ed5c9e00c9c3cfe61a3aaaf5ff011ce479 | [
"MIT"
] | null | null | null | _posts/0000-01-02-aram9321.md | aram9321/github-slideshow | 79f551ed5c9e00c9c3cfe61a3aaaf5ff011ce479 | [
"MIT"
] | 3 | 2022-01-24T03:43:59.000Z | 2022-01-24T05:18:01.000Z | _posts/0000-01-02-aram9321.md | aram9321/github-slideshow | 79f551ed5c9e00c9c3cfe61a3aaaf5ff011ce479 | [
"MIT"
] | null | null | null | ---
layout: slide
title: "Welcome to our second slide!"
---
“Life is not a problem to be solved, but a reality to be experienced.”– Soren Kierkegaard
Use the left arrow to go back!
| 25.857143 | 89 | 0.723757 | eng_Latn | 0.99511 |
d5bc636e4f0e31a1c66afd116224140db21f2344 | 767 | md | Markdown | notices/archive/notice_4.md | MagicPowerIO/etcmask | 5decf3740989ca005b34145988b77abc4e782a45 | [
"MIT"
] | null | null | null | notices/archive/notice_4.md | MagicPowerIO/etcmask | 5decf3740989ca005b34145988b77abc4e782a45 | [
"MIT"
] | null | null | null | notices/archive/notice_4.md | MagicPowerIO/etcmask | 5decf3740989ca005b34145988b77abc4e782a45 | [
"MIT"
] | null | null | null | Dear ETCMask Users,
There have been several instances of high-profile legitimate websites such as BTC Manager and Games Workshop that have had their websites temporarily compromised. This involves showing a fake ETCMask window on the page asking for user's seed phrases. ETCMask will never open itself in this way and users are encouraged to report these instances immediately to either [our phishing blacklist](https://github.com/MetaMask/eth-phishing-detect/issues) or our support email at [[email protected]](mailto:[email protected]).
Please read our full article on this ongoing issue at [https://medium.com/metamask/new-phishing-strategy-becoming-common-1b1123837168](https://medium.com/metamask/new-phishing-strategy-becoming-common-1b1123837168).
| 109.571429 | 526 | 0.818774 | eng_Latn | 0.975885 |
d5bcc1bdb9e7b0fa4a174e7b0fe1c1823f82cd4e | 4,847 | md | Markdown | add/metadata/System.Windows.Controls/StickyNoteControl.meta.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Windows.Controls/StickyNoteControl.meta.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Windows.Controls/StickyNoteControl.meta.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
uid: System.Windows.Controls.StickyNoteControl
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.IsActive
ms.technology:
- "dotnet-wpf"
ms.author: "dotnet-bot"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontFamily
ms.technology:
- "dotnet-wpf"
ms.author: "dotnet-bot"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.DeleteNoteCommand
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.InkCommand
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.PenWidth
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.Author
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.StickyNoteTypeProperty
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontSizeProperty
ms.technology:
- "dotnet-wpf"
ms.author: "dotnet-bot"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.IsMouseOverAnchorProperty
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontWeight
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.TextSchemaName
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.InkSchemaName
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.IsActiveProperty
ms.technology:
- "dotnet-wpf"
ms.author: "dotnet-bot"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.IsExpanded
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontStyleProperty
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.StickyNoteType
ms.technology:
- "dotnet-wpf"
ms.author: "dotnet-bot"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.PenWidthProperty
ms.technology:
- "dotnet-wpf"
ms.author: "dotnet-bot"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontStyle
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontFamilyProperty
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontSize
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontStretchProperty
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.IsMouseOverAnchor
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.AuthorProperty
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.OnApplyTemplate
ms.technology:
- "dotnet-wpf"
ms.author: "dotnet-bot"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontStretch
ms.technology:
- "dotnet-wpf"
ms.author: "dotnet-bot"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.IsExpandedProperty
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.CaptionFontWeightProperty
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
---
uid: System.Windows.Controls.StickyNoteControl.AnchorInfo
ms.technology:
- "dotnet-wpf"
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
---
| 19.158103 | 73 | 0.739426 | yue_Hant | 0.316156 |
d5bd0ef1e47e415bc9f60867862b80002c397b49 | 1,733 | md | Markdown | pages/privacy-policy.md | dscst/dscst.github.io | ae85e0b222edb28649752d0e608f0509f028123a | [
"MIT"
] | null | null | null | pages/privacy-policy.md | dscst/dscst.github.io | ae85e0b222edb28649752d0e608f0509f028123a | [
"MIT"
] | null | null | null | pages/privacy-policy.md | dscst/dscst.github.io | ae85e0b222edb28649752d0e608f0509f028123a | [
"MIT"
] | null | null | null | ---
layout: page
title: Privacy Policy
permalink: /privacy-policy/
---
### Information that is gathered from visitors
In common with other websites, log files are stored on the web server saving details such as the visitor's IP address, browser type, referring page and time of visit.
Cookies may be used to remember visitor preferences when interacting with the website.
Where registration is required, the visitor's email and a username will be stored on the server.
### How the Information is used
The information is used to enhance the vistor's experience when using the website to display personalised content and possibly advertising.
E-mail addresses will not be sold, rented or leased to 3rd parties.
E-mail may be sent to inform you of news of our services or offers by us or our affiliates.
### Visitor Options
If you have subscribed to one of our services, you may unsubscribe by following the instructions which are included in e-mail that you receive.
You may be able to block cookies via your browser settings but this may prevent you from access to certain features of the website.
### Cookies
Cookies are small digital signature files that are stored by your web browser that allow your preferences to be recorded when visiting the website. Also they may be used to track your return visits to the website.
3rd party advertising companies may also use cookies for tracking purposes.
### Google Ads
Google, as a third party vendor, uses cookies to serve ads.
Google's use of the DART cookie enables it to serve ads to visitors based on their visit to sites they visit on the Internet.
Website visitors may opt out of the use of the DART cookie by visiting the Google ad and content network privacy policy. | 48.138889 | 213 | 0.792268 | eng_Latn | 0.999921 |
d5bd284ef5acd85549399d3e06f4caa8b5ccd51c | 61 | md | Markdown | docs/chapters/06-Navigationsunterstützung-in-Computerspielen/fragestellung.md | UniRegensburg/User-Interface-Design-In-Computer-Games | 04aa8b9615c78354d53d86a02446f485fc722c0a | [
"CC0-1.0"
] | null | null | null | docs/chapters/06-Navigationsunterstützung-in-Computerspielen/fragestellung.md | UniRegensburg/User-Interface-Design-In-Computer-Games | 04aa8b9615c78354d53d86a02446f485fc722c0a | [
"CC0-1.0"
] | null | null | null | docs/chapters/06-Navigationsunterstützung-in-Computerspielen/fragestellung.md | UniRegensburg/User-Interface-Design-In-Computer-Games | 04aa8b9615c78354d53d86a02446f485fc722c0a | [
"CC0-1.0"
] | null | null | null | *Navigationsunterstützung in Computerspielen*
# Fragestellung | 30.5 | 45 | 0.885246 | deu_Latn | 0.995753 |
d5bd9304d0917c646f6b4cf51f8fe2e54989fb7d | 591 | md | Markdown | README.md | thesoncriel/eyeroid | 187179f8a6dd102501a5b105d67bbcce97bce37e | [
"MIT"
] | null | null | null | README.md | thesoncriel/eyeroid | 187179f8a6dd102501a5b105d67bbcce97bce37e | [
"MIT"
] | null | null | null | README.md | thesoncriel/eyeroid | 187179f8a6dd102501a5b105d67bbcce97bce37e | [
"MIT"
] | null | null | null | # 아이로이드
카센터 물품 및 고객관리용 안드로이드 모바일 어플리케이션.
각 상품별로 기재된 바코드를 통해 상품을 등록하고
그 상품을 통한 매출, 입고 관리등을 할 수 있다.
## 사용기술 및 환경
* Android 1.5
* Java 6
* SQLite
* zxing (지브라 크로싱) 을 통한 바코드 인식기 적용
* 검색 시 자동 완성 기능 적용
## 기타
* 2010년 교내 경시대회 대상
* 2010 경남 e-biz 출품작: 장려상
## Licence
MIT
## Screen Shots
| 23.64 | 75 | 0.705584 | kor_Hang | 0.999549 |
d5be12d6674c517c6b3fdfb6102475d28d82777d | 163,508 | md | Markdown | aspnetcore/fundamentals/routing.md | AdamWorley/AspNetCore.Docs | a4921a36b1120f2890d88a964ee20fe2b132589b | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-10-02T13:32:36.000Z | 2021-10-02T13:32:36.000Z | aspnetcore/fundamentals/routing.md | daveabrock/AspNetCore.Docs | bca5d2079025cf717f7a517eb16b18788d6cd308 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnetcore/fundamentals/routing.md | daveabrock/AspNetCore.Docs | bca5d2079025cf717f7a517eb16b18788d6cd308 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Routing in ASP.NET Core
author: rick-anderson
description: Discover how ASP.NET Core routing is responsible for matching HTTP requests and dispatching to executable endpoints.
monikerRange: '>= aspnetcore-2.1'
ms.author: riande
ms.custom: mvc
ms.date: 4/1/2020
no-loc: ["ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
uid: fundamentals/routing
---
# Routing in ASP.NET Core
By [Ryan Nowak](https://github.com/rynowak), [Kirk Larkin](https://twitter.com/serpent5), and [Rick Anderson](https://twitter.com/RickAndMSFT)
::: moniker range=">= aspnetcore-3.0"
Routing is responsible for matching incoming HTTP requests and dispatching those requests to the app's executable endpoints. [Endpoints](#endpoint) are the app's units of executable request-handling code. Endpoints are defined in the app and configured when the app starts. The endpoint matching process can extract values from the request's URL and provide those values for request processing. Using endpoint information from the app, routing is also able to generate URLs that map to endpoints.
Apps can configure routing using:
- Controllers
- Razor Pages
- SignalR
- gRPC Services
- Endpoint-enabled [middleware](xref:fundamentals/middleware/index) such as [Health Checks](xref:host-and-deploy/health-checks).
- Delegates and lambdas registered with routing.
This document covers low-level details of ASP.NET Core routing. For information on configuring routing:
* For controllers, see <xref:mvc/controllers/routing>.
* For Razor Pages conventions, see <xref:razor-pages/razor-pages-conventions>.
The endpoint routing system described in this document applies to ASP.NET Core 3.0 and later. For information on the previous routing system based on <xref:Microsoft.AspNetCore.Routing.IRouter>, select the ASP.NET Core 2.1 version using one of the following approaches:
* The version selector for a previous version.
* Select [ASP.NET Core 2.1 routing](?view=aspnetcore-2.1).
[View or download sample code](https://github.com/aspnet/AspNetCore.Docs/tree/master/aspnetcore/fundamentals/routing/samples/3.x) ([how to download](xref:index#how-to-download-a-sample))
The download samples for this document are enabled by a specific `Startup` class. To run a specific sample, modify *Program.cs* to call the desired `Startup` class.
## Routing basics
All ASP.NET Core templates include routing in the generated code. Routing is registered in the [middleware](xref:fundamentals/middleware/index) pipeline in `Startup.Configure`.
The following code shows a basic example of routing:
[!code-csharp[](routing/samples/3.x/RoutingSample/Startup.cs?name=snippet&highlight=8,10)]
Routing uses a pair of middleware, registered by <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseRouting*> and <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints*>:
* `UseRouting` adds route matching to the middleware pipeline. This middleware looks at the set of endpoints defined in the app, and selects the [best match](#urlm) based on the request.
* `UseEndpoints` adds endpoint execution to the middleware pipeline. It runs the delegate associated with the selected endpoint.
The preceding example includes a single *route to code* endpoint using the [MapGet](xref:Microsoft.AspNetCore.Builder.EndpointRouteBuilderExtensions.MapGet*) method:
* When an HTTP `GET` request is sent to the root URL `/`:
* The request delegate shown executes.
* `Hello World!` is written to the HTTP response. By default, the root URL `/` is `https://localhost:5001/`.
* If the request method is not `GET` or the root URL is not `/`, no route matches and an HTTP 404 is returned.
### Endpoint
<a name="endpoint"></a>
The `MapGet` method is used to define an **endpoint**. An endpoint is something that can be:
* Selected, by matching the URL and HTTP method.
* Executed, by running the delegate.
Endpoints that can be matched and executed by the app are configured in `UseEndpoints`. For example, <xref:Microsoft.AspNetCore.Builder.EndpointRouteBuilderExtensions.MapGet*>, <xref:Microsoft.AspNetCore.Builder.EndpointRouteBuilderExtensions.MapPost*>, and [similar methods](xref:Microsoft.AspNetCore.Builder.EndpointRouteBuilderExtensions) connect request delegates to the routing system.
Additional methods can be used to connect ASP.NET Core framework features to the routing system:
- [MapRazorPages for Razor Pages](xref:Microsoft.AspNetCore.Builder.RazorPagesEndpointRouteBuilderExtensions.MapRazorPages*)
- [MapControllers for controllers](xref:Microsoft.AspNetCore.Builder.ControllerEndpointRouteBuilderExtensions.MapControllers*)
- [MapHub\<THub> for SignalR](xref:Microsoft.AspNetCore.SignalR.HubRouteBuilder.MapHub*)
- [MapGrpcService\<TService> for gRPC](xref:grpc/aspnetcore)
The following example shows routing with a more sophisticated route template:
[!code-csharp[](routing/samples/3.x/RoutingSample/RouteTemplateStartup.cs?name=snippet)]
The string `/hello/{name:alpha}` is a **route template**. It is used to configure how the endpoint is matched. In this case, the template matches:
* A URL like `/hello/Ryan`
* Any URL path that begins with `/hello/` followed by a sequence of alphabetic characters. `:alpha` applies a route constraint that matches only alphabetic characters. [Route constraints](#route-constraint-reference) are explained later in this document.
The second segment of the URL path, `{name:alpha}`:
* Is bound to the `name` parameter.
* Is captured and stored in [HttpRequest.RouteValues](xref:Microsoft.AspNetCore.Http.HttpRequest.RouteValues*).
The endpoint routing system described in this document is new as of ASP.NET Core 3.0. However, all versions of ASP.NET Core support the same set of route template features and route constraints.
The following example shows routing with [health checks](xref:host-and-deploy/health-checks) and authorization:
[!code-csharp[](routing/samples/3.x/RoutingSample/AuthorizationStartup.cs?name=snippet)]
[!INCLUDE[request localized comments](~/includes/code-comments-loc.md)]
The preceding example demonstrates how:
* The authorization middleware can be used with routing.
* Endpoints can be used to configure authorization behavior.
The <xref:Microsoft.AspNetCore.Builder.HealthCheckEndpointRouteBuilderExtensions.MapHealthChecks*> call adds a health check endpoint. Chaining <xref:Microsoft.AspNetCore.Builder.AuthorizationEndpointConventionBuilderExtensions.RequireAuthorization*> on to this call attaches an authorization policy to the endpoint.
Calling <xref:Microsoft.AspNetCore.Builder.AuthAppBuilderExtensions.UseAuthentication*> and <xref:Microsoft.AspNetCore.Builder.AuthorizationAppBuilderExtensions.UseAuthorization*> adds the authentication and authorization middleware. These middleware are placed between <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseRouting*> and `UseEndpoints` so that they can:
* See which endpoint was selected by `UseRouting`.
* Apply an authorization policy before <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints*> dispatches to the endpoint.
<a name="metadata"></a>
### Endpoint metadata
In the preceding example, there are two endpoints, but only the health check endpoint has an authorization policy attached. If the request matches the health check endpoint, `/healthz`, an authorization check is performed. This demonstrates that endpoints can have extra data attached to them. This extra data is called endpoint **metadata**:
* The metadata can be processed by routing-aware middleware.
* The metadata can be of any .NET type.
## Routing concepts
The routing system builds on top of the middleware pipeline by adding the powerful **endpoint** concept. Endpoints represent units of the app's functionality that are distinct from each other in terms of routing, authorization, and any number of ASP.NET Core's systems.
<a name="endpoint"></a>
### ASP.NET Core endpoint definition
An ASP.NET Core endpoint is:
* Executable: Has a <xref:Microsoft.AspNetCore.Http.Endpoint.RequestDelegate>.
* Extensible: Has a [Metadata](xref:Microsoft.AspNetCore.Http.Endpoint.Metadata*) collection.
* Selectable: Optionally, has [routing information](xref:Microsoft.AspNetCore.Routing.RouteEndpoint.RoutePattern*).
* Enumerable: The collection of endpoints can be listed by retrieving the <xref:Microsoft.AspNetCore.Routing.EndpointDataSource> from [DI](xref:fundamentals/dependency-injection).
The following code shows how to retrieve and inspect the endpoint matching the current request:
[!code-csharp[](routing/samples/3.x/RoutingSample/EndpointInspectorStartup.cs?name=snippet)]
The endpoint, if selected, can be retrieved from the `HttpContext`. Its properties can be inspected. Endpoint objects are immutable and cannot be modified after creation. The most common type of endpoint is a <xref:Microsoft.AspNetCore.Routing.RouteEndpoint>. `RouteEndpoint` includes information that allows it to be to selected by the routing system.
In the preceding code, [app.Use](xref:Microsoft.AspNetCore.Builder.UseExtensions.Use*) configures an in-line [middleware](xref:fundamentals/middleware/index).
<a name="mt"></a>
The following code shows that, depending on where `app.Use` is called in the pipeline, there may not be an endpoint:
[!code-csharp[](routing/samples/3.x/RoutingSample/MiddlewareFlowStartup.cs?name=snippet)]
This preceding sample adds `Console.WriteLine` statements that display whether or not an endpoint has been selected. For clarity, the sample assigns a display name to the provided `/` endpoint.
Running this code with a URL of `/` displays:
```txt
1. Endpoint: (null)
2. Endpoint: Hello
3. Endpoint: Hello
```
Running this code with any other URL displays:
```txt
1. Endpoint: (null)
2. Endpoint: (null)
4. Endpoint: (null)
```
This output demonstrates that:
* The endpoint is always null before `UseRouting` is called.
* If a match is found, the endpoint is non-null between `UseRouting` and <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints*>.
* The `UseEndpoints` middleware is **terminal** when a match is found. [Terminal middleware](#tm) is defined later in this document.
* The middleware after `UseEndpoints` execute only when no match is found.
The `UseRouting` middleware uses the [SetEndpoint](xref:Microsoft.AspNetCore.Http.EndpointHttpContextExtensions.SetEndpoint*) method to attach the endpoint to the current context. It's possible to replace the `UseRouting` middleware with custom logic and still get the benefits of using endpoints. Endpoints are a low-level primitive like middleware, and aren't coupled to the routing implementation. Most apps don't need to replace `UseRouting` with custom logic.
The `UseEndpoints` middleware is designed to be used in tandem with the `UseRouting` middleware. The core logic to execute an endpoint isn't complicated. Use <xref:Microsoft.AspNetCore.Http.EndpointHttpContextExtensions.GetEndpoint*> to retrieve the endpoint, and then invoke its <xref:Microsoft.AspNetCore.Http.Endpoint.RequestDelegate> property.
The following code demonstrates how middleware can influence or react to routing:
[!code-csharp[](routing/samples/3.x/RoutingSample/IntegratedMiddlewareStartup.cs?name=snippet)]
The preceding example demonstrates two important concepts:
* Middleware can run before `UseRouting` to modify the data that routing operates upon.
* Usually middleware that appears before routing modifies some property of the request, such as <xref:Microsoft.AspNetCore.Builder.RewriteBuilderExtensions.UseRewriter*>, <xref:Microsoft.AspNetCore.Builder.HttpMethodOverrideExtensions.UseHttpMethodOverride*>, or <xref:Microsoft.AspNetCore.Builder.UsePathBaseExtensions.UsePathBase*>.
* Middleware can run between `UseRouting` and <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints*> to process the results of routing before the endpoint is executed.
* Middleware that runs between `UseRouting` and `UseEndpoints`:
* Usually inspects metadata to understand the endpoints.
* Often makes security decisions, as done by `UseAuthorization` and `UseCors`.
* The combination of middleware and metadata allows configuring policies per-endpoint.
The preceding code shows an example of a custom middleware that supports per-endpoint policies. The middleware writes an *audit log* of access to sensitive data to the console. The middleware can be configured to *audit* an endpoint with the `AuditPolicyAttribute` metadata. This sample demonstrates an *opt-in* pattern where only endpoints that are marked as sensitive are audited. It's possible to define this logic in reverse, auditing everything that isn't marked as safe, for example. The endpoint metadata system is flexible. This logic could be designed in whatever way suits the use case.
The preceding sample code is intended to demonstrate the basic concepts of endpoints. **The sample is not intended for production use**. A more complete version of an *audit log* middleware would:
* Log to a file or database.
* Include details such as the user, IP address, name of the sensitive endpoint, and more.
The audit policy metadata `AuditPolicyAttribute` is defined as an `Attribute` for easier use with class-based frameworks such as controllers and SignalR. When using *route to code*:
* Metadata is attached with a builder API.
* Class-based frameworks include all attributes on the corresponding method and class when creating endpoints.
The best practices for metadata types are to define them either as interfaces or attributes. Interfaces and attributes allow code reuse. The metadata system is flexible and doesn't impose any limitations.
<a name="tm"></a>
### Comparing a terminal middleware and routing
The following code sample contrasts using middleware with using routing:
[!code-csharp[](routing/samples/3.x/RoutingSample/TerminalMiddlewareStartup.cs?name=snippet)]
The style of middleware shown with `Approach 1:` is **terminal middleware**. It's called terminal middleware because it does a matching operation:
* The matching operation in the preceding sample is `Path == "/"` for the middleware and `Path == "/Movie"` for routing.
* When a match is successful, it executes some functionality and returns, rather than invoking the `next` middleware.
It's called terminal middleware because it terminates the search, executes some functionality, and then returns.
Comparing a terminal middleware and routing:
* Both approaches allow terminating the processing pipeline:
* Middleware terminates the pipeline by returning rather than invoking `next`.
* Endpoints are always terminal.
* Terminal middleware allows positioning the middleware at an arbitrary place in the pipeline:
* Endpoints execute at the position of <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints*>.
* Terminal middleware allows arbitrary code to determine when the middleware matches:
* Custom route matching code can be verbose and difficult to write correctly.
* Routing provides straightforward solutions for typical apps. Most apps don't require custom route matching code.
* Endpoints interface with middleware such as `UseAuthorization` and `UseCors`.
* Using a terminal middleware with `UseAuthorization` or `UseCors` requires manual interfacing with the authorization system.
An [endpoint](#endpoint) defines both:
* A delegate to process requests.
* A collection of arbitrary metadata. The metadata is used to implement cross-cutting concerns based on policies and configuration attached to each endpoint.
Terminal middleware can be an effective tool, but can require:
* A significant amount of coding and testing.
* Manual integration with other systems to achieve the desired level of flexibility.
Consider integrating with routing before writing a terminal middleware.
Existing terminal middleware that integrates with [Map](xref:fundamentals/middleware/index#branch-the-middleware-pipeline) or <xref:Microsoft.AspNetCore.Builder.MapWhenExtensions.MapWhen*> can usually be turned into a routing aware endpoint. [MapHealthChecks](https://github.com/aspnet/AspNetCore/blob/master/src/Middleware/HealthChecks/src/Builder/HealthCheckEndpointRouteBuilderExtensions.cs#L16) demonstrates the pattern for router-ware:
* Write an extension method on <xref:Microsoft.AspNetCore.Routing.IEndpointRouteBuilder>.
* Create a nested middleware pipeline using <xref:Microsoft.AspNetCore.Routing.IEndpointRouteBuilder.CreateApplicationBuilder*>.
* Attach the middleware to the new pipeline. In this case, <xref:Microsoft.AspNetCore.Builder.HealthCheckApplicationBuilderExtensions.UseHealthChecks*>.
* <xref:Microsoft.AspNetCore.Builder.IApplicationBuilder.Build*> the middleware pipeline into a <xref:Microsoft.AspNetCore.Http.RequestDelegate>.
* Call `Map` and provide the new middleware pipeline.
* Return the builder object provided by `Map` from the extension method.
The following code shows use of [MapHealthChecks](xref:host-and-deploy/health-checks):
[!code-csharp[](routing/samples/3.x/RoutingSample/AuthorizationStartup.cs?name=snippet)]
The preceding sample shows why returning the builder object is important. Returning the builder object allows the app developer to configure policies such as authorization for the endpoint. In this example, the health checks middleware has no direct integration with the authorization system.
The metadata system was created in response to the problems encountered by extensibility authors using terminal middleware. It's problematic for each middleware to implement its own integration with the authorization system.
<a name="urlm"></a>
### URL matching
* Is the process by which routing matches an incoming request to an [endpoint](#endpoint).
* Is based on data in the URL path and headers.
* Can be extended to consider any data in the request.
When a routing middleware executes, it sets an `Endpoint` and route values to a [request feature](xref:fundamentals/request-features) on the <xref:Microsoft.AspNetCore.Http.HttpContext> from the current request:
* Calling [HttpContext.GetEndpoint](<xref:Microsoft.AspNetCore.Http.EndpointHttpContextExtensions.GetEndpoint*>) gets the endpoint.
* `HttpRequest.RouteValues` gets the collection of route values.
[Middleware](xref:fundamentals/middleware/index) running after the routing middleware can inspect the endpoint and take action. For example, an authorization middleware can interrogate the endpoint's metadata collection for an authorization policy. After all of the middleware in the request processing pipeline is executed, the selected endpoint's delegate is invoked.
The routing system in endpoint routing is responsible for all dispatching decisions. Because the middleware applies policies based on the selected endpoint, it's important that:
* Any decision that can affect dispatching or the application of security policies is made inside the routing system.
> [!WARNING]
> For backwards-compatibility, when a Controller or Razor Pages endpoint delegate is executed, the properties of [RouteContext.RouteData](xref:Microsoft.AspNetCore.Routing.RouteContext.RouteData) are set to appropriate values based on the request processing performed thus far.
>
> The `RouteContext` type will be marked obsolete in a future release:
>
> * Migrate `RouteData.Values` to `HttpRequest.RouteValues`.
> * Migrate `RouteData.DataTokens` to retrieve [IDataTokensMetadata](xref:Microsoft.AspNetCore.Routing.IDataTokensMetadata) from the endpoint metadata.
URL matching operates in a configurable set of phases. In each phase, the output is a set of matches. The set of matches can be narrowed down further by the next phase. The routing implementation does not guarantee a processing order for matching endpoints. **All** possible matches are processed at once. The URL matching phases occur in the following order. ASP.NET Core:
1. Processes the URL path against the set of endpoints and their route templates, collecting **all** of the matches.
1. Takes the preceding list and removes matches that fail with route constraints applied.
1. Takes the preceding list and removes matches that fail the set of [MatcherPolicy](xref:Microsoft.AspNetCore.Routing.MatcherPolicy) instances.
1. Uses the [EndpointSelector](xref:Microsoft.AspNetCore.Routing.Matching.EndpointSelector) to make a final decision from the preceding list.
The list of endpoints is prioritized according to:
* The [RouteEndpoint.Order](xref:Microsoft.AspNetCore.Routing.RouteEndpoint.Order*)
* The [route template precedence](#rtp)
All matching endpoints are processed in each phase until the <xref:Microsoft.AspNetCore.Routing.Matching.EndpointSelector> is reached. The `EndpointSelector` is the final phase. It chooses the highest priority endpoint from the matches as the best match. If there are other matches with the same priority as the best match, an ambiguous match exception is thrown.
The route precedence is computed based on a **more specific** route template being given a higher priority. For example, consider the templates `/hello` and `/{message}`:
* Both match the URL path `/hello`.
* `/hello` is more specific and therefore higher priority.
In general, route precedence does a good job of choosing the best match for the kinds of URL schemes used in practice. Use <xref:Microsoft.AspNetCore.Routing.RouteEndpoint.Order> only when necessary to avoid an ambiguity.
Due to the kinds of extensibility provided by routing, it isn't possible for the routing system to compute ahead of time the ambiguous routes. Consider an example such as the route templates `/{message:alpha}` and `/{message:int}`:
* The `alpha` constraint matches only alphabetic characters.
* The `int` constraint matches only numbers.
* These templates have the same route precedence, but there's no single URL they both match.
* If the routing system reported an ambiguity error at startup, it would block this valid use case.
> [!WARNING]
>
> The order of operations inside <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints*> doesn't influence the behavior of routing, with one exception. <xref:Microsoft.AspNetCore.Builder.ControllerEndpointRouteBuilderExtensions.MapControllerRoute*> and <xref:Microsoft.AspNetCore.Builder.MvcAreaRouteBuilderExtensions.MapAreaRoute*> automatically assign an order value to their endpoints based on the order they are invoked. This simulates long-time behavior of controllers without the routing system providing the same guarantees as older routing implementations.
>
> In the legacy implementation of routing, it's possible to implement routing extensibility that has a dependency on the order in which routes are processed. Endpoint routing in ASP.NET Core 3.0 and later:
>
> * Doesn't have a concept of routes.
> * Doesn't provide ordering guarantees. All endpoints are processed at once.
>
> If this means you're stuck using the legacy routing system, [open a GitHub issue for assistance](https://github.com/dotnet/aspnetcore/issues).
<a name="rtp"></a>
### Route template precedence and endpoint selection order
[Route template precedence](https://github.com/dotnet/aspnetcore/blob/master/src/Http/Routing/src/Template/RoutePrecedence.cs#L16) is a system that assigns each route template a value based on how specific it is. Route template precedence:
* Avoids the need to adjust the order of endpoints in common cases.
* Attempts to match the common-sense expectations of routing behavior.
For example, consider templates `/Products/List` and `/Products/{id}`. It would be reasonable to assume that `/Products/List` is a better match than `/Products/{id}` for the URL path `/Products/List`. The works because the literal segment `/List` is considered to have better precedence than the parameter segment `/{id}`.
The details of how precedence works are coupled to how route templates are defined:
* Templates with more segments are considered more specific.
* A segment with literal text is considered more specific than a parameter segment.
* A parameter segment with a constraint is considered more specific than one without.
* A complex segment is considered as specific as a parameter segment with a constraint.
* Catch-all parameters are the least specific. See **catch-all** in the [Route template reference](#rtr) for important information on catch-all routes.
See the [source code on GitHub](https://github.com/dotnet/aspnetcore/blob/master/src/Http/Routing/src/Template/RoutePrecedence.cs#L189) for a reference of exact values.
<a name="lg"></a>
### URL generation concepts
URL generation:
* Is the process by which routing can create a URL path based on a set of route values.
* Allows for a logical separation between endpoints and the URLs that access them.
Endpoint routing includes the <xref:Microsoft.AspNetCore.Routing.LinkGenerator> API. `LinkGenerator` is a singleton service available from [DI](xref:fundamentals/dependency-injection). The `LinkGenerator` API can be used outside of the context of an executing request. [Mvc.IUrlHelper](xref:Microsoft.AspNetCore.Mvc.IUrlHelper) and scenarios that rely on <xref:Microsoft.AspNetCore.Mvc.IUrlHelper>, such as [Tag Helpers](xref:mvc/views/tag-helpers/intro), HTML Helpers, and [Action Results](xref:mvc/controllers/actions), use the `LinkGenerator` API internally to provide link generating capabilities.
The link generator is backed by the concept of an **address** and **address schemes**. An address scheme is a way of determining the endpoints that should be considered for link generation. For example, the route name and route values scenarios many users are familiar with from controllers and Razor Pages are implemented as an address scheme.
The link generator can link to controllers and Razor Pages via the following extension methods:
* <xref:Microsoft.AspNetCore.Routing.ControllerLinkGeneratorExtensions.GetPathByAction*>
* <xref:Microsoft.AspNetCore.Routing.ControllerLinkGeneratorExtensions.GetUriByAction*>
* <xref:Microsoft.AspNetCore.Routing.PageLinkGeneratorExtensions.GetPathByPage*>
* <xref:Microsoft.AspNetCore.Routing.PageLinkGeneratorExtensions.GetUriByPage*>
Overloads of these methods accept arguments that include the `HttpContext`. These methods are functionally equivalent to [Url.Action](xref:System.Web.Mvc.UrlHelper.Action*) and [Url.Page](xref:Microsoft.AspNetCore.Mvc.UrlHelperExtensions.Page*), but offer additional flexibility and options.
The `GetPath*` methods are most similar to `Url.Action` and `Url.Page`, in that they generate a URI containing an absolute path. The `GetUri*` methods always generate an absolute URI containing a scheme and host. The methods that accept an `HttpContext` generate a URI in the context of the executing request. The [ambient](#ambient) route values, URL base path, scheme, and host from the executing request are used unless overridden.
<xref:Microsoft.AspNetCore.Routing.LinkGenerator> is called with an address. Generating a URI occurs in two steps:
1. An address is bound to a list of endpoints that match the address.
1. Each endpoint's <xref:Microsoft.AspNetCore.Routing.RouteEndpoint.RoutePattern> is evaluated until a route pattern that matches the supplied values is found. The resulting output is combined with the other URI parts supplied to the link generator and returned.
The methods provided by <xref:Microsoft.AspNetCore.Routing.LinkGenerator> support standard link generation capabilities for any type of address. The most convenient way to use the link generator is through extension methods that perform operations for a specific address type:
| Extension Method | Description |
| ---------------- | ----------- |
| <xref:Microsoft.AspNetCore.Routing.LinkGenerator.GetPathByAddress*> | Generates a URI with an absolute path based on the provided values. |
| <xref:Microsoft.AspNetCore.Routing.LinkGenerator.GetUriByAddress*> | Generates an absolute URI based on the provided values. |
> [!WARNING]
> Pay attention to the following implications of calling <xref:Microsoft.AspNetCore.Routing.LinkGenerator> methods:
>
> * Use `GetUri*` extension methods with caution in an app configuration that doesn't validate the `Host` header of incoming requests. If the `Host` header of incoming requests isn't validated, untrusted request input can be sent back to the client in URIs in a view or page. We recommend that all production apps configure their server to validate the `Host` header against known valid values.
>
> * Use <xref:Microsoft.AspNetCore.Routing.LinkGenerator> with caution in middleware in combination with `Map` or `MapWhen`. `Map*` changes the base path of the executing request, which affects the output of link generation. All of the <xref:Microsoft.AspNetCore.Routing.LinkGenerator> APIs allow specifying a base path. Specify an empty base path to undo the `Map*` affect on link generation.
### Middleware example
In the following example, a middleware uses the <xref:Microsoft.AspNetCore.Routing.LinkGenerator> API to create a link to an action method that lists store products. Using the link generator by injecting it into a class and calling `GenerateLink` is available to any class in an app:
[!code-csharp[](routing/samples/3.x/RoutingSample/Middleware/ProductsLinkMiddleware.cs?name=snippet)]
<a name="rtr"></a>
## Route template reference
Tokens within `{}` define route parameters that are bound if the route is matched. More than one route parameter can be defined in a route segment, but route parameters must be separated by a literal value. For example, `{controller=Home}{action=Index}` isn't a valid route, since there's no literal value between `{controller}` and `{action}`. Route parameters must have a name and may have additional attributes specified.
Literal text other than route parameters (for example, `{id}`) and the path separator `/` must match the text in the URL. Text matching is case-insensitive and based on the decoded representation of the URL's path. To match a literal route parameter delimiter `{` or `}`, escape the delimiter by repeating the character. For example `{{` or `}}`.
Asterisk `*` or double asterisk `**`:
* Can be used as a prefix to a route parameter to bind to the rest of the URI.
* Are called a **catch-all** parameters. For example, `blog/{**slug}`:
* Matches any URI that starts with `/blog` and has any value following it.
* The value following `/blog` is assigned to the [slug](https://developer.mozilla.org/docs/Glossary/Slug) route value.
[!INCLUDE[](~/includes/catchall.md)]
Catch-all parameters can also match the empty string.
The catch-all parameter escapes the appropriate characters when the route is used to generate a URL, including path separator `/` characters. For example, the route `foo/{*path}` with route values `{ path = "my/path" }` generates `foo/my%2Fpath`. Note the escaped forward slash. To round-trip path separator characters, use the `**` route parameter prefix. The route `foo/{**path}` with `{ path = "my/path" }` generates `foo/my/path`.
URL patterns that attempt to capture a file name with an optional file extension have additional considerations. For example, consider the template `files/{filename}.{ext?}`. When values for both `filename` and `ext` exist, both values are populated. If only a value for `filename` exists in the URL, the route matches because the trailing `.` is optional. The following URLs match this route:
* `/files/myFile.txt`
* `/files/myFile`
Route parameters may have **default values** designated by specifying the default value after the parameter name separated by an equals sign (`=`). For example, `{controller=Home}` defines `Home` as the default value for `controller`. The default value is used if no value is present in the URL for the parameter. Route parameters are made optional by appending a question mark (`?`) to the end of the parameter name. For example, `id?`. The difference between optional values and default route parameters is:
* A route parameter with a default value always produces a value.
* An optional parameter has a value only when a value is provided by the request URL.
Route parameters may have constraints that must match the route value bound from the URL. Adding `:` and constraint name after the route parameter name specifies an inline constraint on a route parameter. If the constraint requires arguments, they're enclosed in parentheses `(...)` after the constraint name. Multiple *inline constraints* can be specified by appending another `:` and constraint name.
The constraint name and arguments are passed to the <xref:Microsoft.AspNetCore.Routing.IInlineConstraintResolver> service to create an instance of <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> to use in URL processing. For example, the route template `blog/{article:minlength(10)}` specifies a `minlength` constraint with the argument `10`. For more information on route constraints and a list of the constraints provided by the framework, see the [Route constraint reference](#route-constraint-reference) section.
Route parameters may also have parameter transformers. Parameter transformers transform a parameter's value when generating links and matching actions and pages to URLs. Like constraints, parameter transformers can be added inline to a route parameter by adding a `:` and transformer name after the route parameter name. For example, the route template `blog/{article:slugify}` specifies a `slugify` transformer. For more information on parameter transformers, see the [Parameter transformer reference](#parameter-transformer-reference) section.
The following table demonstrates example route templates and their behavior:
| Route Template | Example Matching URI | The request URI… |
| ---------------------------------------- | ----------------------- | -------------------------------------------------------------------------- |
| `hello` | `/hello` | Only matches the single path `/hello`. |
| `{Page=Home}` | `/` | Matches and sets `Page` to `Home`. |
| `{Page=Home}` | `/Contact` | Matches and sets `Page` to `Contact`. |
| `{controller}/{action}/{id?}` | `/Products/List` | Maps to the `Products` controller and `List` action. |
| `{controller}/{action}/{id?}` | `/Products/Details/123` | Maps to the `Products` controller and `Details` action with`id` set to 123. |
| `{controller=Home}/{action=Index}/{id?}` | `/` | Maps to the `Home` controller and `Index` method. `id` is ignored. |
| `{controller=Home}/{action=Index}/{id?}` | `/Products` | Maps to the `Products` controller and `Index` method. `id` is ignored. |
Using a template is generally the simplest approach to routing. Constraints and defaults can also be specified outside the route template.
### Complex segments
Complex segments are processed by matching up literal delimiters from right to left in a [non-greedy](#greedy) way. For example, `[Route("/a{b}c{d}")]` is a complex segment.
Complex segments work in a particular way that must be understood to use them successfully. The example in this section demonstrates why complex segments only really work well when the delimiter text doesn't appear inside the parameter values. Using a [regex](/dotnet/standard/base-types/regular-expressions) and then manually extracting the values is needed for more complex cases.
[!INCLUDE[](~/includes/regex.md)]
This is a summary of the steps that routing performs with the template `/a{b}c{d}` and the URL path `/abcd`. The `|` is used to help visualize how the algorithm works:
* The first literal, right to left, is `c`. So `/abcd` is searched from right and finds `/ab|c|d`.
* Everything to the right (`d`) is now matched to the route parameter `{d}`.
* The next literal, right to left, is `a`. So `/ab|c|d` is searched starting where we left off, then `a` is found `/|a|b|c|d`.
* The value to the right (`b`) is now matched to the route parameter `{b}`.
* There is no remaining text and no remaining route template, so this is a match.
Here's an example of a negative case using the same template `/a{b}c{d}` and the URL path `/aabcd`. The `|` is used to help visualize how the algorithm works. This case isn't a match, which is explained by the same algorithm:
* The first literal, right to left, is `c`. So `/aabcd` is searched from right and finds `/aab|c|d`.
* Everything to the right (`d`) is now matched to the route parameter `{d}`.
* The next literal, right to left, is `a`. So `/aab|c|d` is searched starting where we left off, then `a` is found `/a|a|b|c|d`.
* The value to the right (`b`) is now matched to the route parameter `{b}`.
* At this point there is remaining text `a`, but the algorithm has run out of route template to parse, so this is not a match.
Since the matching algorithm is [non-greedy](#greedy):
* It matches the smallest amount of text possible in each step.
* Any case where the delimiter value appears inside the parameter values results in not matching.
Regular expressions provide much more control over their matching behavior.
<a name="greedy"></a>
Greedy matching, also know as [lazy matching](https://wikipedia.org/wiki/Regular_expression#Lazy_matching), matches the largest possible string. Non-greedy matches the smallest possible string.
## Route constraint reference
Route constraints execute when a match has occurred to the incoming URL and the URL path is tokenized into route values. Route constraints generally inspect the route value associated via the route template and make a true or false decision about whether the value is acceptable. Some route constraints use data outside the route value to consider whether the request can be routed. For example, the <xref:Microsoft.AspNetCore.Routing.Constraints.HttpMethodRouteConstraint> can accept or reject a request based on its HTTP verb. Constraints are used in routing requests and link generation.
> [!WARNING]
> Don't use constraints for input validation. If constraints are used for input validation, invalid input results in a `404` Not Found response. Invalid input should produce a `400` Bad Request with an appropriate error message. Route constraints are used to disambiguate similar routes, not to validate the inputs for a particular route.
The following table demonstrates example route constraints and their expected behavior:
| constraint | Example | Example Matches | Notes |
| ---------- | ------- | --------------- | ----- |
| `int` | `{id:int}` | `123456789`, `-123456789` | Matches any integer |
| `bool` | `{active:bool}` | `true`, `FALSE` | Matches `true` or `false`. Case-insensitive |
| `datetime` | `{dob:datetime}` | `2016-12-31`, `2016-12-31 7:32pm` | Matches a valid `DateTime` value in the invariant culture. See preceding warning. |
| `decimal` | `{price:decimal}` | `49.99`, `-1,000.01` | Matches a valid `decimal` value in the invariant culture. See preceding warning.|
| `double` | `{weight:double}` | `1.234`, `-1,001.01e8` | Matches a valid `double` value in the invariant culture. See preceding warning.|
| `float` | `{weight:float}` | `1.234`, `-1,001.01e8` | Matches a valid `float` value in the invariant culture. See preceding warning.|
| `guid` | `{id:guid}` | `CD2C1638-1638-72D5-1638-DEADBEEF1638` | Matches a valid `Guid` value |
| `long` | `{ticks:long}` | `123456789`, `-123456789` | Matches a valid `long` value |
| `minlength(value)` | `{username:minlength(4)}` | `Rick` | String must be at least 4 characters |
| `maxlength(value)` | `{filename:maxlength(8)}` | `MyFile` | String must be no more than 8 characters |
| `length(length)` | `{filename:length(12)}` | `somefile.txt` | String must be exactly 12 characters long |
| `length(min,max)` | `{filename:length(8,16)}` | `somefile.txt` | String must be at least 8 and no more than 16 characters long |
| `min(value)` | `{age:min(18)}` | `19` | Integer value must be at least 18 |
| `max(value)` | `{age:max(120)}` | `91` | Integer value must be no more than 120 |
| `range(min,max)` | `{age:range(18,120)}` | `91` | Integer value must be at least 18 but no more than 120 |
| `alpha` | `{name:alpha}` | `Rick` | String must consist of one or more alphabetical characters, `a`-`z` and case-insensitive. |
| `regex(expression)` | `{ssn:regex(^\\d{{3}}-\\d{{2}}-\\d{{4}}$)}` | `123-45-6789` | String must match the regular expression. See tips about defining a regular expression. |
| `required` | `{name:required}` | `Rick` | Used to enforce that a non-parameter value is present during URL generation |
[!INCLUDE[](~/includes/regex.md)]
Multiple, colon delimited constraints can be applied to a single parameter. For example, the following constraint restricts a parameter to an integer value of 1 or greater:
```csharp
[Route("users/{id:int:min(1)}")]
public User GetUserById(int id) { }
```
> [!WARNING]
> Route constraints that verify the URL and are converted to a CLR type always use the invariant culture. For example, conversion to the CLR type `int` or `DateTime`. These constraints assume that the URL is not localizable. The framework-provided route constraints don't modify the values stored in route values. All route values parsed from the URL are stored as strings. For example, the `float` constraint attempts to convert the route value to a float, but the converted value is used only to verify it can be converted to a float.
### Regular expressions in constraints
[!INCLUDE[](~/includes/regex.md)]
Regular expressions can be specified as inline constraints using the `regex(...)` route constraint. Methods in the <xref:Microsoft.AspNetCore.Builder.ControllerEndpointRouteBuilderExtensions.MapControllerRoute*> family also accept an object literal of constraints. If that form is used, string values are interpreted as regular expressions.
The following code uses an inline regex constraint:
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupRegex.cs?name=snippet)]
The following code uses an object literal to specify a regex constraint:
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupRegex2.cs?name=snippet)]
The ASP.NET Core framework adds `RegexOptions.IgnoreCase | RegexOptions.Compiled | RegexOptions.CultureInvariant` to the regular expression constructor. See <xref:System.Text.RegularExpressions.RegexOptions> for a description of these members.
Regular expressions use delimiters and tokens similar to those used by routing and the C# language. Regular expression tokens must be escaped. To use the regular expression `^\d{3}-\d{2}-\d{4}$` in an inline constraint, use one of the following:
* Replace `\` characters provided in the string as `\\` characters in the C# source file in order to escape the `\` string escape character.
* [Verbatim string literals](/dotnet/csharp/language-reference/keywords/string).
To escape routing parameter delimiter characters `{`, `}`, `[`, `]`, double the characters in the expression, for example, `{{`, `}}`, `[[`, `]]`. The following table shows a regular expression and its escaped version:
| Regular expression | Escaped regular expression |
| --------------------- | ------------------------------ |
| `^\d{3}-\d{2}-\d{4}$` | `^\\d{{3}}-\\d{{2}}-\\d{{4}}$` |
| `^[a-z]{2}$` | `^[[a-z]]{{2}}$` |
Regular expressions used in routing often start with the `^` character and match the starting position of the string. The expressions often end with the `$` character and match the end of the string. The `^` and `$` characters ensure that the regular expression matches the entire route parameter value. Without the `^` and `$` characters, the regular expression matches any substring within the string, which is often undesirable. The following table provides examples and explains why they match or fail to match:
| Expression | String | Match | Comment |
| ------------ | --------- | :---: | -------------------- |
| `[a-z]{2}` | hello | Yes | Substring matches |
| `[a-z]{2}` | 123abc456 | Yes | Substring matches |
| `[a-z]{2}` | mz | Yes | Matches expression |
| `[a-z]{2}` | MZ | Yes | Not case sensitive |
| `^[a-z]{2}$` | hello | No | See `^` and `$` above |
| `^[a-z]{2}$` | 123abc456 | No | See `^` and `$` above |
For more information on regular expression syntax, see [.NET Framework Regular Expressions](/dotnet/standard/base-types/regular-expression-language-quick-reference).
To constrain a parameter to a known set of possible values, use a regular expression. For example, `{action:regex(^(list|get|create)$)}` only matches the `action` route value to `list`, `get`, or `create`. If passed into the constraints dictionary, the string `^(list|get|create)$` is equivalent. Constraints that are passed in the constraints dictionary that don't match one of the known constraints are also treated as regular expressions. Constraints that are passed within a template that don't match one of the known constraints are not treated as regular expressions.
### Custom route constraints
Custom route constraints can be created by implementing the <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> interface. The `IRouteConstraint` interface contains <xref:System.Web.Routing.IRouteConstraint.Match*>, which returns `true` if the constraint is satisfied and `false` otherwise.
Custom route constraints are rarely needed. Before implementing a custom route constraint, consider alternatives, such as model binding.
The ASP.NET Core [Constraints](https://github.com/dotnet/aspnetcore/tree/master/src/Http/Routing/src/Constraints) folder provides good examples of creating a constraints. For example, [GuidRouteConstraint](https://github.com/dotnet/aspnetcore/blob/master/src/Http/Routing/src/Constraints/GuidRouteConstraint.cs#L18).
To use a custom `IRouteConstraint`, the route constraint type must be registered with the app's <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap> in the service container. A `ConstraintMap` is a dictionary that maps route constraint keys to `IRouteConstraint` implementations that validate those constraints. An app's `ConstraintMap` can be updated in `Startup.ConfigureServices` either as part of a [services.AddRouting](xref:Microsoft.Extensions.DependencyInjection.RoutingServiceCollectionExtensions.AddRouting*) call or by configuring <xref:Microsoft.AspNetCore.Routing.RouteOptions> directly with `services.Configure<RouteOptions>`. For example:
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupConstraint.cs?name=snippet)]
The preceding constraint is applied in the following code:
[!code-csharp[](routing/samples/3.x/RoutingSample/Controllers/TestController.cs?name=snippet&highlight=6,13)]
[!INCLUDE[](~/includes/MyDisplayRouteInfo.md)]
The implementation of `MyCustomConstraint` prevents `0` being applied to a route parameter:
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupConstraint.cs?name=snippet2)]
[!INCLUDE[](~/includes/regex.md)]
The preceding code:
* Prevents `0` in the `{id}` segment of the route.
* Is shown to provide a basic example of implementing a custom constraint. It should not be used in a production app.
The following code is a better approach to preventing an `id` containing a `0` from being processed:
[!code-csharp[](routing/samples/3.x/RoutingSample/Controllers/TestController.cs?name=snippet2)]
The preceding code has the following advantages over the `MyCustomConstraint` approach:
* It doesn't require a custom constraint.
* It returns a more descriptive error when the route parameter includes `0`.
## Parameter transformer reference
Parameter transformers:
* Execute when generating a link using <xref:Microsoft.AspNetCore.Routing.LinkGenerator>.
* Implement <xref:Microsoft.AspNetCore.Routing.IOutboundParameterTransformer?displayProperty=fullName>.
* Are configured using <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap>.
* Take the parameter's route value and transform it to a new string value.
* Result in using the transformed value in the generated link.
For example, a custom `slugify` parameter transformer in route pattern `blog\{article:slugify}` with `Url.Action(new { article = "MyTestArticle" })` generates `blog\my-test-article`.
Consider the following `IOutboundParameterTransformer` implementation:
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupConstraint2.cs?name=snippet2)]
To use a parameter transformer in a route pattern, configure it using <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap> in `Startup.ConfigureServices`:
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupConstraint2.cs?name=snippet)]
The ASP.NET Core framework uses parameter transformers to transform the URI where an endpoint resolves. For example, parameter transformers transform the route values used to match an `area`, `controller`, `action`, and `page`.
```csharp
routes.MapControllerRoute(
name: "default",
template: "{controller:slugify=Home}/{action:slugify=Index}/{id?}");
```
With the preceding route template, the action `SubscriptionManagementController.GetAll` is matched with the URI `/subscription-management/get-all`. A parameter transformer doesn't change the route values used to generate a link. For example, `Url.Action("GetAll", "SubscriptionManagement")` outputs `/subscription-management/get-all`.
ASP.NET Core provides API conventions for using parameter transformers with generated routes:
* The <xref:Microsoft.AspNetCore.Mvc.ApplicationModels.RouteTokenTransformerConvention?displayProperty=fullName> MVC convention applies a specified parameter transformer to all attribute routes in the app. The parameter transformer transforms attribute route tokens as they are replaced. For more information, see [Use a parameter transformer to customize token replacement](xref:mvc/controllers/routing#use-a-parameter-transformer-to-customize-token-replacement).
* Razor Pages uses the <xref:Microsoft.AspNetCore.Mvc.ApplicationModels.PageRouteTransformerConvention> API convention. This convention applies a specified parameter transformer to all automatically discovered Razor Pages. The parameter transformer transforms the folder and file name segments of Razor Pages routes. For more information, see [Use a parameter transformer to customize page routes](xref:razor-pages/razor-pages-conventions#use-a-parameter-transformer-to-customize-page-routes).
<a name="ugr"></a>
## URL generation reference
This section contains a reference for the algorithm implemented by URL generation. In practice, most complex examples of URL generation use controllers or Razor Pages. See [routing in controllers](xref:mvc/controllers/routing) for additional information.
The URL generation process begins with a call to [LinkGenerator.GetPathByAddress](xref:Microsoft.AspNetCore.Routing.LinkGenerator.GetPathByAddress*) or a similar method. The method is provided with an address, a set of route values, and optionally information about the current request from `HttpContext`.
The first step is to use the address to resolve a set of candidate endpoints using an [`IEndpointAddressScheme<TAddress>`](xref:Microsoft.AspNetCore.Routing.IEndpointAddressScheme`1) that matches the address's type.
Once of set of candidates is found by the address scheme, the endpoints are ordered and processed iteratively until a URL generation operation succeeds. URL generation does **not** check for ambiguities, the first result returned is the final result.
### Troubleshooting URL generation with logging
The first step in troubleshooting URL generation is setting the logging level of `Microsoft.AspNetCore.Routing` to `TRACE`. `LinkGenerator` logs many details about its processing which can be useful to troubleshoot problems.
See [URL generation reference](#ugr) for details on URL generation.
### Addresses
Addresses are the concept in URL generation used to bind a call into the link generator to a set of candidate endpoints.
Addresses are an extensible concept that come with two implementations by default:
* Using *endpoint name* (`string`) as the address:
* Provides similar functionality to MVC's route name.
* Uses the <xref:Microsoft.AspNetCore.Routing.IEndpointNameMetadata> metadata type.
* Resolves the provided string against the metadata of all registered endpoints.
* Throws an exception on startup if multiple endpoints use the same name.
* Recommended for general-purpose use outside of controllers and Razor Pages.
* Using *route values* (<xref:Microsoft.AspNetCore.Routing.RouteValuesAddress>) as the address:
* Provides similar functionality to controllers and Razor Pages legacy URL generation.
* Very complex to extend and debug.
* Provides the implementation used by `IUrlHelper`, Tag Helpers, HTML Helpers, Action Results, etc.
The role of the address scheme is to make the association between the address and matching endpoints by arbitrary criteria:
* The endpoint name scheme performs a basic dictionary lookup.
* The route values scheme has a complex best subset of set algorithm.
<a name="ambient"></a>
### Ambient values and explicit values
From the current request, routing accesses the route values of the current request `HttpContext.Request.RouteValues`. The values associated with the current request are referred to as the **ambient values**. For the purpose of clarity, the documentation refers to the route values passed in to methods as **explicit values**.
The following example shows ambient values and explicit values. It provides ambient values from the current request and explicit values: `{ id = 17, }`:
[!code-csharp[](routing/samples/3.x/RoutingSample/Controllers/WidgetController.cs?name=snippet)]
The preceding code:
* Returns `/Widget/Index/17`
* Gets <xref:Microsoft.AspNetCore.Routing.LinkGenerator> via [DI](xref:fundamentals/dependency-injection).
The following code provides no ambient values and explicit values: `{ controller = "Home", action = "Subscribe", id = 17, }`:
[!code-csharp[](routing/samples/3.x/RoutingSample/Controllers/WidgetController.cs?name=snippet2)]
The preceding method returns `/Home/Subscribe/17`
The following code in the `WidgetController` returns `/Widget/Subscribe/17`:
[!code-csharp[](routing/samples/3.x/RoutingSample/Controllers/WidgetController.cs?name=snippet3)]
The following code provides the controller from ambient values in the current request and explicit values: `{ action = "Edit", id = 17, }`:
[!code-csharp[](routing/samples/3.x/RoutingSample/Controllers/GadgetController.cs?name=snippet)]
In the preceding code:
* `/Gadget/Edit/17` is returned.
* <xref:Microsoft.AspNetCore.Mvc.ControllerBase.Url> gets the <xref:Microsoft.AspNetCore.Mvc.IUrlHelper>.
* <xref:Microsoft.AspNetCore.Mvc.UrlHelperExtensions.Action*>
generates a URL with an absolute path for an action method. The URL contains the specified `action` name and `route` values.
The following code provides ambient values from the current request and explicit values: `{ page = "./Edit, id = 17, }`:
[!code-csharp[](routing/samples/3.x/RoutingSample/Pages/Index.cshtml.cs?name=snippet)]
The preceding code sets `url` to `/Edit/17` when the Edit Razor Page contains the following page directive:
`@page "{id:int}"`
If the Edit page doesn't contain the `"{id:int}"` route template, `url` is `/Edit?id=17`.
The behavior of MVC's <xref:Microsoft.AspNetCore.Mvc.IUrlHelper> adds a layer of complexity in addition to the rules described here:
* `IUrlHelper` always provides the route values from the current request as ambient values.
* [IUrlHelper.Action](xref:Microsoft.AspNetCore.Mvc.UrlHelperExtensions.Action*) always copies the current `action` and `controller` route values as explicit values unless overridden by the developer.
* [IUrlHelper.Page](xref:Microsoft.AspNetCore.Mvc.UrlHelperExtensions.Page*) always copies the current `page` route value as an explicit value unless overridden. <!--by the user-->
* `IUrlHelper.Page` always overrides the current `handler` route value with `null` as an explicit values unless overridden.
Users are often surprised by the behavioral details of ambient values, because MVC doesn't seem to follow its own rules. For historical and compatibility reasons, certain route values such as `action`, `controller`, `page`, and `handler` have their own special-case behavior.
The equivalent functionality provided by `LinkGenerator.GetPathByAction` and `LinkGenerator.GetPathByPage` duplicates these anomalies of `IUrlHelper` for compatibility.
### URL generation process
Once the set of candidate endpoints are found, the URL generation algorithm:
* Processes the endpoints iteratively.
* Returns the first successful result.
The first step in this process is called **route value invalidation**. Route value invalidation is the process by which routing decides which route values from the ambient values should be used and which should be ignored. Each ambient value is considered and either combined with the explicit values, or ignored.
The best way to think about the role of ambient values is that they attempt to save application developers typing, in some common cases. Traditionally, the scenarios where ambient values are helpful are related to MVC:
* When linking to another action in the same controller, the controller name doesn't need to be specified.
* When linking to another controller in the same area, the area name doesn't need to be specified.
* When linking to the same action method, route values don't need to be specified.
* When linking to another part of the app, you don't want to carry over route values that have no meaning in that part of the app.
Calls to `LinkGenerator` or `IUrlHelper` that return `null` are usually caused by not understanding route value invalidation. Troubleshoot route value invalidation by explicitly specifying more of the route values to see if that solves the problem.
Route value invalidation works on the assumption that the app's URL scheme is hierarchical, with a hierarchy formed from left-to-right. Consider the basic controller route template `{controller}/{action}/{id?}` to get an intuitive sense of how this works in practice. A **change** to a value **invalidates** all of the route values that appear to the right. This reflects the assumption about hierarchy. If the app has an ambient value for `id`, and the operation specifies a different value for the `controller`:
* `id` won't be reused because `{controller}` is to the left of `{id?}`.
Some examples demonstrating this principle:
* If the explicit values contain a value for `id`, the ambient value for `id` is ignored. The ambient values for `controller` and `action` can be used.
* If the explicit values contain a value for `action`, any ambient value for `action` is ignored. The ambient values for `controller` can be used. If the explicit value for `action` is different from the ambient value for `action`, the `id` value won't be used. If the explicit value for `action` is the same as the ambient value for `action`, the `id` value can be used.
* If the explicit values contain a value for `controller`, any ambient value for `controller` is ignored. If the explicit value for `controller` is different from the ambient value for `controller`, the `action` and `id` values won't be used. If the explicit value for `controller` is the same as the ambient value for `controller`, the `action` and `id` values can be used.
This process is further complicated by the existence of attribute routes and dedicated conventional routes. Controller conventional routes such as `{controller}/{action}/{id?}` specify a hierarchy using route parameters. For [dedicated conventional routes](xref:mvc/controllers/routing#dcr) and [attribute routes](xref:mvc/controllers/routing#ar) to controllers and Razor Pages:
* There is a hierarchy of route values.
* They don't appear in the template.
For these cases, URL generation defines the **required values** concept. Endpoints created by controllers and Razor Pages have required values specified that allow route value invalidation to work.
The route value invalidation algorithm in detail:
* The required value names are combined with the route parameters, then processed from left-to-right.
* For each parameter, the ambient value and explicit value are compared:
* If the ambient value and explicit value are the same, the process continues.
* If the ambient value is present and the explicit value isn't, the ambient value is used when generating the URL.
* If the ambient value isn't present and the explicit value is, reject the ambient value and all subsequent ambient values.
* If the ambient value and the explicit value are present, and the two values are different, reject the ambient value and all subsequent ambient values.
At this point, the URL generation operation is ready to evaluate route constraints. The set of accepted values is combined with the parameter default values, which is provided to constraints. If the constraints all pass, the operation continues.
Next, the **accepted values** can be used to expand the route template. The route template is processed:
* From left-to-right.
* Each parameter has its accepted value substituted.
* With the following special cases:
* If the accepted values is missing a value and the parameter has a default value, the default value is used.
* If the accepted values is missing a value and the parameter is optional, processing continues.
* If any route parameter to the right of a missing optional parameter has a value, the operation fails.
* <!-- review default-valued parameters optional parameters --> Contiguous default-valued parameters and optional parameters are collapsed where possible.
Values explicitly provided that don't match a segment of the route are added to the query string. The following table shows the result when using the route template `{controller}/{action}/{id?}`.
| Ambient Values | Explicit Values | Result |
| ---------------------------------- | -------------------------------------- | ----------------------- |
| controller = "Home" | action = "About" | `/Home/About` |
| controller = "Home" | controller = "Order", action = "About" | `/Order/About` |
| controller = "Home", color = "Red" | action = "About" | `/Home/About` |
| controller = "Home" | action = "About", color = "Red" | `/Home/About?color=Red` |
### Problems with route value invalidation
As of ASP.NET Core 3.0, some URL generation schemes used in earlier ASP.NET Core versions don't work well with URL generation. The ASP.NET Core team plans to add features to address these needs in a future release. For now the best solution is to use legacy routing.
The following code shows an example of a URL generation scheme that's not supported by routing.
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupUnsupported.cs?name=snippet)]
In the preceding code, the `culture` route parameter is used for localization. The desire is to have the `culture` parameter always accepted as an ambient value. However, the `culture` parameter is not accepted as an ambient value because of the way required values work:
* In the `"default"` route template, the `culture` route parameter is to the left of `controller`, so changes to `controller` won't invalidate `culture`.
* In the `"blog"` route template, the `culture` route parameter is considered to be to the right of `controller`, which appears in the required values.
## Configuring endpoint metadata
The following links provide information on configuring endpoint metadata:
* [Enable Cors with endpoint routing](xref:security/cors#enable-cors-with-endpoint-routing)
* [IAuthorizationPolicyProvider sample](https://github.com/dotnet/AspNetCore/tree/release/3.1/src/Security/samples/CustomPolicyProvider) using a custom `[MinimumAgeAuthorize]` attribute
* [Test authentication with the [Authorize] attribute](xref:security/authentication/identity#test-identity)
* <xref:Microsoft.AspNetCore.Builder.AuthorizationEndpointConventionBuilderExtensions.RequireAuthorization*>
* [Selecting the scheme with the [Authorize] attribute](xref:security/authorization/limitingidentitybyscheme#selecting-the-scheme-with-the-authorize-attribute)
* [Apply policies using the [Authorize] attribute](xref:security/authorization/policies#apply-policies-to-mvc-controllers)
* <xref:security/authorization/roles>
<a name="hostmatch"></a>
## Host matching in routes with RequireHost
<xref:Microsoft.AspNetCore.Builder.RoutingEndpointConventionBuilderExtensions.RequireHost*> applies a constraint to the route which requires the specified host. The `RequireHost` or [[Host]](xref:Microsoft.AspNetCore.Routing.HostAttribute) parameter can be:
* Host: `www.domain.com`, matches `www.domain.com` with any port.
* Host with wildcard: `*.domain.com`, matches `www.domain.com`, `subdomain.domain.com`, or `www.subdomain.domain.com` on any port.
* Port: `*:5000`, matches port 5000 with any host.
* Host and port: `www.domain.com:5000` or `*.domain.com:5000`, matches host and port.
Multiple parameters can be specified using `RequireHost` or `[Host]`. The constraint matches hosts valid for any of the parameters. For example, `[Host("domain.com", "*.domain.com")]` matches `domain.com`, `www.domain.com`, and `subdomain.domain.com`.
The following code uses `RequireHost` to require the specified host on the route:
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupRequireHost.cs?name=snippet)]
The following code uses the `[Host]` attribute on the controller to require any of the specified hosts:
[!code-csharp[](routing/samples/3.x/RoutingSample/Controllers/ProductController.cs?name=snippet)]
When the `[Host]` attribute is applied to both the controller and action method:
* The attribute on the action is used.
* The controller attribute is ignored.
## Performance guidance for routing
Most of routing was updated in ASP.NET Core 3.0 to increase performance.
When an app has performance problems, routing is often suspected as the problem. The reason routing is suspected is that frameworks like controllers and Razor Pages report the amount of time spent inside the framework in their logging messages. When there's a significant difference between the time reported by controllers and the total time of the request:
* Developers eliminate their app code as the source of the problem.
* It's common to assume routing is the cause.
Routing is performance tested using thousands of endpoints. It's unlikely that a typical app will encounter a performance problem just by being too large. The most common root cause of slow routing performance is usually a badly-behaving custom middleware.
This following code sample demonstrates a basic technique for narrowing down the source of delay:
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupDelay.cs?name=snippet)]
To time routing:
* Interleave each middleware with a copy of the timing middleware shown in the preceding code.
* Add a unique identifier to correlate the timing data with the code.
This is a basic way to narrow down the delay when it's significant, for example, more than `10ms`. Subtracting `Time 2` from `Time 1` reports the time spent inside the `UseRouting` middleware.
The following code uses a more compact approach to the preceding timing code:
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupSW.cs?name=snippetSW)]
[!code-csharp[](routing/samples/3.x/RoutingSample/StartupSW.cs?name=snippet)]
### Potentially expensive routing features
The following list provides some insight into routing features that are relatively expensive compared with basic route templates:
* Regular expressions: It's possible to write regular expressions that are complex, or have long running time with a small amount of input.
* Complex segments (`{x}-{y}-{z}`):
* Are significantly more expensive than parsing a regular URL path segment.
* Result in many more substrings being allocated.
* The complex segment logic was not updated in ASP.NET Core 3.0 routing performance update.
* Synchronous data access: Many complex apps have database access as part of their routing. ASP.NET Core 2.2 and earlier routing might not provide the right extensibility points to support database access routing. For example, <xref:Microsoft.AspNetCore.Routing.IRouteConstraint>, and <xref:Microsoft.AspNetCore.Mvc.ActionConstraints.IActionConstraint> are synchronous. Extensibility points such as <xref:Microsoft.AspNetCore.Routing.MatcherPolicy> and <xref:Microsoft.AspNetCore.Routing.EndpointSelectorContext> are asynchronous.
## Guidance for library authors
This section contains guidance for library authors building on top of routing. These details are intended to ensure that app developers have a good experience using libraries and frameworks that extend routing.
### Define endpoints
To create a framework that uses routing for URL matching, start by defining a user experience that builds on top of <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints*>.
**DO** build on top of <xref:Microsoft.AspNetCore.Routing.IEndpointRouteBuilder>. This allows users to compose your framework with other ASP.NET Core features without confusion. Every ASP.NET Core template includes routing. Assume routing is present and familiar for users.
```csharp
app.UseEndpoints(endpoints =>
{
// Your framework
endpoints.MapMyFramework(...);
endpoints.MapHealthChecks("/healthz");
});
```
**DO** return a sealed concrete type from a call to `MapMyFramework(...)` that implements <xref:Microsoft.AspNetCore.Builder.IEndpointConventionBuilder>. Most framework `Map...` methods follow this pattern. The `IEndpointConventionBuilder` interface:
* Allows composability of metadata.
* Is targeted by a variety of extension methods.
Declaring your own type allows you to add your own framework-specific functionality to the builder. It's ok to wrap a framework-declared builder and forward calls to it.
```csharp
app.UseEndpoints(endpoints =>
{
// Your framework
endpoints.MapMyFramework(...).RequireAuthorization()
.WithMyFrameworkFeature(awesome: true);
endpoints.MapHealthChecks("/healthz");
});
```
**CONSIDER** writing your own <xref:Microsoft.AspNetCore.Routing.EndpointDataSource>. `EndpointDataSource` is the low-level primitive for declaring and updating a collection of endpoints. `EndpointDataSource` is a powerful API used by controllers and Razor Pages.
The routing tests have a [basic example](https://github.com/aspnet/AspNetCore/blob/master/src/Http/Routing/test/testassets/RoutingSandbox/Framework/FrameworkEndpointDataSource.cs#L17) of a non-updating data source.
**DO NOT** attempt to register an `EndpointDataSource` by default. Require users to register your framework in <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints*>. The philosophy of routing is that nothing is included by default, and that `UseEndpoints` is the place to register endpoints.
### Creating routing-integrated middleware
**CONSIDER** defining metadata types as an interface.
**DO** make it possible to use metadata types as an attribute on classes and methods.
[!code-csharp[](routing/samples/3.x/RoutingSample/ICoolMetadata.cs?name=snippet2)]
Frameworks like controllers and Razor Pages support applying metadata attributes to types and methods. If you declare metadata types:
* Make them accessible as [attributes](/dotnet/csharp/programming-guide/concepts/attributes/).
* Most users are familiar with applying attributes.
Declaring a metadata type as an interface adds another layer of flexibility:
* Interfaces are composable.
* Developers can declare their own types that combine multiple policies.
**DO** make it possible to override metadata, as shown in the following example:
[!code-csharp[](routing/samples/3.x/RoutingSample/ICoolMetadata.cs?name=snippet)]
The best way to follow these guidelines is to avoid defining **marker metadata**:
* Don't just look for the presence of a metadata type.
* Define a property on the metadata and check the property.
The metadata collection is ordered and supports overriding by priority. In the case of controllers, metadata on the action method is most specific.
**DO** make middleware useful with and without routing.
```csharp
app.UseRouting();
app.UseAuthorization(new AuthorizationPolicy() { ... });
app.UseEndpoints(endpoints =>
{
// Your framework
endpoints.MapMyFramework(...).RequireAuthorization();
});
```
As an example of this guideline, consider the `UseAuthorization` middleware. The authorization middleware allows you to pass in a fallback policy. <!-- shown where? (shown here) --> The fallback policy, if specified, applies to both:
* Endpoints without a specified policy.
* Requests that don't match an endpoint.
This makes the authorization middleware useful outside of the context of routing. The authorization middleware can be used for traditional middleware programming.
[!INCLUDE[](~/includes/dbg-route.md)]
::: moniker-end
::: moniker range="= aspnetcore-2.2"
Routing is responsible for mapping request URIs to endpoints and dispatching incoming requests to those endpoints. Routes are defined in the app and configured when the app starts. A route can optionally extract values from the URL contained in the request, and these values can then be used for request processing. Using route information from the app, routing is also able to generate URLs that map to endpoints.
To use the latest routing scenarios in ASP.NET Core 2.2, specify the [compatibility version](xref:mvc/compatibility-version) to the MVC services registration in `Startup.ConfigureServices`:
```csharp
services.AddMvc()
.SetCompatibilityVersion(CompatibilityVersion.Version_2_2);
```
The <xref:Microsoft.AspNetCore.Mvc.MvcOptions.EnableEndpointRouting> option determines if routing should internally use endpoint-based logic or the <xref:Microsoft.AspNetCore.Routing.IRouter>-based logic of ASP.NET Core 2.1 or earlier. When the compatibility version is set to 2.2 or later, the default value is `true`. Set the value to `false` to use the prior routing logic:
```csharp
// Use the routing logic of ASP.NET Core 2.1 or earlier:
services.AddMvc(options => options.EnableEndpointRouting = false)
.SetCompatibilityVersion(CompatibilityVersion.Version_2_2);
```
For more information on <xref:Microsoft.AspNetCore.Routing.IRouter>-based routing, see the [ASP.NET Core 2.1 version of this topic](?view=aspnetcore-2.1).
> [!IMPORTANT]
> This document covers low-level ASP.NET Core routing. For information on ASP.NET Core MVC routing, see <xref:mvc/controllers/routing>. For information on routing conventions in Razor Pages, see <xref:razor-pages/razor-pages-conventions>.
[View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/master/aspnetcore/fundamentals/routing/samples) ([how to download](xref:index#how-to-download-a-sample))
## Routing basics
Most apps should choose a basic and descriptive routing scheme so that URLs are readable and meaningful. The default conventional route `{controller=Home}/{action=Index}/{id?}`:
* Supports a basic and descriptive routing scheme.
* Is a useful starting point for UI-based apps.
Developers commonly add additional terse routes to high-traffic areas of an app in specialized situations using [attribute routing](xref:mvc/controllers/routing#attribute-routing) or dedicated conventional routes. Specialized situations examples include, blog and ecommerce endpoints.
Web APIs should use attribute routing to model the app's functionality as a set of resources where operations are represented by HTTP verbs. This means that many operations, for example, GET, and POST, on the same logical resource use the same URL. Attribute routing provides a level of control that's needed to carefully design an API's public endpoint layout.
Razor Pages apps use default conventional routing to serve named resources in the *Pages* folder of an app. Additional conventions are available that allow you to customize Razor Pages routing behavior. For more information, see <xref:razor-pages/index> and <xref:razor-pages/razor-pages-conventions>.
URL generation support allows the app to be developed without hard-coding URLs to link the app together. This support allows for starting with a basic routing configuration and modifying the routes after the app's resource layout is determined.
Routing uses *endpoints* (`Endpoint`) to represent logical endpoints in an app.
An endpoint defines a delegate to process requests and a collection of arbitrary metadata. The metadata is used implement cross-cutting concerns based on policies and configuration attached to each endpoint.
The routing system has the following characteristics:
* Route template syntax is used to define routes with tokenized route parameters.
* Conventional-style and attribute-style endpoint configuration is permitted.
* <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> is used to determine whether a URL parameter contains a valid value for a given endpoint constraint.
* App models, such as MVC/Razor Pages, register all of their endpoints, which have a predictable implementation of routing scenarios.
* The routing implementation makes routing decisions wherever desired in the middleware pipeline.
* Middleware that appears after a Routing Middleware can inspect the result of the Routing Middleware's endpoint decision for a given request URI.
* It's possible to enumerate all of the endpoints in the app anywhere in the middleware pipeline.
* An app can use routing to generate URLs (for example, for redirection or links) based on endpoint information and thus avoid hard-coded URLs, which helps maintainability.
* URL generation is based on addresses, which support arbitrary extensibility:
* The Link Generator API (<xref:Microsoft.AspNetCore.Routing.LinkGenerator>) can be resolved anywhere using [dependency injection (DI)](xref:fundamentals/dependency-injection) to generate URLs.
* Where the Link Generator API isn't available via DI, <xref:Microsoft.AspNetCore.Mvc.IUrlHelper> offers methods to build URLs.
> [!NOTE]
> With the release of endpoint routing in ASP.NET Core 2.2, endpoint linking is limited to MVC/Razor Pages actions and pages. The expansions of endpoint-linking capabilities is planned for future releases.
Routing is connected to the [middleware](xref:fundamentals/middleware/index) pipeline by the <xref:Microsoft.AspNetCore.Builder.RouterMiddleware> class. [ASP.NET Core MVC](xref:mvc/overview) adds routing to the middleware pipeline as part of its configuration and handles routing in MVC and Razor Pages apps. To learn how to use routing as a standalone component, see the [Use Routing Middleware](#use-routing-middleware) section.
### URL matching
URL matching is the process by which routing dispatches an incoming request to an *endpoint*. This process is based on data in the URL path but can be extended to consider any data in the request. The ability to dispatch requests to separate handlers is key to scaling the size and complexity of an app.
The routing system in endpoint routing is responsible for all dispatching decisions. Since the middleware applies policies based on the selected endpoint, it's important that any decision that can affect dispatching or the application of security policies is made inside the routing system.
When the endpoint delegate is executed, the properties of [RouteContext.RouteData](xref:Microsoft.AspNetCore.Routing.RouteContext.RouteData) are set to appropriate values based on the request processing performed thus far.
[RouteData.Values](xref:Microsoft.AspNetCore.Routing.RouteData.Values*) is a dictionary of *route values* produced from the route. These values are usually determined by tokenizing the URL and can be used to accept user input or to make further dispatching decisions inside the app.
[RouteData.DataTokens](xref:Microsoft.AspNetCore.Routing.RouteData.DataTokens*) is a property bag of additional data related to the matched route. <xref:Microsoft.AspNetCore.Routing.RouteData.DataTokens*> are provided to support associating state data with each route so that the app can make decisions based on which route matched. These values are developer-defined and do **not** affect the behavior of routing in any way. Additionally, values stashed in [RouteData.DataTokens](xref:Microsoft.AspNetCore.Routing.RouteData.DataTokens*) can be of any type, in contrast to [RouteData.Values](xref:Microsoft.AspNetCore.Routing.RouteData.Values), which must be convertible to and from strings.
[RouteData.Routers](xref:Microsoft.AspNetCore.Routing.RouteData.Routers) is a list of the routes that took part in successfully matching the request. Routes can be nested inside of one another. The <xref:Microsoft.AspNetCore.Routing.RouteData.Routers> property reflects the path through the logical tree of routes that resulted in a match. Generally, the first item in <xref:Microsoft.AspNetCore.Routing.RouteData.Routers> is the route collection and should be used for URL generation. The last item in <xref:Microsoft.AspNetCore.Routing.RouteData.Routers> is the route handler that matched.
<a name="lg"></a>
### URL generation with LinkGenerator
URL generation is the process by which routing can create a URL path based on a set of route values. This allows for a logical separation between your endpoints and the URLs that access them.
Endpoint routing includes the Link Generator API (<xref:Microsoft.AspNetCore.Routing.LinkGenerator>). <xref:Microsoft.AspNetCore.Routing.LinkGenerator> is a singleton service that can be retrieved from [DI](xref:fundamentals/dependency-injection). The API can be used outside of the context of an executing request. MVC's <xref:Microsoft.AspNetCore.Mvc.IUrlHelper> and scenarios that rely on <xref:Microsoft.AspNetCore.Mvc.IUrlHelper>, such as [Tag Helpers](xref:mvc/views/tag-helpers/intro), HTML Helpers, and [Action Results](xref:mvc/controllers/actions), use the link generator to provide link generating capabilities.
The link generator is backed by the concept of an *address* and *address schemes*. An address scheme is a way of determining the endpoints that should be considered for link generation. For example, the route name and route values scenarios many users are familiar with from MVC/Razor Pages are implemented as an address scheme.
The link generator can link to MVC/Razor Pages actions and pages via the following extension methods:
* <xref:Microsoft.AspNetCore.Routing.ControllerLinkGeneratorExtensions.GetPathByAction*>
* <xref:Microsoft.AspNetCore.Routing.ControllerLinkGeneratorExtensions.GetUriByAction*>
* <xref:Microsoft.AspNetCore.Routing.PageLinkGeneratorExtensions.GetPathByPage*>
* <xref:Microsoft.AspNetCore.Routing.PageLinkGeneratorExtensions.GetUriByPage*>
An overload of these methods accepts arguments that include the `HttpContext`. These methods are functionally equivalent to `Url.Action` and `Url.Page` but offer additional flexibility and options.
The `GetPath*` methods are most similar to `Url.Action` and `Url.Page` in that they generate a URI containing an absolute path. The `GetUri*` methods always generate an absolute URI containing a scheme and host. The methods that accept an `HttpContext` generate a URI in the context of the executing request. The ambient route values, URL base path, scheme, and host from the executing request are used unless overridden.
<xref:Microsoft.AspNetCore.Routing.LinkGenerator> is called with an address. Generating a URI occurs in two steps:
1. An address is bound to a list of endpoints that match the address.
1. Each endpoint's `RoutePattern` is evaluated until a route pattern that matches the supplied values is found. The resulting output is combined with the other URI parts supplied to the link generator and returned.
The methods provided by <xref:Microsoft.AspNetCore.Routing.LinkGenerator> support standard link generation capabilities for any type of address. The most convenient way to use the link generator is through extension methods that perform operations for a specific address type.
| Extension Method | Description |
| ------------------ | ------------------------------------------------------------------- |
| <xref:Microsoft.AspNetCore.Routing.LinkGenerator.GetPathByAddress*> | Generates a URI with an absolute path based on the provided values. |
| <xref:Microsoft.AspNetCore.Routing.LinkGenerator.GetUriByAddress*> | Generates an absolute URI based on the provided values. |
> [!WARNING]
> Pay attention to the following implications of calling <xref:Microsoft.AspNetCore.Routing.LinkGenerator> methods:
>
> * Use `GetUri*` extension methods with caution in an app configuration that doesn't validate the `Host` header of incoming requests. If the `Host` header of incoming requests isn't validated, untrusted request input can be sent back to the client in URIs in a view/page. We recommend that all production apps configure their server to validate the `Host` header against known valid values.
>
> * Use <xref:Microsoft.AspNetCore.Routing.LinkGenerator> with caution in middleware in combination with `Map` or `MapWhen`. `Map*` changes the base path of the executing request, which affects the output of link generation. All of the <xref:Microsoft.AspNetCore.Routing.LinkGenerator> APIs allow specifying a base path. Always specify an empty base path to undo `Map*`'s affect on link generation.
## Differences from earlier versions of routing
A few differences exist between endpoint routing in ASP.NET Core 2.2 or later and earlier versions of routing in ASP.NET Core:
* The endpoint routing system doesn't support <xref:Microsoft.AspNetCore.Routing.IRouter>-based extensibility, including inheriting from <xref:Microsoft.AspNetCore.Routing.Route>.
* Endpoint routing doesn't support [WebApiCompatShim](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.WebApiCompatShim). Use the 2.1 [compatibility version](xref:mvc/compatibility-version) (`.SetCompatibilityVersion(CompatibilityVersion.Version_2_1)`) to continue using the compatibility shim.
* Endpoint Routing has different behavior for the casing of generated URIs when using conventional routes.
Consider the following default route template:
```csharp
app.UseMvc(routes =>
{
routes.MapRoute("default", "{controller=Home}/{action=Index}/{id?}");
});
```
Suppose you generate a link to an action using the following route:
```csharp
var link = Url.Action("ReadPost", "blog", new { id = 17, });
```
With <xref:Microsoft.AspNetCore.Routing.IRouter>-based routing, this code generates a URI of `/blog/ReadPost/17`, which respects the casing of the provided route value. Endpoint routing in ASP.NET Core 2.2 or later produces `/Blog/ReadPost/17` ("Blog" is capitalized). Endpoint routing provides the `IOutboundParameterTransformer` interface that can be used to customize this behavior globally or to apply different conventions for mapping URLs.
For more information, see the [Parameter transformer reference](#parameter-transformer-reference) section.
* Link Generation used by MVC/Razor Pages with conventional routes behaves differently when attempting to link to an controller/action or page that doesn't exist.
Consider the following default route template:
```csharp
app.UseMvc(routes =>
{
routes.MapRoute("default", "{controller=Home}/{action=Index}/{id?}");
});
```
Suppose you generate a link to an action using the default template with the following:
```csharp
var link = Url.Action("ReadPost", "Blog", new { id = 17, });
```
With `IRouter`-based routing, the result is always `/Blog/ReadPost/17`, even if the `BlogController` doesn't exist or doesn't have a `ReadPost` action method. As expected, endpoint routing in ASP.NET Core 2.2 or later produces `/Blog/ReadPost/17` if the action method exists. *However, endpoint routing produces an empty string if the action doesn't exist.* Conceptually, endpoint routing doesn't assume that the endpoint exists if the action doesn't exist.
* The link generation *ambient value invalidation algorithm* behaves differently when used with endpoint routing.
*Ambient value invalidation* is the algorithm that decides which route values from the currently executing request (the ambient values) can be used in link generation operations. Conventional routing always invalidated extra route values when linking to a different action. Attribute routing didn't have this behavior prior to the release of ASP.NET Core 2.2. In earlier versions of ASP.NET Core, links to another action that use the same route parameter names resulted in link generation errors. In ASP.NET Core 2.2 or later, both forms of routing invalidate values when linking to another action.
Consider the following example in ASP.NET Core 2.1 or earlier. When linking to another action (or another page), route values can be reused in undesirable ways.
In */Pages/Store/Product.cshtml*:
```cshtml
@page "{id}"
@Url.Page("/Login")
```
In */Pages/Login.cshtml*:
```cshtml
@page "{id?}"
```
If the URI is `/Store/Product/18` in ASP.NET Core 2.1 or earlier, the link generated on the Store/Info page by `@Url.Page("/Login")` is `/Login/18`. The `id` value of 18 is reused, even though the link destination is different part of the app entirely. The `id` route value in the context of the `/Login` page is probably a user ID value, not a store product ID value.
In endpoint routing with ASP.NET Core 2.2 or later, the result is `/Login`. Ambient values aren't reused when the linked destination is a different action or page.
* Round-tripping route parameter syntax: Forward slashes aren't encoded when using a double-asterisk (`**`) catch-all parameter syntax.
During link generation, the routing system encodes the value captured in a double-asterisk (`**`) catch-all parameter (for example, `{**myparametername}`) except the forward slashes. The double-asterisk catch-all is supported with `IRouter`-based routing in ASP.NET Core 2.2 or later.
The single asterisk catch-all parameter syntax in prior versions of ASP.NET Core (`{*myparametername}`) remains supported, and forward slashes are encoded.
| Route | Link generated with<br>`Url.Action(new { category = "admin/products" })`… |
| ------------------ | --------------------------------------------------------------------- |
| `/search/{*page}` | `/search/admin%2Fproducts` (the forward slash is encoded) |
| `/search/{**page}` | `/search/admin/products` |
### Middleware example
In the following example, a middleware uses the <xref:Microsoft.AspNetCore.Routing.LinkGenerator> API to create link to an action method that lists store products. Using the link generator by injecting it into a class and calling `GenerateLink` is available to any class in an app.
```csharp
using Microsoft.AspNetCore.Routing;
public class ProductsLinkMiddleware
{
private readonly LinkGenerator _linkGenerator;
public ProductsLinkMiddleware(RequestDelegate next, LinkGenerator linkGenerator)
{
_linkGenerator = linkGenerator;
}
public async Task InvokeAsync(HttpContext httpContext)
{
var url = _linkGenerator.GetPathByAction("ListProducts", "Store");
httpContext.Response.ContentType = "text/plain";
await httpContext.Response.WriteAsync($"Go to {url} to see our products.");
}
}
```
### Create routes
Most apps create routes by calling <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> or one of the similar extension methods defined on <xref:Microsoft.AspNetCore.Routing.IRouteBuilder>. Any of the <xref:Microsoft.AspNetCore.Routing.IRouteBuilder> extension methods create an instance of <xref:Microsoft.AspNetCore.Routing.Route> and add it to the route collection.
<xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> doesn't accept a route handler parameter. <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> only adds routes that are handled by the <xref:Microsoft.AspNetCore.Routing.RouteBuilder.DefaultHandler*>. To learn more about routing in MVC, see <xref:mvc/controllers/routing>.
The following code example is an example of a <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> call used by a typical ASP.NET Core MVC route definition:
```csharp
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
```
This template matches a URL path and extracts the route values. For example, the path `/Products/Details/17` generates the following route values: `{ controller = Products, action = Details, id = 17 }`.
Route values are determined by splitting the URL path into segments and matching each segment with the *route parameter* name in the route template. Route parameters are named. The parameters defined by enclosing the parameter name in braces `{ ... }`.
The preceding template could also match the URL path `/` and produce the values `{ controller = Home, action = Index }`. This occurs because the `{controller}` and `{action}` route parameters have default values and the `id` route parameter is optional. An equals sign (`=`) followed by a value after the route parameter name defines a default value for the parameter. A question mark (`?`) after the route parameter name defines an optional parameter.
Route parameters with a default value *always* produce a route value when the route matches. Optional parameters don't produce a route value if there is no corresponding URL path segment. See the [Route template reference](#route-template-reference) section for a thorough description of route template scenarios and syntax.
In the following example, the route parameter definition `{id:int}` defines a [route constraint](#route-constraint-reference) for the `id` route parameter:
```csharp
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id:int}");
```
This template matches a URL path like `/Products/Details/17` but not `/Products/Details/Apples`. Route constraints implement <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> and inspect route values to verify them. In this example, the route value `id` must be convertible to an integer. See [route-constraint-reference](#route-constraint-reference) for an explanation of route constraints provided by the framework.
Additional overloads of <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> accept values for `constraints`, `dataTokens`, and `defaults`. The typical usage of these parameters is to pass an anonymously typed object, where the property names of the anonymous type match route parameter names.
The following <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> examples create equivalent routes:
```csharp
routes.MapRoute(
name: "default_route",
template: "{controller}/{action}/{id?}",
defaults: new { controller = "Home", action = "Index" });
routes.MapRoute(
name: "default_route",
template: "{controller=Home}/{action=Index}/{id?}");
```
> [!TIP]
> The inline syntax for defining constraints and defaults can be convenient for simple routes. However, there are scenarios, such as data tokens, that aren't supported by inline syntax.
The following example demonstrates a few additional scenarios:
```csharp
routes.MapRoute(
name: "blog",
template: "Blog/{**article}",
defaults: new { controller = "Blog", action = "ReadArticle" });
```
The preceding template matches a URL path like `/Blog/All-About-Routing/Introduction` and extracts the values `{ controller = Blog, action = ReadArticle, article = All-About-Routing/Introduction }`. The default route values for `controller` and `action` are produced by the route even though there are no corresponding route parameters in the template. Default values can be specified in the route template. The `article` route parameter is defined as a *catch-all* by the appearance of an double asterisk (`**`) before the route parameter name. Catch-all route parameters capture the remainder of the URL path and can also match the empty string.
The following example adds route constraints and data tokens:
```csharp
routes.MapRoute(
name: "us_english_products",
template: "en-US/Products/{id}",
defaults: new { controller = "Products", action = "Details" },
constraints: new { id = new IntRouteConstraint() },
dataTokens: new { locale = "en-US" });
```
The preceding template matches a URL path like `/en-US/Products/5` and extracts the values `{ controller = Products, action = Details, id = 5 }` and the data tokens `{ locale = en-US }`.
### Route class URL generation
The <xref:Microsoft.AspNetCore.Routing.Route> class can also perform URL generation by combining a set of route values with its route template. This is logically the reverse process of matching the URL path.
> [!TIP]
> To better understand URL generation, imagine what URL you want to generate and then think about how a route template would match that URL. What values would be produced? This is the rough equivalent of how URL generation works in the <xref:Microsoft.AspNetCore.Routing.Route> class.
The following example uses a general ASP.NET Core MVC default route:
```csharp
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
```
With the route values `{ controller = Products, action = List }`, the URL `/Products/List` is generated. The route values are substituted for the corresponding route parameters to form the URL path. Since `id` is an optional route parameter, the URL is successfully generated without a value for `id`.
With the route values `{ controller = Home, action = Index }`, the URL `/` is generated. The provided route values match the default values, and the segments corresponding to the default values are safely omitted.
Both URLs generated round-trip with the following route definition (`/Home/Index` and `/`) produce the same route values that were used to generate the URL.
> [!NOTE]
> An app using ASP.NET Core MVC should use <xref:Microsoft.AspNetCore.Mvc.Routing.UrlHelper> to generate URLs instead of calling into routing directly.
For more information on URL generation, see the [Url generation reference](#url-generation-reference) section.
## Use Routing Middleware
Reference the [Microsoft.AspNetCore.App metapackage](xref:fundamentals/metapackage-app) in the app's project file.
Add routing to the service container in `Startup.ConfigureServices`:
[!code-csharp[](routing/samples/2.x/RoutingSample/Startup.cs?name=snippet_ConfigureServices&highlight=3)]
Routes must be configured in the `Startup.Configure` method. The sample app uses the following APIs:
* <xref:Microsoft.AspNetCore.Routing.RouteBuilder>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapGet*>: Matches only HTTP GET requests.
* <xref:Microsoft.AspNetCore.Builder.RoutingBuilderExtensions.UseRouter*>
[!code-csharp[](routing/samples/2.x/RoutingSample/Startup.cs?name=snippet_RouteHandler)]
The following table shows the responses with the given URIs.
| URI | Response |
| ---------------------- | ------------------------------------------------- |
| `/package/create/3` | Hello! Route values: [operation, create], [id, 3] |
| `/package/track/-3` | Hello! Route values: [operation, track], [id, -3] |
| `/package/track/-3/` | Hello! Route values: [operation, track], [id, -3] |
| `/package/track/` | The request falls through, no match. |
| `GET /hello/Joe` | Hi, Joe! |
| `POST /hello/Joe` | The request falls through, matches HTTP GET only. |
| `GET /hello/Joe/Smith` | The request falls through, no match. |
The framework provides a set of extension methods for creating routes (<xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions>):
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapDelete*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapGet*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewareDelete*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewareGet*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewarePost*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewarePut*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewareRoute*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewareVerb*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapPost*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapPut*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapRoute*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapVerb*>
The `Map[Verb]` methods use constraints to limit the route to the HTTP Verb in the method name. For example, see <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapGet*> and <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapVerb*>.
## Route template reference
Tokens within curly braces (`{ ... }`) define *route parameters* that are bound if the route is matched. You can define more than one route parameter in a route segment, but they must be separated by a literal value. For example, `{controller=Home}{action=Index}` isn't a valid route, since there's no literal value between `{controller}` and `{action}`. These route parameters must have a name and may have additional attributes specified.
Literal text other than route parameters (for example, `{id}`) and the path separator `/` must match the text in the URL. Text matching is case-insensitive and based on the decoded representation of the URLs path. To match a literal route parameter delimiter (`{` or `}`), escape the delimiter by repeating the character (`{{` or `}}`).
URL patterns that attempt to capture a file name with an optional file extension have additional considerations. For example, consider the template `files/{filename}.{ext?}`. When values for both `filename` and `ext` exist, both values are populated. If only a value for `filename` exists in the URL, the route matches because the trailing period (`.`) is optional. The following URLs match this route:
* `/files/myFile.txt`
* `/files/myFile`
You can use an asterisk (`*`) or double asterisk (`**`) as a prefix to a route parameter to bind to the rest of the URI. These are called a *catch-all* parameters. For example, `blog/{**slug}` matches any URI that starts with `/blog` and has any value following it, which is assigned to the `slug` route value. Catch-all parameters can also match the empty string.
The catch-all parameter escapes the appropriate characters when the route is used to generate a URL, including path separator (`/`) characters. For example, the route `foo/{*path}` with route values `{ path = "my/path" }` generates `foo/my%2Fpath`. Note the escaped forward slash. To round-trip path separator characters, use the `**` route parameter prefix. The route `foo/{**path}` with `{ path = "my/path" }` generates `foo/my/path`.
Route parameters may have *default values* designated by specifying the default value after the parameter name separated by an equals sign (`=`). For example, `{controller=Home}` defines `Home` as the default value for `controller`. The default value is used if no value is present in the URL for the parameter. Route parameters are made optional by appending a question mark (`?`) to the end of the parameter name, as in `id?`. The difference between optional values and default route parameters is that a route parameter with a default value always produces a value—an optional parameter has a value only when a value is provided by the request URL.
Route parameters may have constraints that must match the route value bound from the URL. Adding a colon (`:`) and constraint name after the route parameter name specifies an *inline constraint* on a route parameter. If the constraint requires arguments, they're enclosed in parentheses (`(...)`) after the constraint name. Multiple inline constraints can be specified by appending another colon (`:`) and constraint name.
The constraint name and arguments are passed to the <xref:Microsoft.AspNetCore.Routing.IInlineConstraintResolver> service to create an instance of <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> to use in URL processing. For example, the route template `blog/{article:minlength(10)}` specifies a `minlength` constraint with the argument `10`. For more information on route constraints and a list of the constraints provided by the framework, see the [Route constraint reference](#route-constraint-reference) section.
Route parameters may also have parameter transformers, which transform a parameter's value when generating links and matching actions and pages to URLs. Like constraints, parameter transformers can be added inline to a route parameter by adding a colon (`:`) and transformer name after the route parameter name. For example, the route template `blog/{article:slugify}` specifies a `slugify` transformer. For more information on parameter transformers, see the [Parameter transformer reference](#parameter-transformer-reference) section.
The following table demonstrates example route templates and their behavior.
| Route Template | Example Matching URI | The request URI… |
| ---------------------------------------- | ----------------------- | -------------------------------------------------------------------------- |
| `hello` | `/hello` | Only matches the single path `/hello`. |
| `{Page=Home}` | `/` | Matches and sets `Page` to `Home`. |
| `{Page=Home}` | `/Contact` | Matches and sets `Page` to `Contact`. |
| `{controller}/{action}/{id?}` | `/Products/List` | Maps to the `Products` controller and `List` action. |
| `{controller}/{action}/{id?}` | `/Products/Details/123` | Maps to the `Products` controller and `Details` action (`id` set to 123). |
| `{controller=Home}/{action=Index}/{id?}` | `/` | Maps to the `Home` controller and `Index` method (`id` is ignored). |
Using a template is generally the simplest approach to routing. Constraints and defaults can also be specified outside the route template.
> [!TIP]
> Enable [Logging](xref:fundamentals/logging/index) to see how the built-in routing implementations, such as <xref:Microsoft.AspNetCore.Routing.Route>, match requests.
## Reserved routing names
The following keywords are reserved names and can't be used as route names or parameters:
* `action`
* `area`
* `controller`
* `handler`
* `page`
## Route constraint reference
Route constraints execute when a match has occurred to the incoming URL and the URL path is tokenized into route values. Route constraints generally inspect the route value associated via the route template and make a yes/no decision about whether or not the value is acceptable. Some route constraints use data outside the route value to consider whether the request can be routed. For example, the <xref:Microsoft.AspNetCore.Routing.Constraints.HttpMethodRouteConstraint> can accept or reject a request based on its HTTP verb. Constraints are used in routing requests and link generation.
> [!WARNING]
> Don't use constraints for **input validation**. If constraints are used for **input validation**, invalid input results in a *404 - Not Found* response instead of a *400 - Bad Request* with an appropriate error message. Route constraints are used to **disambiguate** similar routes, not to validate the inputs for a particular route.
The following table demonstrates example route constraints and their expected behavior.
| Constraint | Example | Example matches | Notes |
|------------|---------|-----------------|-------|
| `int` | `{id:int}` | `123456789`, `-123456789` | Matches any integer.|
| `bool` | `{active:bool}` | `true`, `FALSE` | Matches `true` or `false`. Case-insensitive.|
| `datetime` | `{dob:datetime}` | `2016-12-31`, `2016-12-31 7:32pm` | Matches a valid `DateTime` value in the invariant culture. See preceding warning.|
| `decimal` | `{price:decimal}` | `49.99`, `-1,000.01` | Matches a valid `decimal` value in the invariant culture. See preceding warning.|
| `double` | `{weight:double}` | `1.234`, `-1,001.01e8` | Matches a valid `double` value in the invariant culture. See preceding warning.|
| `float` | `{weight:float}` | `1.234`, `-1,001.01e8` | Matches a valid `float` value in the invariant culture. See preceding warning.|
| `guid` | `{id:guid}` | `CD2C1638-1638-72D5-1638-DEADBEEF1638`, `{CD2C1638-1638-72D5-1638-DEADBEEF1638}` | Matches a valid `Guid` value.|
| `long` | `{ticks:long}` | `123456789`, `-123456789` | Matches a valid `long` value.|
| `minlength(value)` | `{username:minlength(4)}` | `Rick` | String must be at least 4 characters.|
| `maxlength(value)` | `{filename:maxlength(8)}` | `MyFile` | String has maximum of 8 characters.|
| `length(length)` | `{filename:length(12)}` | `somefile.txt` | String must be exactly 12 characters long.|
| `length(min,max)` | `{filename:length(8,16)}` | `somefile.txt` | String must be at least 8 and has maximum of 16 characters.|
| `min(value)` | `{age:min(18)}` | `19` | Integer value must be at least 18.|
| `max(value)` | `{age:max(120)}` | `91` | Integer value maximum of 120.|
| `range(min,max)` | `{age:range(18,120)}` | `91` | Integer value must be at least 18 and maximum of 120.|
| `alpha` | `{name:alpha}` | `Rick` | String must consist of one or more alphabetical characters `a`-`z`. Case-insensitive.|
| `regex(expression)` | `{ssn:regex(^\\d{{3}}-\\d{{2}}-\\d{{4}}$)}` | `123-45-6789` | String must match the regular expression. See tips about defining a regular expression.|
| `required` | `{name:required}` | `Rick` | Used to enforce that a non-parameter value is present during URL generation.|
Multiple, colon-delimited constraints can be applied to a single parameter. For example, the following constraint restricts a parameter to an integer value of 1 or greater:
```csharp
[Route("users/{id:int:min(1)}")]
public User GetUserById(int id) { }
```
> [!WARNING]
> Route constraints that verify the URL and are converted to a CLR type (such as `int` or `DateTime`) always use the invariant culture. These constraints assume that the URL is non-localizable. The framework-provided route constraints don't modify the values stored in route values. All route values parsed from the URL are stored as strings. For example, the `float` constraint attempts to convert the route value to a float, but the converted value is used only to verify it can be converted to a float.
## Regular expressions
The ASP.NET Core framework adds `RegexOptions.IgnoreCase | RegexOptions.Compiled | RegexOptions.CultureInvariant` to the regular expression constructor. See <xref:System.Text.RegularExpressions.RegexOptions> for a description of these members.
Regular expressions use delimiters and tokens similar to those used by routing and the C# language. Regular expression tokens must be escaped. To use the regular expression `^\d{3}-\d{2}-\d{4}$` in routing:
* The expression must have the single backslash `\` characters provided in the string as double backslash `\\` characters in the source code.
* The regular expression must us `\\` in order to escape the `\` string escape character.
* The regular expression doesn't require `\\` when using [verbatim string literals](/dotnet/csharp/language-reference/keywords/string).
To escape routing parameter delimiter characters `{`, `}`, `[`, `]`, double the characters in the expression `{{`, `}`, `[[`, `]]`. The following table shows a regular expression and the escaped version:
| Regular Expression | Escaped Regular Expression |
| --------------------- | ------------------------------ |
| `^\d{3}-\d{2}-\d{4}$` | `^\\d{{3}}-\\d{{2}}-\\d{{4}}$` |
| `^[a-z]{2}$` | `^[[a-z]]{{2}}$` |
Regular expressions used in routing often start with the caret `^` character and match starting position of the string. The expressions often end with the dollar sign `$` character and match end of the string. The `^` and `$` characters ensure that the regular expression match the entire route parameter value. Without the `^` and `$` characters, the regular expression match any substring within the string, which is often undesirable. The following table provides examples and explains why they match or fail to match.
| Expression | String | Match | Comment |
| ------------ | --------- | :---: | -------------------- |
| `[a-z]{2}` | hello | Yes | Substring matches |
| `[a-z]{2}` | 123abc456 | Yes | Substring matches |
| `[a-z]{2}` | mz | Yes | Matches expression |
| `[a-z]{2}` | MZ | Yes | Not case sensitive |
| `^[a-z]{2}$` | hello | No | See `^` and `$` above |
| `^[a-z]{2}$` | 123abc456 | No | See `^` and `$` above |
For more information on regular expression syntax, see [.NET Framework Regular Expressions](/dotnet/standard/base-types/regular-expression-language-quick-reference).
To constrain a parameter to a known set of possible values, use a regular expression. For example, `{action:regex(^(list|get|create)$)}` only matches the `action` route value to `list`, `get`, or `create`. If passed into the constraints dictionary, the string `^(list|get|create)$` is equivalent. Constraints that are passed in the constraints dictionary (not inline within a template) that don't match one of the known constraints are also treated as regular expressions.
## Custom route constraints
In addition to the built-in route constraints, custom route constraints can be created by implementing the <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> interface. The <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> interface contains a single method, `Match`, which returns `true` if the constraint is satisfied and `false` otherwise.
To use a custom <xref:Microsoft.AspNetCore.Routing.IRouteConstraint>, the route constraint type must be registered with the app's <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap> in the app's service container. A <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap> is a dictionary that maps route constraint keys to <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> implementations that validate those constraints. An app's <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap> can be updated in `Startup.ConfigureServices` either as part of a [services.AddRouting](xref:Microsoft.Extensions.DependencyInjection.RoutingServiceCollectionExtensions.AddRouting*) call or by configuring <xref:Microsoft.AspNetCore.Routing.RouteOptions> directly with `services.Configure<RouteOptions>`. For example:
```csharp
services.AddRouting(options =>
{
options.ConstraintMap.Add("customName", typeof(MyCustomConstraint));
});
```
The constraint can then be applied to routes in the usual manner, using the name specified when registering the constraint type. For example:
```csharp
[HttpGet("{id:customName}")]
public ActionResult<string> Get(string id)
```
## Parameter transformer reference
Parameter transformers:
* Execute when generating a link for a <xref:Microsoft.AspNetCore.Routing.Route>.
* Implement `Microsoft.AspNetCore.Routing.IOutboundParameterTransformer`.
* Are configured using <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap>.
* Take the parameter's route value and transform it to a new string value.
* Result in using the transformed value in the generated link.
For example, a custom `slugify` parameter transformer in route pattern `blog\{article:slugify}` with `Url.Action(new { article = "MyTestArticle" })` generates `blog\my-test-article`.
To use a parameter transformer in a route pattern, configure it first using <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap> in `Startup.ConfigureServices`:
```csharp
services.AddRouting(options =>
{
// Replace the type and the name used to refer to it with your own
// IOutboundParameterTransformer implementation
options.ConstraintMap["slugify"] = typeof(SlugifyParameterTransformer);
});
```
Parameter transformers are used by the framework to transform the URI where an endpoint resolves. For example, ASP.NET Core MVC uses parameter transformers to transform the route value used to match an `area`, `controller`, `action`, and `page`.
```csharp
routes.MapRoute(
name: "default",
template: "{controller:slugify=Home}/{action:slugify=Index}/{id?}");
```
With the preceding route, the action `SubscriptionManagementController.GetAll` is matched with the URI `/subscription-management/get-all`. A parameter transformer doesn't change the route values used to generate a link. For example, `Url.Action("GetAll", "SubscriptionManagement")` outputs `/subscription-management/get-all`.
ASP.NET Core provides API conventions for using a parameter transformers with generated routes:
* ASP.NET Core MVC has the `Microsoft.AspNetCore.Mvc.ApplicationModels.RouteTokenTransformerConvention` API convention. This convention applies a specified parameter transformer to all attribute routes in the app. The parameter transformer transforms attribute route tokens as they are replaced. For more information, see [Use a parameter transformer to customize token replacement](xref:mvc/controllers/routing#use-a-parameter-transformer-to-customize-token-replacement).
* Razor Pages has the `Microsoft.AspNetCore.Mvc.ApplicationModels.PageRouteTransformerConvention` API convention. This convention applies a specified parameter transformer to all automatically discovered Razor Pages. The parameter transformer transforms the folder and file name segments of Razor Pages routes. For more information, see [Use a parameter transformer to customize page routes](xref:razor-pages/razor-pages-conventions#use-a-parameter-transformer-to-customize-page-routes).
## URL generation reference
The following example shows how to generate a link to a route given a dictionary of route values and a <xref:Microsoft.AspNetCore.Routing.RouteCollection>.
[!code-csharp[](routing/samples/2.x/RoutingSample/Startup.cs?name=snippet_Dictionary)]
The <xref:Microsoft.AspNetCore.Routing.VirtualPathData.VirtualPath> generated at the end of the preceding sample is `/package/create/123`. The dictionary supplies the `operation` and `id` route values of the "Track Package Route" template, `package/{operation}/{id}`. For details, see the sample code in the [Use Routing Middleware](#use-routing-middleware) section or the [sample app](https://github.com/dotnet/AspNetCore.Docs/tree/master/aspnetcore/fundamentals/routing/samples).
The second parameter to the <xref:Microsoft.AspNetCore.Routing.VirtualPathContext> constructor is a collection of *ambient values*. Ambient values are convenient to use because they limit the number of values a developer must specify within a request context. The current route values of the current request are considered ambient values for link generation. In an ASP.NET Core MVC app's `About` action of the `HomeController`, you don't need to specify the controller route value to link to the `Index` action—the ambient value of `Home` is used.
Ambient values that don't match a parameter are ignored. Ambient values are also ignored when an explicitly provided value overrides the ambient value. Matching occurs from left to right in the URL.
Values explicitly provided but that don't match a segment of the route are added to the query string. The following table shows the result when using the route template `{controller}/{action}/{id?}`.
| Ambient Values | Explicit Values | Result |
| ---------------------------------- | -------------------------------------- | ----------------------- |
| controller = "Home" | action = "About" | `/Home/About` |
| controller = "Home" | controller = "Order", action = "About" | `/Order/About` |
| controller = "Home", color = "Red" | action = "About" | `/Home/About` |
| controller = "Home" | action = "About", color = "Red" | `/Home/About?color=Red` |
If a route has a default value that doesn't correspond to a parameter and that value is explicitly provided, it must match the default value:
```csharp
routes.MapRoute("blog_route", "blog/{*slug}",
defaults: new { controller = "Blog", action = "ReadPost" });
```
Link generation only generates a link for this route when the matching values for `controller` and `action` are provided.
## Complex segments
Complex segments (for example `[Route("/x{token}y")]`) are processed by matching up literals from right to left in a non-greedy way. See [this code](https://github.com/dotnet/AspNetCore/blob/release/2.2/src/Http/Routing/src/Patterns/RoutePatternMatcher.cs#L293) for a detailed explanation of how complex segments are matched. The [code sample](https://github.com/dotnet/AspNetCore/blob/release/2.2/src/Http/Routing/src/Patterns/RoutePatternMatcher.cs#L293) is not used by ASP.NET Core, but it provides a good explanation of complex segments.
<!-- While that code is no longer used by ASP.NET Core for complex segment matching, it provides a good match to the current algorithm. The [current code](https://github.com/dotnet/AspNetCore/blob/91514c9af7e0f4c44029b51f05a01c6fe4c96e4c/src/Http/Routing/src/Matching/DfaMatcherBuilder.cs#L227-L244) is too abstracted from matching to be useful for understanding complex segment matching.
-->
::: moniker-end
::: moniker range="< aspnetcore-2.2"
Routing is responsible for mapping request URIs to route handlers and dispatching an incoming requests. Routes are defined in the app and configured when the app starts. A route can optionally extract values from the URL contained in the request, and these values can then be used for request processing. Using configured routes from the app, routing is able to generate URLs that map to route handlers.
To use the latest routing scenarios in ASP.NET Core 2.1, specify the [compatibility version](xref:mvc/compatibility-version) to the MVC services registration in `Startup.ConfigureServices`:
```csharp
services.AddMvc()
.SetCompatibilityVersion(CompatibilityVersion.Version_2_1);
```
> [!IMPORTANT]
> This document covers low-level ASP.NET Core routing. For information on ASP.NET Core MVC routing, see <xref:mvc/controllers/routing>. For information on routing conventions in Razor Pages, see <xref:razor-pages/razor-pages-conventions>.
[View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/master/aspnetcore/fundamentals/routing/samples) ([how to download](xref:index#how-to-download-a-sample))
## Routing basics
Most apps should choose a basic and descriptive routing scheme so that URLs are readable and meaningful. The default conventional route `{controller=Home}/{action=Index}/{id?}`:
* Supports a basic and descriptive routing scheme.
* Is a useful starting point for UI-based apps.
Developers commonly add additional terse routes to high-traffic areas of an app in specialized situations (for example, blog and ecommerce endpoints) using [attribute routing](xref:mvc/controllers/routing#attribute-routing) or dedicated conventional routes.
Web APIs should use attribute routing to model the app's functionality as a set of resources where operations are represented by HTTP verbs. This means that many operations (for example, GET, POST) on the same logical resource will use the same URL. Attribute routing provides a level of control that's needed to carefully design an API's public endpoint layout.
Razor Pages apps use default conventional routing to serve named resources in the *Pages* folder of an app. Additional conventions are available that allow you to customize Razor Pages routing behavior. For more information, see <xref:razor-pages/index> and <xref:razor-pages/razor-pages-conventions>.
URL generation support allows the app to be developed without hard-coding URLs to link the app together. This support allows for starting with a basic routing configuration and modifying the routes after the app's resource layout is determined.
Routing uses routes implementations of <xref:Microsoft.AspNetCore.Routing.IRouter> to:
* Map incoming requests to *route handlers*.
* Generate the URLs used in responses.
By default, an app has a single collection of routes. When a request arrives, the routes in the collection are processed in the order that they exist in the collection. The framework attempts to match an incoming request URL to a route in the collection by calling the <xref:Microsoft.AspNetCore.Routing.IRouter.RouteAsync*> method on each route in the collection. A response can use routing to generate URLs (for example, for redirection or links) based on route information and thus avoid hard-coded URLs, which helps maintainability.
The routing system has the following characteristics:
* Route template syntax is used to define routes with tokenized route parameters.
* Conventional-style and attribute-style endpoint configuration is permitted.
* <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> is used to determine whether a URL parameter contains a valid value for a given endpoint constraint.
* App models, such as MVC/Razor Pages, register all of their routes, which have a predictable implementation of routing scenarios.
* A response can use routing to generate URLs (for example, for redirection or links) based on route information and thus avoid hard-coded URLs, which helps maintainability.
* URL generation is based on routes, which support arbitrary extensibility. <xref:Microsoft.AspNetCore.Mvc.IUrlHelper> offers methods to build URLs.
<!-- fix [middleware](xref:fundamentals/middleware/index) -->
Routing is connected to the [middleware](xref:fundamentals/middleware/index) pipeline by the <xref:Microsoft.AspNetCore.Builder.RouterMiddleware> class. [ASP.NET Core MVC](xref:mvc/overview) adds routing to the middleware pipeline as part of its configuration and handles routing in MVC and Razor Pages apps. To learn how to use routing as a standalone component, see the [Use Routing Middleware](#use-routing-middleware) section.
### URL matching
URL matching is the process by which routing dispatches an incoming request to a *handler*. This process is based on data in the URL path but can be extended to consider any data in the request. The ability to dispatch requests to separate handlers is key to scaling the size and complexity of an app.
Incoming requests enter the <xref:Microsoft.AspNetCore.Builder.RouterMiddleware>, which calls the <xref:Microsoft.AspNetCore.Routing.IRouter.RouteAsync*> method on each route in sequence. The <xref:Microsoft.AspNetCore.Routing.IRouter> instance chooses whether to *handle* the request by setting the [RouteContext.Handler](xref:Microsoft.AspNetCore.Routing.RouteContext.Handler*) to a non-null <xref:Microsoft.AspNetCore.Http.RequestDelegate>. If a route sets a handler for the request, route processing stops, and the handler is invoked to process the request. If no route handler is found to process the request, the middleware hands the request off to the next middleware in the request pipeline.
The primary input to <xref:Microsoft.AspNetCore.Routing.IRouter.RouteAsync*> is the [RouteContext.HttpContext](xref:Microsoft.AspNetCore.Routing.RouteContext.HttpContext*) associated with the current request. The [RouteContext.Handler](xref:Microsoft.AspNetCore.Routing.RouteContext.Handler) and [RouteContext.RouteData](xref:Microsoft.AspNetCore.Routing.RouteContext.RouteData*) are outputs set after a route is matched.
A match that calls <xref:Microsoft.AspNetCore.Routing.IRouter.RouteAsync*> also sets the properties of the [RouteContext.RouteData](xref:Microsoft.AspNetCore.Routing.RouteContext.RouteData) to appropriate values based on the request processing performed thus far.
[RouteData.Values](xref:Microsoft.AspNetCore.Routing.RouteData.Values*) is a dictionary of *route values* produced from the route. These values are usually determined by tokenizing the URL and can be used to accept user input or to make further dispatching decisions inside the app.
[RouteData.DataTokens](xref:Microsoft.AspNetCore.Routing.RouteData.DataTokens*) is a property bag of additional data related to the matched route. <xref:Microsoft.AspNetCore.Routing.RouteData.DataTokens*> are provided to support associating state data with each route so that the app can make decisions based on which route matched. These values are developer-defined and do **not** affect the behavior of routing in any way. Additionally, values stashed in [RouteData.DataTokens](xref:Microsoft.AspNetCore.Routing.RouteData.DataTokens*) can be of any type, in contrast to [RouteData.Values](xref:Microsoft.AspNetCore.Routing.RouteData.Values), which must be convertible to and from strings.
[RouteData.Routers](xref:Microsoft.AspNetCore.Routing.RouteData.Routers) is a list of the routes that took part in successfully matching the request. Routes can be nested inside of one another. The <xref:Microsoft.AspNetCore.Routing.RouteData.Routers> property reflects the path through the logical tree of routes that resulted in a match. Generally, the first item in <xref:Microsoft.AspNetCore.Routing.RouteData.Routers> is the route collection and should be used for URL generation. The last item in <xref:Microsoft.AspNetCore.Routing.RouteData.Routers> is the route handler that matched.
<a name="lg"></a>
### URL generation
URL generation is the process by which routing can create a URL path based on a set of route values. This allows for a logical separation between route handlers and the URLs that access them.
URL generation follows a similar iterative process, but it starts with user or framework code calling into the <xref:Microsoft.AspNetCore.Routing.IRouter.GetVirtualPath*> method of the route collection. Each *route* has its <xref:Microsoft.AspNetCore.Routing.IRouter.GetVirtualPath*> method called in sequence until a non-null <xref:Microsoft.AspNetCore.Routing.VirtualPathData> is returned.
The primary inputs to <xref:Microsoft.AspNetCore.Routing.IRouter.GetVirtualPath*> are:
* [VirtualPathContext.HttpContext](xref:Microsoft.AspNetCore.Routing.VirtualPathContext.HttpContext)
* [VirtualPathContext.Values](xref:Microsoft.AspNetCore.Routing.VirtualPathContext.Values)
* [VirtualPathContext.AmbientValues](xref:Microsoft.AspNetCore.Routing.VirtualPathContext.AmbientValues)
Routes primarily use the route values provided by <xref:Microsoft.AspNetCore.Routing.VirtualPathContext.Values> and <xref:Microsoft.AspNetCore.Routing.VirtualPathContext.AmbientValues> to decide whether it's possible to generate a URL and what values to include. The <xref:Microsoft.AspNetCore.Routing.VirtualPathContext.AmbientValues> are the set of route values that were produced from matching the current request. In contrast, <xref:Microsoft.AspNetCore.Routing.VirtualPathContext.Values> are the route values that specify how to generate the desired URL for the current operation. The <xref:Microsoft.AspNetCore.Routing.VirtualPathContext.HttpContext> is provided in case a route should obtain services or additional data associated with the current context.
> [!TIP]
> Think of [VirtualPathContext.Values](xref:Microsoft.AspNetCore.Routing.VirtualPathContext.Values*) as a set of overrides for the [VirtualPathContext.AmbientValues](xref:Microsoft.AspNetCore.Routing.VirtualPathContext.AmbientValues*). URL generation attempts to reuse route values from the current request to generate URLs for links using the same route or route values.
The output of <xref:Microsoft.AspNetCore.Routing.IRouter.GetVirtualPath*> is a <xref:Microsoft.AspNetCore.Routing.VirtualPathData>. <xref:Microsoft.AspNetCore.Routing.VirtualPathData> is a parallel of <xref:Microsoft.AspNetCore.Routing.RouteData>. <xref:Microsoft.AspNetCore.Routing.VirtualPathData> contains the <xref:Microsoft.AspNetCore.Routing.VirtualPathData.VirtualPath> for the output URL and some additional properties that should be set by the route.
The [VirtualPathData.VirtualPath](xref:Microsoft.AspNetCore.Routing.VirtualPathData.VirtualPath*) property contains the *virtual path* produced by the route. Depending on your needs, you may need to process the path further. If you want to render the generated URL in HTML, prepend the base path of the app.
The [VirtualPathData.Router](xref:Microsoft.AspNetCore.Routing.VirtualPathData.Router*) is a reference to the route that successfully generated the URL.
The [VirtualPathData.DataTokens](xref:Microsoft.AspNetCore.Routing.VirtualPathData.DataTokens*) properties is a dictionary of additional data related to the route that generated the URL. This is the parallel of [RouteData.DataTokens](xref:Microsoft.AspNetCore.Routing.RouteData.DataTokens*).
### Create routes
Routing provides the <xref:Microsoft.AspNetCore.Routing.Route> class as the standard implementation of <xref:Microsoft.AspNetCore.Routing.IRouter>. <xref:Microsoft.AspNetCore.Routing.Route> uses the *route template* syntax to define patterns to match against the URL path when <xref:Microsoft.AspNetCore.Routing.IRouter.RouteAsync*> is called. <xref:Microsoft.AspNetCore.Routing.Route> uses the same route template to generate a URL when <xref:Microsoft.AspNetCore.Routing.IRouter.GetVirtualPath*> is called.
Most apps create routes by calling <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> or one of the similar extension methods defined on <xref:Microsoft.AspNetCore.Routing.IRouteBuilder>. Any of the <xref:Microsoft.AspNetCore.Routing.IRouteBuilder> extension methods create an instance of <xref:Microsoft.AspNetCore.Routing.Route> and add it to the route collection.
<xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> doesn't accept a route handler parameter. <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> only adds routes that are handled by the <xref:Microsoft.AspNetCore.Routing.RouteBuilder.DefaultHandler*>. The default handler is an `IRouter`, and the handler might not handle the request. For example, ASP.NET Core MVC is typically configured as a default handler that only handles requests that match an available controller and action. To learn more about routing in MVC, see <xref:mvc/controllers/routing>.
The following code example is an example of a <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> call used by a typical ASP.NET Core MVC route definition:
```csharp
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
```
This template matches a URL path and extracts the route values. For example, the path `/Products/Details/17` generates the following route values: `{ controller = Products, action = Details, id = 17 }`.
Route values are determined by splitting the URL path into segments and matching each segment with the *route parameter* name in the route template. Route parameters are named. The parameters defined by enclosing the parameter name in braces `{ ... }`.
The preceding template could also match the URL path `/` and produce the values `{ controller = Home, action = Index }`. This occurs because the `{controller}` and `{action}` route parameters have default values and the `id` route parameter is optional. An equals sign (`=`) followed by a value after the route parameter name defines a default value for the parameter. A question mark (`?`) after the route parameter name defines an optional parameter.
Route parameters with a default value *always* produce a route value when the route matches. Optional parameters don't produce a route value if there is no corresponding URL path segment. See the [Route template reference](#route-template-reference) section for a thorough description of route template scenarios and syntax.
In the following example, the route parameter definition `{id:int}` defines a [route constraint](#route-constraint-reference) for the `id` route parameter:
```csharp
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id:int}");
```
This template matches a URL path like `/Products/Details/17` but not `/Products/Details/Apples`. Route constraints implement <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> and inspect route values to verify them. In this example, the route value `id` must be convertible to an integer. See [route-constraint-reference](#route-constraint-reference) for an explanation of route constraints provided by the framework.
Additional overloads of <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> accept values for `constraints`, `dataTokens`, and `defaults`. The typical usage of these parameters is to pass an anonymously typed object, where the property names of the anonymous type match route parameter names.
The following <xref:Microsoft.AspNetCore.Builder.MapRouteRouteBuilderExtensions.MapRoute*> examples create equivalent routes:
```csharp
routes.MapRoute(
name: "default_route",
template: "{controller}/{action}/{id?}",
defaults: new { controller = "Home", action = "Index" });
routes.MapRoute(
name: "default_route",
template: "{controller=Home}/{action=Index}/{id?}");
```
> [!TIP]
> The inline syntax for defining constraints and defaults can be convenient for simple routes. However, there are scenarios, such as data tokens, that aren't supported by inline syntax.
The following example demonstrates a few additional scenarios:
```csharp
routes.MapRoute(
name: "blog",
template: "Blog/{*article}",
defaults: new { controller = "Blog", action = "ReadArticle" });
```
The preceding template matches a URL path like `/Blog/All-About-Routing/Introduction` and extracts the values `{ controller = Blog, action = ReadArticle, article = All-About-Routing/Introduction }`. The default route values for `controller` and `action` are produced by the route even though there are no corresponding route parameters in the template. Default values can be specified in the route template. The `article` route parameter is defined as a *catch-all* by the appearance of an asterisk (`*`) before the route parameter name. Catch-all route parameters capture the remainder of the URL path and can also match the empty string.
The following example adds route constraints and data tokens:
```csharp
routes.MapRoute(
name: "us_english_products",
template: "en-US/Products/{id}",
defaults: new { controller = "Products", action = "Details" },
constraints: new { id = new IntRouteConstraint() },
dataTokens: new { locale = "en-US" });
```
The preceding template matches a URL path like `/en-US/Products/5` and extracts the values `{ controller = Products, action = Details, id = 5 }` and the data tokens `{ locale = en-US }`.
### Route class URL generation
The <xref:Microsoft.AspNetCore.Routing.Route> class can also perform URL generation by combining a set of route values with its route template. This is logically the reverse process of matching the URL path.
> [!TIP]
> To better understand URL generation, imagine what URL you want to generate and then think about how a route template would match that URL. What values would be produced? This is the rough equivalent of how URL generation works in the <xref:Microsoft.AspNetCore.Routing.Route> class.
The following example uses a general ASP.NET Core MVC default route:
```csharp
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
```
With the route values `{ controller = Products, action = List }`, the URL `/Products/List` is generated. The route values are substituted for the corresponding route parameters to form the URL path. Since `id` is an optional route parameter, the URL is successfully generated without a value for `id`.
With the route values `{ controller = Home, action = Index }`, the URL `/` is generated. The provided route values match the default values, and the segments corresponding to the default values are safely omitted.
Both URLs generated round-trip with the following route definition (`/Home/Index` and `/`) produce the same route values that were used to generate the URL.
> [!NOTE]
> An app using ASP.NET Core MVC should use <xref:Microsoft.AspNetCore.Mvc.Routing.UrlHelper> to generate URLs instead of calling into routing directly.
For more information on URL generation, see the [Url generation reference](#url-generation-reference) section.
## Use routing middleware
Reference the [Microsoft.AspNetCore.App metapackage](xref:fundamentals/metapackage-app) in the app's project file.
Add routing to the service container in `Startup.ConfigureServices`:
[!code-csharp[](routing/samples/2.x/RoutingSample/Startup.cs?name=snippet_ConfigureServices&highlight=3)]
Routes must be configured in the `Startup.Configure` method. The sample app uses the following APIs:
* <xref:Microsoft.AspNetCore.Routing.RouteBuilder>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapGet*>: Matches only HTTP GET requests.
* <xref:Microsoft.AspNetCore.Builder.RoutingBuilderExtensions.UseRouter*>
[!code-csharp[](routing/samples/2.x/RoutingSample/Startup.cs?name=snippet_RouteHandler)]
The following table shows the responses with the given URIs.
| URI | Response |
| ---------------------- | ------------------------------------------------- |
| `/package/create/3` | Hello! Route values: [operation, create], [id, 3] |
| `/package/track/-3` | Hello! Route values: [operation, track], [id, -3] |
| `/package/track/-3/` | Hello! Route values: [operation, track], [id, -3] |
| `/package/track/` | The request falls through, no match. |
| `GET /hello/Joe` | Hi, Joe! |
| `POST /hello/Joe` | The request falls through, matches HTTP GET only. |
| `GET /hello/Joe/Smith` | The request falls through, no match. |
If you're configuring a single route, call <xref:Microsoft.AspNetCore.Builder.RoutingBuilderExtensions.UseRouter*> passing in an `IRouter` instance. You won't need to use <xref:Microsoft.AspNetCore.Routing.RouteBuilder>.
The framework provides a set of extension methods for creating routes (<xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions>):
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapDelete*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapGet*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewareDelete*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewareGet*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewarePost*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewarePut*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewareRoute*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapMiddlewareVerb*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapPost*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapPut*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapRoute*>
* <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapVerb*>
Some of listed methods, such as <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapGet*>, require a <xref:Microsoft.AspNetCore.Http.RequestDelegate>. The <xref:Microsoft.AspNetCore.Http.RequestDelegate> is used as the *route handler* when the route matches. Other methods in this family allow configuring a middleware pipeline for use as the route handler. If the `Map*` method doesn't accept a handler, such as <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapRoute*>, it uses the <xref:Microsoft.AspNetCore.Routing.RouteBuilder.DefaultHandler*>.
The `Map[Verb]` methods use constraints to limit the route to the HTTP Verb in the method name. For example, see <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapGet*> and <xref:Microsoft.AspNetCore.Routing.RequestDelegateRouteBuilderExtensions.MapVerb*>.
## Route template reference
Tokens within curly braces (`{ ... }`) define *route parameters* that are bound if the route is matched. You can define more than one route parameter in a route segment, but they must be separated by a literal value. For example, `{controller=Home}{action=Index}` isn't a valid route, since there's no literal value between `{controller}` and `{action}`. These route parameters must have a name and may have additional attributes specified.
Literal text other than route parameters (for example, `{id}`) and the path separator `/` must match the text in the URL. Text matching is case-insensitive and based on the decoded representation of the URLs path. To match a literal route parameter delimiter (`{` or `}`), escape the delimiter by repeating the character (`{{` or `}}`).
URL patterns that attempt to capture a file name with an optional file extension have additional considerations. For example, consider the template `files/{filename}.{ext?}`. When values for both `filename` and `ext` exist, both values are populated. If only a value for `filename` exists in the URL, the route matches because the trailing period (`.`) is optional. The following URLs match this route:
* `/files/myFile.txt`
* `/files/myFile`
You can use the asterisk (`*`) as a prefix to a route parameter to bind to the rest of the URI. This is called a *catch-all* parameter. For example, `blog/{*slug}` matches any URI that starts with `/blog` and has any value following it, which is assigned to the `slug` route value. Catch-all parameters can also match the empty string.
The catch-all parameter escapes the appropriate characters when the route is used to generate a URL, including path separator (`/`) characters. For example, the route `foo/{*path}` with route values `{ path = "my/path" }` generates `foo/my%2Fpath`. Note the escaped forward slash.
Route parameters may have *default values* designated by specifying the default value after the parameter name separated by an equals sign (`=`). For example, `{controller=Home}` defines `Home` as the default value for `controller`. The default value is used if no value is present in the URL for the parameter. Route parameters are made optional by appending a question mark (`?`) to the end of the parameter name, as in `id?`. The difference between optional values and default route parameters is that a route parameter with a default value always produces a value—an optional parameter has a value only when a value is provided by the request URL.
Route parameters may have constraints that must match the route value bound from the URL. Adding a colon (`:`) and constraint name after the route parameter name specifies an *inline constraint* on a route parameter. If the constraint requires arguments, they're enclosed in parentheses (`(...)`) after the constraint name. Multiple inline constraints can be specified by appending another colon (`:`) and constraint name.
The constraint name and arguments are passed to the <xref:Microsoft.AspNetCore.Routing.IInlineConstraintResolver> service to create an instance of <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> to use in URL processing. For example, the route template `blog/{article:minlength(10)}` specifies a `minlength` constraint with the argument `10`. For more information on route constraints and a list of the constraints provided by the framework, see the [Route constraint reference](#route-constraint-reference) section.
The following table demonstrates example route templates and their behavior.
| Route Template | Example Matching URI | The request URI… |
| ---------------------------------------- | ----------------------- | -------------------------------------------------------------------------- |
| `hello` | `/hello` | Only matches the single path `/hello`. |
| `{Page=Home}` | `/` | Matches and sets `Page` to `Home`. |
| `{Page=Home}` | `/Contact` | Matches and sets `Page` to `Contact`. |
| `{controller}/{action}/{id?}` | `/Products/List` | Maps to the `Products` controller and `List` action. |
| `{controller}/{action}/{id?}` | `/Products/Details/123` | Maps to the `Products` controller and `Details` action (`id` set to 123). |
| `{controller=Home}/{action=Index}/{id?}` | `/` | Maps to the `Home` controller and `Index` method (`id` is ignored). |
Using a template is generally the simplest approach to routing. Constraints and defaults can also be specified outside the route template.
> [!TIP]
> Enable [Logging](xref:fundamentals/logging/index) to see how the built-in routing implementations, such as <xref:Microsoft.AspNetCore.Routing.Route>, match requests.
## Route constraint reference
Route constraints execute when a match has occurred to the incoming URL and the URL path is tokenized into route values. Route constraints generally inspect the route value associated via the route template and make a yes/no decision about whether or not the value is acceptable. Some route constraints use data outside the route value to consider whether the request can be routed. For example, the <xref:Microsoft.AspNetCore.Routing.Constraints.HttpMethodRouteConstraint> can accept or reject a request based on its HTTP verb. Constraints are used in routing requests and link generation.
> [!WARNING]
> Don't use constraints for **input validation**. If constraints are used for **input validation**, invalid input results in a *404 - Not Found* response instead of a *400 - Bad Request* with an appropriate error message. Route constraints are used to **disambiguate** similar routes, not to validate the inputs for a particular route.
The following table demonstrates example route constraints and their expected behavior.
| constraint | Example | Example Matches | Notes |
| ---------- | ------- | --------------- | ----- |
| `int` | `{id:int}` | `123456789`, `-123456789` | Matches any integer |
| `bool` | `{active:bool}` | `true`, `FALSE` | Matches `true` or `false` (case-insensitive) |
| `datetime` | `{dob:datetime}` | `2016-12-31`, `2016-12-31 7:32pm` | Matches a valid `DateTime` value in the invariant culture. See preceding warning.|
| `decimal` | `{price:decimal}` | `49.99`, `-1,000.01` | Matches a valid `decimal` value in the invariant culture. See preceding warning.|
| `double` | `{weight:double}` | `1.234`, `-1,001.01e8` | Matches a valid `double` value in the invariant culture. See preceding warning.|
| `float` | `{weight:float}` | `1.234`, `-1,001.01e8` | Matches a valid `float` value in the invariant culture. See preceding warning.|
| `guid` | `{id:guid}` | `CD2C1638-1638-72D5-1638-DEADBEEF1638`, `{CD2C1638-1638-72D5-1638-DEADBEEF1638}` | Matches a valid `Guid` value |
| `long` | `{ticks:long}` | `123456789`, `-123456789` | Matches a valid `long` value |
| `minlength(value)` | `{username:minlength(4)}` | `Rick` | String must be at least 4 characters |
| `maxlength(value)` | `{filename:maxlength(8)}` | `Richard` | String must be no more than 8 characters |
| `length(length)` | `{filename:length(12)}` | `somefile.txt` | String must be exactly 12 characters long |
| `length(min,max)` | `{filename:length(8,16)}` | `somefile.txt` | String must be at least 8 and no more than 16 characters long |
| `min(value)` | `{age:min(18)}` | `19` | Integer value must be at least 18 |
| `max(value)` | `{age:max(120)}` | `91` | Integer value must be no more than 120 |
| `range(min,max)` | `{age:range(18,120)}` | `91` | Integer value must be at least 18 but no more than 120 |
| `alpha` | `{name:alpha}` | `Rick` | String must consist of one or more alphabetical characters (`a`-`z`, case-insensitive) |
| `regex(expression)` | `{ssn:regex(^\\d{{3}}-\\d{{2}}-\\d{{4}}$)}` | `123-45-6789` | String must match the regular expression (see tips about defining a regular expression) |
| `required` | `{name:required}` | `Rick` | Used to enforce that a non-parameter value is present during URL generation |
Multiple, colon-delimited constraints can be applied to a single parameter. For example, the following constraint restricts a parameter to an integer value of 1 or greater:
```csharp
[Route("users/{id:int:min(1)}")]
public User GetUserById(int id) { }
```
> [!WARNING]
> Route constraints that verify the URL and are converted to a CLR type (such as `int` or `DateTime`) always use the invariant culture. These constraints assume that the URL is non-localizable. The framework-provided route constraints don't modify the values stored in route values. All route values parsed from the URL are stored as strings. For example, the `float` constraint attempts to convert the route value to a float, but the converted value is used only to verify it can be converted to a float.
## Regular expressions
The ASP.NET Core framework adds `RegexOptions.IgnoreCase | RegexOptions.Compiled | RegexOptions.CultureInvariant` to the regular expression constructor. See <xref:System.Text.RegularExpressions.RegexOptions> for a description of these members.
Regular expressions use delimiters and tokens similar to those used by Routing and the C# language. Regular expression tokens must be escaped. To use the regular expression `^\d{3}-\d{2}-\d{4}$` in routing, the expression must have the `\` (single backslash) characters provided in the string as `\\` (double backslash) characters in the C# source file in order to escape the `\` string escape character (unless using [verbatim string literals](/dotnet/csharp/language-reference/keywords/string)). To escape routing parameter delimiter characters (`{`, `}`, `[`, `]`), double the characters in the expression (`{{`, `}`, `[[`, `]]`). The following table shows a regular expression and the escaped version.
| Regular Expression | Escaped Regular Expression |
| --------------------- | ------------------------------ |
| `^\d{3}-\d{2}-\d{4}$` | `^\\d{{3}}-\\d{{2}}-\\d{{4}}$` |
| `^[a-z]{2}$` | `^[[a-z]]{{2}}$` |
Regular expressions used in routing often start with the caret (`^`) character and match starting position of the string. The expressions often end with the dollar sign (`$`) character and match end of the string. The `^` and `$` characters ensure that the regular expression match the entire route parameter value. Without the `^` and `$` characters, the regular expression match any substring within the string, which is often undesirable. The following table provides examples and explains why they match or fail to match.
| Expression | String | Match | Comment |
| ------------ | --------- | :---: | -------------------- |
| `[a-z]{2}` | hello | Yes | Substring matches |
| `[a-z]{2}` | 123abc456 | Yes | Substring matches |
| `[a-z]{2}` | mz | Yes | Matches expression |
| `[a-z]{2}` | MZ | Yes | Not case sensitive |
| `^[a-z]{2}$` | hello | No | See `^` and `$` above |
| `^[a-z]{2}$` | 123abc456 | No | See `^` and `$` above |
For more information on regular expression syntax, see [.NET Framework Regular Expressions](/dotnet/standard/base-types/regular-expression-language-quick-reference).
To constrain a parameter to a known set of possible values, use a regular expression. For example, `{action:regex(^(list|get|create)$)}` only matches the `action` route value to `list`, `get`, or `create`. If passed into the constraints dictionary, the string `^(list|get|create)$` is equivalent. Constraints that are passed in the constraints dictionary (not inline within a template) that don't match one of the known constraints are also treated as regular expressions.
## Custom Route Constraints
In addition to the built-in route constraints, custom route constraints can be created by implementing the <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> interface. The <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> interface contains a single method, `Match`, which returns `true` if the constraint is satisfied and `false` otherwise.
To use a custom <xref:Microsoft.AspNetCore.Routing.IRouteConstraint>, the route constraint type must be registered with the app's <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap> in the app's service container. A <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap> is a dictionary that maps route constraint keys to <xref:Microsoft.AspNetCore.Routing.IRouteConstraint> implementations that validate those constraints. An app's <xref:Microsoft.AspNetCore.Routing.RouteOptions.ConstraintMap> can be updated in `Startup.ConfigureServices` either as part of a [services.AddRouting](xref:Microsoft.Extensions.DependencyInjection.RoutingServiceCollectionExtensions.AddRouting*) call or by configuring <xref:Microsoft.AspNetCore.Routing.RouteOptions> directly with `services.Configure<RouteOptions>`. For example:
```csharp
services.AddRouting(options =>
{
options.ConstraintMap.Add("customName", typeof(MyCustomConstraint));
});
```
The constraint can then be applied to routes in the usual manner, using the name specified when registering the constraint type. For example:
```csharp
[HttpGet("{id:customName}")]
public ActionResult<string> Get(string id)
```
## URL generation reference
The following example shows how to generate a link to a route given a dictionary of route values and a <xref:Microsoft.AspNetCore.Routing.RouteCollection>.
[!code-csharp[](routing/samples/2.x/RoutingSample/Startup.cs?name=snippet_Dictionary)]
The <xref:Microsoft.AspNetCore.Routing.VirtualPathData.VirtualPath> generated at the end of the preceding sample is `/package/create/123`. The dictionary supplies the `operation` and `id` route values of the "Track Package Route" template, `package/{operation}/{id}`. For details, see the sample code in the [Use Routing Middleware](#use-routing-middleware) section or the [sample app](https://github.com/dotnet/AspNetCore.Docs/tree/master/aspnetcore/fundamentals/routing/samples).
The second parameter to the <xref:Microsoft.AspNetCore.Routing.VirtualPathContext> constructor is a collection of *ambient values*. Ambient values are convenient to use because they limit the number of values a developer must specify within a request context. The current route values of the current request are considered ambient values for link generation. In an ASP.NET Core MVC app's `About` action of the `HomeController`, you don't need to specify the controller route value to link to the `Index` action—the ambient value of `Home` is used.
Ambient values that don't match a parameter are ignored. Ambient values are also ignored when an explicitly provided value overrides the ambient value. Matching occurs from left to right in the URL.
Values explicitly provided but that don't match a segment of the route are added to the query string. The following table shows the result when using the route template `{controller}/{action}/{id?}`.
| Ambient Values | Explicit Values | Result |
| ---------------------------------- | -------------------------------------- | ----------------------- |
| controller = "Home" | action = "About" | `/Home/About` |
| controller = "Home" | controller = "Order", action = "About" | `/Order/About` |
| controller = "Home", color = "Red" | action = "About" | `/Home/About` |
| controller = "Home" | action = "About", color = "Red" | `/Home/About?color=Red` |
If a route has a default value that doesn't correspond to a parameter and that value is explicitly provided, it must match the default value:
```csharp
routes.MapRoute("blog_route", "blog/{*slug}",
defaults: new { controller = "Blog", action = "ReadPost" });
```
Link generation only generates a link for this route when the matching values for `controller` and `action` are provided.
## Complex segments
Complex segments (for example `[Route("/x{token}y")]`) are processed by matching up literals from right to left in a non-greedy way. See [this code](https://github.com/aspnet/AspNetCore/blob/release/2.2/src/Http/Routing/src/Patterns/RoutePatternMatcher.cs#L293) for a detailed explanation of how complex segments are matched. The [code sample](https://github.com/aspnet/AspNetCore/blob/release/2.2/src/Http/Routing/src/Patterns/RoutePatternMatcher.cs#L293) is not used by ASP.NET Core, but it provides a good explanation of complex segments.
::: moniker-end
| 82.247485 | 831 | 0.760128 | eng_Latn | 0.982368 |
d5be3a2ad2ed73e0cf706014cc9457cba4db68d2 | 86 | md | Markdown | README.md | eminuk/fun_blueScreen | d8ef785dac278469c935e72c812e277998bd18a1 | [
"Apache-2.0"
] | null | null | null | README.md | eminuk/fun_blueScreen | d8ef785dac278469c935e72c812e277998bd18a1 | [
"Apache-2.0"
] | null | null | null | README.md | eminuk/fun_blueScreen | d8ef785dac278469c935e72c812e277998bd18a1 | [
"Apache-2.0"
] | null | null | null | # fun_blueScreen
windows 7 이전 스타일의 블루 스크린
<https://eminuk.github.io/fun_blueScreen/>
| 17.2 | 42 | 0.767442 | kor_Hang | 0.998302 |
d5bfac70a4128f11bf07b3a5466b7afc03704f7f | 8,414 | md | Markdown | byos/serverless/deployment.md | kyleburnsdev/OpenHack | 35f54eed0efa15241879b875fc691e0efcd8be27 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-10-16T11:42:05.000Z | 2020-10-16T11:42:05.000Z | byos/serverless/deployment.md | kyleburnsdev/OpenHack | 35f54eed0efa15241879b875fc691e0efcd8be27 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | byos/serverless/deployment.md | kyleburnsdev/OpenHack | 35f54eed0efa15241879b875fc691e0efcd8be27 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-09-14T03:17:22.000Z | 2021-09-15T15:06:17.000Z | # Serverless Openhack #
## Setting up Permissions
Before continuing ensure you understand the permissions needed to run the OpenHack on your Azure subscription.
**Initial Setup**
To perform the setup and deployment to prepare for the OpenHack you must be be assigned to the Owner role on the Azure subscription(s).
To validate this, navigate to the <a href="https://portal.azure.com" target="_blank">Azure Portal</a>. Click on **All Services** -> **Subscriptions** -> **Access Control (IAM)**.
Enter the email address in the **Check access** text box to view the current permissions of the user performing the setup.
**Performing the OpenHack**
Each attendee in the OpenHack will be assigned the **Owner** role on a resource group unique to their team. This is covered later in this document in the deployment section.
## Common Azure Resources
The following is a list of common Azure resources that are deployed and utilized during the OpenHack.
Ensure that these services are not blocked by Azure Policy. As this is an OpenHack, the services that attendees can utilize are not limited to this list so subscriptins with a tightly controlled service catalog may run into issues if the service an attendee wishes to use is disabled via policy.
| Azure resource | Resource Providers |
| ------------------------ | --------------------------------------- |
| Azure Logic Apps | Microsoft.Logic |
| Azure Functions | Microsoft.Web |
| Azure App Service | Microsoft.Web |
| Azure Storage | Microsoft.Storage |
| Azure Cosmos DB | Microsoft.DocumentDb |
| Event Hub | Microsoft.EventHub |
| Event Grid | Microsoft.EventGrid |
| Azure Cognitive Services | Microsoft.CognitiveServices |
| Virtual Network | Microsoft.Network |
| Azure Stream Analytics | Microsoft.StreamAnalytics |
| Virtual Machine | Microsoft.VMWare |
| Azure DevOps | Microsoft.VSOnline |
| Service Bus | Microsoft.ServiceBus |
> Note: Resource Provider Registration can be found at https://portal.azure.com/_yourtenantname_.onmicrosoft.com/resource/subscriptions/_yoursubscriptionid_/resourceproviders
## Attendee Computers
Attendees will be required to install software on the workstations that they are performing the OpenHack on. Ensure they have adequate permissions to perform software installation.
# Deployment Instructions #
### For deployment, you will run a powershell script that executes an ARM template to setup the appropriate Resource Group for each team. You will then manually add team members as owwers to the resource group. ###
### Powershell ###
1. Open a **PowerShell ISE** window, run the following command, if prompted, click **Yes to All**:
```PowerShell
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
```
2. Make sure you have the latest PowerShell Azure module installed by executing the following command:
```PowerShell
Install-Module -Name Az -AllowClobber -Scope CurrentUser
```
3. If you installed an update, **close** the PowerShell ISE window, then **re-open** it. This ensures that the latest version of the Az module is used.
4. Execute the following to sign in to the Azure account:
```PowerShell
Connect-AzAccount
```
5. Open the `serverless\deploy\deployAll.ps1` PowerShell script in the PowerShell ISE window. There is **nothing** to update, but if you wanted you ***could*** set the location and not require the read-in from the prompt.:
```PowerShell
$region = Read-Host "What Region Resources be deployed to (i.e. centralus, southcentralus, japaneast, etc)?";
#could be
$region = "centralus"
```
6. Press **F5** to run the script, this will do the following:
> *Note: if you receive an error that `azuredeploy.json` cannot be found, make sure the current directory of the Console window of **ISE** is the `serverless\deploy` folder.*
* Create resource group entitled **ServerlessOpenHackRGXX-[location]** where XX is the two-digit team number and location is the location you entered or have in the script. For example, team 2 in southcentralus would have rg ServerlessOpenHackRG02-southcentralus
* Deploy two storage accounts with containers [sohsalesxxxxxxxxx] and [sohvmdiagxxxxxxxxx]
* Deploy a VPN [soh-vnet]
* Deploy a Network Interface [soh-jumpbox-nic]
* Deploy a Network Security Group [soh-jumpbox-nsg]
* Deploy a public ID [soh-jumpbox-pip]
* Deoply a VM dis [soh-jumpbox_OsDisk_1_xxxxxxxxxxxxx]
* Deploy a VM [soh-jumpbox]
### Manual step ###
7. After deployment, manually add appropriate users with owner access on the appropriate resource group for their team, so that they will have ability to create and deploy resources in that resource group.
# Deployment Artifacts / Validation #
### After deployment has completed, you should see the following resources in each team's Resource Group: ###
* Team XX resource group (i.e. ServerlessOpenHackRG01-centralus)
* VM - [soh-jumpbox]
* NIC - [soh-jumpbox-nic]
* NSG - [soh-jumpbox-nsg]
* Public IP - [soh-jumpbox-pip]
* Disk - [soh-jumpbox_OsDisk_1_xxxxxxxx]
* VPN - [soh-vnet]
* Storage Sales [sohsalesxxxxxxxxxx]
* Storage VMDiagnostics [sohvmdiagxxxxxxxxx]
### More detail on the usage of the services ###
## As the teams progress: ##
* Make sure teams can create and work with storage
* Make sure teams can create Logic Apps
* Make sure teams can create functions using standard/free function app service, and eventually updated to premium
* Make sure teams can create APIM
* Make sure teams can create Event Hubs and integrate triggers with Event Grid
* Make sure teams can create Service Bus and use for appropriate messaging
* Make sure teams can use Stream Analytics to filter information
* Make sure teams can provision cognitive services
## Services and application overview ##
* Logic Apps
* users will make at least two, likely four or five
* responding to events and processing to push emails against a 3rd party Outlook/Business server
* route messages to functions or other responding events
* aggregate data for reporting, etc.
* Cosmos DB and/or Azure Tables
* Cosmos DB will be a lot easier in the later challenges, so recommend using Cosmos DB
* They will need to be able to create tables and respond to events against Cosmos DB
* APIM
* participants will create an API management gateway to group internal and external apis
* use APIM to build various subscriptions for access
* Azure Functions
* multiple functions will be created/deployed
* http or event grid or storage triggered, will eventually need to be able to push requests to a VPN endpoint
* App Service
* for azure functions
* starts with basic/free plan
* will eventually need Premium plan for network integration to route traffic/lock down functions.
* Cognitive Services to parse intent on messages/reviews
* using Text Analytics API, integrated with events and queues
* Event Grid/Event Hub for message processing
* Service Bus for message queueing
* Azure Storage
* public blob with container to receive hundreds of csv files that will be pushed to the storage by third party app
* ability to respond to storage creation events via Logic App or Azure Function
* Networking
* teams will need build something that pushes to a third-party VPN
* VM
* a Jumpbox VM is created for teams to view VPN endpoints from third-party service.
* Stream Analytics
* To aggregate data for reporting,
## Other tools/resources: ##
* DevOps
* teams will need to setup a CI/CD pipeline, recommend use of DevOps to deploy functions to to Azure
OR
* GitHub
* use a github pipeline to deploy to azure
* One or more of the following:
* Visual Studio - teams will need to be able to write code in Visual Studio
* Java / Maven
* VS Code / Python & node/other development
* Postman
| 45.728261 | 296 | 0.707987 | eng_Latn | 0.98947 |
d5c00e57404af425134cb25ce1ba44ff91c2dac8 | 604 | md | Markdown | api/Project.WorkWeek.Finish.md | skucab/VBA-Docs | 2912fe0343ddeef19007524ac662d3fcb8c0df09 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-08T20:10:22.000Z | 2021-04-08T20:10:22.000Z | api/Project.WorkWeek.Finish.md | skucab/VBA-Docs | 2912fe0343ddeef19007524ac662d3fcb8c0df09 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-09-28T07:52:15.000Z | 2021-09-28T07:52:15.000Z | api/Project.WorkWeek.Finish.md | skucab/VBA-Docs | 2912fe0343ddeef19007524ac662d3fcb8c0df09 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-09-28T07:45:29.000Z | 2021-09-28T07:45:29.000Z | ---
title: WorkWeek.Finish Property (Project)
ms.prod: project-server
api_name:
- Project.WorkWeek.Finish
ms.assetid: d66fac85-0644-4f7d-445f-c4712aee6dbe
ms.date: 06/08/2017
localization_priority: Normal
---
# WorkWeek.Finish Property (Project)
Gets or sets the finish date of a work week represented by the **WorkWeek** object. Read/write **Variant**.
## Syntax
_expression_. `Finish`
_expression_ An expression that returns a [WorkWeek](./Project.WorkWeek.md) object.
## See also
[WorkWeek Object](Project.WorkWeek.md)
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 20.827586 | 107 | 0.754967 | eng_Latn | 0.89286 |
d5c129c8f45534ddf7a0577e5f0d46fb586387b9 | 668 | md | Markdown | lib/bids-matlab/tests/data/reports/ds000117_anat.md | cpp-lln-lab/eeg_bids_conversion | 6e3de0df284b261fbf9c5effaf022e25881271d2 | [
"MIT"
] | 2 | 2021-10-15T08:20:43.000Z | 2021-10-31T20:34:26.000Z | lib/bids-matlab/tests/data/reports/ds000117_anat.md | cpp-lln-lab/eeg_bids_conversion | 6e3de0df284b261fbf9c5effaf022e25881271d2 | [
"MIT"
] | null | null | null | lib/bids-matlab/tests/data/reports/ds000117_anat.md | cpp-lln-lab/eeg_bids_conversion | 6e3de0df284b261fbf9c5effaf022e25881271d2 | [
"MIT"
] | 1 | 2021-10-15T08:22:10.000Z | 2021-10-15T08:22:10.000Z | ANAT REPORT
The data acquisition was performed in the MRC Cognition and Brain Sciences Unit,
{{InstitutionalDepartmentName}}, 15 Chaucer Road, Cambridge CB2 7EF, UK.
MRI scans were acquired at 3 Tesla using a TrioTim system from Siemens, with serial
number 35119. The software version was syngo_MR_B15.
MPRAGE GR_IR SP_MP_OSP T1w structural MRI data were collected ({{nb_slices}} slices;
repetition time, TR= 2.25 s; echo time, TE= {{echo_time}} ms; flip angle, FA=
9 deg; field of view, FOV= {{fov}} mm; matrix size= {{mat_size}}; voxel size=
{{vox_size}} mm).
This text was automatically generated by [BIDS-matlab](https://github.com/bids-standard/bids-matlab).
| 44.533333 | 101 | 0.758982 | eng_Latn | 0.933788 |
d5c175998e9fb80182aa26ab5ab7e87b8256916c | 11,387 | md | Markdown | draft/PHP/Pengenalan Dasar PHP.md | ffadilaputra/miniclass-web | fc5568e5b06ce69b1996e5b5d07692fa44acf2e6 | [
"MIT"
] | 1 | 2022-03-12T12:11:46.000Z | 2022-03-12T12:11:46.000Z | draft/PHP/Pengenalan Dasar PHP.md | ffadilaputra/miniclass-web | fc5568e5b06ce69b1996e5b5d07692fa44acf2e6 | [
"MIT"
] | null | null | null | draft/PHP/Pengenalan Dasar PHP.md | ffadilaputra/miniclass-web | fc5568e5b06ce69b1996e5b5d07692fa44acf2e6 | [
"MIT"
] | null | null | null | # 1. PENGENALAN DASAR PHP
## 1.1 Pengertian PHP
PHP berasal dari kata <i>Hypertext Preprocessor</i> atau dapat juga disebut dengan <i>server-side programming/script</i> adalah sebuah bahasa pemrograman yang dijalankan/diproses oleh web server atau bisa disebut open source.
PHP dapat digunakan untuk membuat website dinamis yang dapat menyesuaikan tampilan tergantung kondisi serta dapat membuat halaman yang berbeda sesuai dengan inputan dari user. Lalu juga dapat menyimpan data ke dalam database, dan sebagainya.
<br>
<br>
## 1.2 Sintaks PHP
Berikut sintaks dasar penulisan PHP. Diawali dengan tag `<?php` dan diakhiri dengan tag penutup `?>`
``` PHP
<?php
echo "Hello World!";
?>
```
Kode program PHP dapat disisipkan ke dalam HTML. Agar dapat menjalankan kode program PHP, maka file harus disimpan sebagai file PHP dengan ekstensi .php
``` HTML
<html>
<head>
</head>
<body>
<?php
echo "Hello World!";
?>
</body>
</html>
```
Kode Program diatas akan menampilkan output berupa kalimat "Hello World!"
<br>
## 1.3 Aturan Dasar PHP
- Penulisan Perintah dalam PHP
<br>Setiap diakhir baris perintah diakhiri dengan tanda _semicolon_ atau titik koma ( ; )
- Case Sensitive
<br> Di dalam PHP membedakan huruf besar dan huruf kecil untuk penamaan variabel, sehingga variabel ```$name``` dan ```$NAME``` dianggap sebagai 2 variabel yang berbeda. Contoh penulisan variabel seperti dibawah ini
``` PHP
<?php
$name = “Nama Anda”;
echo $name; // output: Nama Anda
ECHO $name; // output: Nama Anda
echo $NAME; // output: error, karena tidak ada variabel $NAME
?>
```
- Komentar
<br> 1) Komentar satu baris dapat menggunakan // atau #
<br> 2) Komentar dua baris atau banyak dapat menggunakan /*……*/
<br> 3) Komentar <b>HARUS</b> berada di jalur mereka sendiri
``` PHP
<?php
$keliling = 4 * $sisi; // mengitung keliling persegi
echo $keliling; # menampilkan hasil
?>
```
- Echo dan Print
<br> Dapat menampilkan data ke layar dengan menggunakan perintah echo dan print. Untuk penulisannya sama saja, tetapi yang membedakan hanyalah kode bawaannya yaitu echo dan print.
``` PHP
<?php
$kalimat1 = "Halo Selamat Malam";
$kalimat2 = "Selamat Datang di Miniclass Web";
echo "<h1> $kalimat1 </h1>"; // menampilkan "Halo Selamat Malam"
echo "<h2> $kalimat2 </h2>"; // menampilkan "Selamat Datang di Miniclass Web"
print "<h1> $kalimat1 </h1>"; // menampilkan "Halo Selamat Malam"
print "<h2> $kalimat2 </h2>"; // menampilkan "Selamat Datang di Miniclass Web"
?>
```
## 1.4 Variabel
Variabel adalah kode program dalam bahasa pemrograman untuk menyimpan suatu nilai sementara yang dimana nantinya akan dikembalikan.
Aturan-aturan variabel dalam PHP
1. Penulisan variabel harus diawali dengan tanda dollar ($)
2. Variabel berisi karakter alfanumerik. Nama variabel harus diawali dengan huruf atau karakter garis bawah ( _ ), tidak boleh diawali dengan angka.
3. Variabel tidak perlu dideklarasikan terlebih dahulu.
4. Variabel merupakan case sensitive.
``` PHP
<?php
// Penulisan yang salah
$4six; // Variabel tidak boleh menggunakan angka didepan
$jenis kelamin // Variabel tidak boleh menggunakan spasi
?>
```
``` PHP
<?php
// Penulisan yang benar
$a;
$nama;
$Kelas;
$_tanggal_lahir;
$NAMA_LENGKAP;
?>
```
## 1.5 Tipe Data
Sama seperti di bahasa pemrograman yang lain, di dalam PHP juga memiliki tipe data yang sama yaitu Integer, String, Float, Boolean, Array, Resource, dan NULL. Tetapi, pada PHP tidak perlu menuliskan tipe datanya.
``` PHP
<?php
$text = "Hello World!";
$angka = 12345;
$desimal = 3.5;
$kosong = NULL;
?>
```
## 1.6 Operator
Operator adalah simbol operasi yang digunakan untuk suatu nilai dan variabel.
Berikut 7 jenis operator PHP:
- Operator Relasi
- Operator Logika
- Operator Aritmatika
- Operator Assignment
- Operator Increment & Decrement
- Operator Bitwise, dan
- Operator Ternary
### <br>1.6.1 Operator Relasi
``` PHP
<?php
$angka1 = 8;
$angka2 = 23;
echo "<h2>Operator Relasi</h2>";
echo "$angka1 < $angka2 adalah "; var_dump($angka1 < $angka2);
echo "<br>$angka1 > $angka2 adalah "; var_dump($angka1 > $angka2);
echo "<br>$angka1 == $angka2 adalah "; var_dump($angka1 == $angka2);
echo "<br>$angka1 != $angka2 adalah "; var_dump($angka1 != $angka2);
?>
```
### 1.6.2 Operator Logika
``` PHP
<?php
$angka1 = 8;
$angka2 = 23;
echo "<h2>Operator Logika</h2>";
echo "angka1 AND angka2 adalah "; var_dump($angka1 AND $angka2);
echo "<br> angka1 OR angka2 adalah "; var_dump($angka1 OR $angka2);
echo "<br> angka1 XOR angka2 adalah "; var_dump($angka1 XOR $angka2);
echo "<br> angka1 && angka2 adalah "; var_dump($angka1 && $angka2);
echo "<br> angka1 || angka2 adalah "; var_dump($angka1 || $angka2);
echo "<br> !angka1 || angka2 adalah "; var_dump(!$angka1 || $angka2);
?>
```
### 1.6.3 Operator Aritmatika
``` PHP
<?php
$angka1 = 8;
$angka2 = 23;
echo "<h2>Operator Aritmatika</h2>";
echo "Hasil penjumlahan $angka1 dan $angka2 adalah ";
echo $angka1 + $angka2;
echo "<br>Hasil pengurangan $angka1 dan $angka2 adalah ";
echo $angka1 - $angka2;
echo "<br>Hasil perkalian $angka1 dan $angka2 adalah ";
echo $angka1 * $angka2;
echo "<br>Hasil pembagian $angka1 dan $angka2 adalah ";
echo $angka1 / $angka2;
echo "<br>Hasil modulus $angka1 dan $angka2 adalah ";
echo $angka1 % $angka2;
echo "<br>Hasil decrement $angka1 adalah ";
echo --$angka1;
echo "<br>Hasil increment $angka2 adalah ";
echo ++$angka2;
?>
```
### 1.6.4 Operator Assignment
Assignment by Value yaitu memberikan nilai ke suatu variabel
``` PHP
<?php
echo "<h3>Operasi Penjumlahan</h3>";
$angka = 8;
$angka += 23;
echo "Hasil operasi tersebut adalah $angka";
echo "<br><br>";
echo "<h3>Operasi Pengurangan</h3>";
$angka = 8;
$angka -= 23;
echo "Hasil operasi tersebut adalah $angka";
echo "<br><br>";
echo "<h3>Operasi Perkalian</h3>";
$angka = 8;
$angka *= 23;
echo "Hasil operasi tersebut adalah $angka";
echo "<br><br>";
echo "<h3>Operasi Pembagian</h3>";
$angka = 8;
$angka /= 23;
echo "Hasil operasi tersebut adalah $angka";
echo "<br><br>";
echo "<h3>Operasi Modulus</h3>";
$angka = 8;
$angka %= 23;
echo "Hasil operasi tersebut adalah $angka";
echo "<br><br>";
echo "<h3>Operasi Penggabungan Angka</h3>";
$angka = 8;
$angka .= 23;
echo "Hasil operasi tersebut adalah $angka";
?>
```
### 1.6.5 Operator Increment & Decrement
- Pre-Increment (++a)
<br>Menambahkan 1 nilai sebelum operasi telah dilakukan
- Post-Increment (a++)
<br>Menambahkan 1 nilai setelah operasi telah dilakukan
- Pre-Decrement (--a)
<br>Mengurangi 1 nilai sebelum operasi telah dilakukan
- Post-Decrement (a--)
<br>Mengurangi 1 nilai setelah operasi telah dilakukan
``` PHP
<?php
$a = 2;
echo "-- Pre Increment --";
echo "<br>Hasil A: " . $a;
echo "<br>Hasil A: " . ++$a;
echo "<br>Hasil A: " . $a;
$a = 2;
echo "<br><br>-- Post Increment --";
echo "<br>Hasil A: " . $a;
echo "<br>Hasil A: " . $a++;
echo "<br>Hasil A: " . $a;
?>
```
``` PHP
<?php
$b = 5;
echo "-- Pre Decrement --";
echo "<br>Hasil B: " . $b;
echo "<br>Hasil B: " . --$b;
echo "<br>Hasil B: " . $b;
$b = 5;
echo "<br><br>-- Post Decrement --";
echo "<br>Hasil B: " . $b;
echo "<br>Hasil B: " . $b--;
echo "<br>Hasil B: " . $b;
?>
```
### 1.6.6 Operator Bitwise
- Bitwise OR ( | )
<br>Bernilai 1 jika salah satu bit bernilai 1 dan selain itu bernilai 0
``` PHP
<?php
$a = 3; // 0011 (Bilangan Biner)
$b = 6; // 0110
echo "Hasil Output = " . ($a|$b); // output = 7
// 0011
// 0110
// -----
// 0111 -> 7
?>
```
- Bitwise AND ( & )
<br>Bernilai 1 ketika semua bit bernilai 1 dan selain itu bernilai 0
``` PHP
<?php
$a = 3; // 0011 (Bilangan Biner)
$b = 6; // 0110
echo "Hasil Output = " . ($a&$b); // output = 2
// 0011
// 0110
// -----
// 0010 -> 2
?>
```
- Bitwise XOR ( ^ )
<br>Bernilai 1 jika terdapat salah satu bit-nya memiliki nilai 1 dan 0 dan bernilai 0 jika semua bit memiliki nilai 1 atau 0
``` PHP
<?php
$a = 3; // 0011 (Bilangan Biner)
$b = 6; // 0110
echo "Hasil Output = " . ($a^$b); // output = 5
// 0011
// 0110
// -----
// 0101 -> 5
?>
```
- Bitwise Negasi/Kebalikan ( ~ )
<br>Jika bit bernilai 1 maka akan menghasilkan 0 sedangkan bit bernilai 0 maka akan menghasilkan 1
``` PHP
<?php
$c = 7; // 0111 (Bilangan Biner)
echo "Hasil Output = " . ~$c; // output = -8
// 0111 // RUMUS
// ----- // ~n = -(n+1)
// 1000 -> 8 // ~(-n) = (n-1)
?>
```
- Bitwise Right Shift ( >> )
<br>Pergeseran bit ke kanan sebanyak n. n adalah banyaknya pergeseran
``` PHP
<?php
$d = 4; // 0100 (Bilangan Biner)
echo "Hasil Output = " . $d>>2; // output = 1
// 0100
// -----
// 0001 -> 1
?>
```
- Bitwise Left Shift ( << )
<br>Pergeseran bit ke kiri sebanyak n. n adalah banyaknya pergeseran
``` PHP
<?php
$d = 4; // 0100 (Bilangan Biner)
echo "Hasil Output = " . $d<<2; // output = 16
// 0100
// -----
// 0000 -> 16
?>
```
### 1.6.7 Operator Ternary
Operator Ternary adalah operator yang melibatkan 3 buah operand. Operator Ternary digunakan untuk melakukan penilaian terhadap suatu nilai yang didasari oleh ekspresi tertentu.
``` PHP
<?php
$p = "Miniclass Web";
$hasil;
$hasil = ($p == "Miniclass Web" ? "Mari Kita Belajar Web" : "Batal Belajar Web");
echo $hasil; // Output = Mari Kita Belajar Web
?>
```
# 2. Percabangan
## 2.1. If - Else
Percabangan If/Else memiliki dua pilihan. Jika kondisi bernilai true, maka blok if akan dikerjakan. Jika kondisi bernilai false, maka blok else akan dikerjakan.
```php
<?php
$tiket = 1;
if ($tiket > 0 ){
echo "Kamu boleh masuk ke kereta ini";
} else {
echo "Silahkan beli tiket dulu";
}
?>
```
## 2.2. If - Else if - Else
Percabangan If/Elseif/Else sama dengan percabangan If/Else. Bedanya percabangan If/Elseif/Else bisa memiliki lebih dari 2 kondisi
```php
<?php
$tiket = 1;
if ($tiket = 1 ){
echo "Kamu boleh masuk ke kereta ini";
} elseif($tiket > 1){
echo "Siapa pemilik tiket yang lainnya?";
}
} else {
echo "Silahkan beli tiket dulu";
}
?>
```
# 3. Perulangan
## 3.1. For
Perulangan for digunakan ketika Anda mengetahui sebelumnya berapa kali skrip tersebut harus dijalankan.
```php
<?php
for ($x = 0; $x <= 10; $x++) {
echo "The number is: $x <br>";
}
?>
```
## 3.2. While
Perulangan while akan melakukan pengecekan kondisi terlebih dahulu. Setelah itu, jika kondisinya bernilai benar maka blok kode tersebut akan dieksekusi. Begitupun seterusnya, sampai menemukan kondisi yang bernilai salah.
```php
<?php
$x = 1;
while($x <= 5) {
echo "The number is: $x<br>";
$x++;
}
?>
```
## 3.3. Do While
Perulangan do while akan selalu mengeksekusi blok kode satu kali. Kemudian akan memeriksa kondisi, dan jika kondisinya bernilai benar maka blok kode tersebut akan diulangi lagi sampai menemukan kondisi yang bernilai salah.
```php
<?php
$x = 1;
do {
echo "The number is: $x <br>";
$x++;
} while ($x <= 5);
?>
```
| 25.588764 | 241 | 0.629402 | ind_Latn | 0.898878 |
d5c1f8fb820b2109dd7307d259a919dc7d12b917 | 1,775 | md | Markdown | doc/blog/release/node-v0-7-2-unstable.md | racker/node | 7338d9b66ee8b15aeb38d0bb3f03861f2458b10b | [
"BSD-2-Clause"
] | 1 | 2015-05-29T20:21:07.000Z | 2015-05-29T20:21:07.000Z | doc/blog/release/node-v0-7-2-unstable.md | trojanspike/node | 2d0011f53256e7a1a707a6672772d36260f81691 | [
"BSD-2-Clause"
] | null | null | null | doc/blog/release/node-v0-7-2-unstable.md | trojanspike/node | 2d0011f53256e7a1a707a6672772d36260f81691 | [
"BSD-2-Clause"
] | 1 | 2020-03-05T23:42:00.000Z | 2020-03-05T23:42:00.000Z | version: 0.7.2
title: Node v0.7.2 (unstable)
author: Isaac Schlueter
date: Wed Feb 01 2012 13:13:04 GMT-0800 (PST)
status: publish
category: release
slug: node-v0-7-2-unstable
<p>2012.02.01, Version 0.7.2 (unstable)</p>
<ul>
<li><p>Update V8 to 3.8.9</p></li>
<li><p>Support for sharing streams across Isolates (Igor Zinkovsky)</p></li>
<li><p>#2636 - Fix case where http_parsers are freed too early (koichik)</p></li>
<li><p>url: Support for IPv6 addresses in URLs (Łukasz Walukiewicz)</p></li>
<li><p>child_process: Add disconnect() method to child processes (Andreas Madsen)</p></li>
<li><p>fs: add O_EXCL support, exclusive open file (Ben Noordhuis)</p></li>
<li><p>fs: more specific error messages (Tj Holowaychuk)</p></li>
<li><p>tty: emit 'unknown' key event if key sequence not found (Dan VerWeire, Nathan Rajlich)</p></li>
<li><p>build: compile release build too if BUILDTYPE=Debug (Ben Noordhuis)</p></li>
<li><p>module: fix --debug-brk on symlinked scripts (Fedor Indutny)</p></li>
<li><p>zlib: fix <code>Failed to set dictionary</code> issue (Fedor Indutny)</p></li>
<li><p>waf: predict target arch for OS X (Fedor Indutny)</p></li>
</ul><p>Source Code: <a href="http://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz">http://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz</a></p>
<p>Windows Installer: <a href="http://nodejs.org/dist/v0.7.2/node-v0.7.2.msi">http://nodejs.org/dist/v0.7.2/node-v0.7.2.msi</a></p>
<p>Macintosh Installer: <a href="http://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg">http://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg</a></p>
<p>Website: <a href="http://nodejs.org/docs/v0.7.2/">http://nodejs.org/docs/v0.7.2/</a></p>
<p>Documentation: <a href="http://nodejs.org/docs/v0.7.2/api/">http://nodejs.org/docs/v0.7.2/api/</a></p>
| 53.787879 | 137 | 0.674366 | yue_Hant | 0.303652 |
d5c226ea670e1cfa5fb7f7654cb074d69d62f7cc | 10,951 | md | Markdown | articles/cdn/cdn-standard-rules-engine-match-conditions.md | Jontii/azure-docs.sv-se | d2551c12e17b442dc0b577205d034dcd6c73cff9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cdn/cdn-standard-rules-engine-match-conditions.md | Jontii/azure-docs.sv-se | d2551c12e17b442dc0b577205d034dcd6c73cff9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cdn/cdn-standard-rules-engine-match-conditions.md | Jontii/azure-docs.sv-se | d2551c12e17b442dc0b577205d034dcd6c73cff9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Matchnings villkor i standard regel motorn för Azure CDN | Microsoft Docs
description: Referens dokumentation för matchnings villkor i standard regel motorn för Azure Content Delivery Network (Azure CDN).
services: cdn
author: asudbring
ms.service: azure-cdn
ms.topic: article
ms.date: 11/01/2019
ms.author: allensu
ms.openlocfilehash: b8050b973027ac91ede0ba98f4d1c76831da9828
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 10/09/2020
ms.locfileid: "81259942"
---
# <a name="match-conditions-in-the-standard-rules-engine-for-azure-cdn"></a>Matchnings villkor i standard regel motorn för Azure CDN
I [standard regel motorn](cdn-standard-rules-engine.md) för Azure Content Delivery Network (Azure CDN) består en regel av ett eller flera matchnings villkor och en åtgärd. Den här artikeln innehåller detaljerade beskrivningar av de matchnings villkor som du kan använda i standard regel motorn för Azure CDN.
Den första delen av en regel är ett matchnings villkor eller en uppsättning matchnings villkor. I standard regel motorn för Azure CDN kan varje regel ha upp till fyra matchnings villkor. Ett matchnings villkor identifierar vissa typer av begär Anden för vilka definierade åtgärder utförs. Om du använder flera matchnings villkor grupperas matchnings villkoren tillsammans med hjälp av och logik.
Du kan till exempel använda ett matchnings villkor för att:
- Filtrera förfrågningar baserat på en speciell IP-adress, land eller region.
- Filtrera förfrågningar efter rubrik information.
- Filtrera begär Anden från mobila enheter eller Skriv bords enheter.
## <a name="match-conditions"></a>Matchnings villkor
Följande matchnings villkor är tillgängliga för användning i standard regel motorn för Azure CDN.
### <a name="device-type"></a>Enhetstyp
Identifierar förfrågningar som görs från en mobil enhet eller en stationär enhet.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Värden som stöds
---------|----------------
Lika med, inte lika med | Mobil, stationär
### <a name="http-version"></a>HTTP-version
Identifierar begär Anden baserat på HTTP-versionen av begäran.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Värden som stöds
---------|----------------
Lika med, inte lika med | 2,0, 1,1, 1,0, 0,9, alla
### <a name="request-cookies"></a>Begär cookies
Identifierar förfrågningar baserat på cookie-information i inkommande begäran.
#### <a name="required-fields"></a>Obligatoriska fält
Namn på cookie | Operator | Cookie-värde | Skift läges omvandling
------------|----------|--------------|---------------
Sträng | [Lista med standard operatorer](#standard-operator-list) | Sträng, heltal | Ingen transformering, till versaler, till gemener
#### <a name="key-information"></a>Viktig information
- Du kan inte använda jokertecken (inklusive asterisker ( \* )) när du anger ett cookie-namn. du måste använda ett exakt cookie-namn.
- Du kan bara ange ett enda cookie-namn per instans av matchnings villkoret.
- Cookie-namn jämförelser är inte Skift läges känsliga.
- Om du vill ange flera cookie-värden använder du ett enda blank steg mellan varje cookie-värde.
- Cookie-värden kan dra nytta av jokertecken.
- Om ett jokertecken inte har angetts uppfyller det här matchnings villkoret bara en exakt matchning. Till exempel kommer "värde" att matcha "värde" men inte "värde1".
### <a name="post-argument"></a>Publicera argument
Identifierar begär Anden baserat på argument som definierats för metoden POST-begäran som används i begäran.
#### <a name="required-fields"></a>Obligatoriska fält
Argumentnamn | Operator | Argumentvärde | Skift läges omvandling
--------------|----------|----------------|---------------
Sträng | [Lista med standard operatorer](#standard-operator-list) | Sträng, heltal | Ingen transformering, till versaler, till gemener
### <a name="query-string"></a>Frågesträng
Identifierar begär Anden som innehåller en speciell frågesträngparametern. Den här parametern har angetts till ett värde som matchar ett angivet mönster. Parametrar för frågesträng (till exempel **parameter = värde**) i URL: en för begäran avgör om det här villkoret är uppfyllt. Detta matchnings villkor identifierar en frågesträngparametern efter dess namn och accepterar ett eller flera värden för parametervärdet.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Frågesträng | Skift läges omvandling
---------|--------------|---------------
[Lista med standard operatorer](#standard-operator-list) | Sträng, heltal | Ingen transformering, till versaler, till gemener
### <a name="remote-address"></a>Fjärradress
Identifierar förfrågningar baserat på beställarens plats eller IP-adress.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Värden som stöds
---------|-----------------
Alla | E.t.
Geo-matchning | Landskod
IP-matchning | IP-adress (blankstegsavgränsad)
Inte alla | E.t.
Ingen geo-matchning | Landskod
Inte IP-matchning | IP-adress (blankstegsavgränsad)
#### <a name="key-information"></a>Viktig information
- Använd CIDR-notering.
- Om du vill ange flera IP-adresser och IP-adressblock använder du ett enda blank steg mellan värdena:
- **IPv4-exempel**: *1.2.3.4 10.20.30.40* matchar alla begär Anden som kommer från adressen 1.2.3.4 eller 10.20.30.40.
- **IPv6-exempel**: *1:2:3:4:5:6:7:8 10:20:30:40:50:60:70:80* matchar alla begär Anden som kommer från adress 1:2:3:4:5:6:7:8 eller 10:20:30:40:50:60:70:80.
- Syntaxen för ett IP-adressblock är bas-IP-adressen följt av ett snedstreck och prefixets storlek. Exempel:
- **IPv4-exempel**: *5.5.5.64/26* matchar alla begär Anden som kommer från adresser 5.5.5.64 via 5.5.5.127.
- **IPv6-exempel**: *1:2:3:/48* matchar alla begär Anden som kommer från adresser 1:2:3:0:0:0:0:0 till och med 1:2: 3: FFFF: FFFF: FFFF: FFFF: FFFF.
### <a name="request-body"></a>Begärandetext
Identifierar förfrågningar baserat på en speciell text som visas i bröd texten i begäran.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Begärandetext | Skift läges omvandling
---------|--------------|---------------
[Lista med standard operatorer](#standard-operator-list) | Sträng, heltal | Ingen transformering, till versaler, till gemener
### <a name="request-header"></a>Begärandehuvud
Identifierar begär Anden som använder ett särskilt huvud i begäran.
#### <a name="required-fields"></a>Obligatoriska fält
Huvudnamn | Operator | Huvudvärde | Skift läges omvandling
------------|----------|--------------|---------------
Sträng | [Lista med standard operatorer](#standard-operator-list) | Sträng, heltal | Ingen transformering, till versaler, till gemener
### <a name="request-method"></a>Metod för begäran
Identifierar begär Anden som använder den angivna förfrågnings metoden.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Värden som stöds
---------|----------------
Lika med, inte lika med | HÄMTA, POSTA, PLACERA, TA BORT, HUVUD, ALTERNATIV, SPÅRA
#### <a name="key-information"></a>Viktig information
- Endast GET Request-metoden kan generera cachelagrat innehåll i Azure CDN. Alla andra metoder för begäran är proxy via nätverket.
### <a name="request-protocol"></a>Protokoll för begäran
Identifierar begär Anden som använder det angivna protokoll som används.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Värden som stöds
---------|----------------
Lika med, inte lika med | HTTP, HTTPS
### <a name="request-url"></a>Begärans-URL
Identifierar begär Anden som matchar angiven URL.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Begärans-URL | Skift läges omvandling
---------|-------------|---------------
[Lista med standard operatorer](#standard-operator-list) | Sträng, heltal | Ingen transformering, till versaler, till gemener
#### <a name="key-information"></a>Viktig information
- När du använder det här regel villkoret ska du se till att inkludera protokoll information. Exempel: * https://www . \<yourdomain\> . com*.
### <a name="url-file-extension"></a>URL-filtillägg
Identifierar begär Anden som innehåller det angivna fil namns tillägget i fil namnet i den begärda URL: en.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Anknytning | Skift läges omvandling
---------|-----------|---------------
[Lista med standard operatorer](#standard-operator-list) | Sträng, heltal | Ingen transformering, till versaler, till gemener
#### <a name="key-information"></a>Viktig information
- Inkludera inte en inledande period för tillägg. Använd till exempel *HTML* i stället för *. html*.
### <a name="url-file-name"></a>URL-filnamn
Identifierar begär Anden som innehåller det angivna fil namnet i begärd URL.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Filnamn | Skift läges omvandling
---------|-----------|---------------
[Lista med standard operatorer](#standard-operator-list) | Sträng, heltal | Ingen transformering, till versaler, till gemener
#### <a name="key-information"></a>Viktig information
- Om du vill ange flera fil namn avgränsar du varje fil namn med ett enda blank steg.
### <a name="url-path"></a>URL-sökväg
Identifierar begär Anden som innehåller den angivna sökvägen i begär ande-URL: en.
#### <a name="required-fields"></a>Obligatoriska fält
Operator | Värde | Skift läges omvandling
---------|-------|---------------
[Lista med standard operatorer](#standard-operator-list) | Sträng, heltal | Ingen transformering, till versaler, till gemener
#### <a name="key-information"></a>Viktig information
- Ett fil namns värde kan dra nytta av jokertecken. Varje fil namns mönster kan till exempel bestå av en eller flera asterisker (*), där varje asterisk matchar en sekvens med ett eller flera tecken.
## <a name="reference-for-rules-engine-match-conditions"></a>Referens för regel motorns matchnings villkor
### <a name="standard-operator-list"></a>Lista med standard operatorer
Följande operatorer är giltiga för regler som accepterar värden från standard operator listan:
- Alla
- Lika med
- Innehåller
- Börjar med
- Slutar med
- Mindre än
- Mindre än eller lika med
- Större än
- Större än eller lika med
- Inte alla
- Innehåller inte
- Börjar inte med
- Slutar inte med
- Inte mindre än
- Inte mindre än eller lika med
- Inte större än
- Inte större än eller lika med
För numeriska operatorer som *mindre än* och *större än eller lika med*, baseras jämförelsen på längd. I det här fallet ska värdet i matchnings villkoret vara ett heltal som är lika med den längd som du vill jämföra.
## <a name="next-steps"></a>Nästa steg
- [Översikt över Azure CDN](cdn-overview.md)
- [Referens för standardregelmotor](cdn-standard-rules-engine-reference.md)
- [Åtgärder i standard regel motorn](cdn-standard-rules-engine-actions.md)
- [Kräv HTTPS med hjälp av standardregelmotorn](cdn-standard-rules-engine.md)
| 43.97992 | 417 | 0.725139 | swe_Latn | 0.997895 |
d5c38b1eef36e196269b414090071a9864fcf804 | 932 | md | Markdown | versioned_docs/version-v1.3/cli/vela_completion_bash.md | s4rd1nh4/kubevela.io | eb86fdcaedb5f2383a37323cc8984b582a14b2ac | [
"Apache-2.0"
] | null | null | null | versioned_docs/version-v1.3/cli/vela_completion_bash.md | s4rd1nh4/kubevela.io | eb86fdcaedb5f2383a37323cc8984b582a14b2ac | [
"Apache-2.0"
] | null | null | null | versioned_docs/version-v1.3/cli/vela_completion_bash.md | s4rd1nh4/kubevela.io | eb86fdcaedb5f2383a37323cc8984b582a14b2ac | [
"Apache-2.0"
] | null | null | null | ---
title: vela completion bash
---
generate autocompletions script for bash
### Synopsis
Generate the autocompletion script for Vela for the bash shell.
To load completions in your current shell session:
$ source <(vela completion bash)
To load completions for every new session, execute once:
Linux:
$ vela completion bash > /etc/bash_completion.d/vela
MacOS:
$ vela completion bash > /usr/local/etc/bash_completion.d/vela
```
vela completion bash
```
### Options
```
-h, --help help for bash
```
### Options inherited from parent commands
```
-y, --yes Assume yes for all user prompts
```
### SEE ALSO
* [vela completion](vela_completion) - Output shell completion code for the specified shell (bash or zsh)
#### Go Back to [CLI Commands](vela) Homepage.
###### Auto generated by spf13/cobra on 19-Apr-2022, refer to [script in KubeVela](https://github.com/oam-dev/kubevela/tree/master/hack/docgen).
| 20.711111 | 144 | 0.713519 | eng_Latn | 0.85225 |
d5c3b8e253047b861a432410e03d392e64fc892f | 9,228 | md | Markdown | crazytien_QueryList_readme.md | lua-study/0 | 161010a7530d62864e917d1d3253e1fa0a8413f9 | [
"Apache-2.0"
] | 3 | 2021-06-08T07:57:41.000Z | 2022-02-03T18:50:19.000Z | crazytien_QueryList_readme.md | lua-study/0 | 161010a7530d62864e917d1d3253e1fa0a8413f9 | [
"Apache-2.0"
] | null | null | null | crazytien_QueryList_readme.md | lua-study/0 | 161010a7530d62864e917d1d3253e1fa0a8413f9 | [
"Apache-2.0"
] | 5 | 2021-03-11T07:42:05.000Z | 2021-09-08T05:43:56.000Z |
# QueryList
`QueryList` is a simple, elegant, extensible PHP Web Scraper (crawler/spider) ,based on phpQuery.
[API Documentation](https://github.com/jae-jae/QueryList/wiki)
[中文文档](README-ZH.md)
## Features
- Have the same CSS3 DOM selector as jQuery
- Have the same DOM manipulation API as jQuery
- Have a generic list crawling program
- Have a strong HTTP request suite, easy to achieve such as: simulated landing, forged browser, HTTP proxy and other complex network requests
- Have a messy code solution
- Have powerful content filtering, you can use the jQuey selector to filter content
- Has a high degree of modular design, scalability and strong
- Have an expressive API
- Has a wealth of plug-ins
Through plug-ins you can easily implement things like:
- Multithreaded crawl
- Crawl JavaScript dynamic rendering page (PhantomJS/headless WebKit)
- Image downloads to local
- Simulate browser behavior such as submitting Form forms
- Web crawler
- .....
## Requirements
- PHP >= 7.0
## Installation
By Composer installation:
```
composer require jaeger/querylist
```
## Usage
#### DOM Traversal and Manipulation
- Crawl「GitHub」all picture links
```php
QueryList::get('https://github.com')->find('img')->attrs('src');
```
- Crawl Google search results
```php
$ql = QueryList::get('https://www.google.co.jp/search?q=QueryList');
$ql->find('title')->text(); //The page title
$ql->find('meta[name=keywords]')->content; //The page keywords
$ql->find('h3>a')->texts(); //Get a list of search results titles
$ql->find('h3>a')->attrs('href'); //Get a list of search results links
$ql->find('img')->src; //Gets the link address of the first image
$ql->find('img:eq(1)')->src; //Gets the link address of the second image
$ql->find('img')->eq(2)->src; //Gets the link address of the third image
// Loop all the images
$ql->find('img')->map(function($img){
echo $img->alt; //Print the alt attribute of the image
});
```
- More usage
```php
$ql->find('#head')->append(' Append content ')->find('div')->htmls();
$ql->find('.two')->children('img')->attrs('alt'); // Get the class is the "two" element under all img child nodes
// Loop class is the "two" element under all child nodes
$data = $ql->find('.two')->children()->map(function ($item){
// Use "is" to determine the node type
if($item->is('a')){
return $item->text();
}elseif($item->is('img'))
{
return $item->alt;
}
});
$ql->find('a')->attr('href', 'newVal')->removeClass('className')->html('newHtml')->...
$ql->find('div > p')->add('div > ul')->filter(':has(a)')->find('p:first')->nextAll()->andSelf()->...
$ql->find('div.old')->replaceWith( $ql->find('div.new')->clone())->appendTo('.trash')->prepend('Deleted')->...
```
#### List crawl
Crawl the title and link of the Google search results list:
```php
$data = QueryList::get('https://www.google.co.jp/search?q=QueryList')
// Set the crawl rules
->rules([
'title'=>array('h3','text'),
'link'=>array('h3>a','href')
])
->query()->getData();
print_r($data->all());
```
Results:
```
Array
(
[0] => Array
(
[title] => Angular - QueryList
[link] => https://angular.io/api/core/QueryList
)
[1] => Array
(
[title] => QueryList | @angular/core - Angularリファレンス - Web Creative Park
[link] => http://www.webcreativepark.net/angular/querylist/
)
[2] => Array
(
[title] => QueryListにQueryを追加したり、追加されたことを感知する | TIPS ...
[link] => http://www.webcreativepark.net/angular/querylist_query_add_subscribe/
)
//...
)
```
#### Encode convert
```php
// Out charset :UTF-8
// In charset :GB2312
QueryList::get('https://top.etao.com')->encoding('UTF-8','GB2312')->find('a')->texts();
// Out charset:UTF-8
// In charset:Automatic Identification
QueryList::get('https://top.etao.com')->encoding('UTF-8')->find('a')->texts();
```
#### HTTP Client (GuzzleHttp)
- Carry cookie login GitHub
```php
//Crawl GitHub content
$ql = QueryList::get('https://github.com','param1=testvalue & params2=somevalue',[
'headers' => [
// Fill in the cookie from the browser
'Cookie' => 'SINAGLOBAL=546064; wb_cmtLike_2112031=1; wvr=6;....'
]
]);
//echo $ql->getHtml();
$userName = $ql->find('.header-nav-current-user>.css-truncate-target')->text();
echo $userName;
```
- Use the Http proxy
```php
$urlParams = ['param1' => 'testvalue','params2' => 'somevalue'];
$opts = [
// Set the http proxy
'proxy' => 'http://222.141.11.17:8118',
//Set the timeout time in seconds
'timeout' => 30,
// Fake HTTP headers
'headers' => [
'Referer' => 'https://querylist.cc/',
'User-Agent' => 'testing/1.0',
'Accept' => 'application/json',
'X-Foo' => ['Bar', 'Baz'],
'Cookie' => 'abc=111;xxx=222'
]
];
$ql->get('http://httpbin.org/get',$urlParams,$opts);
// echo $ql->getHtml();
```
- Analog login
```php
// Post login
$ql = QueryList::post('http://xxxx.com/login',[
'username' => 'admin',
'password' => '123456'
])->get('http://xxx.com/admin');
// Crawl pages that need to be logged in to access
$ql->get('http://xxx.com/admin/page');
//echo $ql->getHtml();
```
#### Submit forms
Login GitHub
```php
// Get the QueryList instance
$ql = QueryList::getInstance();
// Get the login form
$form = $ql->get('https://github.com/login')->find('form');
// Fill in the GitHub username and password
$form->find('input[name=login]')->val('your github username or email');
$form->find('input[name=password]')->val('your github password');
// Serialize the form data
$fromData = $form->serializeArray();
$postData = [];
foreach ($fromData as $item) {
$postData[$item['name']] = $item['value'];
}
// Submit the login form
$actionUrl = 'https://github.com'.$form->attr('action');
$ql->post($actionUrl,$postData);
// To determine whether the login is successful
// echo $ql->getHtml();
$userName = $ql->find('.header-nav-current-user>.css-truncate-target')->text();
if($userName)
{
echo 'Login successful ! Welcome:'.$userName;
}else{
echo 'Login failed !';
}
```
#### Bind function extension
Customize the extension of a `myHttp` method:
```php
$ql = QueryList::getInstance();
//Bind a `myHttp` method to the QueryList object
$ql->bind('myHttp',function ($url){
// $this is the current QueryList object
$html = file_get_contents($url);
$this->setHtml($html);
return $this;
});
// And then you can call by the name of the binding
$data = $ql->myHttp('https://toutiao.io')->find('h3 a')->texts();
print_r($data->all());
```
Or package to class, and then bind:
```php
$ql->bind('myHttp',function ($url){
return new MyHttp($this,$url);
});
```
#### Plugin used
- Use the PhantomJS plugin to crawl JavaScript dynamically rendered pages:
```php
// Set the PhantomJS binary file path during installation
$ql = QueryList::use(PhantomJs::class,'/usr/local/bin/phantomjs');
// Crawl「500px」all picture links
$data = $ql->browser('https://500px.com/editors')->find('img')->attrs('src');
print_r($data->all());
// Use the HTTP proxy
$ql->browser('https://500px.com/editors',false,[
'--proxy' => '192.168.1.42:8080',
'--proxy-type' => 'http'
])
```
- Using the CURL multithreading plug-in, multi-threaded crawling GitHub trending :
```php
$ql = QueryList::use(CurlMulti::class);
$ql->curlMulti([
'https://github.com/trending/php',
'https://github.com/trending/go',
//.....more urls
])
// Called if task is success
->success(function (QueryList $ql,CurlMulti $curl,$r){
echo "Current url:{$r['info']['url']} \r\n";
$data = $ql->find('h3 a')->texts();
print_r($data->all());
})
// Task fail callback
->error(function ($errorInfo,CurlMulti $curl){
echo "Current url:{$errorInfo['info']['url']} \r\n";
print_r($errorInfo['error']);
})
->start([
// Maximum number of threads
'maxThread' => 10,
// Number of error retries
'maxTry' => 3,
]);
```
## Plugins
- [jae-jae/QueryList-PhantomJS](https://github.com/jae-jae/QueryList-PhantomJS):Use PhantomJS to crawl Javascript dynamically rendered page.
- [jae-jae/QueryList-CurlMulti](https://github.com/jae-jae/QueryList-CurlMulti) : Curl multi threading.
- [jae-jae/QueryList-AbsoluteUrl](https://github.com/jae-jae/QueryList-AbsoluteUrl) : Converting relative urls to absolute.
- [jae-jae/QueryList-Rule-Google](https://github.com/jae-jae/QueryList-Rule-Google) : Google searcher.
- [jae-jae/QueryList-Rule-Baidu](https://github.com/jae-jae/QueryList-Rule-Baidu) : Baidu searcher.
View more QueryList plugins and QueryList-based products: [QueryList Community](https://github.com/jae-jae/QueryList-Community)
## Contributing
Welcome to contribute code for the QueryList。About Contributing Plugins can be viewed:[QueryList Plugin Contributing Guide](https://github.com/jae-jae/QueryList-Community/blob/master/CONTRIBUTING.md)
## Author
Jaeger
If this library is useful for you, say thanks [buying me a beer :beer:](https://www.paypal.me/jaepay)!
## Lisence
QueryList is licensed under the license of MIT. See the LICENSE for more details.
# 良心友情链接
[腾讯QQ群快速检索](http://u.720life.cn/s/8cf73f7c)
[软件免费开发论坛](http://u.720life.cn/s/bbb01dc0) | 29.767742 | 199 | 0.651062 | kor_Hang | 0.289676 |
d5c3c1e74bd43ef5401e54889279f531621b5fb6 | 710 | md | Markdown | docs/content/en/docs/_index.md | agc93/vortex-cncremastered | f04270705428bbd8074dfef080ec7f27ba0f03fb | [
"MIT"
] | 2 | 2020-06-11T04:09:18.000Z | 2020-06-13T14:57:16.000Z | docs/content/en/docs/_index.md | agc93/vortex-cncremastered | f04270705428bbd8074dfef080ec7f27ba0f03fb | [
"MIT"
] | 4 | 2020-12-04T20:53:05.000Z | 2022-03-25T19:09:05.000Z | docs/content/en/docs/_index.md | agc93/vortex-cncremastered | f04270705428bbd8074dfef080ec7f27ba0f03fb | [
"MIT"
] | 1 | 2021-03-25T02:07:43.000Z | 2021-03-25T02:07:43.000Z | ---
title: "Documentation"
linkTitle: "Documentation"
weight: 20
menu:
main:
weight: 20
---
{{% pageinfo %}}
This site includes only the guides for getting started with CnCRV and managing C&C Remastered mods with Vortex. For help with Vortex, check out the [Vortex Support page](https://www.nexusmods.com/about/vortex/).
{{% /pageinfo %}}
Welcome to the User Guide for the C&C Remastered for Vortex project! Navigate the documentation using the links on the sidebar.
Documentation for how to get started with the extension, as well as how to manage your mods is available. Remember, these docs are also [open-source](https://github.com/agc93/vortex-cncremastered) and contributions are always welcome! | 44.375 | 234 | 0.761972 | eng_Latn | 0.991902 |
d5c3ce3d35f82b92e068fd4d9767457b2be9135f | 326 | md | Markdown | README.md | yanhaijing/color | 48df5dba94f2ecb6c9bca55289ea52b39c1e0365 | [
"MIT"
] | 46 | 2016-04-14T05:19:30.000Z | 2019-06-30T08:05:21.000Z | README.md | gelatoYu/changeColor | 0d842473f6cd9c9b7630f8035fff0112013693fe | [
"MIT"
] | 2 | 2016-04-14T08:59:35.000Z | 2018-09-14T14:29:26.000Z | README.md | gelatoYu/changeColor | 0d842473f6cd9c9b7630f8035fff0112013693fe | [
"MIT"
] | 17 | 2016-04-14T06:03:08.000Z | 2021-06-19T14:35:24.000Z | # [看你有多色](http://yanhaijing.com/color/) [](https://github.com/yanhaijing/fis3-base) [](https://github.com/yanhaijing/fis3-base/blob/master/MIT-LICENSE)
看你有多色是一款休闲小游戏，适合所有人群，找出所有色块里颜色不同的一个，快来比比你的眼力吧。
| 65.2 | 276 | 0.757669 | yue_Hant | 0.746708 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.