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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
f4bc5cfee6825bed1fae8d37afbc18f7cb3abbbd | 667 | md | Markdown | content/blog/my-first/index.md | CobyYates/gatsby_blog | b2e85ea20cef623926badd1f3d3a107957bb004a | [
"MIT"
] | null | null | null | content/blog/my-first/index.md | CobyYates/gatsby_blog | b2e85ea20cef623926badd1f3d3a107957bb004a | [
"MIT"
] | null | null | null | content/blog/my-first/index.md | CobyYates/gatsby_blog | b2e85ea20cef623926badd1f3d3a107957bb004a | [
"MIT"
] | null | null | null | ---
title: My First Post-it
date: "2020-02-01T22:12:03.284Z"
description: "This is sweet!"
---
I have only built a blog in Wordpress, so it's cool to see how it is done (much better) in
Gatsby!
I wonder how simple this will be to get fully working?
Oh, and here's a great quote from this Wikipedia on
[salted duck eggs](http://en.wikipedia.org/wiki/Salted_duck_egg).
> So far I have noticed that Gatsby uses Markdown for some, if not all
> of it's content. That is pretty cool and sorta seems like an old
> school thing to do. But I think it will help people learn it better!
> On and these eggs sound really really gross!
| 31.761905 | 90 | 0.734633 | eng_Latn | 0.998226 |
f4bc737a228906abafb66651e58b3a28fac2658c | 2,433 | md | Markdown | src/ka/2022-01/13/06.md | DavidTbilisi/sabbath-school-lessons | 5c791f94026fca45976b16fe5bf12e53398b3a80 | [
"MIT"
] | null | null | null | src/ka/2022-01/13/06.md | DavidTbilisi/sabbath-school-lessons | 5c791f94026fca45976b16fe5bf12e53398b3a80 | [
"MIT"
] | null | null | null | src/ka/2022-01/13/06.md | DavidTbilisi/sabbath-school-lessons | 5c791f94026fca45976b16fe5bf12e53398b3a80 | [
"MIT"
] | 1 | 2021-06-13T12:33:16.000Z | 2021-06-13T12:33:16.000Z | ---
title: გავიდეთ მასთან ბანაკის გარეთ
date: 24/03/2022
---
შეადარეთ ებრ. 13:10-14; მარკ. 8:34; მათ. 10:38; ლუკ. 14:27; გალ.2:20. რას ნიშნავს იესოსთან ბანაკის გარეთ გასვლა?
კარიბჭის მიღმა სივრცე ყველაზე უწმიდური იყო მთელს ბანაკში. აქ წვავდნენ სამსხვერპლო ცხოველების გვამებს (იხ. ლევ. 4:12). კეთროვანებს განდევნიდნენ ბანაკიდან მის საზღვრესბ გარეთ (იხ. ებრ. 13:46), აქ ასევე სიკვდილით სჯიდნენ ღვთის მგმობელებს და სხვა დამნაშავეებს (იხ. ებრ. 13:10-16, 23; 3მეფ. 21:13; საქმე. 7:58). ეს წესები გულისხმობდა, რომ თავად ღმერთი ბანაკში იმყოფებოდა. ამიტომ ყველაფერ უწმიდურს განდევნიდნენ ბანაკის ფარგლებს გარეთ, რადგან ღმერთს არ სურდა ეხილე "უწმიდური" ან "წარმწყმედი" (რიცხ. 5:3; მეორე რჯ. 23:14).
იესო ჯვარზე ეწამა იერუსალიმის საზღვრებს გარეთ (იხ. იოან. 19:17-20). ეს ხაზს უსვამს იმ სირცხვილს, რომლის დათმენაც მოუხდა მას (იხ. ებრ. 12:2). იგი ოფიციალურად გაასამართლეს "ღმერთის გმობისთვის", ამიტომ ისრაელმა ზურგი აქცია მას და ქალაქგარეთ აწამა (იხ. მარკ. 14:63,64; ლევ. 24:11,16). იესო განდევნეს ბანაკიდან, როგორც უწმიდური და შერცხვენილი (იხ. ებრ. 12:2). მაგრამ პავლე შეაგონებს მორწმუნეებს, რომ გაყვნენ იესოს ბანაკს გარეთ და დაითმინონ იგივე სორცხვილი, რომელიც მან გადაიტანა (იხ. ებრ. 13:13). სწორედ ასე არჩია მოსემ "ქრისტესთვის გმობა" ეგვიპტის საგანძურს (ებრ. 11:26).
როგორი პარადოქსულიც არ უნდა იყოს, წერილის ავტორის მოსაზრებით, ამიერიდან ღმერთის ბანაკის გარეთ იმყოფება. გაყვე იესოს ბანაკის გარეთ ნიშნავს, რომ იტვირთო "მისი შეურაცხყოფა" ან სირცხვილი, მაგრამ მიხვიდე "მასთან" (ებრ. 13:13). ასე მოიქცნენ ის ისრაელიანები, რომლებიც "ეძებდნენ უფალს" მას შემდეგ, რაც ერის განდგომილების გამო მოსემ საწმიდრის კარავი გაიტანა ბანაკიდან. ისინი უდაბნოში გავიდნენ ბანაკიდან (იხ. გამ. 33:7). ეს ეპიზოდი გულისხმობს, რომ იესოს უარყოფით ურწმუნონი ღმერთსაც უარყოფენ, მსგავსად ისრაელისა, რომლემაც ოქროს ხბო აიშენა თავისთვის (იხ. გამ. 32,33). ამიტომ ტანჯვისა და სირცხვილის გზა – ღმერთის გზაა.
პავლე სთავაზობს მკითხველებს, რომ გაჰყვნენ იესოს, როგორც წინამძღოლსა და მათი რწმენის სრულმყოფს (იხ. ებრ. 12:2), და ფარულად მიანიშნებს მათ, რომ განიხილონ საკუთარი ამჯამინდელი სატანჯველნი როგორც დროებითი შეზღუდულობა, რომელიც გამოიღებს "სიმართლის ნაყოფს – მშვიდობას" (მუხლი 11). მორწმუნეები ტოვებენ დანგრეულ ქალაქს, ან კარავს და ეძებენ ზეციურ ქალაქს, რომლის არქიტექტორიც თავად უფალია (იხ. ებრ. 13:14; 11:10,16).
რას ნიშნავს თქვენთვის გაჰყვეთ იესოს "ბანაკის გარეთ"? იესოსთან ცხოვრების რომელ ასპექტებს შეუძლიათ გარშემომყოფთა მხრიდან საყვედურები ან დამცირება გამოიწვიონ? | 162.2 | 606 | 0.787505 | kat_Geor | 1.000004 |
f4bc8e13ee19c52b97e50bf3921fcbf04f10376b | 2,133 | md | Markdown | README.md | heartlhj/gorm | a7bf9d9ea428af244534117dc88f5b2368269c29 | [
"MIT"
] | null | null | null | README.md | heartlhj/gorm | a7bf9d9ea428af244534117dc88f5b2368269c29 | [
"MIT"
] | null | null | null | README.md | heartlhj/gorm | a7bf9d9ea428af244534117dc88f5b2368269c29 | [
"MIT"
] | null | null | null | # GORM
The fantastic ORM library for Golang, aims to be developer friendly.
[](https://goreportcard.com/report/github.com/go-gorm/gorm)
[](https://github.com/go-gorm/gorm/actions)
[](https://gitter.im/jinzhu/gorm?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
[](https://opencollective.com/gorm)
[](https://opencollective.com/gorm)
[](https://opensource.org/licenses/MIT)
[](https://pkg.go.dev/github.com/heartlhj/gorm?tab=doc)
## Overview
* Full-Featured ORM
* Associations (Has One, Has Many, Belongs To, Many To Many, Polymorphism, Single-table inheritance)
* Hooks (Before/After Create/Save/Update/Delete/Find)
* Eager loading with `Preload`, `Joins`
* Transactions, Nested Transactions, Save Point, RollbackTo to Saved Point
* Context, Prepared Statment Mode, DryRun Mode
* Batch Insert, FindInBatches, Find To Map
* SQL Builder, Upsert, Locking, Optimizer/Index/Comment Hints, NamedArg
* Composite Primary Key
* Auto Migrations
* Logger
* Extendable, write Plugins based on GORM callbacks
* Every feature comes with tests
* Developer Friendly
## Getting Started
* GORM Guides [https://gorm.io](https://gorm.io)
## Contributing
[You can help to deliver a better GORM, check out things you can do](https://gorm.io/contribute.html)
## License
© Jinzhu, 2013~time.Now
Released under the [MIT License](https://github.com/go-gorm/gorm/blob/master/License)
| 48.477273 | 208 | 0.766057 | yue_Hant | 0.597942 |
f4bccd53f66827f3b01318bafb25aa6ebbaed674 | 383 | md | Markdown | documentation/travis_settings_2020_0715.md | TwoRavens/TwoRavens | e5f820557d6646df525ceed15e17d79f4159cf0a | [
"Apache-2.0"
] | 20 | 2017-12-11T07:26:06.000Z | 2021-11-22T16:16:20.000Z | documentation/travis_settings_2020_0715.md | TwoRavens/TwoRavens | e5f820557d6646df525ceed15e17d79f4159cf0a | [
"Apache-2.0"
] | 849 | 2017-10-20T18:21:18.000Z | 2022-02-18T02:45:44.000Z | documentation/travis_settings_2020_0715.md | TwoRavens/TwoRavens | e5f820557d6646df525ceed15e17d79f4159cf0a | [
"Apache-2.0"
] | 1 | 2020-05-18T06:02:13.000Z | 2020-05-18T06:02:13.000Z | # Variables set on Travis for Builds
- site: https://travis-ci.com/github/TwoRavens/TwoRavens/settings
## Variables
- name: DJANGO_SETTINGS_MODULE
- value: tworavensproject.settings.local_settings
- name: DOCKER_PASSWORD
- value: (hidden)
- name: DOCKER_USERNAME
- value: (hidden)
- name: IS_TRAVIS_BUILD
- value: True
- name: RAVENS_VOLUME_DIR
- value: ./ravens_volume
| 22.529412 | 65 | 0.746736 | yue_Hant | 0.732014 |
f4bce143c603ce8e79df4955f1333ffd53c185e6 | 1,407 | md | Markdown | _chapters/update-the-app.md | grundmanise/serverless-stack-com | f97397dd8da48e1f87cc4dd82fb807228d645402 | [
"MIT"
] | null | null | null | _chapters/update-the-app.md | grundmanise/serverless-stack-com | f97397dd8da48e1f87cc4dd82fb807228d645402 | [
"MIT"
] | null | null | null | _chapters/update-the-app.md | grundmanise/serverless-stack-com | f97397dd8da48e1f87cc4dd82fb807228d645402 | [
"MIT"
] | null | null | null | ---
layout: post
title: Update the App
date: 2017-02-13 00:00:00
code: frontend
description: Tutorial on how to make changes to your React.js single page application.
comments_id: 69
---
Let's make a couple of quick changes to test the process of deploying updates to our app.
We are going to add a Login and Signup button to our lander to give users a clear call to action.
<img class="code-marker" src="/assets/s.png" />To do this update our `renderLander` method in `src/containers/Home.js`.
``` coffee
renderLander() {
return (
<div className="lander">
<h1>Scratch</h1>
<p>A simple note taking app</p>
<div>
<Link to="/login" className="btn btn-info btn-lg">
Login
</Link>
<Link to="/signup" className="btn btn-success btn-lg">
Signup
</Link>
</div>
</div>
);
}
```
<img class="code-marker" src="/assets/s.png" />And import the `Link` component from React-Router in the header.
``` javascript
import { Link } from "react-router-dom";
```
<img class="code-marker" src="/assets/s.png" />Also, add a couple of styles to `src/containers/Home.css`.
``` css
.Home .lander div {
padding-top: 20px;
}
.Home .lander div a:first-child {
margin-right: 20px;
}
```
And our lander should look something like this.
Next, let's deploy these updates.
| 24.684211 | 119 | 0.662402 | eng_Latn | 0.79825 |
f4bf6701f1778028dccea77c89a2aac6ca6b00d3 | 6,172 | md | Markdown | articles/cognitive-services/Speech-Service/how-to-configure-openssl-linux.md | pmsousa/azure-docs.pt-pt | bc487beff48df00493484663c200e44d4b24cb18 | [
"CC-BY-4.0",
"MIT"
] | 15 | 2017-08-28T07:46:17.000Z | 2022-02-03T12:49:15.000Z | articles/cognitive-services/Speech-Service/how-to-configure-openssl-linux.md | pmsousa/azure-docs.pt-pt | bc487beff48df00493484663c200e44d4b24cb18 | [
"CC-BY-4.0",
"MIT"
] | 407 | 2018-06-14T16:12:48.000Z | 2021-06-02T16:08:13.000Z | articles/cognitive-services/Speech-Service/how-to-configure-openssl-linux.md | pmsousa/azure-docs.pt-pt | bc487beff48df00493484663c200e44d4b24cb18 | [
"CC-BY-4.0",
"MIT"
] | 17 | 2017-10-04T22:53:31.000Z | 2022-03-10T16:41:59.000Z | ---
title: Como configurar o OpenSSL para Linux
titleSuffix: Azure Cognitive Services
description: Saiba como configurar o OpenSSL para o Linux.
services: cognitive-services
author: jhakulin
manager: nitinme
ms.service: cognitive-services
ms.subservice: speech-service
ms.topic: conceptual
ms.date: 01/16/2020
ms.author: jhakulin
zone_pivot_groups: programming-languages-set-two
ms.openlocfilehash: a6225fec30a87ca0bbe57e414733bc21489f87ad
ms.sourcegitcommit: f28ebb95ae9aaaff3f87d8388a09b41e0b3445b5
ms.translationtype: MT
ms.contentlocale: pt-PT
ms.lasthandoff: 03/30/2021
ms.locfileid: "104577449"
---
# <a name="configure-openssl-for-linux"></a>Configurar o OpenSSL para Linux
Quando utilizar qualquer versão SDK do Discurso antes do 1.9.0, o [OpenSSL](https://www.openssl.org) está configurado dinamicamente para a versão do sistema de anfitrião. Em versões posteriores do Speech SDK, o OpenSSL (versão [1.1.1b)](https://mta.openssl.org/pipermail/openssl-announce/2019-February/000147.html)está estático ligado à biblioteca central do SDK do discurso.
Para garantir a conectividade, verifique se os certificados OpenSSL foram instalados no seu sistema. Executar um comando:
```bash
openssl version -d
```
A saída dos sistemas baseados em Ubuntu/Debian deve ser:
```
OPENSSLDIR: "/usr/lib/ssl"
```
Verifique se existe `certs` subdireção em OPENSSLDIR. No exemplo acima, `/usr/lib/ssl/certs` seria.
* Se houver `/usr/lib/ssl/certs` e contiver muitos ficheiros de certificados individuais (com `.crt` ou `.pem` extensão), não há necessidade de mais ações.
* Se o OPENSSLDIR for outra coisa que `/usr/lib/ssl` não seja e/ou exista um único ficheiro de pacote de certificados em vez de vários ficheiros individuais, é necessário definir uma variável de ambiente SSL adequada para indicar onde os certificados podem ser encontrados.
## <a name="examples"></a>Exemplos
- OPENSSLDIR é `/opt/ssl` . Há `certs` subdireção com muitos `.crt` ou `.pem` ficheiros.
Desaponte a variável `SSL_CERT_DIR` ambiente para apontar antes de executar um programa que utiliza o `/opt/ssl/certs` SDK do discurso. Por exemplo:
```bash
export SSL_CERT_DIR=/opt/ssl/certs
```
- OPENSSLDIR é `/etc/pki/tls` (como em sistemas baseados em RHEL/CentOS). Existe `certs` subdiretório com um ficheiro de pacote de certificados, por exemplo `ca-bundle.crt` .
Desaponte a variável ambiente `SSL_CERT_FILE` para apontar para esse ficheiro antes de executar um programa que utiliza o SDK de discurso. Por exemplo:
```bash
export SSL_CERT_FILE=/etc/pki/tls/certs/ca-bundle.crt
```
## <a name="certificate-revocation-checks"></a>Verificações de revogação de certificados
Ao ligar-se ao Serviço de Fala, o SDK de discurso verificará se o certificado TLS utilizado pelo Serviço de Fala não foi revogado. Para realizar esta verificação, o Speech SDK necessitará de acesso aos pontos de distribuição de CRL para as Autoridades de Certificados utilizadas pela Azure. Neste [documento](https://docs.microsoft.com/azure/security/fundamentals/tls-certificate-changes)pode encontrar-se uma lista de possíveis locais de descarregamento de CRL. Se um certificado tiver sido revogado ou o CRL não puder ser descarregado, o Speech SDK abortará a ligação e levantará o evento cancelado.
No caso de a rede de onde o SDK de discurso está a ser utilizado ser configurada de uma forma que não permita o acesso aos locais de descarregamento de CRL, o controlo CRL pode ser desativado ou definido para não falhar se o CRL não puder ser recuperado. Esta configuração é feita através do objeto de configuração utilizado para criar um objeto Recogniser.
Para continuar com a ligação quando um CRL não pode ser recuperado, coloque a propriedade OPENSSL_CONTINUE_ON_CRL_DOWNLOAD_FAILURE.
::: zone pivot="programming-language-csharp"
```csharp
config.SetProperty("OPENSSL_CONTINUE_ON_CRL_DOWNLOAD_FAILURE", "true");
```
::: zone-end
::: zone pivot="programming-language-cpp"
```C++
config->SetProperty("OPENSSL_CONTINUE_ON_CRL_DOWNLOAD_FAILURE", "true");
```
::: zone-end
::: zone pivot="programming-language-java"
```java
config.setProperty("OPENSSL_CONTINUE_ON_CRL_DOWNLOAD_FAILURE", "true");
```
::: zone-end
::: zone pivot="programming-language-python"
```Python
speech_config.set_property_by_name("OPENSSL_CONTINUE_ON_CRL_DOWNLOAD_FAILURE", "true")?
```
::: zone-end
::: zone pivot="programming-language-more"
```ObjectiveC
[config setPropertyTo:@"true" byName:"OPENSSL_CONTINUE_ON_CRL_DOWNLOAD_FAILURE"];
```
::: zone-end
Quando definido como "verdadeiro" será feita uma tentativa de recuperar o CRL e se a recuperação for bem sucedida, o certificado será verificado para revogação, se a recuperação falhar, a ligação será permitida para continuar.
Para desativar completamente as verificações de revogação de certificados, desative o OPENSSL_DISABLE_CRL_CHECK do imóvel como "verdadeiro".
::: zone pivot="programming-language-csharp"
```csharp
config.SetProperty("OPENSSL_DISABLE_CRL_CHECK", "true");
```
::: zone-end
::: zone pivot="programming-language-cpp"
```C++
config->SetProperty("OPENSSL_DISABLE_CRL_CHECK", "true");
```
::: zone-end
::: zone pivot="programming-language-java"
```java
config.setProperty("OPENSSL_DISABLE_CRL_CHECK", "true");
```
::: zone-end
::: zone pivot="programming-language-python"
```Python
speech_config.set_property_by_name("OPENSSL_DISABLE_CRL_CHECK", "true")?
```
::: zone-end
::: zone pivot="programming-language-more"
```ObjectiveC
[config setPropertyTo:@"true" byName:"OPENSSL_DISABLE_CRL_CHECK"];
```
::: zone-end
> [!NOTE]
> Vale também a pena notar que algumas distribuições de Linux não têm uma variável de ambiente TMP ou TMPDIR definida. Isto fará com que o SDK de voz descarregue sempre a Lista de Revogação de Certificados (CRL), em vez de caching o CRL para o disco para reutilização até expirarem. Para melhorar o desempenho inicial da ligação pode [criar uma variável ambiental chamada TMPDIR e defini-la para o caminho do seu diretório temporário escolhido.](https://help.ubuntu.com/community/EnvironmentVariables)
## <a name="next-steps"></a>Passos seguintes
> [!div class="nextstepaction"]
> [Acerca do SDK de Voz](speech-sdk.md)
| 40.605263 | 601 | 0.778354 | por_Latn | 0.98785 |
f4bfbff36144a34f280decbb12e152148fa804f2 | 1,559 | markdown | Markdown | _posts/2018-1-25-go安装与入门.markdown | dugreen/dugreen.github.io | 226d0503d392481999fc76066e9f130083d75e0d | [
"Apache-2.0"
] | 1 | 2019-11-05T01:49:37.000Z | 2019-11-05T01:49:37.000Z | _posts/2018-1-25-go安装与入门.markdown | dugreen/dugreen.github.io | 226d0503d392481999fc76066e9f130083d75e0d | [
"Apache-2.0"
] | null | null | null | _posts/2018-1-25-go安装与入门.markdown | dugreen/dugreen.github.io | 226d0503d392481999fc76066e9f130083d75e0d | [
"Apache-2.0"
] | null | null | null | ---
layout: post
title: "Go安装与入门"
subtitle: ""
date: 2018-1-25 12:00:00
author: "Dugreen"
header-img: "img/artical-bgs/back4.jpg"
catalog: true
tags:
- Go
---
> 今天逛知乎突然看到一个专栏文章《Hello中国，Go官网回归中国》，最近传知乎的部分业务开始转向Go，开始对这门语言产生了一丝兴趣，然后点进了Go官网，看到全英文官方文档我内心是恐惧的(目前英语水平太菜` _ `)。决心要提高英语水平的我，不不不，决心要提高编程能力的我决定通过这个寒假来攻克它(english -.-)。
## linux平台上安装Go
1.首先到Go的官网下载适合自己硬件平台的压缩包[点我下载](https://golang.google.cn/dl/)
2.将下载好的压缩包文件(go$VERSION.$OS-$ARCH.tar.gz)解压到 /usr/local 目录下(需root权限)
```
tar -C /usr/local -xzf go$VERSION.$OS-$ARCH.tar.gz
```
3.添加 /usr/local/go/bin 到 PATH 环境变量,可以选择添加到/etc/profile 文件下，或者添加到 $HOME/.profile文件下。这两者之间的区别就是前者作用于全部的用户，后者只作用于当前用户。
```
# 把我加进去-.-
export PATH=$PATH:/usr/local/go/bin
```
4.安装Go在用户目录下的某个位置,我这里是 $HOME/gopath ,这里的安装其实是配置自己Go的workspace的位置(感觉怪怪的感觉,其实编写Go的程序需要一个单独的工作区，将该工作区进行一系列的配置(其实就是建几个目录),然后将工作区的路径进行配置)。
```
export GOROOT=$HOME/gopath
export PATH=$PATH:$GOROOT/bin
```
ok,到这个时候所有的下载,安装,配置操作都结束了。到自己的终端中输入 go ，如果你看到一堆输出，那么就表示没有问题了。
接下来就带着看到这里的小伙伴，展示如何运行一个helloworld程序。
首先要解决上面那个拗口的工作区(workspace)的问题，首先进入该工作区的目录下，新建bin pkg src 这三个目录。
要编译并运行一个简单的程序，首先需要选择一个源码包路径来存放这个程序(我这里使用的是 github.com/dugreen/hello )创建这个目录在src下。
```
$ mkdir -p $GOPATH/src/github.com/user/hello
```
接下来创建一个叫做 hello.go 的文件在上面刚创建好的目录下，然后编写下面的代码。
```
package main
import "fmt"
func main() {
fmt.Printf("Hello, world.\n")
}
```
接下来使用 go 来编译并运行这个小程序：
```
$ go install github.com/user/hello
# 其实如果你在当前该程序文件的目录下你可以这样：
$ go install
# 执行可执行文件
$ $GOPATH/bin/hello
```
看的全英文的官网，那个别扭啊啊啊啊！！！
| 14.302752 | 163 | 0.722899 | yue_Hant | 0.758442 |
f4c0185288fcdd562cd280138e3e6352d880d2ed | 1,434 | markdown | Markdown | _posts/blog/2020-02-07-how-to-build-a-blog.markdown | fengdongsheng/fengdongsheng.github.io | 2cedced3a10c7a221c1afc46642d19e17d781b74 | [
"MIT"
] | null | null | null | _posts/blog/2020-02-07-how-to-build-a-blog.markdown | fengdongsheng/fengdongsheng.github.io | 2cedced3a10c7a221c1afc46642d19e17d781b74 | [
"MIT"
] | null | null | null | _posts/blog/2020-02-07-how-to-build-a-blog.markdown | fengdongsheng/fengdongsheng.github.io | 2cedced3a10c7a221c1afc46642d19e17d781b74 | [
"MIT"
] | null | null | null | ---
layout: post
title: "使用jekyll和github page 搭建博客"
date: 2020-02-07 16:37:36
categories: 博客
---
* content
{:toc}
## 简介
第一篇博客，刚刚搭建好jekyll，就粗略写一下。后面补充细节。
## 博客环境的搭建
整个过程前后算下来得有整整一天，看了很多帖子，走了不少弯路。建议在参考其他人的blog时注意一下别人的blog创建时间，
因为很可能他们记录的东西，在软件版本更新后，没有多少参考价值了。整个过程大致就两步：①github部分、②jekyll部分。
### github 仓库
①、github部分分为创建远程仓库、配置本地git环境、配置本地和远程的密钥、创建本地仓库。这些步骤完成后可以去jekyll主题官网下载blog模板，然后git常规操作：add、push可以在通过username.github.io访问效果。
### jekyll
②、jekyll部分最简单但是耽误了最多时间。jekyll的前置环境是ruby，大部分blog都将ruby和devkit分开装的，并且不区分ruby和devkit之间的版本匹配，这使得我尝试了多次都出现了gem本地扩展错误的问题。找到了版本匹配的，却依然出现相同问题（怀疑是版本太低了）。在[rubyinstall](https://rubyinstaller.org/downloads/)官网中有两大类，一类是不包含devkit的exe，一类是包含devkit的exe。如果选择了没有devkit的，会依然出现gem扩展问题，别想着去找单独的devkit，然后安装，因为找不到，找到的就是适配低版本的，然后发现还是同样的错误。
最后怎么解决？直接选择rubyinstall官网上含devkit的exe，运行安装的exe，勾选所有的选项。等一会儿，会在cmd中出现三个可选项，要选第三个，完成后，运行ruby-v确保无误。然后有一步，安装rubygames，这个可以自行baidu、google，可以运行gem -v以确保完成。最后一步，安装jekyll，gem install jekyll，运行jekyll -v确保完成。
## jekyll的使用
创建文件：jekyll new name（可能会有点久）
在同一目录下使用 jekyll s,然后可以在浏览器输入localhost：4000，查看效果
## 其它
可以在powershell中完成整个过程；安装ruby时尽量不要有中文路径，默认安装在c盘挺好。
在修改了_post中的md文件后，提交到github可能会在邮箱收到有‘seo’的错误，将指定文件中的对应代码行删除即可。
再次提交，如果出现，github page不支持主题的错误，通过注释config文件中的theme: plainwhite即可。
可能还会在jekyll build的时候出现：future date的问题，需要在config文件中添加future：true
win10 power shell 打开方式：win+x，选择power shell；
在写markdown的时候注意符号都是英文才对。
| 32.590909 | 315 | 0.808926 | yue_Hant | 0.676582 |
f4c10103ac074259080fc0b0014f5dae69ebb0d4 | 747 | md | Markdown | snippets/partition.md | Bruce-Feldman/30-seconds-of-code | 0d3c02ad080b65bb127bc95f44e424179f9c58e9 | [
"CC0-1.0"
] | 20 | 2018-02-27T23:10:45.000Z | 2022-03-31T07:17:38.000Z | snippets/partition.md | Bruce-Feldman/30-seconds-of-code | 0d3c02ad080b65bb127bc95f44e424179f9c58e9 | [
"CC0-1.0"
] | 261 | 2019-02-12T23:18:07.000Z | 2021-08-02T23:19:27.000Z | snippets/partition.md | Bruce-Feldman/30-seconds-of-code | 0d3c02ad080b65bb127bc95f44e424179f9c58e9 | [
"CC0-1.0"
] | 6 | 2018-03-01T09:43:51.000Z | 2021-08-18T11:02:19.000Z | ### partition
Groups the elements into two arrays, depending on the provided function's truthiness for each element.
Use `Array.reduce()` to create an array of two arrays.
Use `Array.push()` to add elements for which `fn` returns `true` to the first array and elements for which `fn` returns `false` to the second one.
```js
const partition = (arr, fn) =>
arr.reduce(
(acc, val, i, arr) => {
acc[fn(val, i, arr) ? 0 : 1].push(val);
return acc;
},
[[], []]
);
```
```js
const users = [{ user: 'barney', age: 36, active: false }, { user: 'fred', age: 40, active: true }];
partition(users, o => o.active); // [[{ 'user': 'fred', 'age': 40, 'active': true }],[{ 'user': 'barney', 'age': 36, 'active': false }]]
```
| 32.478261 | 146 | 0.594378 | eng_Latn | 0.969994 |
f4c1169afce81fd243179b49e2a3b5d1bd112fca | 12,965 | md | Markdown | articles/iot-hub/tutorial-connectivity.md | jptarqu/azure-docs | de3e738917e10c63531e1c7fd713ffa0a47d08b9 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2018-10-08T20:29:07.000Z | 2021-12-14T12:46:56.000Z | articles/iot-hub/tutorial-connectivity.md | jptarqu/azure-docs | de3e738917e10c63531e1c7fd713ffa0a47d08b9 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-03-16T22:09:49.000Z | 2021-03-16T22:09:49.000Z | articles/iot-hub/tutorial-connectivity.md | jptarqu/azure-docs | de3e738917e10c63531e1c7fd713ffa0a47d08b9 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-03-03T06:03:16.000Z | 2021-03-03T06:03:16.000Z | ---
title: Check device connectivity to Azure IoT Hub
description: Use IoT Hub tools to troubleshoot, during development, device connectivity issues to your IoT hub.
services: iot-hub
author: wesmc7777
manager: philmea
ms.author: wesmc
ms.custom: [mvc, amqp, mqtt, 'Role: Cloud Development', 'Role: IoT Device', devx-track-js, devx-track-azurecli]
ms.date: 02/22/2019
ms.topic: tutorial
ms.service: iot-hub
# As a developer, I want to know what tools I can use to verify connectivity between my IoT devices and my IoT hub.
---
# Tutorial: Use a simulated device to test connectivity with your IoT hub
In this tutorial, you use Azure IoT Hub portal tools and Azure CLI commands to test device connectivity. This tutorial also uses a simple device simulator that you run on your desktop machine.
If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
In this tutorial, you learn how to:
> [!div class="checklist"]
> * Check your device authentication
> * Check device-to-cloud connectivity
> * Check cloud-to-device connectivity
> * Check device twin synchronization
[!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
## Prerequisites
The CLI scripts you run in this tutorial use the [Microsoft Azure IoT Extension for Azure CLI](https://github.com/Azure/azure-iot-cli-extension/blob/master/README.md). To install this extension, run the following CLI command:
```azurecli-interactive
az extension add --name azure-iot
```
[!INCLUDE [iot-hub-cli-version-info](../../includes/iot-hub-cli-version-info.md)]
The device simulator application you run in this tutorial is written using Node.js. You need Node.js v10.x.x or later on your development machine.
You can download Node.js for multiple platforms from [nodejs.org](https://nodejs.org).
You can verify the current version of Node.js on your development machine using the following command:
```cmd/sh
node --version
```
Download the sample device simulator Node.js project from https://github.com/Azure-Samples/azure-iot-samples-node/archive/master.zip and extract the ZIP archive.
Make sure that port 8883 is open in your firewall. The device sample in this tutorial uses MQTT protocol, which communicates over port 8883. This port may be blocked in some corporate and educational network environments. For more information and ways to work around this issue, see [Connecting to IoT Hub (MQTT)](iot-hub-mqtt-support.md#connecting-to-iot-hub).
## Create an IoT hub
If you created a free or standard tier IoT hub in a previous quickstart or tutorial, you can skip this step.
[!INCLUDE [iot-hub-tutorials-create-free-hub](../../includes/iot-hub-tutorials-create-free-hub.md)]
## Check device authentication
A device must authenticate with your hub before it can exchange any data with the hub. You can use the **IoT Devices** tool in the **Device Management** section of the portal to manage your devices and check the authentication keys they're using. In this section of the tutorial, you add a new test device, retrieve its key, and check that the test device can connect to the hub. Later you reset the authentication key to observe what happens when a device tries to use an outdated key. This section of the tutorial uses the Azure portal to create, manage, and monitor a device, and the sample Node.js device simulator.
Sign in to the portal and navigate to your IoT hub. Then navigate to the **IoT Devices** tool:
To register a new device, click **+ Add**, set **Device ID** to **MyTestDevice**, and click **Save**:
To retrieve the connection string for **MyTestDevice**, click on it in the list of devices and then copy the **Connection string-primary key** value. The connection string includes the *shared access key* for the device.
To simulate **MyTestDevice** sending telemetry to your IoT hub, run the Node.js simulated device application you downloaded previously.
In a terminal window on your development machine, navigate to the root folder of the sample Node.js project you downloaded. Then navigate to the **iot-hub\Tutorials\ConnectivityTests** folder.
In the terminal window, run the following commands to install the required libraries and run the simulated device application. Use the device connection string you made a note of when you added the device in the portal.
```cmd/sh
npm install
node SimulatedDevice-1.js "{your device connection string}"
```
The terminal window displays information as it tries to connect to your hub:
You've now successfully authenticated from a device using a device key generated by your IoT hub.
### Reset keys
In this section, you reset the device key and observe the error when the simulated device tries to connect.
To reset the primary device key for **MyTestDevice**, run the following commands:
```azurecli-interactive
# Generate a new Base64 encoded key using the current date
read key < <(date +%s | sha256sum | base64 | head -c 32)
# Requires the IoT Extension for Azure CLI
# az extension add --name azure-iot
# Reset the primary device key for MyTestDevice
az iot hub device-identity update --device-id MyTestDevice --set authentication.symmetricKey.primaryKey=$key --hub-name {YourIoTHubName}
```
In the terminal window on your development machine, run the simulated device application again:
```cmd/sh
npm install
node SimulatedDevice-1.js "{your device connection string}"
```
This time you see an authentication error when the application tries to connect:
### Generate shared access signature (SAS) token
If your device uses one of the IoT Hub device SDKs, the SDK library code generates the SAS token used to authenticate with the hub. A SAS token is generated from the name of your hub, the name of your device, and the device key.
In some scenarios, such as in a cloud protocol gateway or as part of a custom authentication scheme, you may need to generate the SAS token yourself. To troubleshoot issues with your SAS generation code, it's useful to generate a known-good SAS token to use during testing.
> [!NOTE]
> The SimulatedDevice-2.js sample includes examples of generating a SAS token both with and without the SDK.
To generate a known-good SAS token using the CLI, run the following command:
```azurecli-interactive
az iot hub generate-sas-token --device-id MyTestDevice --hub-name {YourIoTHubName}
```
Make a note of the full text of the generated SAS token. A SAS token looks like the following: `SharedAccessSignature sr=tutorials-iot-hub.azure-devices.net%2Fdevices%2FMyTestDevice&sig=....&se=1524155307`
In a terminal window on your development machine, navigate to the root folder of the sample Node.js project you downloaded. Then navigate to the **iot-hub\Tutorials\ConnectivityTests** folder.
In the terminal window, run the following commands to install the required libraries and run the simulated device application:
```cmd/sh
npm install
node SimulatedDevice-2.js "{Your SAS token}"
```
The terminal window displays information as it tries to connect to your hub using the SAS token:
You've now successfully authenticated from a device using a test SAS token generated by a CLI command. The **SimulatedDevice-2.js** file includes sample code that shows you how to generate a SAS token in code.
### Protocols
A device can use any of the following protocols to connect to your IoT hub:
| Protocol | Outbound port |
| --- | --- |
| MQTT |8883 |
| MQTT over WebSockets |443 |
| AMQP |5671 |
| AMQP over WebSockets |443 |
| HTTPS |443 |
If the outbound port is blocked by a firewall, the device can't connect:
## Check device-to-cloud connectivity
After a device connects, it typically tries to send telemetry to your IoT hub. This section shows you how you can verify that the telemetry sent by the device reaches your hub.
First, retrieve the current connection string for your simulated device using the following command:
```azurecli-interactive
az iot hub device-identity show-connection-string --device-id MyTestDevice --output table --hub-name {YourIoTHubName}
```
To run a simulated device that sends messages, navigate to the **iot-hub\Tutorials\ConnectivityTests** folder in the code you downloaded.
In the terminal window, run the following commands to install the required libraries and run the simulated device application:
```cmd/sh
npm install
node SimulatedDevice-3.js "{your device connection string}"
```
The terminal window displays information as it sends telemetry to your hub:
You can use **Metrics** in the portal to verify that the telemetry messages are reaching your IoT hub. Select your IoT hub in the **Resource** drop-down, select **Telemetry messages sent** as the metric, and set the time range to **Past hour**. The chart shows the aggregate count of messages sent by the simulated device:
It takes a few minutes for the metrics to become available after you start the simulated device.
## Check cloud-to-device connectivity
This section shows how you can make a test direct method call to a device to check cloud-to-device connectivity. You run a simulated device on your development machine to listen for direct method calls from your hub.
In a terminal window, use the following command to run the simulated device application:
```cmd/sh
node SimulatedDevice-3.js "{your device connection string}"
```
Use a CLI command to call a direct method on the device:
```azurecli-interactive
az iot hub invoke-device-method --device-id MyTestDevice --method-name TestMethod --timeout 10 --method-payload '{"key":"value"}' --hub-name {YourIoTHubName}
```
The simulated device prints a message to the console when it receives a direct method call:
When the simulated device successfully receives the direct method call, it sends an acknowledgement back to the hub:
## Check twin synchronization
Devices use twins to synchronize state between the device and the hub. In this section, you use CLI commands to send _desired properties_ to a device and read the _reported properties_ sent by the device.
The simulated device you use in this section sends reported properties to the hub whenever it starts up, and prints desired properties to the console whenever it receives them.
In a terminal window, use the following command to run the simulated device application:
```cmd/sh
node SimulatedDevice-3.js "{your device connection string}"
```
To verify that the hub received the reported properties from the device, use the following CLI command:
```azurecli-interactive
az iot hub device-twin show --device-id MyTestDevice --hub-name {YourIoTHubName}
```
In the output from the command, you can see the **devicelaststarted** property in the reported properties section. This property shows the date and time you last started the simulated device.
To verify that the hub can send desired property values to the device, use the following CLI command:
```azurecli-interactive
az iot hub device-twin update --set properties.desired='{"mydesiredproperty":"propertyvalue"}' --device-id MyTestDevice --hub-name {YourIoTHubName}
```
The simulated device prints a message when it receives a desired property update from the hub:
In addition to receiving desired property changes as they're made, the simulated device automatically checks for desired properties when it starts up.
## Clean up resources
If you don't need the IoT hub any longer, delete it and the resource group in the portal. To do so, select the **tutorials-iot-hub-rg** resource group that contains your IoT hub and click **Delete**.
## Next steps
In this tutorial, you've seen how to check your device keys, check device-to-cloud connectivity, check cloud-to-device connectivity, and check device twin synchronization. To learn more about how to monitor your IoT hub, visit the how-to article for IoT Hub monitoring.
> [!div class="nextstepaction"]
> [Monitor with diagnostics](iot-hub-monitor-resource-health.md)
| 48.558052 | 619 | 0.779792 | eng_Latn | 0.993765 |
f4c1bcd5278d5c80227abbb26177335c4ebadb38 | 7,046 | md | Markdown | _posts/2021-03-05-CEO_Interview.md | Standigm/standigm.github.io | 886189119021c7130eedd857d571c216c33a94bd | [
"MIT"
] | null | null | null | _posts/2021-03-05-CEO_Interview.md | Standigm/standigm.github.io | 886189119021c7130eedd857d571c216c33a94bd | [
"MIT"
] | 2 | 2019-06-24T06:16:30.000Z | 2019-11-21T08:54:25.000Z | _posts/2021-03-05-CEO_Interview.md | Standigm/standigm.github.io | 886189119021c7130eedd857d571c216c33a94bd | [
"MIT"
] | 2 | 2018-12-11T00:39:45.000Z | 2019-02-26T03:17:22.000Z | ---
title: "Standigm Races AI Rivals To Become Global Discovery Contender"
date: March 25, 2021
categories:
- News
tags:
- Interview
- AI
- drugdiscovery
- Standigm
- Scrip
---
The South Korean AI-driven drug discovery venture is vying with global rivals in the space to show concrete validation of its approaches in partnered projects, while eyeing international expansion and new fundraising, its CEO says.
**AI Source: ShutterstockPURSUING DISCOVERY OF FIRST-IN-CLASS, NOVEL MOLECULES**
With a goal to offer a new standard in novel drug discovery using artificial intelligence (AI) technology, South Korea's Standigm Inc. is progressing multiple co-research projects with pharma and other partners, and is poised to establish a new laboratory facility this year to further validate the competitiveness of its AI-designed molecules.
Founded in 2015, privately-held Standigm has developed what it says is an automated and all-encompassing AI approach, using experts in chemistry, biology, pharmacology and data structures, as well as AI itself.
Its business model is to focus on the discovery process pre-lead optimization, with the successful output from a collaboration to be further developed by partners or licensed out to a third party.
Jinhan Kim, CEO and co-founder, Standigm
**'Real Output' Matters**
“Technological positioning is crucial. In the end, output matters. How and when can you reach the proof of concept? How much impact can you make?" Standigm CEO and co-founder Jinhan Kim asked rhetorically in an interview with Scrip. "Many AI-driven drug discovery companies have technology to generate new molecules but only a few have the technology to discover new targets. That is how we are differentiated.”
Over the past few years, the use of AI in drug discovery has become one of the most hyped technologies in the sector. Big pharma has also been investing in the field both internally and via external partnerships. Concrete evidence of the theoretical benefits came in 2019 when two companies, including UK-based Exscientia Ltd., lay claim to a major milestone in the form of the first AI-discovered drug. (Also see "The Drug Hunter’s Assistant: Accelerating Drug Discovery With AI" - In Vivo, 25 Nov, 2019.)
Strategy-wise, Standigm's focus on early-stage discovery means it is pursuing first-in-class drugs, and it is equipped with technology portfolios in line with this strategy. “In terms of capability to generate the 'real output', or things we can actually sell, I would say Standigm lags just behind a few top AI drug discovery firms globally,” Kim said.
Pursuing full-stack industrialization of the discovery process using AI approaches, Standigm’s platforms range from novel target discovery to drug lead generation. It has achieved the automation of molecular design workflow through its Dark MolFactory system and automation has been extended to the entire discovery process using multiple proprietary platforms, including Standigm ASK (target discovery), Standigm BEST (lead selection) and Standigm Insight (drug repurposing).
ASK can identify targets utilizing an explainable deep learning model, while BEST generates novel compounds satisfying the desired properties of partners by exploring an AI-generated latent chemical discovery space that maps compound structure patterns into information-rich representations.
Existing or novel compounds can be generated by decoding any points in this space, and the Insight platform meanwhile can reinforce any in-house compound by the discovery of potential hidden indications and pathways using target prediction.
**New Indication Success**
At present, Standigm is progressing 18 pipeline assets with partners across various therapeutic areas including cancer and skin diseases. The most advanced is at the lead optimization stage and is set to move on into preclinical development later this year.
One of the venture's recent notable achievements was in January, when it and partner SK Chemicals Co., Ltd., a major Korean group, successfully identified a new rheumatoid arthritis indication for a US FDA-approved drug using Standigm Insight, and have now filed for a patent. This was the first successful result of the firms' partnership, which aims to identify novel lead compounds and repurpose existing drugs for both rheumatoid arthritis and non-alcoholic steatohepatitis (NASH).
In a mouse model of collagen-induced arthritis, the compound showed comparable or better improvements in disease activity score than reference drugs such as methotrexate and hydroxychloroquine. Further research and development of the compound is ongoing with the objective of completing preclinical studies, and the companies expect significant reductions in cost and time for preclinical and clinical development for the new indication.
Standigm is also collaborating with various other pharma companies both at home and abroad, as well as with research institutes and hospitals.
With Hanmi Pharmaceutical Co., Ltd., another leading Korean group, it is developing pipeline candidates in areas including cancer and NASH. It has also reached a co-research and development agreement with HK inno.N to discover new chemical compound structures using its AI platforms.
Speaking on partnership strategy, CEO Kim said he considers reliability the most important factor. “We seek partners that don’t reach dual contracts and who prioritize success of the compounds and projects and not those who pursue other objectives such as raising stock prices or corporate images.
"Secondly, we want partners who prioritize our projects. Otherwise, it can slow progress of the projects or disrupt allocation of budgets for the projects.”
**New Lab, IPO Plans**
Standigm plans to establish a new drug synthesis laboratory with the aim of improving synergies between data-driven AI and actual physical experimental work. “There are things that AI is good at but also areas that don’t work well when we go further. We need to resolve this issue. At present, only a few global companies, such as Exscientia, have independent synthesis labs," Kim observed.
So far, the bioventure has raised about $60m in total, including pre-IPO funding of $44.5m earlier this month. As part of the partnership with SK, the SK Group conglomerate has invested KRW10bn ($8.8m) in Standigm and together with the group’s new drug development subsidiary SK Biopharmaceuticals - which also operates an AI-based drug platform - the two parties aim to grow into global market leaders in the space.
Standigm's near-term funding goal is to launch an initial public offering on the Kosdaq market in South Korea sometime this year. In the longer term, it aims to enter, and generate revenues from, the global market.
“We have been planning to advance into other markets but the plan has been delayed partly due to the COVID-19 situation and IPO plan. We are trying to establish offices in countries such as the US and UK but the timing and other details haven’t been finalized,” the CEO said. | 111.84127 | 507 | 0.809963 | eng_Latn | 0.999595 |
f4c248bb7bf00905102104e2a69fdb431362be79 | 1,461 | md | Markdown | Readme.md | kishorerv93/alexa-skill-kubernetes | b73a7cb0d4fae283caef3e0fc6e4196f91eb092b | [
"Apache-2.0"
] | null | null | null | Readme.md | kishorerv93/alexa-skill-kubernetes | b73a7cb0d4fae283caef3e0fc6e4196f91eb092b | [
"Apache-2.0"
] | null | null | null | Readme.md | kishorerv93/alexa-skill-kubernetes | b73a7cb0d4fae283caef3e0fc6e4196f91eb092b | [
"Apache-2.0"
] | null | null | null | # Kubernetes Skill for Alexa
## Overview
This is a simple skill for Amazon Alexa that allows Alexa to interact with an existing Kubernetes cluster.
It's implemented as Amazon Lambda Function, which is configured via environment variables (e.g. kubernetes master url, oauth token etc).
## Features
Currently it supports the following intents:
- Get namespaces / projects
- Switch to namespace / project
- Get deployments
- Get (failing )pods
- Get services
## Building & Installation
You can build and install the function using something like:
mvn clean package shade:shade com.github.seanroy:lambda-maven-plugin:deploy-lambda -DaccessKey=`pass aws/access_key` -DsecretKey=`pass aws/sec
The above assumes that you are using [password-store](https://passwordstore.org) for managing credentials (which btw you should do rahter than keeping them lying around as env vars...).
If not, feel free to substitute the `pass` bits with your actual access key and secret.
If for any reason, the function is not automatically created, you can manually upload the generated zip.
## Configuring the Function
To specify which is the cluster, how to authenticate etc, you'll need to specify a couple of environment variables to the lambda console:
- KUBERNETES_MASTER
- KUBERNETES_AUTH_TOKEN
- ALEXA_SKILL_ID
### Todo
- Use word distance so that we accept words that might not be `equals()` but are close to being equals (e.g. more than 80%).
| 33.976744 | 185 | 0.769336 | eng_Latn | 0.995563 |
f4c2552dbbb52cc4c786f4e08d7ae02a768f4e80 | 14,422 | md | Markdown | README.md | FrankTianTT/Masked_Face_Recognition | 2b2a8844b20f550313c65be671f93e90c080ff6a | [
"MIT"
] | 60 | 2021-04-06T15:01:51.000Z | 2022-03-27T07:26:28.000Z | README.md | FrankTianTT/Masked_Face_Recognition | 2b2a8844b20f550313c65be671f93e90c080ff6a | [
"MIT"
] | 9 | 2021-04-11T15:23:50.000Z | 2022-03-21T08:30:31.000Z | README.md | FrankTianTT/Masked_Face_Recognition | 2b2a8844b20f550313c65be671f93e90c080ff6a | [
"MIT"
] | 11 | 2021-09-07T07:58:21.000Z | 2022-03-19T16:26:15.000Z | # Masked Facial Recognition
2020/2021 HKUST CSE FYP Masked Facial Recognition, developer: Sam Yuen, Alan Xie, Tony Cheng
Supervisor: Prof. Dit-Yan YEUNG
This Github repository shows how to train a masked face recognition model. We use the masked facial recognition models to build a building security system in another [Github repository](https://github.com/SamYuen101234/BSMFR).
### Download masked facial recognition train and test data
We use a tool call [MaskTheFace](https://sites.google.com/view/masktheface/home) to simulate masked facial images based on some famous face image datasets. We choose several different masks to simulate. They are green surgical mask (#44b4a8), blue surgical mask (#1ca0f4), white N95 mask (#FFFFFF), white KN-95 mask and black cloth mask (#000000).
Preview of part of the data:
Figure 1. Some training data of CASIA after preprocessing
Figure 2. Some image pairs of Evaluation and testing sets, the upper two pairs are same person, the bottom two pairs are different people
| Dataset | # Identities|# Images |
| ----------- | ----------- | ----------- |
| CASIA | 10,585 | 492,832 |
| VGG2 | 8,631 | 2,024,897 |
| LFW (eval+test) | 5,749 | 64,811 |
- Information of all datasets shown above is after preprocessing so the numbers and sizes differ from the original datasets
1. Training set 1 (Masked CASIA) 3GB
Link: [Google Drive](https://drive.google.com/file/d/1wqLxMbV335dHkX_7lLCROABd6-aC149B/view?usp=sharing)
2. Training set 2 (Masked VGG2) 11GB
Link: [Google Drive](https://drive.google.com/file/d/1qPwssuYgieeM_38gBJ9N-s-S1ySRo9Ka/view?usp=sharing)
3. Training CSV (Masked CASIA + Masked VGG2) 115MB
Link: [Google Drive](https://drive.google.com/file/d/1BrZtoDbdc61pdH2GQ4v1GJKr9cQM-jVh/view?usp=sharing)
3. Test set (LFW), including evaluation set and test set, 148MB
Link: [Google Drive](https://drive.google.com/file/d/1bVP3gbAHjzB33wkEbG8MChd7tp1Ee2Oo/view?usp=sharing)
4. Evaluation set 1 CSV (all same person pairs) 7MB
Link: [Google Drive](https://drive.google.com/file/d/1f3NTKV4YxOmHsZHgEm9MTacW85fyiZRM/view?usp=sharing)
5. Evaluation set 2 CSV (all different person pairs) 7MB
Link: [Google Drive](https://drive.google.com/file/d/1RdFbIGDiMMVaAPpt8CsykJRqTE4GfJH3/view?usp=sharing)
7. Test CSV, 782KB
Link: [Google Drive](https://drive.google.com/file/d/15axXyvMhlu4z3_jAZJh16f5wucoOS_Jd/view?usp=sharing)
8. Real faces, 81MB
Link: [Google Drive](https://drive.google.com/file/d/1EBR2jgBLNhMoyZxA6f4ffX1la8VWStXa/view?usp=sharing)
There are totally 75 real people in this real face dataset, every class has 3 no masked and masked images seperately. Some of than has higher resolution and has not been cropped and aligned by MTCNN. It is becuase we use this data on our recognition system to simulate users' registration.
Most of them are politicans or celebrities. Some of the real faces are from [MRF2](https://sites.google.com/view/masktheface/home), some of them are collected by us from Google.
### Download Pre-train models
| Models | # Architect|# Loss func |# Pre-trained |# Acc |
| ----------- | ----------- | ----------- |----------- |----------- |
| Model1 | InceptionResNetV1 | ArcFace with focal loss |Yes |95.xx% |
| Model2 | InceptionResNetV1 | Triplet loss with online triplet mining |Yes |94.xx% |
| Model3 | SE-ResNeXt-101 | ArcFace with focal loss |No |93.xx% |
* You may train a model with better performance than ours because we are dealing with our fyp in limited time. You can feel free to fine tune the hyperparameters or deal with any other approaches with our resources.
Model1 (148MB)
Link: [Google Drive](https://drive.google.com/file/d/1DsMV1R5eqwHiVgfujlCa4NSpqmk-ecor/view?usp=sharing)
(Please be careful that model 2 and its optimizer are combined in this .pth format rather than .pt format)
Model2 (290MB, including model and optimizer)
Link: [Google Drive](https://drive.google.com/file/d/1aZE6NEvIqIkwFn6U-vBkhbmG4yz38AFQ/view?usp=sharing)
Model3 (229MB)
Link: [Google Drive](https://drive.google.com/file/d/1pdbNvqtemODmp7f9qGXqTnt1f_F-pKMN/view?usp=sharing)
To load the model 2, you need to use this function becuase this model was trained by another groupmate:
def load(name, model, optimizer):
checkpoint = torch.load('../Model/' + name)
model.load_state_dict(checkpoint['model_state_dict'])
optimizer.load_state_dict(checkpoint['optimizer_state_dict'])
for state in optimizer.state.values():
for k, v in state.items():
if isinstance(v, torch.Tensor):
state[k] = v.cuda()
If you want to know more about the training process and concept, you can read our progress report, final report and the following papers:
1. [Our final report, the masked facial recognition system](https://drive.google.com/file/d/1UMAxqBX42XRubtzxHzHe0-mYubYd9yXQ/view?usp=sharing)
2. [Our progress report (Implementation section)](https://drive.google.com/file/d/17qEgb0ZC0Ml7gym4rl2ShGBbrjmXATQz/view?usp=sharing)
3. [FaceNet: A Unified Embedding for Face Recognition and Clustering](https://arxiv.org/abs/1503.03832)
4. [Offline versus Online Triplet Mining based on Extreme Distances of Histopathology Patches](https://arxiv.org/abs/2007.02200)
5. [Masked Face Recognition for Secure Authentication](https://arxiv.org/abs/2008.11104)
6. [Deep metric learning using Triplet network](https://arxiv.org/abs/1412.6622)
7. [ArcFace: Additive Angular Margin Loss for Deep Face Recognition](https://arxiv.org/abs/1801.07698)
8. [Normal Face Recignition with ArcFace in Pytorch](https://github.com/ZhaoJ9014/face.evoLVe.PyTorch)
You can find more in the reference list.
### Run
Before you run you need to install the follow package or library first:
> pip install tqdm
>
> pip install facenet-pytorch
>
> pip install efficientnet
>
> pip install timm
We expect that you have install other common packages like torch, numpy, pandas...
Create folders call models and result under this directory to save the models and eval images during training or change the directory in the script (train.py).
To train a model with online triplet mining, run:
> python3 main.py
To train a model with ArcFace, run:
> python3 main2.py
### Methodolegy
Figure 3. Architects for Triplet loss and ArcFace
Figure 4. A simple method for triplet loss but this might suffer from model collapse
Figure 5. Online triplet mining method, the more popular one for triplet mining.
To know more our training methods in details, please read our progress report and the paper in reference.
### Result
In our experiment, we observe that Arcface's performance is slightly better than online triplet mining and also the training time per epoch is shorter than online triplet mining. It is becuase online triplet mining need to sample mini batch to calculate the hardest/semi-hard triplet loss. We only show the result of the model 1 (Pre-trained InceptionResNetV1 with Arcface here)
#### Train result
In the paper [Masked Face Recognition for Secure Authentication](https://arxiv.org/abs/2008.11104), they mentioned that they tried online triplet mining and train the InceptionResNetV1 without pre-trained. We also followed the same method to train a model, but the result is not that good as the one shown in their paper. In our experiment with online triplet mining, the model was difficult to converge and it is very sensitive to how you select the triplet pairs e.g. hardest triplets or semi-hard triplets. Then, arcface is much easier to be controlled compared with online triplet mining.
Training loss: Since we use pre-trained model, the loss reduces and converges more easier than without transfer learning. Without pre-trained, the model needs to be trained with more epochs (around 60 - 120 epochs) compared to 20 - 30 epochs with pre-trained model. We also use multi-step lr decay scheduler to reduce the learning rate. At the beginning, the learning rate is 0.1. The lr will decay 0.1 after epoch 5, 10, 15 and 20.
Figure 6. Training loss with learning rate decay
We also tried SE-ResNeXt-101 and EffectiveNetB2 to B4. The two models only have the pre-trained version on ImageNet. It is not suitable for transfer learning on face recognition. However, we also did experiment on their pre-trained version and starting from scratch. The result is that there may result collaspe in the model very easily which was not only happened with triplet loss but also arcface sometimes. EfficientNet is usually more likely to result in model collapse after few training epochs.
Figure7. Model Collapse of EfficientNet B4
#### Evaluation method
Eval graph: The L2 distance of the embeddings of the image pairs. We will calculate and plot this graph at the end of each epoch.
Figure 8. Eval graph
IOU: We plot the eval graph at the end of each epoch. IOU = area of the intersection / area of the eval graph
Figure 9. IOU
The model with lowest IOU will be saved as the best model.
#### Test result
We use 6,482 pairs of images to be the test set, half of the pairs are the same person and the another half is different people.
Label 0 means that the pair is from two different people and label 1 means that they are from the same person.
This result is from the model1 InceptionResnetV1 with ArcFace.
The accuracy is almost 96%.
The test result matches the eval result. As you can see, more pairs of same person are classified incorrectly.
Figure 10. Confusion matrix
Evaluation matrix:
Accuracy: 0.9585004628201172
precision recall f1-score support
0 0.93 0.99 0.96 3241
1 0.99 0.93 0.96 3241
accuracy 0.96 6482
macro avg 0.96 0.96 0.96 6482
weighted avg 0.96 0.96 0.96 6482
**Please be careful that the face recognition test performance here may be different from a face recognition system. It is becuase face recognition system needs more technical approaches rather then a CNN model with threshold only.**
### What you can improve through our resources
1. Try fix the problem of model collapse in EfficientNet. If you have sufficient computational power, you can try EfficientNet B7. We used a workstation with 4 RTX2080 Ti 11GB GPUs, but the cuda does not have enough memory when we try EfficientNet B7. We believe that EfficientNet is much more powerful than InceptionResNetV1 according to Google's paper.
2. Compare Online triplet mining and arcface again, we did not perform too much experiment on them becuase of limited FYP period.
3. Try to sample a more balancing dataset based on our training set, this means that each class have same number of images.
4. Fine tune the hyperparameters
5. Try more new techniques
6. Use real masked facial images to train, rather than using simulated masked images. (This is quite difficult, we can only wait some research team like VGG from U of Oxford to collect a large real masked facial images)
**Masked facial recognition is not that difficult or impossible. The most difficult part is that how to achieve a performance as good as normal facial recognition (>99% accuracy). Also, the most time consuming part / difficult part is not machine learning techniques/approaches here. It is how to collect a suitable training dataset with enough data. You can find some papers about this topic quite easily, but it is not easy to find suitable datasets/code. That why we open-source our pre-processed training data to everyone.**
### Reference list
Only show some important reference:
1. [Schroff, Florian & Kalenichenko, Dmitry & Philbin, James. (2015). FaceNet: A unified embedding for face recognition and clustering. 815-823.10.1109/CVPR.2015.7298682.](https://arxiv.org/abs/1503.03832)
2. [GitHub. X-Zhangyang/Real-World-Masked-Face-Dataset](https://github.com/X-zhangyang/Real-World-Masked-Face-Dataset)
3. [Aqeel Anwar, Arijit Raychowdhury (2020), Masked Face Recognition for Secure Authentication, arXiv:2008.11104](https://arxiv.org/abs/2008.11104)
4. [Mingxing Tan, Quoc V. Le (2019), EfficientNet: Rethinking Model Scaling for Convolutional Neural Networks, arXiv:1905.11946](https://arxiv.org/abs/1905.11946)
5. [Filip Radenović, Giorgos Tolias, Ondřej Chum (2017), Fine-tuning CNN Image Retrieval with No Human Annotation, arXiv:1711.02512](https://arxiv.org/abs/1711.02512)
6. [Jiankang Deng, Jia Guo, Niannan Xue, Stefanos Zafeiriou (2018), ArcFace: Additive Angular Margin Loss for Deep Face Recognition, arXiv:1801.07698](https://arxiv.org/abs/1801.07698)
7. [Tsung-Yi Lin, Priya Goyal, Ross Girshick, Kaiming He, Piotr Dollár (2017), Focal Loss for Dense Object Detection, arXiv:1708.02002](https://arxiv.org/abs/1708.02002)
8. [GitHub. aqeelanwar/MaskTheFace.](https://github.com/aqeelanwar/MaskTheFace)
9. [Kaipeng Zhang, Zhanpeng Zhang, Zhifeng Li, Yu Qiao (2016), Joint Face Detection and Alignment using Multi-task Cascaded Convolutional Networks, arXiv:1604.02878](https://arxiv.org/abs/1604.02878)
10. [Olivier Moindrot blog. 2018. Triplet Loss and Online Triplet Mining in TensorFlow - Olivier Moindrot.](https://omoindrot.github.io/triplet-loss)
11. [GitHub. NegatioN/OnlineMiningTripletLoss.](https://github.com/NegatioN/OnlineMiningTripletLoss)
12. [GitHub. rwightman/triplet_loss.py.](https://gist.github.com/rwightman/fff86a015efddcba8b3c8008167ea705)
13. [Github. ZhaoJ9014/face.evoLVe.PyTorch.](https://github.com/ZhaoJ9014/face.evoLVe.PyTorch)
### License
MIT license is used here. You can follow the permission to do whatever you want. However, some of our code is from other developers, you should be careful that some of them may be prohibited from commerical use.
### Contact
Please feel free to push your changes to improve the code here. If you have any problems, you could contact us through <[email protected]>
| 57.230159 | 594 | 0.751283 | eng_Latn | 0.964556 |
f4c29e1002ecdf1bb4751552616754fcce3e9fb8 | 19 | md | Markdown | README.md | Bosco98/TextToSpeech-Web | 95099c234c76db67e0fe6ebadb0e4e462ad6480e | [
"MIT"
] | null | null | null | README.md | Bosco98/TextToSpeech-Web | 95099c234c76db67e0fe6ebadb0e4e462ad6480e | [
"MIT"
] | null | null | null | README.md | Bosco98/TextToSpeech-Web | 95099c234c76db67e0fe6ebadb0e4e462ad6480e | [
"MIT"
] | null | null | null | # TextToSpeech-Web
| 9.5 | 18 | 0.789474 | kor_Hang | 0.702998 |
f4c2f139da22e476fa6e1295afd9252aa1a9a971 | 1,053 | md | Markdown | src/pages/sessions/flash-gordon.md | Marchie/manyharrier.co.uk | 48cde1650ba066bcd4a706a279d469e16f8b5a98 | [
"MIT"
] | null | null | null | src/pages/sessions/flash-gordon.md | Marchie/manyharrier.co.uk | 48cde1650ba066bcd4a706a279d469e16f8b5a98 | [
"MIT"
] | null | null | null | src/pages/sessions/flash-gordon.md | Marchie/manyharrier.co.uk | 48cde1650ba066bcd4a706a279d469e16f8b5a98 | [
"MIT"
] | null | null | null | ---
templateKey: session
sessionKey: Flash Gordon
description: A track training session
---
This is a distance based session, consisting of one 800m effort,
eight 300m efforts, then one 800m effort to finish.
The session in full:
* **800m effort** (two laps of the track)
* 1 minute standing recovery
* **300m effort** (three-quarters of a lap)
* 100m jog recovery (one-quarter of a lap)
* **300m effort** (three-quarters of a lap)
* 100m jog recovery (one-quarter of a lap)
* **300m effort** (three-quarters of a lap)
* 100m jog recovery (one-quarter of a lap)
* **300m effort** (three-quarters of a lap)
* 100m jog recovery (one-quarter of a lap)
* **300m effort** (three-quarters of a lap)
* 100m jog recovery (one-quarter of a lap)
* **300m effort** (three-quarters of a lap)
* 100m jog recovery (one-quarter of a lap)
* **300m effort** (three-quarters of a lap)
* 100m jog recovery (one-quarter of a lap)
* **300m effort** (three-quarters of a lap)
* 100m jog recovery (one-quarter of a lap)
* **800m effort** (two laps of the track)
* Finish!
| 31.909091 | 64 | 0.705603 | eng_Latn | 0.978974 |
f4c38cac2960629c38f8ee6587e46d46e8fa10e3 | 1,216 | md | Markdown | docs/Mods/Immersive_Petroleum/CraftTweaker_Support/FuelRegistration.md | Efimero/CraftTweaker-Documentation | 764a9dafd4829ce81251370ed1e461079b01393a | [
"MIT"
] | null | null | null | docs/Mods/Immersive_Petroleum/CraftTweaker_Support/FuelRegistration.md | Efimero/CraftTweaker-Documentation | 764a9dafd4829ce81251370ed1e461079b01393a | [
"MIT"
] | null | null | null | docs/Mods/Immersive_Petroleum/CraftTweaker_Support/FuelRegistration.md | Efimero/CraftTweaker-Documentation | 764a9dafd4829ce81251370ed1e461079b01393a | [
"MIT"
] | null | null | null | # Fuel Registration
## Motorboat
### registerMotorboatFuel
|Type |Data Type |
|------------------|--------------------------------------------------|
|Input |[Fluidstack](/Vanilla/Liquids/ILiquidStack) |
|mB/t |Integer |
#### Code Example:
```JAVA
mods.immersivepetroleum.Motorboat.registerMotorboatFuel(ILiquidStack fuelEntry, int mbPerTick);
mods.immersivepetroleum.Motorboat.registerMotorboatFuel(<liquid:water>, 5);
```
## Portable Generator
### registerPortableGenFuel
|Type |Data Type |
|-------------------|-------------------------------------------------|
|Input |[Fluidstack](/Vanilla/Liquids/ILiquidStack) |
|Flux/t |Integer |
|mB/t |Integer |
#### Code Example:
```JAVA
mods.immersivepetroleum.PortableGenerator.registerPortableGenFuel(ILiquidStack fuelEntry, int fluxPerTick, int mbPerTick);
mods.immersivepetroleum.PortableGenerator.registerPortableGenFuel(<liquid:water>, 2048, 50);
```
| 32.864865 | 122 | 0.48602 | yue_Hant | 0.651585 |
f4c3e366ab9c58253c3c963350a79d89a5d9063c | 13,920 | md | Markdown | docs/mfc/mfc-activex-controls-licensing-an-activex-control.md | Chrissavi/cpp-docs.de-de | 6cc90f896a0a1baabb898a00f813f77f058bb7e5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/mfc-activex-controls-licensing-an-activex-control.md | Chrissavi/cpp-docs.de-de | 6cc90f896a0a1baabb898a00f813f77f058bb7e5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/mfc-activex-controls-licensing-an-activex-control.md | Chrissavi/cpp-docs.de-de | 6cc90f896a0a1baabb898a00f813f77f058bb7e5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'MFC-ActiveX-Steuerelemente: Lizenzieren eines ActiveX-Steuerelements'
ms.date: 11/19/2018
helpviewer_keywords:
- COleObjectFactory class [MFC], licensing controls
- MFC ActiveX controls [MFC], licensing
- VerifyLicenseKey method [MFC]
- VerifyUserLicense method [MFC]
- GetLicenseKey method [MFC]
- licensing ActiveX controls
ms.assetid: cacd9e45-701a-4a1f-8f1f-b0b39f6ac303
ms.openlocfilehash: 4fe2fcf63cce02ed6c1c9943e6d0fe6ffab00a92
ms.sourcegitcommit: c21b05042debc97d14875e019ee9d698691ffc0b
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 06/09/2020
ms.locfileid: "84622367"
---
# <a name="mfc-activex-controls-licensing-an-activex-control"></a>MFC-ActiveX-Steuerelemente: Lizenzieren eines ActiveX-Steuerelements
Lizenzierungs Unterstützung, ein optionales Feature von ActiveX-Steuerelementen, ermöglicht Ihnen, zu steuern, wer das Steuerelement verwenden oder verteilen kann. (Informationen zur weiteren Erörterung von Lizenzierungs Problemen finden Sie unter Lizenzierungsprobleme beim [Upgrade eines vorhandenen ActiveX-Steuer](upgrading-an-existing-activex-control.md)Elements.)
> [!IMPORTANT]
> ActiveX ist eine ältere Technologie, die nicht für die neue Entwicklung verwendet werden sollte. Weitere Informationen zu modernen Technologien, die ActiveX ersetzen, finden Sie unter ActiveX-Steuer [Elemente](activex-controls.md).
In diesem Artikel werden die folgenden Themen behandelt:
- [Übersicht über die ActiveX-Steuerelement Lizenzierung](#_core_overview_of_activex_control_licensing)
- [Erstellen eines lizenzierten Steuer Elements](#_core_creating_a_licensed_control)
- [Lizenzierungs Unterstützung](#_core_licensing_support)
- [Anpassen der Lizenzierung eines ActiveX-Steuer Elements](#_core_customizing_the_licensing_of_an_activex_control)
ActiveX-Steuerelemente, die eine Lizenzierung implementieren, ermöglichen es Ihnen, als Steuerelement Entwickler zu bestimmen, wie andere Benutzer das ActiveX-Steuerelement verwenden werden. Sie stellen dem Steuerelement Käufer das-Steuerelement und bereit. Die-Datei mit der Vereinbarung, dass der Käufer das Steuerelement verteilen darf, jedoch nicht. Die-Datei mit einer Anwendung, die das-Steuerelement verwendet. Dadurch wird verhindert, dass Benutzer dieser Anwendung neue Anwendungen schreiben, die das-Steuerelement verwenden, ohne zuvor das Steuerelement von Ihnen zu lizenzieren.
## <a name="overview-of-activex-control-licensing"></a><a name="_core_overview_of_activex_control_licensing"></a>Übersicht über die ActiveX-Steuerelement Lizenzierung
Zur Unterstützung von Lizenzierung für ActiveX-Steuerelemente stellt die [COleObjectFactory](reference/coleobjectfactory-class.md) -Klasse eine Implementierung für mehrere Funktionen in der `IClassFactory2` -Schnittstelle bereit: `IClassFactory2::RequestLicKey` , `IClassFactory2::GetLicInfo` und `IClassFactory2::CreateInstanceLic` . Wenn der Container Anwendungsentwickler eine Anforderung zum Erstellen einer Instanz des-Steuer Elements sendet, wird aufgerufen, `GetLicInfo` um das-Steuerelement zu überprüfen. Die Datei "lischen" ist vorhanden. Wenn das Steuerelement lizenziert ist, kann eine Instanz des Steuer Elements erstellt und in den Container eingefügt werden. Nachdem der Entwickler die Containeranwendung erstellt hat, wird dieses Mal ein weiterer Funktionsaufruf durch `RequestLicKey` geführt. Diese Funktion gibt einen Lizenzschlüssel (eine einfache Zeichenfolge) an die Containeranwendung zurück. Der zurückgegebene Schlüssel wird dann in die Anwendung eingebettet.
In der folgenden Abbildung wird die Lizenz Überprüfung eines ActiveX-Steuer Elements veranschaulicht, das während der Entwicklung einer Containeranwendung verwendet wird. Wie bereits erwähnt, muss der Container Anwendungsentwickler über die richtige verfügen. Auf dem Entwicklungs Computer installierter LIC-Datei zum Erstellen einer Instanz des Steuer Elements.
 <br/>
Überprüfung eines lizenzierten ActiveX-Steuerelements während der Entwicklung
Der nächste Prozess, der in der folgenden Abbildung gezeigt wird, tritt auf, wenn der Endbenutzer die Containeranwendung ausführt.
Wenn die Anwendung gestartet wird, muss in der Regel eine Instanz des Steuer Elements erstellt werden. Der Container erreicht dies durch Aufrufen von, indem er `CreateInstanceLic` den eingebetteten Lizenzschlüssel als Parameter übergibt. Anschließend wird ein Zeichen folgen Vergleich zwischen dem eingebetteten Lizenzschlüssel und der eigenen Kopie des Lizenzschlüssels des-Steuer Elements vorgenommen. Wenn die Entsprechung erfolgreich ist, wird eine Instanz des Steuer Elements erstellt, und die Anwendung wird weiterhin normal ausgeführt. Beachten Sie, dass die. Die LIC-Datei muss auf dem Computer des Steuer Elements nicht vorhanden sein.
 <br/>
Überprüfung eines lizenzierten ActiveX-Steuerelements während der Ausführung
Die Steuerelement Lizenzierung besteht aus zwei grundlegenden Komponenten: spezifischer Code in der Steuerungs-Implementierungs-DLL und der Lizenzdatei. Der Code besteht aus zwei (oder möglicherweise drei) Funktionsaufrufen und einer Zeichenfolge, die im folgenden als "Lizenz Zeichenfolge" bezeichnet wird und einen Urheberrechts Hinweis enthält. Diese Aufrufe und die Lizenz Zeichenfolge finden Sie in der Implementierung des Steuer Elements (. Cpp-Datei. Die vom ActiveX-Steuerelement-Assistenten generierte Lizenzdatei ist eine Textdatei mit einer Copyright Erklärung. Der Name wird mit dem Projektnamen mit einem benannt. Die Erweiterung "lischen", z. b. Beispiel. Fröhlich. Ein lizenziertes Steuerelement muss von der Lizenzdatei begleitet werden, wenn die Entwurfszeit Verwendung erforderlich ist.
## <a name="creating-a-licensed-control"></a><a name="_core_creating_a_licensed_control"></a>Erstellen eines lizenzierten Steuer Elements
Wenn Sie den ActiveX-Steuerelement-Assistenten verwenden, um das Steuerelement Framework zu erstellen, können Sie den Lizenzierungs Support problemlos einschließen. Wenn Sie angeben, dass das Steuerelement über eine Laufzeitlizenz verfügen soll, fügt der ActiveX-Steuerelement-Assistent der Control-Klasse Code hinzu, um die Lizenzierung zu unterstützen. Der Code umfasst Funktionen, die einen Schlüssel und eine Lizenzdatei für die Lizenz Überprüfung verwenden. Diese Funktionen können auch so geändert werden, dass die Steuerelement Lizenzierung angepasst wird. Weitere Informationen zur Lizenz Anpassung finden Sie unter [Anpassen der Lizenzierung eines ActiveX-Steuer](#_core_customizing_the_licensing_of_an_activex_control) Elements weiter unten in diesem Artikel.
#### <a name="to-add-support-for-licensing-with-the-activex-control-wizard-when-you-create-your-control-project"></a>So fügen Sie Unterstützung für die Lizenzierung mit dem ActiveX-Steuerelement-Assistenten hinzu
1. Verwenden Sie die Anweisungen unter [Erstellen eines MFC-ActiveX-Steuer](reference/creating-an-mfc-activex-control.md)Elements. Auf der Seite **Anwendungseinstellungen** des ActiveX-Steuerelement-Assistenten ist die Option zum Erstellen des Steuer Elements mit der Laufzeitlizenz enthalten.
Der ActiveX-Steuerelement-Assistent generiert nun ein ActiveX-Steuerelement Framework, das grundlegende Lizenzierungs Unterstützung umfasst Eine ausführliche Erläuterung des Lizenzierungs Codes finden Sie im nächsten Thema.
## <a name="licensing-support"></a><a name="_core_licensing_support"></a>Lizenzierungs Unterstützung
Wenn Sie mithilfe des ActiveX-Steuerelement-Assistenten einem ActiveX-Steuerelement Lizenzierungs Unterstützung hinzufügen, fügt der ActiveX-Steuerelement-Assistent Code hinzu, der die Lizenzierungs Funktion deklariert und implementiert, dem Steuerelement Header und den Implementierungs Dateien. Dieser Code besteht aus einer `VerifyUserLicense` Member-Funktion und einer `GetLicenseKey` Member-Funktion, die die in [COleObjectFactory](reference/coleobjectfactory-class.md) gefundenen Standard Implementierungen überschreiben. Diese Funktionen rufen die Steuerelement Lizenz ab und überprüfen Sie.
> [!NOTE]
> Eine dritte Member-Funktion `VerifyLicenseKey` wird nicht vom ActiveX-Steuerelement-Assistenten generiert, kann jedoch überschrieben werden, um das Überprüfungs Verhalten des Lizenzschlüssels anzupassen.
Diese Member-Funktionen sind:
- [Verigyuserlicense](reference/coleobjectfactory-class.md#verifyuserlicense)
Überprüft, ob das Steuerelement Entwurfszeit Verwendung zulässt, indem das System auf das vorhanden sein der Steuerelement Lizenzdatei überprüft wird. Diese Funktion wird vom Framework als Teil der Verarbeitung von `IClassFactory2::GetLicInfo` und aufgerufen `IClassFactory::CreateInstanceLic` .
- [Getlicenabkey](reference/coleobjectfactory-class.md#getlicensekey)
Fordert einen eindeutigen Schlüssel von der Steuerelement-DLL an. Dieser Schlüssel ist in die Containeranwendung eingebettet und wird später in Verbindung mit verwendet, `VerifyLicenseKey` um eine Instanz des Steuer Elements zu erstellen. Diese Funktion wird vom Framework als Teil der Verarbeitung aufgerufen `IClassFactory2::RequestLicKey` .
- [Verifylicenabkey](reference/coleobjectfactory-class.md#verifylicensekey)
Überprüft, ob der eingebettete Schlüssel und der eindeutige Schlüssel des Steuer Elements identisch sind. Dies ermöglicht es dem Container, eine Instanz des Steuer Elements für seine Verwendung zu erstellen. Diese Funktion wird vom Framework als Teil der Verarbeitung aufgerufen `IClassFactory2::CreateInstanceLic` und kann überschrieben werden, um eine angepasste Überprüfung des Lizenzschlüssels bereitzustellen. Die Standard Implementierung führt einen Zeichen folgen Vergleich durch. Weitere Informationen finden Sie weiter unten in diesem Artikel unter [Anpassen der Lizenzierung eines ActiveX-Steuer](#_core_customizing_the_licensing_of_an_activex_control)Elements.
### <a name="header-file-modifications"></a><a name="_core_header_file_modifications"></a>Header Dateiänderungen
Der ActiveX-Steuerelement-Assistent platziert den folgenden Code in der Header Datei des Steuer Elements. In diesem Beispiel werden zwei Member-Funktionen des `CSampleCtrl` -Objekts `factory` deklariert, ein Objekt, das das vorhanden sein des-Steuer Elements überprüft. Eine beliebige Datei und eine andere, die den Lizenzschlüssel abruft, der in der Anwendung verwendet werden soll, die das Steuerelement enthält:
[!code-cpp[NVC_MFC_AxUI#39](codesnippet/cpp/mfc-activex-controls-licensing-an-activex-control_1.h)]
### <a name="implementation-file-modifications"></a><a name="_core_implementation_file_modifications"></a>Implementierungs Dateiänderungen
Der ActiveX-Steuerelement-Assistent platziert die folgenden zwei Anweisungen in der Implementierungs Datei des Steuer Elements, um den Lizenz Dateinamen und die Lizenz Zeichenfolge
[!code-cpp[NVC_MFC_AxUI#40](codesnippet/cpp/mfc-activex-controls-licensing-an-activex-control_2.cpp)]
> [!NOTE]
> Wenn Sie `szLicString` in irgendeiner Weise ändern, müssen Sie auch die erste Zeile im Steuerelement ändern. Die Datei-oder Lizenzierungs Funktion funktioniert nicht ordnungsgemäß.
Der ActiveX-Steuerelement-Assistent fügt den folgenden Code in die Implementierungs Datei des Steuer Elements ein, um die `VerifyUserLicense` -und-Funktionen zu definieren `GetLicenseKey` :
[!code-cpp[NVC_MFC_AxUI#41](codesnippet/cpp/mfc-activex-controls-licensing-an-activex-control_3.cpp)]
Schließlich ändert der **ActiveX-Steuer** Element-Assistent das Steuerelement Projekt. IDL-Datei. Das **lizenzierte** Schlüsselwort wird der Co-Klassen Deklaration des Steuer Elements hinzugefügt, wie im folgenden Beispiel gezeigt:
[!code-cpp[NVC_MFC_AxUI#42](codesnippet/cpp/mfc-activex-controls-licensing-an-activex-control_4.idl)]
## <a name="customizing-the-licensing-of-an-activex-control"></a><a name="_core_customizing_the_licensing_of_an_activex_control"></a>Anpassen der Lizenzierung eines ActiveX-Steuer Elements
Da `VerifyUserLicense` , `GetLicenseKey` und `VerifyLicenseKey` als Virtual Member-Funktionen der Steuerelement-Factoryklasse deklariert werden, können Sie das Lizenzierungs Verhalten des Steuer Elements anpassen.
Beispielsweise können Sie mehrere Lizenzierungs Stufen für das-Steuerelement bereitstellen, indem Sie die-oder-Member-Funktionen überschreiben `VerifyUserLicense` `VerifyLicenseKey` . Innerhalb dieser Funktion können Sie anpassen, welche Eigenschaften oder Methoden für den Benutzer entsprechend der erkannten Lizenz Stufe verfügbar gemacht werden.
Sie können der Funktion auch Code hinzufügen `VerifyLicenseKey` , der eine benutzerdefinierte Methode bereitstellt, um den Benutzer darüber zu informieren, dass die Steuerelement Erstellung fehlgeschlagen ist In der `VerifyLicenseKey` Member-Funktion können Sie beispielsweise ein Meldungs Feld anzeigen, das besagt, dass das Steuerelement nicht initialisiert werden konnte und warum.
> [!NOTE]
> Eine andere Möglichkeit zum Anpassen der Überprüfung der ActiveX-Steuerelement Lizenz besteht darin, die Registrierungsdatenbank für einen bestimmten Registrierungsschlüssel zu überprüfen, anstatt zu aufrufen `AfxVerifyLicFile` . Ein Beispiel für die Standard Implementierung finden Sie im Abschnitt [Implementierungs Dateiänderungen](#_core_implementation_file_modifications) in diesem Artikel.
Weitere Informationen zu Lizenzierungs Problemen finden Sie unter Lizenzierungsprobleme beim [Aktualisieren eines vorhandenen ActiveX-Steuer](upgrading-an-existing-activex-control.md)Elements.
## <a name="see-also"></a>Siehe auch
[MFC-ActiveX-Steuerelemente](mfc-activex-controls.md)<br/>
[MFC-ActiveX-Steuerelement-Assistent](reference/mfc-activex-control-wizard.md)
| 109.606299 | 983 | 0.836422 | deu_Latn | 0.993475 |
f4c4086b610ac3d919f591eae0815e0fa7125796 | 1,543 | md | Markdown | dev-itpro/developer/properties/devenv-defaultlayout-property.md | loreleishannonmsft/dynamics365smb-devitpro-pb | f1a47084439835bbef2fb42d9f79364f586f2f7d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | dev-itpro/developer/properties/devenv-defaultlayout-property.md | loreleishannonmsft/dynamics365smb-devitpro-pb | f1a47084439835bbef2fb42d9f79364f586f2f7d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | dev-itpro/developer/properties/devenv-defaultlayout-property.md | loreleishannonmsft/dynamics365smb-devitpro-pb | f1a47084439835bbef2fb42d9f79364f586f2f7d | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-10-12T09:28:55.000Z | 2022-03-10T19:18:40.000Z | ---
title: "DefaultLayout Property"
ms.custom: na
ms.date: 04/01/2019
ms.reviewer: na
ms.suite: na
ms.tgt_pltfrm: na
ms.topic: article
ms.service: "dynamics365-business-central"
ms.assetid: b2f560c0-bda3-467e-8e81-50cdf8e64ed5
caps.latest.revision: 3
author: SusanneWindfeldPedersen
---
# DefaultLayout Property
Specifies whether the report uses the built-in RDLC or Word report layout by default.
## Applies to
- Reports
## Property Value
- **RDLC** - specifies the built-in RDLC layout as the default layout.
- **Word** - specifies the built-in Word layout as the default layout.
## Syntax
```
DefaultLayout = Word;
```
## Remarks
A report object can include a built-in layout of either an RDLC type, Word type, or both. When you set the property to a type, then that layout type is used by default to view, save and print a report. Users can change a report to use another layout from the [!INCLUDE[d365fin_long_md](../includes/d365fin_long_md.md)] client.
<!--
For more information, see [Built-in and Custom Report Layouts](Designing-Report-Layouts-from-the-Microsoft-Dynamics-NAV-Development-Environment.md#BuiltinCustomLayouts).
-->
## See Also
[Report Object](../devenv-report-object.md)
<!--
[Designing Report Layouts from the Microsoft Dynamics NAV Development Environment](Designing-Report-Layouts-from-the-Microsoft-Dynamics-NAV-Development-Environment.md)
[How to. Specify the Default Built-in Report Layout](How-to.-Specify-the-Default-Built-in-Report-Layout.md)
--> | 34.288889 | 329 | 0.738172 | eng_Latn | 0.879007 |
f4c43306a0e8010269b583f16bd5c2b63f768877 | 237 | md | Markdown | content/lua/rule/allyfactionminimum.md | xackery/eqquestapi | e3bb4d58651c7c2bb1ced94deb59115946eed3c5 | [
"MIT"
] | null | null | null | content/lua/rule/allyfactionminimum.md | xackery/eqquestapi | e3bb4d58651c7c2bb1ced94deb59115946eed3c5 | [
"MIT"
] | 1 | 2020-09-08T17:21:08.000Z | 2020-09-08T17:21:08.000Z | content/lua/rule/allyfactionminimum.md | xackery/eqquestapi | e3bb4d58651c7c2bb1ced94deb59115946eed3c5 | [
"MIT"
] | 1 | 2020-08-29T00:49:26.000Z | 2020-08-29T00:49:26.000Z | ---
title: Rule AllyFactionMinimum
searchTitle: Lua Rule AllyFactionMinimum
weight: 1
hidden: true
menuTitle: Rule AllyFactionMinimum
---
## AllyFactionMinimum
This represents a AllyFactionMinimum Rule
```lua
Rule.AllyFactionMinimum
``` | 18.230769 | 41 | 0.805907 | kor_Hang | 0.280827 |
f4c44b7d51189162e2371fe7dfeefbdde92b88b9 | 16 | md | Markdown | README.md | onerca/whisk | a0a355a20d3342c4c2911508b2d3c4ae72b00973 | [
"Apache-2.0"
] | null | null | null | README.md | onerca/whisk | a0a355a20d3342c4c2911508b2d3c4ae72b00973 | [
"Apache-2.0"
] | null | null | null | README.md | onerca/whisk | a0a355a20d3342c4c2911508b2d3c4ae72b00973 | [
"Apache-2.0"
] | null | null | null | # whisk
我还是个小孩子
| 5.333333 | 7 | 0.75 | eng_Latn | 0.859726 |
f4c45bbd961f3602be32191b20353bc4b9153709 | 1,280 | md | Markdown | docs/standard/data/xml/converting-dotnet-types-to-strings.md | heeae0502/docs.ko-kr | af81ad5ed25d3b32c2420f59ced0754daa861f43 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/data/xml/converting-dotnet-types-to-strings.md | heeae0502/docs.ko-kr | af81ad5ed25d3b32c2420f59ced0754daa861f43 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/data/xml/converting-dotnet-types-to-strings.md | heeae0502/docs.ko-kr | af81ad5ed25d3b32c2420f59ced0754daa861f43 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: .NET Framework 형식을 문자열로 변환
ms.date: 03/30/2017
ms.technology: dotnet-standard
ms.assetid: dc2e2b65-f623-4dc3-938b-d2a054d6832c
ms.openlocfilehash: a63e0175f6660967eb4aa678c6731d353e44e2d5
ms.sourcegitcommit: 5f236cd78cf09593c8945a7d753e0850e96a0b80
ms.translationtype: MT
ms.contentlocale: ko-KR
ms.lasthandoff: 01/07/2020
ms.locfileid: "75711079"
---
# <a name="converting-net-framework-types-to-strings"></a>.NET Framework 형식을 문자열로 변환
.NET Framework 형식을 문자열로 변환하려면 **ToString** 메서드를 사용합니다. **ToString** 메서드는 전달된 형식의 문자열 표현을 반환합니다. 다음 표에서는 XSD(XML 스키마) 사양에 대응하는 형식으로 문자열을 반환하는 .NET Framework 형식의 목록을 보여 줍니다.
|.NET Framework 형식|반환된 문자열 형식|
|-------------------------|--------------------------|
|Boolean|"true", "false"|
|Single.PositiveInfinity|"INF"|
|Single.NegativeInfinity|"-INF"|
|Double.PositiveInfinity|"INF"|
|Double.NegativeInfinity|"-INF"|
|DateTime|형식은 "yyyy-MM-ddTHH:mm:sszzzzzz" 및 해당 하위 집합입니다.|
|Timespan|형식은 PnYnMnTnHnMnS입니다. 예를 들어, `P2Y10M15DT10H30M20S`는 2년 10개월 15일 10시간 30분 20초의 지속 시간을 나타냅니다.|
## <a name="see-also"></a>참조
- [XML 데이터 형식 변환](../../../../docs/standard/data/xml/conversion-of-xml-data-types.md)
- [문자열을 .NET Framework 데이터 형식으로 변환](../../../../docs/standard/data/xml/converting-strings-to-dotnet-data-types.md)
| 42.666667 | 173 | 0.703125 | kor_Hang | 0.97851 |
f4c494a31388e512263932680a1c630c4ae3286d | 3,736 | md | Markdown | reference/7.1/Microsoft.PowerShell.Utility/Write-Debug.md | tylerl0706/PowerShell-Docs | 79e8ad80344685339ff2198e054e19cf1be6e0cd | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-11-17T07:32:23.000Z | 2021-11-17T07:32:23.000Z | reference/7.1/Microsoft.PowerShell.Utility/Write-Debug.md | tylerl0706/PowerShell-Docs | 79e8ad80344685339ff2198e054e19cf1be6e0cd | [
"CC-BY-4.0",
"MIT"
] | null | null | null | reference/7.1/Microsoft.PowerShell.Utility/Write-Debug.md | tylerl0706/PowerShell-Docs | 79e8ad80344685339ff2198e054e19cf1be6e0cd | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-04-06T23:17:28.000Z | 2020-04-06T23:17:28.000Z | ---
external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml
keywords: powershell,cmdlet
locale: en-us
Module Name: Microsoft.PowerShell.Utility
ms.date: 04/04/2019
online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/write-debug?view=powershell-7.x&WT.mc_id=ps-gethelp
schema: 2.0.0
title: Write-Debug
---
# Write-Debug
## SYNOPSIS
Writes a debug message to the console.
## SYNTAX
```
Write-Debug [-Message] <String> [<CommonParameters>]
```
## DESCRIPTION
The `Write-Debug` cmdlet writes debug messages to the console from a script or command.
By default, debug messages are not displayed in the console, but you can display them by using the
**Debug** parameter or the `$DebugPreference` variable.
## EXAMPLES
### Example 1: Understand $DebugPreference
This example writes a debug message.
```powershell
Write-Debug "Cannot open file."
```
The default value of `$DebugPreference` is **SilentlyContinue**. Therefore, the message is not
displayed in the console.
### Example 2: Change the value of $DebugPreference
This example shows the effect of changing the value of the `$DebugPreference` variable. First, we
display the current value of `$DebugPreference` and attempt to write a debug message. Then we change
the value of `$DebugPreference` to **Continue**, which allows debug messages to be displayed.
```
PS> $DebugPreference
SilentlyContinue
PS> Write-Debug "Cannot open file."
PS>
PS> $DebugPreference = "Continue"
PS> Write-Debug "Cannot open file."
DEBUG: Cannot open file.
```
For more information about `$DebugPreference`, see [about_Preference_Variables](../Microsoft.PowerShell.Core/About/about_Preference_Variables.md).
### Example 3: Use the Debug parameter to override $DebugPreference
The `Test-Debug` function writes the value of the `$DebugPreference` variable to the PowerShell host
and to the Debug stream. In this example, we use the **Debug** parameter to override the
`$DebugPreference` value.
```powershell
function Test-Debug {
[CmdletBinding()]
param()
Write-Debug ('$DebugPreference is ' + $DebugPreference)
Write-Host ('$DebugPreference is ' + $DebugPreference)
}
```
```
PS> Test-Debug
$DebugPreference is SilentlyContinue
PS> Test-Debug -Debug
DEBUG: $DebugPreference is Continue
$DebugPreference is Continue
PS> $DebugPreference
SilentlyContinue
```
Notice that the value of `$DebugPreference` changes when you use the **Debug** parameter. This
change only affects the scope of the function. The value is not affected outside the function.
For more information about the **Debug** common parameter, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
## PARAMETERS
### -Message
Specifies the debug message to send to the console.
```yaml
Type: String
Parameter Sets: (All)
Aliases: Msg
Required: True
Position: 0
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: False
```
### CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
-InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose,
-WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
## INPUTS
### System.String
You can pipe a string that contains a debug message to `Write-Debug`.
## OUTPUTS
### None
`Write-Debug` only writes to the debug stream. It does not return any output.
## NOTES
## RELATED LINKS
[Write-Error](Write-Error.md)
[Write-Host](Write-Host.md)
[Write-Output](Write-Output.md)
[Write-Progress](Write-Progress.md)
[Write-Verbose](Write-Verbose.md)
[Write-Warning](Write-Warning.md)
| 25.944444 | 146 | 0.758565 | eng_Latn | 0.661265 |
f4c4ce17c6389f004e3b4935c14f10fece75a74c | 236,906 | md | Markdown | packages/portal/CHANGELOG.md | Synerise/synerise-design | daaf50ad62081d7ad77eb4ac65100173df77c731 | [
"MIT"
] | 93 | 2019-09-20T10:35:03.000Z | 2022-03-29T21:59:12.000Z | packages/portal/CHANGELOG.md | Synerise/synerise-design | daaf50ad62081d7ad77eb4ac65100173df77c731 | [
"MIT"
] | 17 | 2020-03-11T14:20:33.000Z | 2022-03-22T18:30:28.000Z | packages/portal/CHANGELOG.md | Synerise/synerise-design | daaf50ad62081d7ad77eb4ac65100173df77c731 | [
"MIT"
] | 23 | 2019-09-20T08:57:51.000Z | 2022-02-22T19:24:02.000Z | # Change Log
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
# [0.140.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.140.0) (2021-10-26)
### Bug Fixes
* **alert:** add props to set duration of close toast ([03f0f50](https://github.com/synerise/synerise-design/commit/03f0f502f633986a26bd4691624767de41f56e14))
* **alert:** add props to set duration of close toast ([2be2b9a](https://github.com/synerise/synerise-design/commit/2be2b9afbeacdcb114659f42c7bb8ac231c8f98c))
* **alert:** fix button and padding ([0152d97](https://github.com/synerise/synerise-design/commit/0152d973610af603ed7e59ab6c66de4f1d064a9f))
* **alert:** fix button and padding ([f4f8ab4](https://github.com/synerise/synerise-design/commit/f4f8ab48b937338e989af2e68cd9e1f01e31b3e4))
* **alert:** fix component ([210baa2](https://github.com/synerise/synerise-design/commit/210baa238e131bf4b2ca430e451479ea25c88f9b))
* **alert:** fix component ([fb7b928](https://github.com/synerise/synerise-design/commit/fb7b92844fe958cddc10bbe01fa1e3f3378471d6))
* **alert:** fix props ([ab9b3f1](https://github.com/synerise/synerise-design/commit/ab9b3f1350d4349cd86c6fcb0eca2a2b4fdb92de))
* **alert:** fix props ([d262657](https://github.com/synerise/synerise-design/commit/d262657b8f66ef31cdc0b9abde6b6321048b050a))
* **alert:** fix styles and add props ([0d829d2](https://github.com/synerise/synerise-design/commit/0d829d26111780ee006cd26c3c5dc76962ae8c99))
* **alert:** fix styles and add props ([b555b8a](https://github.com/synerise/synerise-design/commit/b555b8af547c632fca82d8024514561f20636dd6))
* **alert:** new component broadcast-bar ([0525d34](https://github.com/synerise/synerise-design/commit/0525d345c2aefc097db832b8fd2693dca3902ea5))
* **alert:** new component Toast ([f1ed36b](https://github.com/synerise/synerise-design/commit/f1ed36b88d98ef81e487eb6b8418ea6bb4be6a3d))
* **alert:** new component Toast ([665f9dc](https://github.com/synerise/synerise-design/commit/665f9dcc2ea5812ef7ef3a5fa4fafd6590c78ecb))
* **card-tabs:** add colorDot and fix props ([e779c6a](https://github.com/synerise/synerise-design/commit/e779c6a433bbd7755171afc42a63e8e3410e8a82))
* **card-tabs:** add colorDot and fix props ([82d8b91](https://github.com/synerise/synerise-design/commit/82d8b91e10e8bd393c53aacb45e7156ce77457db))
* **card-tabs:** fix knobs and styles in inline edit ([ae7bb6a](https://github.com/synerise/synerise-design/commit/ae7bb6a82a88845bb540603cc580db2111a785c3))
* **card-tabs:** fix knobs and styles in inline edit ([7eea4a2](https://github.com/synerise/synerise-design/commit/7eea4a2743daa396111a2d4bce8576183cd6c6ab))
* **card-tabs:** fix single card-tabs to be draggable ([88721cf](https://github.com/synerise/synerise-design/commit/88721cfc0de3060af49ed18921ef882f7c765cd0))
* **card-tabs:** fix single card-tabs to be draggable ([9aa7c99](https://github.com/synerise/synerise-design/commit/9aa7c9926b3b203ba2f16285071c7a333f6f7bff))
* **code-snippet:** fix styles and change structure ([51fce52](https://github.com/synerise/synerise-design/commit/51fce520b33c531428e3f64ed42b3a6641fc43e7))
* **code-snippet:** fix styles and change structure ([041643d](https://github.com/synerise/synerise-design/commit/041643d6643ac901fa6a499756b91bf02c8c4116))
### Features
* **code-snippet:** add new component code-snippet ([d797539](https://github.com/synerise/synerise-design/commit/d797539ff42a7ccdecee7f8ae3e033a3d787e847))
* **code-snippet:** add new component code-snippet ([5cbd721](https://github.com/synerise/synerise-design/commit/5cbd721e67a30136cd8d4e26fb97c66a498ae511))
* **code-snippet:** add own style files to codeTypes ([8b33a9d](https://github.com/synerise/synerise-design/commit/8b33a9d1caa8021c3d7530b6c57cc8420e1cae4c))
* **code-snippet:** add own style files to codeTypes ([eb8a9a7](https://github.com/synerise/synerise-design/commit/eb8a9a70f92ba504e5559a67ac87720f9c1f3de3))
* **navbar:** addalert notification suffix ([127a980](https://github.com/synerise/synerise-design/commit/127a980410f99b876c4eafc9e44f8804281eea33))
* **navbar:** addalert notification suffix ([afc0397](https://github.com/synerise/synerise-design/commit/afc0397b17c5167d9fce3875e27fd5f05700ca2e))
* **tags:** add extra prop asPill ([bc21290](https://github.com/synerise/synerise-design/commit/bc21290803c06a0b9dbb274d1a5a9598db07fe13))
* **tags:** add extra prop asPill ([fcc9b56](https://github.com/synerise/synerise-design/commit/fcc9b565c75907f737eca5574b6bd9b3cfdb9c32))
# [0.139.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.139.0) (2021-10-19)
### Bug Fixes
* **alert:** add props to set duration of close toast ([03f0f50](https://github.com/synerise/synerise-design/commit/03f0f502f633986a26bd4691624767de41f56e14))
* **alert:** add props to set duration of close toast ([2be2b9a](https://github.com/synerise/synerise-design/commit/2be2b9afbeacdcb114659f42c7bb8ac231c8f98c))
* **alert:** fix button and padding ([0152d97](https://github.com/synerise/synerise-design/commit/0152d973610af603ed7e59ab6c66de4f1d064a9f))
* **alert:** fix button and padding ([f4f8ab4](https://github.com/synerise/synerise-design/commit/f4f8ab48b937338e989af2e68cd9e1f01e31b3e4))
* **alert:** fix component ([210baa2](https://github.com/synerise/synerise-design/commit/210baa238e131bf4b2ca430e451479ea25c88f9b))
* **alert:** fix component ([fb7b928](https://github.com/synerise/synerise-design/commit/fb7b92844fe958cddc10bbe01fa1e3f3378471d6))
* **alert:** fix props ([ab9b3f1](https://github.com/synerise/synerise-design/commit/ab9b3f1350d4349cd86c6fcb0eca2a2b4fdb92de))
* **alert:** fix props ([d262657](https://github.com/synerise/synerise-design/commit/d262657b8f66ef31cdc0b9abde6b6321048b050a))
* **alert:** fix styles and add props ([0d829d2](https://github.com/synerise/synerise-design/commit/0d829d26111780ee006cd26c3c5dc76962ae8c99))
* **alert:** fix styles and add props ([b555b8a](https://github.com/synerise/synerise-design/commit/b555b8af547c632fca82d8024514561f20636dd6))
* **alert:** new component broadcast-bar ([0525d34](https://github.com/synerise/synerise-design/commit/0525d345c2aefc097db832b8fd2693dca3902ea5))
* **alert:** new component Toast ([f1ed36b](https://github.com/synerise/synerise-design/commit/f1ed36b88d98ef81e487eb6b8418ea6bb4be6a3d))
* **alert:** new component Toast ([665f9dc](https://github.com/synerise/synerise-design/commit/665f9dcc2ea5812ef7ef3a5fa4fafd6590c78ecb))
* **card-tabs:** add colorDot and fix props ([e779c6a](https://github.com/synerise/synerise-design/commit/e779c6a433bbd7755171afc42a63e8e3410e8a82))
* **card-tabs:** add colorDot and fix props ([82d8b91](https://github.com/synerise/synerise-design/commit/82d8b91e10e8bd393c53aacb45e7156ce77457db))
* **card-tabs:** fix knobs and styles in inline edit ([ae7bb6a](https://github.com/synerise/synerise-design/commit/ae7bb6a82a88845bb540603cc580db2111a785c3))
* **card-tabs:** fix knobs and styles in inline edit ([7eea4a2](https://github.com/synerise/synerise-design/commit/7eea4a2743daa396111a2d4bce8576183cd6c6ab))
* **card-tabs:** fix single card-tabs to be draggable ([88721cf](https://github.com/synerise/synerise-design/commit/88721cfc0de3060af49ed18921ef882f7c765cd0))
* **card-tabs:** fix single card-tabs to be draggable ([9aa7c99](https://github.com/synerise/synerise-design/commit/9aa7c9926b3b203ba2f16285071c7a333f6f7bff))
* **code-snippet:** fix styles and change structure ([51fce52](https://github.com/synerise/synerise-design/commit/51fce520b33c531428e3f64ed42b3a6641fc43e7))
* **code-snippet:** fix styles and change structure ([041643d](https://github.com/synerise/synerise-design/commit/041643d6643ac901fa6a499756b91bf02c8c4116))
### Features
* **code-snippet:** add new component code-snippet ([d797539](https://github.com/synerise/synerise-design/commit/d797539ff42a7ccdecee7f8ae3e033a3d787e847))
* **code-snippet:** add new component code-snippet ([5cbd721](https://github.com/synerise/synerise-design/commit/5cbd721e67a30136cd8d4e26fb97c66a498ae511))
* **code-snippet:** add own style files to codeTypes ([8b33a9d](https://github.com/synerise/synerise-design/commit/8b33a9d1caa8021c3d7530b6c57cc8420e1cae4c))
* **code-snippet:** add own style files to codeTypes ([eb8a9a7](https://github.com/synerise/synerise-design/commit/eb8a9a70f92ba504e5559a67ac87720f9c1f3de3))
* **navbar:** addalert notification suffix ([127a980](https://github.com/synerise/synerise-design/commit/127a980410f99b876c4eafc9e44f8804281eea33))
* **navbar:** addalert notification suffix ([afc0397](https://github.com/synerise/synerise-design/commit/afc0397b17c5167d9fce3875e27fd5f05700ca2e))
* **tags:** add extra prop asPill ([bc21290](https://github.com/synerise/synerise-design/commit/bc21290803c06a0b9dbb274d1a5a9598db07fe13))
* **tags:** add extra prop asPill ([fcc9b56](https://github.com/synerise/synerise-design/commit/fcc9b565c75907f737eca5574b6bd9b3cfdb9c32))
# [0.138.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.138.0) (2021-10-19)
### Bug Fixes
* **condition:** performance improvements ([c3f54cf](https://github.com/synerise/synerise-design/commit/c3f54cffcf2cfcb58da8686b88800fffed5e26ce))
### Features
* **context-selector:** adds infinitescroll and virtualization ([dc8592e](https://github.com/synerise/synerise-design/commit/dc8592e42c161502c44527cbb4a80a25670e95a9))
* **context-selector:** adds virtualization ([9dba88c](https://github.com/synerise/synerise-design/commit/9dba88c9598a7a22977a06dba1813f687f714161))
* **context-selector:** optimization improvements ([28feae6](https://github.com/synerise/synerise-design/commit/28feae6ebc0e07c37c6c83f5197e80ea7c59347f))
* **context-selector:** update example in storybook ([1997229](https://github.com/synerise/synerise-design/commit/19972291b641ce3e0ddc6ba5a641f4413224f97b))
* **docs:** update stories ([d1b95c0](https://github.com/synerise/synerise-design/commit/d1b95c04637df73b092728203ffd7fd973c20e64))
* **factors:** adds infinite scroll & virtualization ([1d7b818](https://github.com/synerise/synerise-design/commit/1d7b818ae087e2bf10285d0db5c47d13fe2d5ec7))
# [0.137.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.137.0) (2021-09-30)
### Features
* **condition:** adds autoclearCondition props ([58111ea](https://github.com/synerise/synerise-design/commit/58111ea895ad4b77eafc82257d263820f7b3cf39))
# [0.136.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.136.0) (2021-09-21)
### Bug Fixes
* **alert:** fix prop ([74c6c46](https://github.com/synerise/synerise-design/commit/74c6c4605f75af6855fba5b83081fa0823b289b0))
* **alert:** fix props ([bf938e9](https://github.com/synerise/synerise-design/commit/bf938e9e15ec12b70e2eddb9827cc66fb169c072))
* **alert:** fix props and tests ([2639ac3](https://github.com/synerise/synerise-design/commit/2639ac3e775a8879722e1fbaf137fb0d0c07a0e9))
* **alert:** two new components IconAlert and InlineAlert ([7e28f50](https://github.com/synerise/synerise-design/commit/7e28f50cb5b5d5c35d10b7c196d3cb36b112df15))
* **button:** delete component but add it to stories ([5b6e88d](https://github.com/synerise/synerise-design/commit/5b6e88d84c500908037b2ff45eb328deca33e08e))
* **popconfirm:** add new buttons and closeIcon ([4201b84](https://github.com/synerise/synerise-design/commit/4201b84de4ac551afe84feeac7805238da517535))
* **popconfirm:** fix styles ([eba797b](https://github.com/synerise/synerise-design/commit/eba797ba6f49810af127d204b04a5ecb44844fc6))
* **sidebar:** add new component SidebarWithButton ([2a26939](https://github.com/synerise/synerise-design/commit/2a26939ce8ef5866fceaf9050f4eef71f0eefa2b))
* **sidebar:** add tests and add to readme informations ([0652fad](https://github.com/synerise/synerise-design/commit/0652fad170c662782002731d498fef48d107f439))
* **sidebar:** add tests and add to readme informations ([dcda0b1](https://github.com/synerise/synerise-design/commit/dcda0b12ba35dba24cdf464266b01f7ea563c94e))
* **table:** add new columns ([76b3dcb](https://github.com/synerise/synerise-design/commit/76b3dcb07b545a04fb8b2c59b69bb643a146a79d))
* **table:** add width to columns ([2eb41e1](https://github.com/synerise/synerise-design/commit/2eb41e1234d9850773acf7c3ca292409f3536f8a))
* **table:** new table with fixed options ([6acbc6f](https://github.com/synerise/synerise-design/commit/6acbc6fabdb59ef40ec869fe058371759c088ae8))
### Features
* **toolbar-buttons:** add new component toolbar ([cd9a8da](https://github.com/synerise/synerise-design/commit/cd9a8dad1a2dc5ede118e0dd21016b637ca30a23))
* **treemenu:** current state ([281349b](https://github.com/synerise/synerise-design/commit/281349bd246f8ab696f3ec9b912d779944cdf82a))
* **treemenu:** STOR-673 new TreeMenu component ([c5f95fa](https://github.com/synerise/synerise-design/commit/c5f95fa3e196b546cf7232f8dd62179f87ce6e3c))
* **treemenu:** update stories ([89b3602](https://github.com/synerise/synerise-design/commit/89b3602d37589135a830f355f2850e83b87a5c86))
## [0.135.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.135.1) (2021-07-30)
**Note:** Version bump only for package portal
# [0.135.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.135.0) (2021-07-30)
### Bug Fixes
* **alert:** add prop for text ([d3037c5](https://github.com/synerise/synerise-design/commit/d3037c5949e4b8c9ff255354c357412cfcdac6d9))
* **alert:** fix styles and add new types of styles ([4f30690](https://github.com/synerise/synerise-design/commit/4f3069095fc23b79240dc1c493d5fb0db3e1afc1))
* **alert:** fix styles and add props to set custom colors ([a259c49](https://github.com/synerise/synerise-design/commit/a259c490fa676183492d2c41ac8bbaad17874910))
* **alert:** fix styles and component unordered list ([da76a77](https://github.com/synerise/synerise-design/commit/da76a778123563f8797f6b5a433a0bcd9c4f34f9))
* **alert:** new components section message and semantic colors ([b111358](https://github.com/synerise/synerise-design/commit/b111358cc22ecea0b42b333635edbbf10e83f34d))
* **alert:** update documents and tests ([59aa598](https://github.com/synerise/synerise-design/commit/59aa598f2947827578b879c5127c66faca4d5609))
* **avatar:** fix styles and prop in skeleton avatar ([317845e](https://github.com/synerise/synerise-design/commit/317845ed1b044fb9b5cf4e613e7f8baec2d1a247))
* **button:** fix styles ([86b5911](https://github.com/synerise/synerise-design/commit/86b591146208ac1eccaecdeedd85c31dafef43f9))
* **button-group:** add validate state to split-buttons ([b112c6c](https://github.com/synerise/synerise-design/commit/b112c6ce0f2e702095fb15f4b6b9a917b2790ffd))
### Features
* **card:** add ability to define static content ([78b04b6](https://github.com/synerise/synerise-design/commit/78b04b6105e0cb444291ddb8a5e1b9aa189f2a91))
# [0.134.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.134.0) (2021-07-19)
### Bug Fixes
* move theme settings to addons.ts file from config.ts file ([0d77fdf](https://github.com/synerise/synerise-design/commit/0d77fdf47d5f4fb254758fd69b334ffcc5a5595a))
* **avatar:** add new components userAvatar and objectAvatar ([da91d26](https://github.com/synerise/synerise-design/commit/da91d2669d6c541c0e0f7c62aab88fa012899783))
* **button:** add prop in table-skeleton ([82310e9](https://github.com/synerise/synerise-design/commit/82310e96c4f8884015b95722d2c2c0c796d13bba))
* **button:** add skeleten button ([e4f169e](https://github.com/synerise/synerise-design/commit/e4f169ed04b44360ed71ae49e2c9b8dfa920cc80))
* **checkbox:** add new component skeleton-checkbox ([118db79](https://github.com/synerise/synerise-design/commit/118db7969353b4a4666991bdd1c0870bd5f9a9b5))
* **checkbox:** fix name of skeleton-checkbox ([2e87bea](https://github.com/synerise/synerise-design/commit/2e87bea0fa94bcad603ca7d706be0b6e937a4374))
* **dropdown:** add new component skeletonDropdown ([4c5b057](https://github.com/synerise/synerise-design/commit/4c5b057eabd44a3159f7c78b46d8057ef7af8a9a))
* **dropdown:** fix skeletonDropdown ([2d5ad9c](https://github.com/synerise/synerise-design/commit/2d5ad9c9e29d0198f1c60abdc47654f67bbefe15))
* **dropdown:** fix styles of skeleton-dropdown ([bb78878](https://github.com/synerise/synerise-design/commit/bb78878ff2d3abe3f302d928297161589bb7ce76))
* **menu:** add skeleten menu ([e3c53ab](https://github.com/synerise/synerise-design/commit/e3c53abe59662a6a09314d33dc8865ed9128c081))
* **ordered-list:** add new component OrderedListSkeleton ([f214537](https://github.com/synerise/synerise-design/commit/f2145375b3c021528e3cbd3406405adda8cc2636))
* **ordered-list:** add new component OrderedListSkeleton ([723e671](https://github.com/synerise/synerise-design/commit/723e67158ac133073c5387ed104c39f87722aa5c))
* **ordered-list:** fix styles of skeleton-ordered-list ([6ec9be4](https://github.com/synerise/synerise-design/commit/6ec9be46681e59936e20ab13c4bb449f621adb01))
* **page-header:** add new component withSkeleton ([a948a38](https://github.com/synerise/synerise-design/commit/a948a381487e9c27481bc9b12b5269abab82e997))
* **page-header:** add prop in table-skeleton ([91ff994](https://github.com/synerise/synerise-design/commit/91ff9940eab83bea9650c2f51bbda62acb1721e0))
* **page-header:** fix page-header-skeleton ([1f69e14](https://github.com/synerise/synerise-design/commit/1f69e14ec4a0284e35c395de14d8b4c8e20c33fe))
* **skeleton:** change animation styles and update readme ([1076727](https://github.com/synerise/synerise-design/commit/1076727160834593c7c30ec3e1ce28f52d0ca076))
* **table:** add new component skeletonTable ([81e3010](https://github.com/synerise/synerise-design/commit/81e30100e8c64e4fad1cd2a2ee20a0bb16084983))
* **table:** add prop in table-skeleton ([9465e0a](https://github.com/synerise/synerise-design/commit/9465e0a2858750c8c8f2a1218965383679b7bc05))
* **table:** fix prop hideTitlePart ([a93ba88](https://github.com/synerise/synerise-design/commit/a93ba888da0554ebb76e80f142e1a7c13dcfabe2))
* **table:** fix skeletonTable ([370ff0d](https://github.com/synerise/synerise-design/commit/370ff0d115c69f0674c0eca1eef2aa3f90fa2714))
* **table:** fix styles of skeleton-table ([6719a2c](https://github.com/synerise/synerise-design/commit/6719a2c476177b390096bdd802d6b26979f5a6a3))
* **unordered-list:** fix names of components ([df68c17](https://github.com/synerise/synerise-design/commit/df68c177654da372f54b61443285d69727879b03))
### Features
* **skeleton:** add props to fix animation ([1b3b693](https://github.com/synerise/synerise-design/commit/1b3b6931e188e0c843075067a0c2a7f3c7d5f1ab))
* **skeleton:** add skeleton ([ad19b6d](https://github.com/synerise/synerise-design/commit/ad19b6d87a69e12384cf5a7203deee0fb3f08802))
* **skeleton:** add stories ([2c1baf9](https://github.com/synerise/synerise-design/commit/2c1baf9dc2b5eae0f0dff031f4efb451ee9ccf4b))
* **skeleton:** new component skeleton ([c1e0deb](https://github.com/synerise/synerise-design/commit/c1e0deb5952121232c7300468e8145b4a8fd1b12))
# [0.133.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.133.0) (2021-07-19)
### Features
* **typography:** updates stories ([ab7fc6b](https://github.com/synerise/synerise-design/commit/ab7fc6b9911e86f88147117288b89916a2744682))
## [0.132.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.132.1) (2021-07-08)
**Note:** Version bump only for package portal
# [0.132.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.132.0) (2021-06-28)
### Bug Fixes
* **dropdown:** advanced example real search ([fcc762c](https://github.com/synerise/synerise-design/commit/fcc762cbca62d3e1d1c0007d9a96d0d482a92025))
### Features
* **dropdown:** add advanced dropdown example with lazy-load and search debounce ([0a59a98](https://github.com/synerise/synerise-design/commit/0a59a98aaf26f9be04d0da86b11acb8cd1545a92))
## [0.131.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.131.1) (2021-06-21)
### Bug Fixes
* **serach:** fixes visibility of params when suggestions list is empty ([4d6983f](https://github.com/synerise/synerise-design/commit/4d6983f2970e3fe727ff6150dd467d8d612ddaf1))
# [0.131.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.131.0) (2021-06-16)
### Features
* **table:** add showBackToTopButton to infinite scroll in VirtualTable ([be3ce68](https://github.com/synerise/synerise-design/commit/be3ce68ba1cd2f03c8172270de06df3eb90f526f))
## [0.130.11](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.11) (2021-06-14)
### Bug Fixes
* **file-uploader:** add text/csv to upload on all type uploader ([f0bbc77](https://github.com/synerise/synerise-design/commit/f0bbc7758b93077bbaa5b4fd67c518a5b9cd277a))
* **file-uploader:** fix styles of components ([e561e68](https://github.com/synerise/synerise-design/commit/e561e68e2a81a673296aefac7c4124c14496b886))
* **file-uploader:** new componennts and fixes ([8774c65](https://github.com/synerise/synerise-design/commit/8774c65dd20828d7fae4c8583cdf038dbe81b4f5))
* **items-roll:** fixes ([3be1de1](https://github.com/synerise/synerise-design/commit/3be1de11967bf5fabcc4245362a8e3cf631ec2f1))
* **portal:** add new logo ([ab6dea6](https://github.com/synerise/synerise-design/commit/ab6dea682b457c75e457940ef0169f7f3f84ab97))
* **portal:** add new stories Welcome ([79b4b84](https://github.com/synerise/synerise-design/commit/79b4b84ea3241cf76ca736414ab6f115befc8dfa))
* **portal:** add order in and change names of folders in storybook ([feab7b3](https://github.com/synerise/synerise-design/commit/feab7b3dd72a3ee373ecc3553763d5753e45c09b))
* **portal:** change image sb_colloid.png ([5886c87](https://github.com/synerise/synerise-design/commit/5886c87ef00262c0f9cfccdedb9095863b130ff7))
* **portal:** change logo ([90ac763](https://github.com/synerise/synerise-design/commit/90ac76374f7b8c7c0b1d51d89079113f7ba352dd))
* **portal:** change logo ([50f3f7f](https://github.com/synerise/synerise-design/commit/50f3f7f4ae9cc668c583b7768c9ed2ef3dedfee9))
* **portal:** change stories to alphabetical order ([aba5b5e](https://github.com/synerise/synerise-design/commit/aba5b5e655a471051273646eb361e49d54464f56))
* **portal:** changed stories indentation level ([c592486](https://github.com/synerise/synerise-design/commit/c592486cecc42d1119c32a74744cf538db0d12ba))
* **portal:** update and change some styles in storybook ([04c5595](https://github.com/synerise/synerise-design/commit/04c5595d64174cbf187db3255292faaf8df3143a))
## [0.130.10](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.10) (2021-06-09)
### Bug Fixes
* **items-roll:** fixes ([dfe2481](https://github.com/synerise/synerise-design/commit/dfe2481f2aa7a0f37e4363a22a76657b2ad00346))
## [0.130.9](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.9) (2021-05-25)
### Bug Fixes
* **button:** removes focus styles for disabled button ([873791c](https://github.com/synerise/synerise-design/commit/873791cec04f207d2a0ccc71808f78a135ef7fe8))
* **file-uploader:** fix defualt uploader props and props in uploaderAvatar ([7e3c476](https://github.com/synerise/synerise-design/commit/7e3c476030c3206408b618a5391cbe697f9e9260))
* **file-uploader:** fix defualt uploader styles and popconfirm button ([d898d20](https://github.com/synerise/synerise-design/commit/d898d20055869864072e050a62d0e4ba664c5453))
* **file-uploader:** new component avatar uploader ([e240d95](https://github.com/synerise/synerise-design/commit/e240d95c39c77f72ade64047be96d5d68bed591c))
* **item-filter:** update items sorting by selected id ([41e432c](https://github.com/synerise/synerise-design/commit/41e432cd2dbb46c0d345192c21ee6958925995ef))
* **table:** sorted columns styles in VirtualTable ([fae8839](https://github.com/synerise/synerise-design/commit/fae88395bbaca4752af43f816fb30f8b0112d39d))
## [0.130.8](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.8) (2021-05-24)
### Bug Fixes
* **menu:** fixes Menu.Divider styles ([bcb1235](https://github.com/synerise/synerise-design/commit/bcb1235a18f1511e9077db0446f02b882695952f))
## [0.130.7](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.7) (2021-05-20)
**Note:** Version bump only for package portal
## [0.130.6](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.6) (2021-05-20)
**Note:** Version bump only for package portal
## [0.130.5](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.5) (2021-05-20)
### Bug Fixes
* **table:** fix table head cells text position ([ac99de9](https://github.com/synerise/synerise-design/commit/ac99de99929db17842f3d089963071397bc645ce))
## [0.130.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.4) (2021-05-20)
### Bug Fixes
* **date-picker:** add hideNow prop ([bceb5d1](https://github.com/synerise/synerise-design/commit/bceb5d15a5cb53a65cc9469d200eb5ec8e9e00ee))
## [0.130.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.3) (2021-05-14)
**Note:** Version bump only for package portal
## [0.130.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.2) (2021-05-14)
**Note:** Version bump only for package portal
## [0.130.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.1) (2021-05-14)
**Note:** Version bump only for package portal
# [0.130.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.130.0) (2021-05-10)
### Features
* **table:** add new sorting to GroupTable ([e6c897e](https://github.com/synerise/synerise-design/commit/e6c897ef10d5c7b9fa1d4e0fcb6edc32acc0f7e9))
## [0.129.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.129.1) (2021-05-06)
**Note:** Version bump only for package portal
# [0.129.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.129.0) (2021-05-06)
### Bug Fixes
* **file-uploader:** add icons to type of uploader file and fix styles ([b816f33](https://github.com/synerise/synerise-design/commit/b816f3394f073f5a89ba4ffe8c9ff871cb8f3743))
* **file-uploader:** change component styles and add new features ([b28f7b9](https://github.com/synerise/synerise-design/commit/b28f7b948e94b853048532b6a4d9aac2ad0e3aac))
* **file-uploader:** fix props ([1d281c8](https://github.com/synerise/synerise-design/commit/1d281c8853d2bba9927b3d7107ecceac9ca28b11))
* **file-uploader:** fix props text and add them ([570e338](https://github.com/synerise/synerise-design/commit/570e3380d88fad1716c06b2221447e34d6334032))
* **file-uploader:** fix props text and some styles ([b113d5f](https://github.com/synerise/synerise-design/commit/b113d5f39a26c01a9b6971db83113d1aa76e29ca))
* **file-uploader:** remove disabled text prop ([ae4d049](https://github.com/synerise/synerise-design/commit/ae4d0493b42f7baa364bad15f150e1d00227cecf))
* **portal:** change defaultViewport to 1920 ([bfd9c54](https://github.com/synerise/synerise-design/commit/bfd9c54b5df0be6a49808e9f07ee50436fe656c4))
* **portal:** delete defaultViewport ([f839f29](https://github.com/synerise/synerise-design/commit/f839f2906aae361357bc6bb57d751635c1c43d6c))
* **table:** fix table cell of avatar S ([f9fe976](https://github.com/synerise/synerise-design/commit/f9fe976991eeee13dd45920b0910be15f2108869))
### Features
* **alert:** add info type to InlineAlert ([3146c3a](https://github.com/synerise/synerise-design/commit/3146c3a2518ebdd764e78078dafaa941d066b434))
* **table:** add infinite scroll to VirtualTable ([bad0b27](https://github.com/synerise/synerise-design/commit/bad0b2788c8649320a775977b23cbe6b4822141e))
* **table:** add title with separator ([14f6426](https://github.com/synerise/synerise-design/commit/14f6426eca1d383478b9842bc25cedcd4e08e8a1))
# [0.128.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.128.0) (2021-04-22)
### Bug Fixes
* **alert:** add new component alertWithIcon ([7b1a6a1](https://github.com/synerise/synerise-design/commit/7b1a6a157d82028c48c5e3147e9270968243add1))
* **alert:** fix styles and remove unneeded knobs ([ba39d93](https://github.com/synerise/synerise-design/commit/ba39d9382a8d7a676c6acbfaf7ae719af07bf030))
* **empty-states:** fix names of sizes icons ([d18b905](https://github.com/synerise/synerise-design/commit/d18b9055a84211e8af494dc9e8026248d803971e))
* **empty-states:** fix styles, add all L and XL Icons ([89fe867](https://github.com/synerise/synerise-design/commit/89fe867cd1c1915fd2b72c99691034921280ce9b))
* **loader:** add new loaderSmallComplex and loaderMediumComplex ([bded682](https://github.com/synerise/synerise-design/commit/bded682eae3bad16717df66ef2d9d43d9f3eb694))
* **loader:** delete prop to set color and add to change font size ([7e9a23f](https://github.com/synerise/synerise-design/commit/7e9a23f205428cdd2c607c3bca3a484236423f5c))
* **loader:** fix name of knobs ([375731d](https://github.com/synerise/synerise-design/commit/375731d08383f511affa3dfb1a74669cb4b274f3))
* **menu:** add changes to show on hover checkboxes on childs ([eeaa329](https://github.com/synerise/synerise-design/commit/eeaa329604dc8ca91b2f3d0ff76da85e0447dbd6))
* **menu:** add hidden text in parent ([cb01deb](https://github.com/synerise/synerise-design/commit/cb01debb5a7cbe6081db60e237fe546ed1c8d21e))
* **menu:** add hidden text in parent and add inline edit ([a5732cb](https://github.com/synerise/synerise-design/commit/a5732cb444070aa3367de7dea1708f95d6799d07))
* **menu:** add option to set check children checked when parent is ([a9b2f47](https://github.com/synerise/synerise-design/commit/a9b2f4741f8dd1a12afbcfcfa00e009fb9508f5a))
* **menu:** add some styles and option to select all menu items active ([b93bd76](https://github.com/synerise/synerise-design/commit/b93bd76e5227982eee03e86afbe358b20ab9b982))
* **menu:** add some styles and to select all menu items with check ([800f612](https://github.com/synerise/synerise-design/commit/800f6128d762e595e4d4da5ad173e7a674223739))
* **menu:** change color of icon ([879cebd](https://github.com/synerise/synerise-design/commit/879cebd5459ebb8ee1961c91bfd096bb4e557e54))
* **menu:** change styles and add option to show checkbox on hover ([317a581](https://github.com/synerise/synerise-design/commit/317a581a87cd4f4b33875a1e38b033b7d7370afa))
* **menu:** change styles and move dropdown ([9a84e04](https://github.com/synerise/synerise-design/commit/9a84e04e9e4b46747650f33848a29789aa660cff))
* **menu:** new component accordion-menu ([8ae017d](https://github.com/synerise/synerise-design/commit/8ae017d947b78277665b3afb1b9a47015b7c9337))
* **portal:** fix categories in tables ([e15faa1](https://github.com/synerise/synerise-design/commit/e15faa160b9533ef7199ed5f57f98570e8e72035))
* **portal:** labels in ColumnManager ([4e19b65](https://github.com/synerise/synerise-design/commit/4e19b6570b640111f8fa812663cd850cfb339260))
* **portal:** names in story ([ba6ad2f](https://github.com/synerise/synerise-design/commit/ba6ad2f3440d9bf7f8cfa07dc5b5a90e11b6cef1))
* **portal:** STOR-694 fix views bugs ([45ed60a](https://github.com/synerise/synerise-design/commit/45ed60ae230a7957e9d3f2216c27d23e256eda70))
* **portal:** STOR-694 update stories ([bb542b2](https://github.com/synerise/synerise-design/commit/bb542b2e1f9e28aadd06bced0eac6e1cc99d5240))
* **portal:** table stories bugs ([0d9de62](https://github.com/synerise/synerise-design/commit/0d9de62a771187ecbfaa7cc935f1bf4b04a5238a))
* **table:** fix grouped table story ([2492b16](https://github.com/synerise/synerise-design/commit/2492b160000b8fcd3fe019880f5939f4ba38ad4a))
* **tagslist:** change name in item ([f503ad8](https://github.com/synerise/synerise-design/commit/f503ad8e3c48d46a27cb0163a938e6c2c594f745))
### Features
* **dropdown:** set default open trigger to click ([59b9d8f](https://github.com/synerise/synerise-design/commit/59b9d8f51a4fb6beb4062f4f526bf209a2b02e85))
* **empty-states:** new component empty-states ([02a89bf](https://github.com/synerise/synerise-design/commit/02a89bfac159b912d9b84d318510088414b2b9ca))
* **footer:** new component footer ([6c11dd3](https://github.com/synerise/synerise-design/commit/6c11dd3b24f7fe634367d848c3310b9998ea37da))
* **logic:** true as default matching value ([bf39b4b](https://github.com/synerise/synerise-design/commit/bf39b4b619ec1392c293cb63f12dc9bdd3e2cb18))
## [0.127.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.127.3) (2021-04-07)
### Bug Fixes
* **table:** set sort menu width ([0e26464](https://github.com/synerise/synerise-design/commit/0e26464085a6c06d7d30fa8ea455b75e9acd4f52))
## [0.127.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.127.2) (2021-03-29)
**Note:** Version bump only for package portal
## [0.127.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.127.1) (2021-03-24)
**Note:** Version bump only for package portal
# [0.127.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.127.0) (2021-03-22)
### Features
* **portal:** STOR-698 implement new avatar api ([634faba](https://github.com/synerise/synerise-design/commit/634faba949f967170086d49cf540fc8bcefd8e9a))
# [0.126.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.126.0) (2021-03-19)
### Bug Fixes
* resolved conflicts ([196f535](https://github.com/synerise/synerise-design/commit/196f535303c35cd69074422050737b44c40ca59f))
* **table:** fix dropdown in select in table ([844a72e](https://github.com/synerise/synerise-design/commit/844a72e89d07377f68d1c0c7c84b16353c107018))
### Features
* **date-range-picker:** added custom units handling ([d3271e3](https://github.com/synerise/synerise-design/commit/d3271e3b7d3ac4aafd881a6b5cce04901fd38e72))
* **icon:** merge to dev ([f248315](https://github.com/synerise/synerise-design/commit/f248315c25501d3c81c1c6bbb0f221eec7897590))
# [0.125.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.125.0) (2021-03-16)
### Features
* **icon:** replace dashboard icon ([d17b051](https://github.com/synerise/synerise-design/commit/d17b0518c1facd9df8db2096d54fe6a85e9c0ea9))
# [0.124.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.124.0) (2021-03-16)
### Bug Fixes
* **avatar:** add 'auto' color to user and object avatar ([8d9bf33](https://github.com/synerise/synerise-design/commit/8d9bf3354ac0b7affdcd84db91ae5ba50fdef0d4))
* **avatar:** small size in Desciption -> onModal ([b42abd1](https://github.com/synerise/synerise-design/commit/b42abd176408ea6d42b08534eb03286af09c3300))
* **date-range-picker:** remove internal state inside new filters ([8dcf42f](https://github.com/synerise/synerise-design/commit/8dcf42f264e426cf4cf418020808ae71de5d9114))
* **portal:** avatars in icon picker ([a75a42b](https://github.com/synerise/synerise-design/commit/a75a42bca79c93d541a575e31ac29821060350a3))
* **portal:** move tooltipProps to tooltip prop ([ef9893a](https://github.com/synerise/synerise-design/commit/ef9893a264a6c597a6106ea3e6762c0e3f8cd7d1))
* **portal:** new avatar images ([4968b20](https://github.com/synerise/synerise-design/commit/4968b204df71b7389452d51423a96d1643092aeb))
* **portal:** remove large from avatar label cell ([5b593aa](https://github.com/synerise/synerise-design/commit/5b593aaeb7cb2486dbce7af2ebefa2ee73ef4ab9))
* **portal:** remove story that shouldn't be there ([a3eb460](https://github.com/synerise/synerise-design/commit/a3eb46053bdd11cc11a89ec84033b3b45990fb63))
* **portal:** small avatar story fixes ([a4c8aad](https://github.com/synerise/synerise-design/commit/a4c8aadedb91adbb2893d837c88f54a30deb6612))
* **portal:** STOR-698 fix stories ([f2ad388](https://github.com/synerise/synerise-design/commit/f2ad3880d202c96d2c2979ba0734b5daf312ccc3))
* **portal:** use new avatars in stories ([ef3bc3f](https://github.com/synerise/synerise-design/commit/ef3bc3f16516f218c6c5624b75e5f61912fe2656))
* **portal:** use new Avatars in Table ([e76441f](https://github.com/synerise/synerise-design/commit/e76441fe9789a604d86038b522176115d5b4540d))
### Features
* **avatar:** STOR-700 change avatar sizes + add UserAvatar ([a1bb5b4](https://github.com/synerise/synerise-design/commit/a1bb5b43debc5c9b152d5d2303ef5ba29591f3b9))
* **date-range-picker:** handle timeFormat in new filter ([70a864d](https://github.com/synerise/synerise-design/commit/70a864de0b3671dce933a3e539d3f64cd65d84c8))
* **date-range-picker:** range filter selection modes ([29c2ce3](https://github.com/synerise/synerise-design/commit/29c2ce3d0473c4e17d9726bfe7e4ea3930fc8697))
* **time-window:** added timeWindow component ([4eb7b9b](https://github.com/synerise/synerise-design/commit/4eb7b9b6922702bc3a80eef878d80de7a908730d))
# [0.123.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.123.0) (2021-03-15)
### Features
* **message:** set default duration to 3s ([7dbedf0](https://github.com/synerise/synerise-design/commit/7dbedf005d555c9b744fb08d1fbff32abe5b4c82))
## [0.122.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.122.2) (2021-03-12)
### Bug Fixes
* **manageable-list:** adds tooltip to moveTo buttons ([ae9f76b](https://github.com/synerise/synerise-design/commit/ae9f76b7f82d44b0bd7b16a31a81cf7538b8d965))
## [0.122.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.122.1) (2021-03-10)
**Note:** Version bump only for package portal
# [0.122.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.122.0) (2021-03-10)
### Features
* **manageable-list:** adds buttons to move items to first/last position ([bd0fdda](https://github.com/synerise/synerise-design/commit/bd0fdda6f72073c2d3b1281c7ec11271e298b4e3))
## [0.121.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.121.3) (2021-03-09)
### Bug Fixes
* **subtle-form:** style statuses inside select ([f3b8bf2](https://github.com/synerise/synerise-design/commit/f3b8bf2578c1deb82d44fae30b6aa16bb11aef7f))
* **table:** delete Icon Avatar Label ([8bf19e7](https://github.com/synerise/synerise-design/commit/8bf19e7534ca0abb0ba474a9dba5a9cc28286c3c))
* **unordered-list:** fix styles unorderd-list ([1abe904](https://github.com/synerise/synerise-design/commit/1abe904c75c37f4f95da286212012a27575dfd5c))
## [0.121.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.121.2) (2021-03-08)
### Bug Fixes
* **condition:** minior fixes ([26982be](https://github.com/synerise/synerise-design/commit/26982bee3f682e6f8d5126e4143c80c4405f6bae))
## [0.121.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.121.1) (2021-03-02)
**Note:** Version bump only for package portal
# [0.121.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.121.0) (2021-03-01)
### Bug Fixes
* **docs:** move checkboxes to folder ([bc19eb7](https://github.com/synerise/synerise-design/commit/bc19eb70ba31b87424daa49598811325534d48e5))
* **docs:** remove public as it doesn't exist ([1d7c3c2](https://github.com/synerise/synerise-design/commit/1d7c3c236dda4aa9405d64a1f079e3892826f36d))
* **docs:** upgrade storybook 6.1.17 ([80e8f64](https://github.com/synerise/synerise-design/commit/80e8f6470e697aa1a07ee2bdddd3376b46b1191f))
* **loader:** add new prop mode to set absolute position of loader ([57a2888](https://github.com/synerise/synerise-design/commit/57a2888e0cac3d948aedcd65ba729eab258cbe30))
* **manageable-list:** add knobs to pick item in manageable-list ([83ebd28](https://github.com/synerise/synerise-design/commit/83ebd285b9cec5e0a215da3024a94d2ee5a87c7b))
* **manageable-list:** change names ([faf5161](https://github.com/synerise/synerise-design/commit/faf51610adfb7d154cd9e94d459cdf9ec0591208))
* **manageable-list:** delete unnecessary components and fix suffix to pick ([a6ba134](https://github.com/synerise/synerise-design/commit/a6ba1349ca29cf2ce7ade541ad4de315a802b507))
* **manageable-list:** fix disabled radio buttons ([af27ee5](https://github.com/synerise/synerise-design/commit/af27ee5e59272fbda3716bdf9a3104acb2775114))
* **ordered-list:** fix stories order ([23f3686](https://github.com/synerise/synerise-design/commit/23f3686bedbb44d1f8d0c9e541fe135f49675c50))
* **ordered-list:** fix styles of ordered list ([64c3466](https://github.com/synerise/synerise-design/commit/64c346676d88e87294aca0bf317655bb242a618e))
* **ordered-list:** fix styles of ordered-list ([f7d7ef4](https://github.com/synerise/synerise-design/commit/f7d7ef4fe1cd8730ac5ff998bfb1818cbd6f0926))
* **ordered-list:** new ordered list ([2124d7f](https://github.com/synerise/synerise-design/commit/2124d7f6244c1798d42bb32864958a76949e2196))
* **page-header:** add checkS icon to picked item ([bbcb366](https://github.com/synerise/synerise-design/commit/bbcb36625d06a1fee669b72d68384d55f6ff7c56))
* **page-header:** add prop to rotate icon when clicked ([e372652](https://github.com/synerise/synerise-design/commit/e3726525330fc852963a374993ae25f1b06ca9ad))
* **subtle-form:** select styles for statuses ([2fc23e4](https://github.com/synerise/synerise-design/commit/2fc23e4d9299145c831a2d6d8812674bb6608a79))
* **subtle-form:** status select story fixes ([be88102](https://github.com/synerise/synerise-design/commit/be88102510491ea1e6f57057835a2bbda03d15f0))
* **subtle-form:** text changes in stories ([dc44ab5](https://github.com/synerise/synerise-design/commit/dc44ab5d867ea19aae6b3a241cb17beaaed21419))
* **subtle-form:** unused code in stories ([92ee7e7](https://github.com/synerise/synerise-design/commit/92ee7e7e44b758c7ba22915006fb16ff9d43d819))
* **table:** fix stories with selection limi ([d342437](https://github.com/synerise/synerise-design/commit/d342437b0900fb2945a49653f24b788fd0e12ea2))
* **table:** remove starIcon from table ([5650ac2](https://github.com/synerise/synerise-design/commit/5650ac2197e3abed1ba7194f0cb0a72424fae0a4))
* **table:** remove width to fix table on firefox ([979bdc4](https://github.com/synerise/synerise-design/commit/979bdc4e0c8c4c6cff1661fb89f214fef75219f6))
* **table:** STOR-685 show add item button on hover ([181ba1e](https://github.com/synerise/synerise-design/commit/181ba1e7d20ca8e3ffa7991b6e8295f0e4e7567b))
* **tagslist:** fix and optimize ([2ddccaf](https://github.com/synerise/synerise-design/commit/2ddccaf0a62ee6b5d1fd57e98a553fd313042794))
* **tagslist:** fix stepping and naming ([78bc4e3](https://github.com/synerise/synerise-design/commit/78bc4e316c1e6638afd681786f25a996ff589c24))
* **tagslist:** some switches in storybook ([ad8a680](https://github.com/synerise/synerise-design/commit/ad8a680bb44fe16db1f166fcecbf2916ab756dbf))
* **tagslist:** STOR-636 fix show-hide / trigger button knob ([b8c3d0b](https://github.com/synerise/synerise-design/commit/b8c3d0b8b9fe91928750678d8eca13d27698211f))
* **unordered-list:** fix styles of icon list ([8d16972](https://github.com/synerise/synerise-design/commit/8d16972b5591d67a0b890ed80d27adb82951a2df))
* **unordered-list:** fix styles of icon list ([db43bcc](https://github.com/synerise/synerise-design/commit/db43bcc8e511d5d82f62b6ee87ddd3ae92c235b7))
* **unordered-list:** fix styles of icons in icon list ([f70a979](https://github.com/synerise/synerise-design/commit/f70a979437586f514414c1be5106002057583814))
* **unordered-list:** fix styles of icons in icon list ([f8b9373](https://github.com/synerise/synerise-design/commit/f8b9373535f9d90e71ff3d32866f25b662af0f7f))
* **unordered-list:** fix styles of unordered list ([d6f7bd3](https://github.com/synerise/synerise-design/commit/d6f7bd30b627eccfddb22ff78948fce683a654d3))
### Features
* **ordered-list:** add new stories unordered list and icon list ([79e640d](https://github.com/synerise/synerise-design/commit/79e640d64566ca9de29e162bd5630e6dac91c2b9))
* **progress-bar:** add progress tiles ([b2a2167](https://github.com/synerise/synerise-design/commit/b2a2167c7f9a39646618298a86ca400dbc532d45))
* **tagslist:** more refactor and bug fixes ([7b2d22c](https://github.com/synerise/synerise-design/commit/7b2d22c54ecbd85a8487bc116151a791c83706da))
* **tagslist:** new AddModal and other stuff ([ee35c22](https://github.com/synerise/synerise-design/commit/ee35c22e21b3460b54c8758ccc5fe20535c0e89f))
* **tagslist:** refactor ([10c562c](https://github.com/synerise/synerise-design/commit/10c562cb4e28fee68534d78154ddb443f6f2054d))
* **tagslist:** STOR-636 add visiblity menu ([4adfabb](https://github.com/synerise/synerise-design/commit/4adfabb98c7deaba977941b20fe2e7df1375f90c))
* **tagslist:** STOR-636 after filename change, rename inside files ([459e301](https://github.com/synerise/synerise-design/commit/459e30142f44ca4a32a3763dc8e7f2dc58bfcc26))
* **tagslist:** STOR-636 fixes ([ef7991f](https://github.com/synerise/synerise-design/commit/ef7991f8913c933e162c375637560c49b580e96c))
* **tagslist:** STOR-636 rename Folders to TagsList ([b102793](https://github.com/synerise/synerise-design/commit/b102793d8171fa83b12b18a7c6317e68330989b5))
* **tagslist:** STOR-636 use stored dataSource and show it in story ([3a365e6](https://github.com/synerise/synerise-design/commit/3a365e6f4d0388b1ed5c2cc3ce7bc9a6adc6e91c))
* **tagslist:** Update stories ([6e875df](https://github.com/synerise/synerise-design/commit/6e875dfb6d8675fb2bcb72fc0ce65662a8172387))
# [0.120.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.120.0) (2021-02-17)
### Features
* **progress-bar:** add progress tiles ([ba7a987](https://github.com/synerise/synerise-design/commit/ba7a987f4859c0021d30f0cbc6a510919ae34893))
# [0.119.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.119.0) (2021-02-15)
### Features
* **progress-bar:** add progress tiles ([3a4a29a](https://github.com/synerise/synerise-design/commit/3a4a29a959d6842a9c873ba8dacf6da32211370b))
## [0.118.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.118.1) (2021-02-08)
**Note:** Version bump only for package portal
# [0.118.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.118.0) (2021-02-05)
### Features
* **table:** add selection limit ([7697b91](https://github.com/synerise/synerise-design/commit/7697b916ad116b9b3ed8d79d436e47d4fcc5228c))
# [0.117.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.117.0) (2021-02-03)
### Bug Fixes
* **item-picker:** close dropdown on bottom action ([cd39911](https://github.com/synerise/synerise-design/commit/cd39911c33ce5e9a9c3694fadadec35052311bd0))
# [0.116.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.116.0) (2021-02-01)
### Bug Fixes
* **condition:** clearing conditions on change context/subject/operator ([37a0b64](https://github.com/synerise/synerise-design/commit/37a0b64ac60dd602c6c99396750fe3a7ab7ebb28))
* **item-picker:** fix storybook ui ([d66c907](https://github.com/synerise/synerise-design/commit/d66c907f83a5fc5897be6f048a663ec8fff176f8))
* **loader:** add export to counter function ([2ba9055](https://github.com/synerise/synerise-design/commit/2ba90550f1a4caa505a5df8239f3096b567f3c1c))
* **loader:** change animation of percent number in loader ([8cad001](https://github.com/synerise/synerise-design/commit/8cad001bece3b5875e42d7e03b10db2326acc44c))
* **logic:** add default texts ([a3f9b4e](https://github.com/synerise/synerise-design/commit/a3f9b4ef5a09c6402805b3575cf05eb20d7ef1e3))
* **result:** add new icons Xl to pick in deafult result component ([bc08487](https://github.com/synerise/synerise-design/commit/bc0848733b338e6b432bf0a89927778b419d4def))
* **result:** add new icons Xl to pick in deafult result component ([4b8d5a4](https://github.com/synerise/synerise-design/commit/4b8d5a4b5ef51e2edee2aa16223d17a2165d63ff))
* **result:** fix order of knobs ([a9dc1ca](https://github.com/synerise/synerise-design/commit/a9dc1ca57ba8d296783d670a68ff1b3231580437))
* **sidebar-object:** hide Menu.Divider when only onId action available ([0aefe90](https://github.com/synerise/synerise-design/commit/0aefe905f3c42f27bab16374d198b96659268104))
* **slider:** add maxMark knobs ([07a5e71](https://github.com/synerise/synerise-design/commit/07a5e7167ee2e83efa3aa360249beb73976b8584))
* **slider:** add wrapping description and hidding scales when handler is close to them ([f0f426b](https://github.com/synerise/synerise-design/commit/f0f426bf2a6ce3fd42c6aaebb49bfd8ff7594a25))
* **step-card:** move example to 'Filter' category in sb ([5e6fae8](https://github.com/synerise/synerise-design/commit/5e6fae854939e7f6ddee6ac3e8a4c1e273473b61))
* **subtle-form:** added checked icon in stories ([cad7662](https://github.com/synerise/synerise-design/commit/cad76622defd646dde53e60e5c2106591b3694fb))
* **table:** change PercentageWrapper to Counter function ([e6479ba](https://github.com/synerise/synerise-design/commit/e6479badc6d2c20eb594300d5b3d24a3a8778fbf))
* **table:** delete get loading function ([b4f8891](https://github.com/synerise/synerise-design/commit/b4f889111f2833cec64c734ae16a11437de3759d))
* **table:** delete knobs and change cell to Avatar with loading state ([952849d](https://github.com/synerise/synerise-design/commit/952849db733ad6d57792d7e9a3d69cab52e71dc5))
* **table:** delete returns in functions ([01038df](https://github.com/synerise/synerise-design/commit/01038dfe311b184ec48e2b00c036b8a6bb2069af))
* **table:** delete un needed function ([e0a7937](https://github.com/synerise/synerise-design/commit/e0a793791a3c7249739719f0a7467b8269413e21))
* **table:** STOR-656 replace icon for user ([ba8e04e](https://github.com/synerise/synerise-design/commit/ba8e04e8eb81dca4629f72bcfbf0d9e7e98540f9))
### Features
* **checkbox-tristate:** STOR-638 new component CheckboxTristate ([7c28df8](https://github.com/synerise/synerise-design/commit/7c28df84e5a18ec913e2ffb4a05e9967bf252f38))
* **condition:** add option for change order of steps ([20911ca](https://github.com/synerise/synerise-design/commit/20911cab9c3e8358057ea0eb73c0047f52616922))
* **filter:** init component ([e98f134](https://github.com/synerise/synerise-design/commit/e98f1344da0c42ef2cd66835dab34ce4017d8b72))
* **item-picker:** add bottom action ([0eed3a9](https://github.com/synerise/synerise-design/commit/0eed3a95f9de29af30005945125216aea858e712))
* **item-picker:** add onFocus and onBlur handlers ([00df343](https://github.com/synerise/synerise-design/commit/00df343215a9806dc30b88354637015c2e57cce6))
* **step-card:** add example with condition ([bc01741](https://github.com/synerise/synerise-design/commit/bc017410266c4ed0e4e80e0279068fdac5152ba3))
* **step-card:** add styles ([2be1f3b](https://github.com/synerise/synerise-design/commit/2be1f3b5781de7b8bf7f69d49f897e12c2aa271c))
* **step-card:** init component ([a66ee2a](https://github.com/synerise/synerise-design/commit/a66ee2a4163ef2cb3dfbedc8f7fb8b74150c8a9c))
* **step-card:** update types ([fcf3d1d](https://github.com/synerise/synerise-design/commit/fcf3d1d3e81b6a9060f2c83c4fc58a4a99d05baa))
## [0.115.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.115.2) (2021-01-27)
### Bug Fixes
* **sidebar-object:** hide Menu.Divider when only onId action available ([adbd633](https://github.com/synerise/synerise-design/commit/adbd633c6c27c7d6c8ee625de0df4acd1f0bd2e8))
## [0.115.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.115.1) (2021-01-27)
**Note:** Version bump only for package portal
# [0.115.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.115.0) (2021-01-22)
### Features
* **item-picker:** add bottom action ([145f5df](https://github.com/synerise/synerise-design/commit/145f5df49c690f10bc6fe07cece1eab6f1e27c16))
# [0.114.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.114.0) (2021-01-21)
### Bug Fixes
* **collector:** disable selection on suggestions list ([1d296ea](https://github.com/synerise/synerise-design/commit/1d296eacd4692df3ee12c1ec60121c87150e96a3))
### Features
* **item-picker:** add bottom action ([ae2045a](https://github.com/synerise/synerise-design/commit/ae2045aebd88e7b1efc36a04cd757512d68da117))
# [0.113.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.113.0) (2021-01-20)
### Bug Fixes
* **cruds:** storybook story fixes ([a44e49f](https://github.com/synerise/synerise-design/commit/a44e49fb752d7e4a894158169df2abcbf9e4652d))
* **date-picker:** set container width to 100% ([edc738e](https://github.com/synerise/synerise-design/commit/edc738e9e0a6418b06645aa24fca8e29515bf957))
* **loader:** add percent value of loader ([888006a](https://github.com/synerise/synerise-design/commit/888006a27bf5466e75544a18697f57ec9b6c6312))
* **loader:** change showPercent value to false ([c792e41](https://github.com/synerise/synerise-design/commit/c792e414ab99d1697562c51922499a09f327136d))
* **subtle-form:** fixed inactive element rendering, added stories ([0a990c1](https://github.com/synerise/synerise-design/commit/0a990c141138327406549689557cc517fd3375bb))
* **subtle-form:** input number styles ([b08dedc](https://github.com/synerise/synerise-design/commit/b08dedc6f19893e0273f604934a3a78c871722e2))
* resolved conflicts with dev ([66c6e28](https://github.com/synerise/synerise-design/commit/66c6e28546fe0efc0e93943f0bd10779091f0116))
* **subtle-form:** fixed inactive element rendering, added stories ([b00659f](https://github.com/synerise/synerise-design/commit/b00659f0bb3309b66b2b1d0c5640e15a519212f3))
* **subtle-form:** input placeholder styles ([afbc748](https://github.com/synerise/synerise-design/commit/afbc7484d26a8df080bdccd2954b505c2fd8a47e))
### Features
* **subtle-form:** added input as subtle field ([e8a8d42](https://github.com/synerise/synerise-design/commit/e8a8d4203aecc07e62c1589e57a37b426098c92d))
* **subtle-form:** added input as subtle field ([0c753d7](https://github.com/synerise/synerise-design/commit/0c753d725ae509d72931fcf69a44f8f9d3d77c34))
* **subtle-form:** generic subtle form field ([c71ffbb](https://github.com/synerise/synerise-design/commit/c71ffbb63aa12bfbe7892e4da11f1c2a2fc9e65f))
* **subtle-form:** generic subtle form field ([f3eef58](https://github.com/synerise/synerise-design/commit/f3eef583794541c9872e576ffe13901ac1607c6e))
## [0.112.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.112.2) (2021-01-15)
### Bug Fixes
* **sidebar-object:** add button with starred icon to header in sidebar-object ([3d48de1](https://github.com/synerise/synerise-design/commit/3d48de1682cc25687022b5923ab360abe2d2bd74))
* **sidebar-object:** delete unnecessary import ([c82e676](https://github.com/synerise/synerise-design/commit/c82e676fee3a4fc60765988a1aef4413b82f5479))
* **sidebar-object:** remove knobs to set starred active ([6c8653c](https://github.com/synerise/synerise-design/commit/6c8653c809392e907c9e9d5056b1d60e382e39dc))
* **table:** passed inputProps in stories ([9218398](https://github.com/synerise/synerise-design/commit/9218398197b7d4cd6ce4df7dca173573a3ecb990))
## [0.112.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.112.1) (2021-01-14)
### Bug Fixes
* **manageable-list:** fix styles of FilterItem & ItemMeta ([ac0f3f6](https://github.com/synerise/synerise-design/commit/ac0f3f63ef51f521d8a5e970a3640835e920885e))
* **sidebar-object:** add starred icon to header in sidebar-object ([48ccaf0](https://github.com/synerise/synerise-design/commit/48ccaf03bafd09001cb72146ff9fd5462f409d77))
* **sidebar-object:** add starred icon to header in sidebar-object default ([79ee578](https://github.com/synerise/synerise-design/commit/79ee5784229ea6e14f1c5a0313e872311b5a083d))
* **sidebar-object:** move header above scrollbar wrapper ([0242c22](https://github.com/synerise/synerise-design/commit/0242c22134c55c38718a0d344252a9fbea395b3d))
# [0.112.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.112.0) (2021-01-13)
### Bug Fixes
* **completed-within:** fix styles ([c71ad81](https://github.com/synerise/synerise-design/commit/c71ad81afca4932e4019b18762faa382ded123e7))
* **context-selector:** client version with selected value ([0d154b4](https://github.com/synerise/synerise-design/commit/0d154b4a42577cd0c6b0390da2be8691eda6d15f))
* **input:** pass autosize object to textarea ([bc68f5d](https://github.com/synerise/synerise-design/commit/bc68f5dc201eca1830ae7dcfb2dbe1c5feb54a0b))
* **page-header:** fix component page header with dropdown ([0227020](https://github.com/synerise/synerise-design/commit/0227020bd560d3ee1ca1424970613d5a1729a418))
* **progress-bar:** fix placement of label in progress bar ([e37820e](https://github.com/synerise/synerise-design/commit/e37820e67b786780a61e93d3313ae99e4e6d11a9))
* **slider:** fix disabled dots styles ([7662a6c](https://github.com/synerise/synerise-design/commit/7662a6c89a41da43856f468f36c10db5d731e153))
* **slider:** fix focusing handlers and description ([1196f83](https://github.com/synerise/synerise-design/commit/1196f837205d5d0eced4a575b1ae9de0376d5036))
* **slider:** fix style disabled of dots ([3f1e4c4](https://github.com/synerise/synerise-design/commit/3f1e4c41b37e6d886be25981897047dade790431))
* **slider:** fix styles in default slider ([9871aa3](https://github.com/synerise/synerise-design/commit/9871aa3f78a80e4284dbbce2ce057fa6c70eb0f4))
* **slider:** fix styles of dots ([6430737](https://github.com/synerise/synerise-design/commit/6430737007bd98634187d5e0fa5bacabfc8658a5))
* **slider:** fix styles of tooltip, track, rail and handle ([757e9a9](https://github.com/synerise/synerise-design/commit/757e9a9bc536c8b05123252f8ff881833182a802))
* **slider:** remove inverted knobs and remove highlight value and mark ([e34f0bd](https://github.com/synerise/synerise-design/commit/e34f0bd6f0e7f6b356efe82c9cd33cbf46ec1238))
* **table:** add progress bar to default table ([d5f9fc6](https://github.com/synerise/synerise-design/commit/d5f9fc65b6fd101ae6402bd7aa663d0573b076b3))
* **table:** fix placement of label in progress bar and add name type of cell ([dd31d6f](https://github.com/synerise/synerise-design/commit/dd31d6f2bac7899ab7dc6c3f204b399d0e89b22c))
### Features
* **condition:** add context to step configuration ([8b3fdb5](https://github.com/synerise/synerise-design/commit/8b3fdb5eaf9e8b586b79fa426875e096e341dcb8))
* **context-selector:** rename props `value` and `onChange` ([0ee75d2](https://github.com/synerise/synerise-design/commit/0ee75d2a0ba6595e0ada2ee502347954a2a6cf30))
* **cruds:** expose single action as subcomponent ([8e2b29e](https://github.com/synerise/synerise-design/commit/8e2b29e703719b6432b0f8749cd97f250c697e49))
* **subject:** rename prop `selectItem` to `onSelectItem` ([406cf3f](https://github.com/synerise/synerise-design/commit/406cf3f57e8eb57153f7fb5b979a580b142f4694))
## [0.111.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.111.3) (2021-01-05)
### Bug Fixes
* **collector:** hide suggestions list on cancel ([0ab6601](https://github.com/synerise/synerise-design/commit/0ab6601b37e1775a827c6056b6bb80daa12489d0))
## [0.111.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.111.2) (2021-01-04)
### Bug Fixes
* **date-range-picker:** replaced texts with translations ([6fa40bd](https://github.com/synerise/synerise-design/commit/6fa40bd159c5f202789b3752f16bcd93e66a2c1c))
* **progress-bar:** add 100% width to the multivalue variant ([1b29d01](https://github.com/synerise/synerise-design/commit/1b29d01eeea10e582a90d12f9220c3d38cfeb917))
* **progress-bar:** add new small bar component ([932a95c](https://github.com/synerise/synerise-design/commit/932a95ca664419f815058023a027981e73f0b34e))
* **progress-bar:** add new small bar component ([d5c64a2](https://github.com/synerise/synerise-design/commit/d5c64a2e60f6792a403e084212c47a3630dfb09b))
## [0.111.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.111.1) (2020-12-22)
### Bug Fixes
* **wizard:** disable render on portal to fix scrollbar position ([0f66a8e](https://github.com/synerise/synerise-design/commit/0f66a8e1ca8d5023431d1996ea03d92b9b29f478))
# [0.111.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.111.0) (2020-12-21)
### Bug Fixes
* **completed-within:** fix selected value state ([f17fef1](https://github.com/synerise/synerise-design/commit/f17fef15afa8bba1869cffe616fb701ecc5db65d))
* **dropdown:** add option to close dropdown by click outside in example1 and withTabs ([fa1a104](https://github.com/synerise/synerise-design/commit/fa1a1040553884eb1cc93c7520cfdea5041ad754))
* **page-header:** cleanup ([c6f4b47](https://github.com/synerise/synerise-design/commit/c6f4b47cbc1da03f7e5fdfe66ddac0bd2e58f8a1))
* **page-header:** fix page header with tooltip icon position ([912f877](https://github.com/synerise/synerise-design/commit/912f8773bfbfc1e87a53e6e8e0c0a7104c40b8c9))
* **slider:** add styles to ant-slider-track and props disabled ([a53631a](https://github.com/synerise/synerise-design/commit/a53631a49bd9b34e2e5eb2c46e79ed3c34840b6b))
* **slider:** hide first and last mark, add new prop ([66f6373](https://github.com/synerise/synerise-design/commit/66f6373cf60737d0decbac5d8d2c40837bac26ca))
* **slider:** linter errors ([da0d7ad](https://github.com/synerise/synerise-design/commit/da0d7ad7ef8b00384236103346d2ee5e3800996c))
* **slider:** new multivaluerange component ([e5765ce](https://github.com/synerise/synerise-design/commit/e5765ce46694a258ed8de0c9815010f10f3c760f))
### Features
* **context-selector:** add ContextSelector component ([2ca8b54](https://github.com/synerise/synerise-design/commit/2ca8b5407ecfaa393843bed55ab143becdfd94ea))
* **logic:** add Logic component ([f59a330](https://github.com/synerise/synerise-design/commit/f59a330b63310cafa2c21223908bfb0f5029985f))
* **logic:** add Matching component ([0b772bd](https://github.com/synerise/synerise-design/commit/0b772bde72df48ebf96841927e70b753a752462d))
* **slider:** allocation variant added ([ff080a8](https://github.com/synerise/synerise-design/commit/ff080a8834f1f34a638dca8a1e07287dae5812dd))
* **stepper:** add small mode ([6ec7181](https://github.com/synerise/synerise-design/commit/6ec7181886ccfd97f099aa63c10bcb66f9c84d39))
* **subject:** rename prop showPreviow to onShowPreview ([7ea1279](https://github.com/synerise/synerise-design/commit/7ea1279ec7208bef7a26300a02393a385d988839))
* **wizard:** add wizard component ([5e2a280](https://github.com/synerise/synerise-design/commit/5e2a280390c95e08b10fc3f404bfec2c5ad3b697))
* **wizard:** add wizard component ([a787c0f](https://github.com/synerise/synerise-design/commit/a787c0f76fcaa56ecb86ddc8fecbbe16d4c07655))
* **wizard:** styles improvements ([addfcae](https://github.com/synerise/synerise-design/commit/addfcae58413e55722c3b9195dab85aa98c3cfac))
# [0.110.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.110.0) (2020-12-14)
### Bug Fixes
* **card:** add option to set header in footer ([5da311d](https://github.com/synerise/synerise-design/commit/5da311d005a488c8f15536b03e75b44df7a15874))
* **card:** change name of set footer active knobs and fix animation ([3af55ea](https://github.com/synerise/synerise-design/commit/3af55eab47ed6855142daff67974f20a5480ebb3))
* **card:** change name of showSideChildrenWhenHeaderHidden knobs ([121d3f0](https://github.com/synerise/synerise-design/commit/121d3f0bc0296939b82450aa934f976a9d02322c))
* **card:** fix props in single card ([af51415](https://github.com/synerise/synerise-design/commit/af51415e4543e6c372bbe7d8bfb189f81f64b6ec))
* **card:** remove footer prop ([9a55fe3](https://github.com/synerise/synerise-design/commit/9a55fe376ede31549ab311b34e2ed57bfd008b7e))
* **page-header:** fix stories ([6f0a511](https://github.com/synerise/synerise-design/commit/6f0a511687d96f3cedd082c67bf6fb360960b801))
* **stepper:** fix knobs in storybook ([b67c0ea](https://github.com/synerise/synerise-design/commit/b67c0ea1613931096d1e6f80f6c44ee5e7382659))
* **stepper:** fix storybook examples ([18e9987](https://github.com/synerise/synerise-design/commit/18e9987f8a20f1796cacb1ce0d2f0d9a356c2be2))
* **subtle-form:** height and placeholder fixes ([ec8399b](https://github.com/synerise/synerise-design/commit/ec8399b12f87f94135cdc32965f7e3fbaffa6c67))
### Features
* **alert:** add InlineAlert component ([da34414](https://github.com/synerise/synerise-design/commit/da34414e8267f4c343b2998df86946eb2201acb7))
* **completed-within:** add CompletedWithin component ([5b508b6](https://github.com/synerise/synerise-design/commit/5b508b6cebde22be6fee101038a0acfe6b2447f3))
* **completed-within:** add dependecies ([3137a7f](https://github.com/synerise/synerise-design/commit/3137a7f2304f3ea42b1a05491071fc25ee3f0639))
* **completed-within:** add tests and documentation ([fec4e0d](https://github.com/synerise/synerise-design/commit/fec4e0d3fd7b79d6145c09ae6b5e8769ceca0393))
* **format-picker:** add FormatPicker component ([4b9462a](https://github.com/synerise/synerise-design/commit/4b9462a00816c018b9c6d504daeb36eff214c122))
* **format-picker:** update storybook exampe ([b54824b](https://github.com/synerise/synerise-design/commit/b54824b0912b7afa474435caa75d2c24b6c29cd7))
* **items-roll:** add changeSelectionDropdownProps prop ([ece497f](https://github.com/synerise/synerise-design/commit/ece497f84358917eeb8910d39ea6cbfb9888973f))
* **page-header:** add title tooltip ([314608f](https://github.com/synerise/synerise-design/commit/314608fe013e9c978b8e9a88a4b293676e7500dc))
# [0.109.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.109.0) (2020-12-14)
### Features
* **date-picker:** add suffix and prefix to input & datepicker ([69e21ba](https://github.com/synerise/synerise-design/commit/69e21baf4c91135f51c301dfc69b6501d1e68235))
* **page-header:** add title tooltip ([7df28ce](https://github.com/synerise/synerise-design/commit/7df28ce8d36703293c9a9b1cc6016d7492ad5008))
# [0.108.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.108.0) (2020-12-04)
### Bug Fixes
* **tags:** added missing translations keys ([0705ca2](https://github.com/synerise/synerise-design/commit/0705ca2ac33d4a430d74e6d42883efcd9aad4962))
### Features
* **stepper:** add stepper example in header and in modal ([0d2c059](https://github.com/synerise/synerise-design/commit/0d2c05930e250617f8b66ba2b9afac30cbfd1aa1))
# [0.107.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.107.0) (2020-12-02)
### Bug Fixes
* **action-area:** fix text alignment ([d549abb](https://github.com/synerise/synerise-design/commit/d549abb74f687f27bac0eb0bad2a4753c5c0b8de))
* **date-picker:** handling disabled state ([2cf037e](https://github.com/synerise/synerise-design/commit/2cf037e30256ea4bb9716b204e4454fe9227fb54))
* **dropdown:** fix bottom action ([deb703b](https://github.com/synerise/synerise-design/commit/deb703b98aeda67752fd5120023572d46240847a))
* **page-header:** fix rightSide styles ([e0ddc49](https://github.com/synerise/synerise-design/commit/e0ddc4910b2c9d634957814b5e464d1baf4be2ca))
* **sidebar-object:** add prop to add new element to it also to pick read only title or edit able ([4a131fc](https://github.com/synerise/synerise-design/commit/4a131fcfc846da8d22472349b2907029f487bddc))
* **sidebar-object:** add props description ([59087d2](https://github.com/synerise/synerise-design/commit/59087d2369c2fdaf6d4f11b340a45ac5e9e1b25e))
* **sidebar-object:** add props to buttons ([cd053f9](https://github.com/synerise/synerise-design/commit/cd053f963dff87dad60ddd9f3eacd10216cd9a2c))
* **sidebar-object:** delete showBackIcon from campaign component ([a23a606](https://github.com/synerise/synerise-design/commit/a23a60601ca03ceb6f3c53859716b0460e99dc24))
* **sidebar-object:** set showBackIcon on false ([f69d280](https://github.com/synerise/synerise-design/commit/f69d280516740a31e181a9c708d8a609d8047842))
* **subtle-form:** disabled state styles for select and date ([407e017](https://github.com/synerise/synerise-design/commit/407e017bc444aac2d6829d0240383e3e55b5190b))
* **table:** add option to set active star and add star to avatar cells ([7fd0433](https://github.com/synerise/synerise-design/commit/7fd0433399eae533c0034d877dc15e3bb0413822))
* **table:** change title to label and fix tooltip ([a4141a6](https://github.com/synerise/synerise-design/commit/a4141a644afcb9049b3a9ae311377e43dd341855))
* **table:** fix showMore styles ([f16a22a](https://github.com/synerise/synerise-design/commit/f16a22a1c946dc390dee4c13c35bf94c5d14bba0))
* **table:** fix styles of show-more button, add key prop to datasource ([77aca1a](https://github.com/synerise/synerise-design/commit/77aca1a97b18bb3e7a50975807e1659933158398))
* **table:** show autogenerated title with number of results ([c89db07](https://github.com/synerise/synerise-design/commit/c89db0762fda62623fd52a96a44babd05c9fb413))
### Features
* **action-area:** add ActionArea component ([7c147a4](https://github.com/synerise/synerise-design/commit/7c147a41761cc4c5743247e662b87a810e5366c7))
* **action-area:** add withMargin prop ([8c3cd50](https://github.com/synerise/synerise-design/commit/8c3cd5008f388d13fde506a6396bbd1141616221))
* **description:** add dotted, and numbered list types ([9d8e78a](https://github.com/synerise/synerise-design/commit/9d8e78a74def7ee1d390f87bfa25e31cc20681eb))
* **dropdown:** add TextTrigger ([5d7028f](https://github.com/synerise/synerise-design/commit/5d7028f3160cbd4e14e5c56ae80efd21798c2606))
* **dropdown:** add TextTrigger ([84c5b79](https://github.com/synerise/synerise-design/commit/84c5b79bd28f6b8414e50fae300349b349ed70a9))
* **modal:** add example with stepper ([7858ec9](https://github.com/synerise/synerise-design/commit/7858ec95d811558b3f066c8d18c3ba2900c177f5))
* **page-header:** add example with dropdown ([cf532aa](https://github.com/synerise/synerise-design/commit/cf532aabef0790a40ef4e9edee087f2357d6d9f7))
* **stepper:** add Stepper component ([3c0afbc](https://github.com/synerise/synerise-design/commit/3c0afbc5869f43317b7bafa9d447476398d25fa2))
* **stepper:** vertical stepper ([2833204](https://github.com/synerise/synerise-design/commit/2833204ac87126c436cd0a9a096c22dafda2bc89))
* **table:** improve translations ([0c10fd7](https://github.com/synerise/synerise-design/commit/0c10fd7b4b06fe7a2b043246f57818e45a9cab89))
## [0.106.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.106.2) (2020-11-25)
### Bug Fixes
* **button:** add props split mode ([6aebd5f](https://github.com/synerise/synerise-design/commit/6aebd5fe14896ff5c083118f3d204d3ebe231651))
* **button:** fix props in button-split and fix color styles ([357801f](https://github.com/synerise/synerise-design/commit/357801f25dec4a6723951736e8eb17fc5d9ab8cf))
* **loader:** add optional props color ([3a7f23a](https://github.com/synerise/synerise-design/commit/3a7f23a129f9eb86a968c62c0e79aca7ae06bfd1))
* **loader:** add props to change color of loader ([9ab9ad1](https://github.com/synerise/synerise-design/commit/9ab9ad1abbe6eaa824a584fe4b427e0b85fbc280))
* **tabs:** change knobs setSufix to setCounter ([904806e](https://github.com/synerise/synerise-design/commit/904806e8590b5923b8cec25babaf676e480e5e5d))
* **tabs:** change knobs setSufix to setCounter ([e4d0e20](https://github.com/synerise/synerise-design/commit/e4d0e20f351ea4ef2e1257bd7eea0024b473bca3))
* **tags:** change icon to Add3M ([43c6e5b](https://github.com/synerise/synerise-design/commit/43c6e5bb5d5e304147d6f89301067407fc025358))
* **tags:** fix color of added tags ([4e6ec44](https://github.com/synerise/synerise-design/commit/4e6ec440f0b195726edf6158e5d430da37f3225c))
## [0.106.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.106.1) (2020-11-18)
### Bug Fixes
* **badge:** change name of knobs ([d2aff28](https://github.com/synerise/synerise-design/commit/d2aff283f5641acdd5734f1cd6c9d4405698e30a))
* **badge:** set pulsing on true ([7e3d4f4](https://github.com/synerise/synerise-design/commit/7e3d4f493641ad9beb2acca97b6c9b590fb9f872))
* **button:** change working of split buttton ([65e3811](https://github.com/synerise/synerise-design/commit/65e3811948b158cc6c2605babf9aef2b8a575e3b))
* **button:** remove margin from split buttton ([4acec0d](https://github.com/synerise/synerise-design/commit/4acec0d7db82f84dd689adf862135cfda772b1e7))
* **button:** remove styles in index.stories of split buttton ([24cf6fc](https://github.com/synerise/synerise-design/commit/24cf6fc09238275097268ef320691f47d4762011))
* **dropdown:** fix items in data, add no results and fix focus on button ([a539784](https://github.com/synerise/synerise-design/commit/a539784876ddcd1106cd5443e7943e8a233bee07))
* **status:** add customStatus and option to change color ([7d90233](https://github.com/synerise/synerise-design/commit/7d90233d8993bef84bab6854e6cdce52460f5fa2))
* **status:** change name to pillSmall and color name disabled to default ([15b03e2](https://github.com/synerise/synerise-design/commit/15b03e289e493d94121331339041b7e6c5d5b698))
* **subtle-form:** added textarea disabled props ([820388e](https://github.com/synerise/synerise-design/commit/820388e1619cf424f8ee10bc3502128706ea5f83))
* **tags:** change colors of tags to default grey and on hover colors to red ([38ba28c](https://github.com/synerise/synerise-design/commit/38ba28c7a9de2576838ca08534bde67d11305366))
* **tags:** fix styles, export getColorText ([fc54740](https://github.com/synerise/synerise-design/commit/fc54740ee4fec83d8291b3254d0e83d55a8aa7c4))
# [0.106.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.106.0) (2020-11-13)
### Features
* **search:** update storybook example ([607e0ca](https://github.com/synerise/synerise-design/commit/607e0ca0927c6e37ea93ee922afdda5dff517c92))
## [0.105.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.105.1) (2020-11-12)
**Note:** Version bump only for package portal
# [0.105.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.105.0) (2020-11-12)
### Bug Fixes
* **badge:** change animation and add outline to prop flag ([bd28cea](https://github.com/synerise/synerise-design/commit/bd28cea85c3530a6b44641c8ccc0b8ce3c60a1cb))
* **cascader:** change name ([a70d51a](https://github.com/synerise/synerise-design/commit/a70d51a4cf9c35640c56da2752dfdb3ff49a1ab3))
* **cascader:** create own folder in dropdowncomponent ([79ba6a3](https://github.com/synerise/synerise-design/commit/79ba6a3887e1b0db4ebe5f9eeb5610eee6019579))
* **dropdown:** change button and list to menu in overlayExample and some styles ([b67f598](https://github.com/synerise/synerise-design/commit/b67f598a0e41ab0c8b2d8db005a4c8aef95c4d44))
* **dropdown:** fix some styles of items and add option to select by keys up/down ([6cce5bc](https://github.com/synerise/synerise-design/commit/6cce5bcb3ce548952d5c19a1511ef148da96ccbd))
* **dropdown:** remove dataSource ([17a78ff](https://github.com/synerise/synerise-design/commit/17a78ffe539d0d64217c86646cb8a14407dc3265))
* **status:** change to pills component ([45e112b](https://github.com/synerise/synerise-design/commit/45e112b48931ac4f1f58743ba330aa6a4b885c6a))
* **table:** fix issues from CR ([12817d1](https://github.com/synerise/synerise-design/commit/12817d115d55ea615b2ee517ee9ed86a3c31daaf))
* **table:** remove unsed props ([e7f950f](https://github.com/synerise/synerise-design/commit/e7f950f2ee8c6408eb9c810fcb010c75957a4db5))
* **tags:** change to pills component ([970ee9a](https://github.com/synerise/synerise-design/commit/970ee9ad7655e2e6966d82a24eadfc5aa7bcd059))
### Features
* **table:** add example of cell with more items ([cfaf6bb](https://github.com/synerise/synerise-design/commit/cfaf6bbc717e3b2da4a80591af651df8b440a5dd))
* **table:** add example of show more cell ([fba870b](https://github.com/synerise/synerise-design/commit/fba870bdca1c0450a360d67d3bb23a2124e3b200))
* **table:** add i18n into ShowMore cell ([2c0ca54](https://github.com/synerise/synerise-design/commit/2c0ca547f55fdac57630c1e66027276dbff9a4a5))
* **table:** update examples in storybook ([095f0ac](https://github.com/synerise/synerise-design/commit/095f0ac7c97b94d892aec92bc4ce498920a4ae56))
## [0.104.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.104.1) (2020-11-09)
### Bug Fixes
* **cascader:** change name ([f1dd56e](https://github.com/synerise/synerise-design/commit/f1dd56ea09afd91be7d92437d981ff31d8a60a68))
* **cascader:** move to dropdown components ([25decab](https://github.com/synerise/synerise-design/commit/25decab6a80ff2545524764f6ff5481357fcb04c))
* **dropdown:** add two new components default and withSearch ([372ca1b](https://github.com/synerise/synerise-design/commit/372ca1bdac585e7bf86ce2c63278e7851c3a3c9c))
* **dropdown:** add two new components default and withSearch ([de76451](https://github.com/synerise/synerise-design/commit/de76451b975d8363f92e20bd3d70b192dd164111))
* **dropdown:** delete datasource ([2c05641](https://github.com/synerise/synerise-design/commit/2c056418bb104dd4ca86816be493ce38290306c6))
* **dropdown:** fix menu styles and box-shadow ([8721a5b](https://github.com/synerise/synerise-design/commit/8721a5b19876091db673b26748e8003ce245281e))
* **dropdown:** fix menu styles, border-radius add no results and highlighted text ([bffa658](https://github.com/synerise/synerise-design/commit/bffa658ebbdbfa52b17a63ce50c8db0e9e27b04e))
* **sidebar-object:** fix box-shadow ([3dc00ea](https://github.com/synerise/synerise-design/commit/3dc00ea0fc973001e89e95f6d5b13b78d3cfe9a6))
# [0.104.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.104.0) (2020-11-06)
### Features
* **search:** onParameterChange returns parameter name and full param ([8588080](https://github.com/synerise/synerise-design/commit/85880803760a4c3cfb3bc14db9c78c7a6197d7ce))
# [0.103.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.103.0) (2020-11-04)
### Bug Fixes
* **badge:** add props pulsing to add animation ([6ebd8dd](https://github.com/synerise/synerise-design/commit/6ebd8dd0a718984ec7ceeb266bb1672ae02b935a))
* **select:** add allowClear props to storybook ([66b6f8d](https://github.com/synerise/synerise-design/commit/66b6f8d14bebfc1c6705aed29056c23b3ff5117c))
### Features
* **tooltip:** custom tooltips in input ([b7cd7d3](https://github.com/synerise/synerise-design/commit/b7cd7d36cfef8e6c7523b4e7ba2770b476ca3e92))
## [0.102.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.102.4) (2020-10-30)
**Note:** Version bump only for package portal
## [0.102.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.102.3) (2020-10-30)
### Bug Fixes
* **avatar-group:** fix storybook example ([5fde308](https://github.com/synerise/synerise-design/commit/5fde30805ba25f9bc22f9fa7b711fbf1ffaeabd2))
## [0.102.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.102.2) (2020-10-29)
### Bug Fixes
* **portal:** used secondary button in results stories ([c1fbf17](https://github.com/synerise/synerise-design/commit/c1fbf17f4ef04606e50f2bf2d8624b7b0447c348))
* **tooltip:** add new type tooltips API and header with label ([e6bb579](https://github.com/synerise/synerise-design/commit/e6bb579b2fd28486eea430bae77aac9d0cb608b2))
* **tooltip:** fix type tooltips status and header with label ([fa2d2dc](https://github.com/synerise/synerise-design/commit/fa2d2dc9a6798346e9026a92c863587f60dedb75))
## [0.102.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.102.1) (2020-10-28)
### Bug Fixes
* **collector:** add an option to hide right panel ([16594cf](https://github.com/synerise/synerise-design/commit/16594cfc13fe666fc87d6e93ddc30cc098b0fd5f))
# [0.102.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.102.0) (2020-10-28)
### Bug Fixes
* **collector:** use object array instead of string array as entry ([a23f4f4](https://github.com/synerise/synerise-design/commit/a23f4f493b1880ff426cc92091889d72aec440ca))
* **collector:** used objects instead of strings as input ([9a6a5a7](https://github.com/synerise/synerise-design/commit/9a6a5a75450917c550e229481c1e41e3ae913080))
* **input:** fix date mask ([324ed87](https://github.com/synerise/synerise-design/commit/324ed87ad226561bed384e2c0a12cdefb6be06df))
* **portal:** added icons in header knobs in table stories ([b7e12c4](https://github.com/synerise/synerise-design/commit/b7e12c49e66e79fc17f1f58a21cb2bc869b8f04c))
* **select:** add prop highlight ([7a68a2d](https://github.com/synerise/synerise-design/commit/7a68a2d42126ac268ac0d9b3ad4e7d9265d65b06))
* **select:** add prop highlight ([f9b9ba8](https://github.com/synerise/synerise-design/commit/f9b9ba8ce162945d7e2ebb579ba46e804a16ba94))
* **table:** iconTooltipCell - render label only when provided ([f8898f6](https://github.com/synerise/synerise-design/commit/f8898f6812632910ac5786caaa39ef0f1bfc85ab))
### Features
* **table:** added IconTooltipCell ([f08cae9](https://github.com/synerise/synerise-design/commit/f08cae9138e57f3bbbbd5525f40dcca32291da37))
## [0.101.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.101.1) (2020-10-22)
**Note:** Version bump only for package portal
# [0.101.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.101.0) (2020-10-22)
### Bug Fixes
* **cascader:** maxHeight handling improved ([0091ead](https://github.com/synerise/synerise-design/commit/0091eadd9c43e84f10666d63849537a3182efa44))
* **input:** add no result ([3249509](https://github.com/synerise/synerise-design/commit/32495096185cfe6bd18550c04d3bfac9baffc07f))
* **input:** fix date mask ([a3df929](https://github.com/synerise/synerise-design/commit/a3df9290f33ff332516f55ccfe5c60ec5b185c04))
* **menu:** fixed disabled state, added userInfo story ([8bfada7](https://github.com/synerise/synerise-design/commit/8bfada718fcc2b164f4caa01b208a8efe7d1f3c9))
* **select:** add dateSelect component ([cf75609](https://github.com/synerise/synerise-design/commit/cf75609715819cc9977b3a37c46e883a214f17cb))
* **select:** change styles in dateSelect ([6c0af87](https://github.com/synerise/synerise-design/commit/6c0af873473a9027588eed5faed02bd886eb9234))
* **subtle-form:** added stricter typings, updated stories ([52e42eb](https://github.com/synerise/synerise-design/commit/52e42ebb5c54dbb16da64726ed06815642519245))
* **subtle-form:** allow to clear on subtle date picker story ([2ba13bd](https://github.com/synerise/synerise-design/commit/2ba13bddcf03ca769a335751e9e86e0d1bfdde30))
* **subtle-form:** removed console log from stories ([e65f9ed](https://github.com/synerise/synerise-design/commit/e65f9ed8f5484cef60e25b9573b163a1cd9d67f7))
### Features
* **portal:** added new menu stories ([a0149c8](https://github.com/synerise/synerise-design/commit/a0149c8fa9d68550e9477dea75d5e4cddebdd108))
## [0.100.5](https://github.com/synerise/synerise-design/compare/[email protected]@0.100.5) (2020-10-20)
### Bug Fixes
* **input:** add inputwithflag to input group and add masks to datemaskinput ([f3c74ca](https://github.com/synerise/synerise-design/commit/f3c74cae2723ec106b26116ee6add5bf51efde04))
* **input:** add minHeight of content above ([7d9253c](https://github.com/synerise/synerise-design/commit/7d9253c4478bc760488ad066996eb23d71b2bb35))
* **input:** add minHeight of Label and change paddings ([f6c86ac](https://github.com/synerise/synerise-design/commit/f6c86ac4cbde32b26c79d537378fdfac6f634e99))
* **input:** change padding and width ([f431f2f](https://github.com/synerise/synerise-design/commit/f431f2f033a663f39ee0157e81b9e581b7eed23f))
* **input:** change width ([d878bd8](https://github.com/synerise/synerise-design/commit/d878bd887e0c3cea0c4bfba610e4169a3c92f4b2))
* **input:** fix input with mask and add some maskedinputs ([7febe6a](https://github.com/synerise/synerise-design/commit/7febe6a171105535f68f88980714b150f291b323))
* **portal:** removed typo from select story ([ebb8809](https://github.com/synerise/synerise-design/commit/ebb8809cb5d6a9e08e9708c1f8af63102c1be3fc))
## [0.100.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.100.4) (2020-10-16)
### Bug Fixes
* **manageable-list:** fix max-height of expandable ItemContent ([009b12d](https://github.com/synerise/synerise-design/commit/009b12dbcd9c1c91c6c229fba5711b529c171f67))
## [0.100.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.100.3) (2020-10-15)
### Bug Fixes
* **sidebar-object:** change padding ([37102c4](https://github.com/synerise/synerise-design/commit/37102c4eea707991c9eb40047517f29c82565a85))
* **subtle-form:** fixed margins and displaying rows ([9eee1b5](https://github.com/synerise/synerise-design/commit/9eee1b56862bf72bb7a6c22dd8e64a18e71d20c0))
## [0.100.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.100.2) (2020-10-14)
### Bug Fixes
* **sidebar-object:** change and deletes some props ([e336e94](https://github.com/synerise/synerise-design/commit/e336e9437583b888a31bc2bfe7868b66563ee810))
## [0.100.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.100.1) (2020-10-13)
**Note:** Version bump only for package portal
# [0.100.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.100.0) (2020-10-12)
### Bug Fixes
* **date-range-picker:** apply saved filter choosen from dropdown ([1806858](https://github.com/synerise/synerise-design/commit/1806858e1a9028cf4e8959a9075683e93684eb26))
* **date-range-picker:** fixed paddings and added summary of collapsed addon ([4ff931f](https://github.com/synerise/synerise-design/commit/4ff931ff6d34c84b96e0485dc3cd463faf0eac7f))
* **date-range-picker:** rebased dev ([a3207d4](https://github.com/synerise/synerise-design/commit/a3207d4e956bfa8e11f1273544254b07f307ce52))
* **sidebar-object:** change props to inline edit and change which tab is active ([3727c8e](https://github.com/synerise/synerise-design/commit/3727c8eb29e87d087bd8b5ef07cf55a03202c707))
### Features
* **date-range-picker:** added ability to remove the filter ([61b8a10](https://github.com/synerise/synerise-design/commit/61b8a10e9f590a3fc2e4b7db180f4fc8537238a3))
* **date-range-picker:** added an option to select saved filter ([b62a59a](https://github.com/synerise/synerise-design/commit/b62a59aabc95ebc3939cd90e320ba67f52017f23))
* **date-range-picker:** added range filter component ([c152698](https://github.com/synerise/synerise-design/commit/c152698f6d9fa5f2aa2320c3bda651360583f170))
* **date-range-picker:** added range filter component ([33d6ed7](https://github.com/synerise/synerise-design/commit/33d6ed7f71b7218f12eda770993b171c6d420a17))
* **date-range-picker:** added range filter component ([19f0283](https://github.com/synerise/synerise-design/commit/19f0283c43b7c95a65ca6b7548cc555d97d8b640))
## [0.99.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.99.3) (2020-10-12)
**Note:** Version bump only for package portal
## [0.99.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.99.2) (2020-10-12)
### Bug Fixes
* **folders:** changed story on storybook ([85e246c](https://github.com/synerise/synerise-design/commit/85e246ccdc074f6c53b9aa900282f754c19f99e5))
* **sidebar-object:** change paddings and margins, add footer and to props documantation ([daa7994](https://github.com/synerise/synerise-design/commit/daa79943f165f913b6f805b83f6216bab3299378))
## [0.99.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.99.1) (2020-10-09)
### Bug Fixes
* **card:** removed showContent prop, fixed max height ([2f366ea](https://github.com/synerise/synerise-design/commit/2f366ea4086614cb659f7eec5d222d306ba86f3d))
* **layout:** removed unused card prop from stories ([eec8b26](https://github.com/synerise/synerise-design/commit/eec8b26199981bb0a94f82049b7b744ed1021e50))
* **table:** removed unused card prop from stories ([f1493b0](https://github.com/synerise/synerise-design/commit/f1493b031bc636ffd455bc799a1e53f938dba38f))
# [0.99.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.99.0) (2020-10-09)
### Bug Fixes
* **sidebar-object:** change padding and delete text-overflow ([dd8a91c](https://github.com/synerise/synerise-design/commit/dd8a91ca41a5f08cdbc5e176396af90da067b1b1))
* **sidebar-object:** remove overview component from sidebarobject.tsx ([48fb3a4](https://github.com/synerise/synerise-design/commit/48fb3a451c0f75b3c613c995c2173da0ac97f7d7))
### Features
* **button:** move Crud and SingleAction to separate Crud component ([a10976a](https://github.com/synerise/synerise-design/commit/a10976a2677823ea8064068eea7e0c53611cfc78))
* **cruds:** add Cruds component ([15498ba](https://github.com/synerise/synerise-design/commit/15498bad6e40649f8807c20c96fbdb58b5260f17))
* **tooltip:** add example of tooltip with button ([a8ddb13](https://github.com/synerise/synerise-design/commit/a8ddb1373fdad98d82330c5db1069dc413772007))
# [0.98.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.98.0) (2020-10-06)
### Bug Fixes
* **subtle-form:** error state fixes ([a5b0408](https://github.com/synerise/synerise-design/commit/a5b0408fa1953672115e87621a1bfaf9937e6ae0))
### Features
* **subtle-form:** passed and handled error props to the subcomponents ([4a55e05](https://github.com/synerise/synerise-design/commit/4a55e05dba339da52e2b77b38a10c5cff368b421))
# [0.97.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.97.0) (2020-10-06)
### Bug Fixes
* **factors:** fix issues from QA ([018db66](https://github.com/synerise/synerise-design/commit/018db665818b693ffe1765645ea8d8b0acea0016))
* **inline-edit:** delete width from props ([60d9a38](https://github.com/synerise/synerise-design/commit/60d9a38edbc32dda33a8eeb6e5423637e88ebdf1))
* **layout:** fix missing logo in storybook ([0f9685e](https://github.com/synerise/synerise-design/commit/0f9685e3ad10da2d65493d28d0bb82c7effdb00f))
* **navbar:** fix missing logo in storybook ([18f807c](https://github.com/synerise/synerise-design/commit/18f807cc77ffd67f47ae3feed48c65f0e3465ddb))
* **sidebar-object:** add knobs to show icons and folders and fix subtle-form ([fe7f464](https://github.com/synerise/synerise-design/commit/fe7f4648e2e6ee9ded2edcb0e71416d4c74c936d))
* **subtle-form:** allow to define children ([bac3e20](https://github.com/synerise/synerise-design/commit/bac3e20d36f3ce0987507a9f7f7d3ae57c3d59bf))
* **subtle-form:** fixed handling text overflow ([dcd9bb8](https://github.com/synerise/synerise-design/commit/dcd9bb8a792e3feb6fd0e25a5c4ac7779bd39553))
* **subtle-form:** fixed placeholder of the date ([4cd5f5e](https://github.com/synerise/synerise-design/commit/4cd5f5ea6fd6ace2c9c946061d4ec683082840ba))
* **subtle-form:** fixing the build for current date picker version ([ca165cf](https://github.com/synerise/synerise-design/commit/ca165cfb6186fa6155ee9f2fbdf5de45e20c0c5a))
* **tabs:** fix line ounder the counter ([a817fce](https://github.com/synerise/synerise-design/commit/a817fcecb7b97b8ca9a799f2ba9bee36c2358de9))
* **tabs:** fix line ounder the counter ([cf78804](https://github.com/synerise/synerise-design/commit/cf78804b1d84baa4eb30a14d07fb637e2ca4c4b2))
### Features
* **grid:** update grid size on xsmall ([f9bea08](https://github.com/synerise/synerise-design/commit/f9bea08cb5d38212a91d6fb1cb8b49f850bc7a32))
* **layout:** add new Layout examples ([f84da64](https://github.com/synerise/synerise-design/commit/f84da6416cc0516a36be077cdad420ab4e1ec5e7))
* **layout:** add story with fullwidth ([0361f98](https://github.com/synerise/synerise-design/commit/0361f984916ea4c29e717052d1339a0548f315eb))
* **layout:** move Stories to separate category ([78730d6](https://github.com/synerise/synerise-design/commit/78730d6931356a9670351e3bff3a9e6e900b0ade))
* **layout:** update sidebars ([9eeb849](https://github.com/synerise/synerise-design/commit/9eeb849c77d930fbf027fb2404b581a51eca17dd))
* **subtle-form:** added subtle date picker ([a5b5575](https://github.com/synerise/synerise-design/commit/a5b55759f6849a8faefa9c33699cbdd2c16f4a89))
* **subtle-form:** added subtle select base ([13e6d9a](https://github.com/synerise/synerise-design/commit/13e6d9aacb36e1d4e1f9ae6aea163811d238abb6))
* **subtle-form:** added subtle select stories ([694e832](https://github.com/synerise/synerise-design/commit/694e8323154a2e18412998797a4f8ca8eccede67))
## [0.96.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.96.4) (2020-10-05)
### Bug Fixes
* **menu:** control max height by size prop ([d010176](https://github.com/synerise/synerise-design/commit/d010176ac2cffdd27a023c577369fb4c34f9867f))
## [0.96.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.96.3) (2020-10-02)
**Note:** Version bump only for package portal
## [0.96.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.96.2) (2020-09-29)
### Bug Fixes
* **date-range-picke:** added missing translations and texts ([915d846](https://github.com/synerise/synerise-design/commit/915d846916bb90621c83fa954b59cf558a701e5b))
## [0.96.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.96.1) (2020-09-28)
### Bug Fixes
* **sidebar-object:** name of placeholder changed and fix items in dropdown ([367c71d](https://github.com/synerise/synerise-design/commit/367c71d9fc2f998756f5537d6717c06ec47004a7))
* **tabs:** add counter to tabs ([85786ba](https://github.com/synerise/synerise-design/commit/85786ba5cbda5e887b93ff957d93456103676524))
# [0.96.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.96.0) (2020-09-25)
### Bug Fixes
* **card-tabs:** update example in storybook ([77dcb1b](https://github.com/synerise/synerise-design/commit/77dcb1be381d39b25a659a20196a3a2cf0fc3129))
* **condition:** clear selection on change subject/param/operator ([18da9f3](https://github.com/synerise/synerise-design/commit/18da9f378afdf447ad8bc10f149c08e832205f55))
* **condition:** fix stories ([9868e89](https://github.com/synerise/synerise-design/commit/9868e89273306c9f5d47a3b46a4253e0d782748a))
* **condition:** move examples to Filter category ([314ce7e](https://github.com/synerise/synerise-design/commit/314ce7e198fbbe5a4fc864bccd832182d7ae2907))
* **docs:** fix default viewport in storybook ([1302336](https://github.com/synerise/synerise-design/commit/13023362e6a27d3ac976ec817ae09bf40c512f3c))
* **docs:** update docs story ([f5007d7](https://github.com/synerise/synerise-design/commit/f5007d7db83446e682a242588d29663b4c839680))
* **factors:** autofocus on search input ([dd8ec41](https://github.com/synerise/synerise-design/commit/dd8ec41ca45bf98437e24d4ca015b87c9dab00f7))
* **factors:** fix example in storybook ([4e50faa](https://github.com/synerise/synerise-design/commit/4e50faae4375ee74f36aad2d22ba70397bb66bb4))
* **factors:** fix farmula modal, expansible text modal, autocomplete ([92a7e94](https://github.com/synerise/synerise-design/commit/92a7e94af258a9601686d08d63f2317d79ddcfa0))
* **folders:** added an offset to the actions dropdown ([b1de1e0](https://github.com/synerise/synerise-design/commit/b1de1e04740d9f759a81e1f418e1524c6009ae38))
* **folders:** added changed after ux review ([8eb8af6](https://github.com/synerise/synerise-design/commit/8eb8af633b4957017f58b029632a8fa0e1744225))
* **folders:** added max visible items count handling ([2619151](https://github.com/synerise/synerise-design/commit/261915191592b9d3af21fb91521f14bfb16aba51))
* **folders:** fixed bugs with blank space in name ([4616ea4](https://github.com/synerise/synerise-design/commit/4616ea4ee2c2470c5c105064c9b9919a02f5050b))
* **folders:** fixed popover for adding the item ([ad59738](https://github.com/synerise/synerise-design/commit/ad597389d6df473dd10e2006bd2805fe8bf1d85c))
* **folders:** fixed show more and less buttons ([a57b95b](https://github.com/synerise/synerise-design/commit/a57b95b1008145ba99c5b63f06a37f15ac66c44e))
* **folders:** show more and less cmp fixes ([125bae2](https://github.com/synerise/synerise-design/commit/125bae2f4c4dcf71e92448825aa7afdcc503e230))
* **folders:** styling fixes after review ([beb8644](https://github.com/synerise/synerise-design/commit/beb86443e5403769067ceab585647b5595e4ec20))
* **grid:** change grid items size in storybook on 'sm' breakpoint ([bf983e8](https://github.com/synerise/synerise-design/commit/bf983e88f53f3d8ace574c40dbf01d9a7f59af69))
* **grid:** change styles of gridwrapper in storybook ([1da7001](https://github.com/synerise/synerise-design/commit/1da7001c01631d923f039221589ad23bc165a6ee))
* **grid:** fix strorybook example ([3a04820](https://github.com/synerise/synerise-design/commit/3a04820146dc28193b0c522db933053e09ea855f))
* **grid:** fix strorybook example ([b1813d4](https://github.com/synerise/synerise-design/commit/b1813d4efcdd4fd1eb56e050ce7854958c3bee6e))
* **grid:** fix strorybook example ([6a247eb](https://github.com/synerise/synerise-design/commit/6a247ebf71dab9e90b75727cf80f3522f0116c38))
* **inline-edit:** add inline select component ([25ed7c6](https://github.com/synerise/synerise-design/commit/25ed7c6bc01b9557e23378a565e8d091c046eb72))
* **inline-edit:** fix paddings and styles ([87e2a6d](https://github.com/synerise/synerise-design/commit/87e2a6d0f157f4aa532220f5d37eb96055ec1239))
* **modal:** modal stories ([3140fb4](https://github.com/synerise/synerise-design/commit/3140fb480cbea8bc71bf8effb1254279a8c46ecf))
* **operators:** add missing translation in storybook example ([25b31e0](https://github.com/synerise/synerise-design/commit/25b31e0c130bdbbd7e21eeacca8048c1d85582d6))
* **portal:** fix typo in folders stories ([6d18569](https://github.com/synerise/synerise-design/commit/6d1856918f05d5d94869a1f76af6e3f0fac0b037))
* **sidebar-object:** change string in textDescription ([d7328ee](https://github.com/synerise/synerise-design/commit/d7328ee78927ff65e2c8e5d52aa27ab13285af99))
* **sidebar-object:** change width of inline edit and dropdwon styles ([ef224f8](https://github.com/synerise/synerise-design/commit/ef224f861951c65bfe33364fc588520f4e2e56dd))
* **sidebar-object:** delete some knobs and add subtleForm ([b975924](https://github.com/synerise/synerise-design/commit/b9759241d96eae53ec1dd08b8e78ae913880dbe3))
* **sidebar-object:** fix opening dropdowns, fix inline-edits, ([e103f3a](https://github.com/synerise/synerise-design/commit/e103f3a839a140d03cc24ce3a99561f707b10fa1))
* **subtle-form:** fixing the types and build ([92a6212](https://github.com/synerise/synerise-design/commit/92a62126ab9679586e8ec49d8016f9127aa78097))
### Features
* **condition:** add operators ([ceeb0e4](https://github.com/synerise/synerise-design/commit/ceeb0e418812ceb4e895e0285d8ed952cbe8bdd1))
* **condition:** add translations ([4b5735f](https://github.com/synerise/synerise-design/commit/4b5735f46ab221b8fb7db8209ee5baf12857e372))
* **condition:** condition component ([151d0dc](https://github.com/synerise/synerise-design/commit/151d0dc0cf06bb39d9a6e829bcb13a690bd78a79))
* **condition:** init condition component ([6eccc4e](https://github.com/synerise/synerise-design/commit/6eccc4e056fee08ebfced9bd3d47f041cd689a25))
* **docs:** storybook-addon-viewport ([c9c3d16](https://github.com/synerise/synerise-design/commit/c9c3d160622d1e1e250e7c73d1bb76fef13f09b3))
* **factors:** add translations ([253f00c](https://github.com/synerise/synerise-design/commit/253f00c31d022880864c1c0df8cfa5091450dc1c))
* **factors:** init factors component ([d23dc64](https://github.com/synerise/synerise-design/commit/d23dc64cbc17274fa0a27d920eebb6c32924cc02))
* **factors:** withoutTypeSelector mode ([0af0622](https://github.com/synerise/synerise-design/commit/0af0622d6b096cc60445e232bdc43b98d6bd5a99))
* **folders:** added custom filters ([f3a933f](https://github.com/synerise/synerise-design/commit/f3a933f58f34199230e8fddb6effacb3863f9d55))
* **folders:** added delete modal ([9b4732e](https://github.com/synerise/synerise-design/commit/9b4732e21c3fa51b1bd12a3b01bf25241ebd3202))
* **folders:** added folders component ([2a940c5](https://github.com/synerise/synerise-design/commit/2a940c5593e464eb26c7f1d6612a62b74e8542ca))
* **folders:** added sorting by name and favoutire ([09e0770](https://github.com/synerise/synerise-design/commit/09e07701a4c0ede8dbcda0bede48503e7ce2c297))
* **grid:** add example with customizable grid ([e33c580](https://github.com/synerise/synerise-design/commit/e33c58012248b2054dbaf015b2f0b31d06d4d26a))
* **grid:** init component ([b0d07d2](https://github.com/synerise/synerise-design/commit/b0d07d2fff61110909977c85318d2b81ef7ca3d9))
* **grid:** styles, basic example in storybook ([3f873f3](https://github.com/synerise/synerise-design/commit/3f873f335993998d71b305ff3876e129c517999d))
* **grid:** update example in storybook ([ae5c700](https://github.com/synerise/synerise-design/commit/ae5c700e9c3ed1b3607c6481f31b08c6ec6f7dc0))
* **menu:** added handling tags as suffix ([745eb25](https://github.com/synerise/synerise-design/commit/745eb2565429d18aea0933fbda4ce662c3b9eb87))
* **modal:** examples with few footers example ([856c585](https://github.com/synerise/synerise-design/commit/856c585c7f3a9d788c46982dc344d7516140b3df))
* **operators:** add Check Icon for selected operator ([25d4a9b](https://github.com/synerise/synerise-design/commit/25d4a9b0d0151a851b546e752423c5397e0cde58))
* **operators:** add translations ([c422c9a](https://github.com/synerise/synerise-design/commit/c422c9ac57d9d40f09ed245f000e6c66f95f6061))
* **operators:** operators component ([dd6b085](https://github.com/synerise/synerise-design/commit/dd6b08591651f18e68bef9f298efe37e80e346c7))
* **portal:** cleaned up menu item story ([21dedc0](https://github.com/synerise/synerise-design/commit/21dedc0f9648feb0828ae78bfc3c4f0c9aa88eea))
* **search:** added a story with debounce implementation ([71420a7](https://github.com/synerise/synerise-design/commit/71420a77629c7faa247b777314e9279944d48cbb))
* **sidebar-object:** add props checked ([a8c0d1f](https://github.com/synerise/synerise-design/commit/a8c0d1f4b1d77d06575cfb7687ca63c6865ae8c7))
* **sidebar-object:** Added component ([2fcf43a](https://github.com/synerise/synerise-design/commit/2fcf43a01eb84b8e8cbd223f35ba983bb1260294))
* **sidebar-object:** Added component sidebar-object ([be24147](https://github.com/synerise/synerise-design/commit/be24147a2aa12bf7a52ae9f8d25c3fbcbcee6f84))
* **sidebar-object:** Added tests and documentation sidebar-object ([be09267](https://github.com/synerise/synerise-design/commit/be09267373d75fc54cdf2d963c29fbbe4bc5bdb9))
* **sidebar-object:** fix props onChange ([21b815c](https://github.com/synerise/synerise-design/commit/21b815c961dfafdd01d2d1b47105a21fb999df6c))
* **sidebar-object:** resolve problems ([3345703](https://github.com/synerise/synerise-design/commit/3345703e4dc876bb6f4062440aa7bb1db7ba649e))
* **subject:** add subject components ([021fc23](https://github.com/synerise/synerise-design/commit/021fc234a0ec577d8edf9eb0124483ab1fb74369))
* **subject:** add translations ([9d4fadd](https://github.com/synerise/synerise-design/commit/9d4fadda7a242fdb355f4017df162e7005d2d5f8))
* **subject:** add translations ([2533f7a](https://github.com/synerise/synerise-design/commit/2533f7afda34ba302a2f96ac12829b67369b6b7b))
* **subtle-form:** added subtle-form component ([a445ea1](https://github.com/synerise/synerise-design/commit/a445ea184b9414ac51a0adf0a543166e7b2c6491))
## [0.95.6](https://github.com/synerise/synerise-design/compare/[email protected]@0.95.6) (2020-09-18)
### Bug Fixes
* **select:** fix placeholder & search input position ([c7a862e](https://github.com/synerise/synerise-design/commit/c7a862e34ffa837b2dc794353c8f89e1d8b88af9))
## [0.95.5](https://github.com/synerise/synerise-design/compare/[email protected]@0.95.5) (2020-09-01)
### Bug Fixes
* **badge:** fix badge and add padding in count ([f657c7c](https://github.com/synerise/synerise-design/commit/f657c7c78b9e770a455404b8af9f6fb5b88f3b6c))
* **card:** fixed opening card ([1605d54](https://github.com/synerise/synerise-design/commit/1605d547c5bfd2fdacaf8b37dc5bb3127151cb72))
* **switch:** delete error text ([59ada87](https://github.com/synerise/synerise-design/commit/59ada87997e983c1d46c66d371a9d85620fcd139))
* **switch:** fixed focus on switch add validation state, change colors ([acab2ef](https://github.com/synerise/synerise-design/commit/acab2efbfe5a7811e46c36dc9c54baa86d58cc1a))
* **tags:** fix badge in tags and fix text of add button tag ([88648fb](https://github.com/synerise/synerise-design/commit/88648fb38165546596901fbbbe3078d4c89e2896))
## [0.95.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.95.4) (2020-08-27)
### Bug Fixes
* **item-picker:** added virtualization to the dropdown ([5ef7bd9](https://github.com/synerise/synerise-design/commit/5ef7bd90750ce551a78e9797a9e4bdbf849e9b5c))
## [0.95.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.95.3) (2020-08-26)
### Bug Fixes
* **table:** fix stories with expandable tables ([fa0f899](https://github.com/synerise/synerise-design/commit/fa0f8996c65b10c15d850c0fc8ee9d29a0ca2d42))
## [0.95.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.95.2) (2020-08-25)
### Bug Fixes
* **table:** fix onRow handlers ([8e24c2b](https://github.com/synerise/synerise-design/commit/8e24c2b9ae67de26a37a241437dc846e2ebc79d3))
## [0.95.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.95.1) (2020-08-21)
**Note:** Version bump only for package portal
# [0.95.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.95.0) (2020-08-21)
### Bug Fixes
* **card:** fix stories ([1567698](https://github.com/synerise/synerise-design/commit/15676981b32c31c2e16c3faffa99da6ef56b3a76))
* **card-select:** change outline to setBackground fix problem with focus ([88ee5f3](https://github.com/synerise/synerise-design/commit/88ee5f3e4963e62b7e298c6c3b186326d709f820))
* **card-select:** fix focus state, add setbackground with raised state ([241eb56](https://github.com/synerise/synerise-design/commit/241eb560e3109377d28c006ab37f370a827b0efa))
* **card-select:** remove React.Suspense from stories ([80fe6c7](https://github.com/synerise/synerise-design/commit/80fe6c7036bb67928d88d2eee22fc7c54081f8dc))
* **collector:** allow for longer label in story ([a268f97](https://github.com/synerise/synerise-design/commit/a268f979ad318cd303ef2f23bd66766b24801924))
* **input:** added exception for white select ([314d8d4](https://github.com/synerise/synerise-design/commit/314d8d479edb9279f87fc8f4a958ff270865f008))
* **progress-bar:** add to choose color ([9040226](https://github.com/synerise/synerise-design/commit/9040226b5828e78920ea08ccd19f557743ec7f67))
* **progress-bar:** add to choose color ([9481e4f](https://github.com/synerise/synerise-design/commit/9481e4f6a8d25fb3f359c9f2ccbea38b383375fe))
* **select:** fixes for handling classname props ([dbad11e](https://github.com/synerise/synerise-design/commit/dbad11e8d3d50ebdec0a56be23417d4823f3bd75))
* **typography:** fix typography examle in storybook ([669ab95](https://github.com/synerise/synerise-design/commit/669ab95283aef104466f64a5a9dcee3ce69eaac1))
### Features
* **typography:** add missing h5 and h6 elements ([c162f11](https://github.com/synerise/synerise-design/commit/c162f113da6b46c841ddf448d7e1c8e35cfc8457))
## [0.94.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.94.2) (2020-08-18)
### Bug Fixes
* **card-select:** change paddings and fix problem with number columns ([6f8ef67](https://github.com/synerise/synerise-design/commit/6f8ef67b36acf466459f65387a41eb84c60ad62f))
* **collector:** ux review fixes ([fed40a6](https://github.com/synerise/synerise-design/commit/fed40a6929bbbeb0a7021e4bf6abf5755d25b0a7))
* **icon:** update names of stories ([05b92f8](https://github.com/synerise/synerise-design/commit/05b92f815bd7dc7d4f45fe999d08b297cef0ba5a))
* **popconfirm:** update names of stories ([6156d29](https://github.com/synerise/synerise-design/commit/6156d293382c384a471f00375479b60c6da4f5f5))
* **progress-bar:** change to separate knobs of percentage bars ([57a0ec2](https://github.com/synerise/synerise-design/commit/57a0ec295ffcaf883fc1e2d8152149d560e0d8c7))
* **table:** cleanup stories ([f7eca68](https://github.com/synerise/synerise-design/commit/f7eca68994f336f29c098fbdc405cb6eeed730c1))
* **table:** fix expandable story ([7f6f73c](https://github.com/synerise/synerise-design/commit/7f6f73c79000eef4f03da30635e0ffb53b288c65))
* **table:** fix TreeTable styles ([0ccf17b](https://github.com/synerise/synerise-design/commit/0ccf17b936163629903706d04c08568f8198fdb4))
* **tags:** add clear icon, tooltip and fix padding of separator ([7d9a602](https://github.com/synerise/synerise-design/commit/7d9a602ccf52d44516eaa99846c2e86ac1ded8aa))
## [0.94.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.94.1) (2020-08-17)
### Bug Fixes
* **collector:** bump search and input component ([2ce9ca7](https://github.com/synerise/synerise-design/commit/2ce9ca7878d6533d2f19ee0e6fa04bf54e165e5f))
* **date-range-picker:** second ux review changes ([e0bb07b](https://github.com/synerise/synerise-design/commit/e0bb07b783f5eb5db7259d7310211aeaba0ae044))
* **layout:** fixed knobs import in stories ([e3fdb74](https://github.com/synerise/synerise-design/commit/e3fdb743dd50cc7a8abd8a29e93c11b131ce66fb))
# [0.94.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.94.0) (2020-08-12)
### Bug Fixes
* **badge:** change size ant font weight ([32e8053](https://github.com/synerise/synerise-design/commit/32e8053dab8222277721c293a787e73d06838db3))
* **collector:** added nav panel to the dropdown ([854a8ff](https://github.com/synerise/synerise-design/commit/854a8ffd01c522e2765347ca3c6398d62dbf3f2b))
* **tags:** add props overlayStyle and maxHeight ([49eca18](https://github.com/synerise/synerise-design/commit/49eca1836299ebd2db5fd280ab693bef25a3c33b))
* **tags:** change paddings, margins, add scrollbar and add color ([c0ad179](https://github.com/synerise/synerise-design/commit/c0ad179bf194da6940a775e14b832d19e23be563))
### Features
* **collector:** added collector ([d8419b8](https://github.com/synerise/synerise-design/commit/d8419b80cef857d27bdc424cfc2766e6778752ac))
* **collector:** added dropdown with filtering ([1cc8d79](https://github.com/synerise/synerise-design/commit/1cc8d79c2b998ef51437a7c7e73a57d332f64cf7))
* **collector:** added gradient overlay and suggestions filtering ([60647b5](https://github.com/synerise/synerise-design/commit/60647b545c92d693982a0758f156f0847cd3740c))
# [0.93.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.93.0) (2020-08-11)
### Bug Fixes
* **date-range-picker:** changed folder structure to pass the deploy ([b482a9f](https://github.com/synerise/synerise-design/commit/b482a9f5239c77d23aa37bb04502c9b98b61fe78))
* **date-range-picker:** code review changes ([4af8679](https://github.com/synerise/synerise-design/commit/4af867978c0f228266224cbf52183b8e3ac4c693))
* **date-range-picker:** ux review changes and fixes ([53c879d](https://github.com/synerise/synerise-design/commit/53c879d33da85c7399a5ba628a7a87cecba0083c))
* **docs:** remove DataRangePicker from storybook ([54a2930](https://github.com/synerise/synerise-design/commit/54a29304b541b14f08a4bd7e8916fd458415c8a8))
* **file-uploader:** add tooltip to remove icon ([e41fcbf](https://github.com/synerise/synerise-design/commit/e41fcbfa369071dad3ad927e81fdc5f7a57376e5))
* **switch:** add switch with description and text ([5b8bbee](https://github.com/synerise/synerise-design/commit/5b8bbee9d988239e58ba736f96d27f21c3518f41))
* **switch:** delete prop error ([08fd8e7](https://github.com/synerise/synerise-design/commit/08fd8e7b96aa7c2ba0d502d2f51b678e4fa376b3))
### Features
* **icon:** add folder-favourite icons, upadate config of svgr ([6eb30d3](https://github.com/synerise/synerise-design/commit/6eb30d39e38a25ec2bdb062b96037c92490b3adf))
* **icon:** add L & XL icons ([4705eb4](https://github.com/synerise/synerise-design/commit/4705eb48318e520ff7604773a45162ce43734ee0))
## [0.92.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.92.2) (2020-08-07)
### Bug Fixes
* **file-uploader:** change name,background color to white,add active state to uploader ([67e6a4b](https://github.com/synerise/synerise-design/commit/67e6a4b6e52ea3f751dc7dd7b09c78dc5a7c79df))
* **input-number:** changed story ([6eff009](https://github.com/synerise/synerise-design/commit/6eff009b156926cb0236cabb436ace52efc1c7c5))
* **menu:** added an option to highlight selected item ([394904d](https://github.com/synerise/synerise-design/commit/394904db36366ce6f3d966b61c80a09c1b7c7834))
* **menu:** changes in stories ([35d069c](https://github.com/synerise/synerise-design/commit/35d069c463d4396b98cc24085af05e0a53d7cc0e))
* **menu:** code review changes ([54fe83e](https://github.com/synerise/synerise-design/commit/54fe83e2e5809efd1ef3c1dea677aa744aca0c62))
* **menu:** removed unused code from story ([3f46f85](https://github.com/synerise/synerise-design/commit/3f46f85abf7771791cadd7afebbfbe910ccf345b))
* **menu:** reverted the way of displaying stories ([ec622d7](https://github.com/synerise/synerise-design/commit/ec622d71d161efaf58e44ae68b1213be7802a315))
* **menu:** started preparing a story ([62caecc](https://github.com/synerise/synerise-design/commit/62caecca3dd7de635178292a5d6bc4a6cde8c847))
* **progress-bar:** add component multivalue Bar and add option to change colors ([2e6bb48](https://github.com/synerise/synerise-design/commit/2e6bb48ca9cf1b8b0c5edfa61f9282e5968a88a1))
* **progress-bar:** delete text indent and text showing percent of bar ([0a76c18](https://github.com/synerise/synerise-design/commit/0a76c18d8436d81bfdaffa1766738333f7c2d56b))
* **table:** add avatarAction, ellipsis and maxWidth props to AvatarLabel ([c542292](https://github.com/synerise/synerise-design/commit/c5422927b7b88b6eff7c73a53a2bb5187ca601b5))
## [0.92.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.92.1) (2020-08-05)
### Bug Fixes
* **items-roll:** allow to render suffixel passed from items ([5dcdec6](https://github.com/synerise/synerise-design/commit/5dcdec6691c93ed880f8a7f9ad51114d9c5f920a))
# [0.92.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.92.0) (2020-08-05)
### Bug Fixes
* **input-number:** added input number into input group story ([ff27946](https://github.com/synerise/synerise-design/commit/ff27946fc328fd401f24b45f9ed99dec523a4734))
* **menu:** changed the submenu story - ordered knobs ([e1d57af](https://github.com/synerise/synerise-design/commit/e1d57afab4b4e0498534abcb7d4dcff713e77808))
* **table:** improve TreeTable performance ([59e58a2](https://github.com/synerise/synerise-design/commit/59e58a234c3a9cb3505da65aaaf9d1313105f023))
### Features
* **popconfirm:** add examples of withDescription and withImages ([03a7a64](https://github.com/synerise/synerise-design/commit/03a7a64f8340cef5bc755876afe661fa7e326860))
* **popconfirm:** add new types of popconfirm ([0f20892](https://github.com/synerise/synerise-design/commit/0f20892afde63b81644ff24e94d22d1fb8c8bbd3))
# [0.91.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.91.0) (2020-08-04)
### Bug Fixes
* **card:** add prop and add some fixes ([eeb2a77](https://github.com/synerise/synerise-design/commit/eeb2a77ed0a7edd892955b1f9bec6257d1038079))
* **card-select:** add cards and add group of cards ([28a6875](https://github.com/synerise/synerise-design/commit/28a687531cf3d3b35892acbf83308b923f034a1f))
* **card-select:** add cards and add improvments to them ([0e7412c](https://github.com/synerise/synerise-design/commit/0e7412cc91001d3be98ecbed3067db13bdd55cfb))
* **card-select:** add group of cards and group of small cards ([c5b82af](https://github.com/synerise/synerise-design/commit/c5b82af8b416935431909507d0611f8778455097))
* **card-select:** add group of cards and group of small cards ([8b8547c](https://github.com/synerise/synerise-design/commit/8b8547cabbca6b5e05ff16e35d196e9f9eedc3f5))
* **card-select:** add smallcard and with no icon card ([b1fdd41](https://github.com/synerise/synerise-design/commit/b1fdd4185d89d86dcbecbc32ee241201fd5afefb))
* **date-range-picker:** adjusting styles to the zeplin preview ([a9068b4](https://github.com/synerise/synerise-design/commit/a9068b4069ebce86eab0dc2a01b368a9e0c7215a))
* **result:** fix modal sizes ([95fc999](https://github.com/synerise/synerise-design/commit/95fc999826bff83c7f0d9ff12fd00f6720c96a97))
* **sidebar:** change width to 338px ([666de42](https://github.com/synerise/synerise-design/commit/666de42b4fce670e573d40651cb66c4311204510))
### Features
* **input:** add ds-scrollbar into textarea ([3cf7e6e](https://github.com/synerise/synerise-design/commit/3cf7e6e1aa0d11846c3db296ce081f2bef4948b0))
# [0.90.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.90.0) (2020-07-31)
### Bug Fixes
* **card-tabs:** fix issues from ux review ([92b0ea5](https://github.com/synerise/synerise-design/commit/92b0ea5d5288c272830c543e54d253c2c94decd6))
### Features
* **time-picker:** added seperators when using am pm mode ([609f237](https://github.com/synerise/synerise-design/commit/609f23795b4708e4fe6797a8743ad501caa8f4fc))
* **time-picker:** added support for am pm clock modes ([0c79bb0](https://github.com/synerise/synerise-design/commit/0c79bb018f3615569449fe958a94eafcc5065a4e))
## [0.89.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.89.3) (2020-07-30)
### Bug Fixes
* **card-tabs:** add colors props for cards ([fa30e77](https://github.com/synerise/synerise-design/commit/fa30e773832ad9cd3c342d4fd4aca8d9b326e2b4))
* **card-tabs:** add storybook example with single card-tab ([6e4b9e0](https://github.com/synerise/synerise-design/commit/6e4b9e042063f3164148836a827877dddf195294))
* **card-tabs:** fix styles ([59c4d02](https://github.com/synerise/synerise-design/commit/59c4d0242417982ff1eaacbef1e8d784b64ce01f))
## [0.89.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.89.2) (2020-07-29)
### Bug Fixes
* **date-range-picker:** added dropdown ([76f5360](https://github.com/synerise/synerise-design/commit/76f53602c65e2278add32d04bf31aaaca9259a3a))
* **date-range-picker:** added handling undefined values ([65c6241](https://github.com/synerise/synerise-design/commit/65c6241df9274c7457e9891683dab725f16427ad))
* **date-range-picker:** added input component ([f13bd69](https://github.com/synerise/synerise-design/commit/f13bd69d8bfde0b95fca14e09c568f6d6fbbc178))
* **input-number:** added 'raw' props in order to use inputgroup ([6b8a8cc](https://github.com/synerise/synerise-design/commit/6b8a8ccd32ab771cdd015e7572948a403be39c71))
* **pagination:** fix pagination component ([a563e0d](https://github.com/synerise/synerise-design/commit/a563e0d00f107ab0a6bd8edb712cb9217a3c48b2))
## [0.89.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.89.1) (2020-07-28)
### Bug Fixes
* **date-picker:** use start of the day in story ([979b7db](https://github.com/synerise/synerise-design/commit/979b7db6834efe87cbc60098a8ad7b002a9a9908))
* **search:** add onClear prop and update tests and stories ([4de9259](https://github.com/synerise/synerise-design/commit/4de9259b245a49d7821036b3bb05918559c1b900))
# [0.89.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.89.0) (2020-07-24)
### Features
* **app-menu:** add AI Search to example menu ([6f5fcc5](https://github.com/synerise/synerise-design/commit/6f5fcc552358d207bde3179bafa338c4721e3501))
## [0.88.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.88.2) (2020-07-24)
### Bug Fixes
* **card:** change react fragment to div ([62f4dc0](https://github.com/synerise/synerise-design/commit/62f4dc08d127e816c3cb16115b8ef5a93b25ce25))
* **search:** fix blank list while scrolling ([b2ac6c1](https://github.com/synerise/synerise-design/commit/b2ac6c1c8f67aa18332a4b61cceca1ffedf1c393))
* **sidebar:** add padding ([e1491d0](https://github.com/synerise/synerise-design/commit/e1491d0fcfef8cb7c4d4e23a8e6fdaf881362eb1))
* **table:** fix example on card ([691eaf4](https://github.com/synerise/synerise-design/commit/691eaf4115e132a4749e2831c068472f39745953))
## [0.88.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.88.1) (2020-07-22)
### Bug Fixes
* **time-picker:** added a scroll to selected functionality ([9b326ad](https://github.com/synerise/synerise-design/commit/9b326ad6af56485710ab810db679ac45e857b34d))
# [0.88.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.88.0) (2020-07-22)
### Bug Fixes
* **button-group:** change styles of focused button ([152b78d](https://github.com/synerise/synerise-design/commit/152b78db8beda2b2b6c6ba3057d8d2bc39ab63e8))
* **card:** add animation to cards openning ([e6d541c](https://github.com/synerise/synerise-design/commit/e6d541cfda8b5fac256b45e9b7e28ba5d1f87272))
* **items-roll:** fix search clear on grouped example ([250592f](https://github.com/synerise/synerise-design/commit/250592f30f62760993c0a5dbe043663b9b636d95))
* **search:** code review changes ([03c7c7e](https://github.com/synerise/synerise-design/commit/03c7c7e2bd81886070b7d36f44e921ccd1c45bb2))
* **search:** reset scrollTop after clear and select ([827fa73](https://github.com/synerise/synerise-design/commit/827fa73b5dc8f1c6f81ba4df18d61f6b95e694f3))
* **search:** wIP: search performance ([5939748](https://github.com/synerise/synerise-design/commit/593974890d25feca19028387a2565cf11ba3447b))
### Features
* **avatar:** add ProductAvatar component ([8a49086](https://github.com/synerise/synerise-design/commit/8a49086f03c12fe3a86cd1c490b77de6517dddc0))
# [0.87.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.87.0) (2020-07-21)
### Bug Fixes
* **item-picker:** fix withChangeConfirmation prop ([5f92aba](https://github.com/synerise/synerise-design/commit/5f92aba4e3f094bbfde70f5afe128f090dd13c6a))
* **manageable-list:** changed a story ([30e6374](https://github.com/synerise/synerise-design/commit/30e6374a4073c462bbc65f2a929b7ec763c88c02))
* **search:** add onClear prop and update tests and stories ([ded5385](https://github.com/synerise/synerise-design/commit/ded53857c3c55cd87e06c2038ccf1f6926b12b28))
* **sidebar:** change background styles ([e62be74](https://github.com/synerise/synerise-design/commit/e62be74c0657bacfc049c96419c6f1a2cdd24471))
### Features
* **file-uploader:** read and return content of .txt files ([465fae1](https://github.com/synerise/synerise-design/commit/465fae1b1c8590d654b9fc1c78b3afc49b130f7f))
## [0.86.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.86.1) (2020-07-20)
### Bug Fixes
* **search:** add onClear prop and update tests and stories ([c11b557](https://github.com/synerise/synerise-design/commit/c11b5578ef72ec5928f90416be09b74e7036e889))
# [0.86.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.86.0) (2020-07-20)
### Bug Fixes
* **button:** add styles to secondary button and move to button component ([efdea0b](https://github.com/synerise/synerise-design/commit/efdea0bd18d1089370632a282aba72aafe29d037))
* **button:** add styles to secondary button and move to button component ([b62da4c](https://github.com/synerise/synerise-design/commit/b62da4ce88727f370b5c0cb051828386fabb55d1))
* **button-group:** add option and contentbuttons add to button component ([2cc2aad](https://github.com/synerise/synerise-design/commit/2cc2aadead2b4bbe8931b8d6f61933e4ec464e9b))
* **button-group:** add option and contentbuttons add to button component ([e54559e](https://github.com/synerise/synerise-design/commit/e54559eda6d5f569d643b5e97ea218d9a36c99bc))
* **date-picker:** changes after ux review ([eecf99b](https://github.com/synerise/synerise-design/commit/eecf99b492e5f9fc8fa20e1d060e04240aa11704))
* **date-picker:** changes after ux review ([ac339ae](https://github.com/synerise/synerise-design/commit/ac339ae930e4367df55d79b14847a8c95958b349))
* **manageable-list:** fixing the build ([99c8182](https://github.com/synerise/synerise-design/commit/99c81829a6ec6571d20f7f0a6aa3c7ec20fd4637))
* **manageable-list:** fixing the build ([f3aae83](https://github.com/synerise/synerise-design/commit/f3aae83f478557d49a858049b9830d950a27ff82))
* **manageable-list:** trying to steer expanded items from outside ([828b296](https://github.com/synerise/synerise-design/commit/828b296af9fe0460b2ba5f400086b5db1bc606f4))
* **manageable-list:** trying to steer expanded items from outside ([b55f888](https://github.com/synerise/synerise-design/commit/b55f888a45cf7564f13e966dac2c77f5959aecf0))
* **sidebar:** change name ([3c7a85a](https://github.com/synerise/synerise-design/commit/3c7a85aec218562bb66a7c25812b7c8a664e9786))
* **sidebar:** change name ([540d31c](https://github.com/synerise/synerise-design/commit/540d31c3a85d2477b1dae4eadb554280c108c499))
* **table:** grouped table data ([509f751](https://github.com/synerise/synerise-design/commit/509f7512ebe4cadc7030a2466a58d2d7f9c11724))
* **table:** grouped table data ([6bcf5dc](https://github.com/synerise/synerise-design/commit/6bcf5dcac8916c668b6f53071a920bf517165653))
* **table:** VirtualTable improvements ([e20a17c](https://github.com/synerise/synerise-design/commit/e20a17cd95751d3f5d091a6d5f84c3be671a5a5a))
* **table:** VirtualTable improvements ([3a2c3cd](https://github.com/synerise/synerise-design/commit/3a2c3cd02f5057201d6ce62d34cfe7cc29e07a3d))
* **tags:** changes in styles and add SearchM Icon to dropdown ([b219a65](https://github.com/synerise/synerise-design/commit/b219a65d14331dda3ca76056fdcbfba673c09449))
* **tags:** changes in styles and add SearchM Icon to dropdown ([e15d3ba](https://github.com/synerise/synerise-design/commit/e15d3baf2de61940bdae8ed27d1894e107d8c80e))
### Features
* **date-picker:** move story to pickers category ([5717e34](https://github.com/synerise/synerise-design/commit/5717e34c70e90646e1787a420155178c2584e62b))
* **date-picker:** move story to pickers category ([03aea34](https://github.com/synerise/synerise-design/commit/03aea34df3260b7592fc57622627dbd412609861))
* **date-range-picker:** move story to pickers category ([9214f6a](https://github.com/synerise/synerise-design/commit/9214f6a931549cf439cba91faf6398999a6ce7f8))
* **date-range-picker:** move story to pickers category ([8ea6f2a](https://github.com/synerise/synerise-design/commit/8ea6f2ab0cc82dc56c43020f101ca58124934a26))
* **icon:** add a/b-test and chart-pie icons ([a68a934](https://github.com/synerise/synerise-design/commit/a68a934ee82d85ae6bae5a417df3e54cb02e719d))
* **icon-picker:** move story to pickers category ([5d78149](https://github.com/synerise/synerise-design/commit/5d7814910d430804756223bcd8021234c38ce13d))
* **icon-picker:** move story to pickers category ([f60750e](https://github.com/synerise/synerise-design/commit/f60750e8e1a47d1fb9364f54d2a4e58d899b000c))
* **item-picker:** move story to pickers category ([a4823bd](https://github.com/synerise/synerise-design/commit/a4823bd10fa18da6945ad58b4c051a9b2892802f))
* **item-picker:** move story to pickers category ([894162a](https://github.com/synerise/synerise-design/commit/894162af2a3110e2becd0435c48db63b7f119116))
* **time-picker:** move story to pickers category ([9873a50](https://github.com/synerise/synerise-design/commit/9873a50b827f888844bdcd568ab0cb96ab62340e))
* **time-picker:** move story to pickers category ([5129305](https://github.com/synerise/synerise-design/commit/51293056ab972ed756009192b447d2f3554253be))
### Performance Improvements
* **manageable-list:** prevent often rerender ([2917107](https://github.com/synerise/synerise-design/commit/2917107b104f05d0d4430898bb1b82a22a91a9b9))
* **manageable-list:** prevent often rerender ([4272aa8](https://github.com/synerise/synerise-design/commit/4272aa80ca0f1cd5505ad297f9a0f69461955057))
## [0.85.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.85.3) (2020-07-17)
### Bug Fixes
* **search:** add single scroll for dropdown list ([f5e6700](https://github.com/synerise/synerise-design/commit/f5e67006052931166bfd3684c2d49128f9b3ac5c))
## [0.85.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.85.2) (2020-07-16)
### Bug Fixes
* **button:** add example with custom label ([30c8147](https://github.com/synerise/synerise-design/commit/30c81479e35928ac3bc0e3d34cc41c978bb23788))
* **description:** add missing ':' in example labels ([c37c268](https://github.com/synerise/synerise-design/commit/c37c268e0e578e4b005f2e3202699a60ec128a34))
* **items-roll:** fix searchClear ([024327d](https://github.com/synerise/synerise-design/commit/024327dd71b0907aa9348a64fc04c3d18aab7c05))
* **table:** fix expandable rows selecetion ([4c1c045](https://github.com/synerise/synerise-design/commit/4c1c0454fb89350c387ecaf28afae51d2ee1f783))
* **table:** on change selection callback ([0eabab4](https://github.com/synerise/synerise-design/commit/0eabab4ffc29893a3b8dd552ea7af619431fdc73))
## [0.85.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.85.1) (2020-07-15)
### Bug Fixes
* **search:** add hideLabel prop ([5d81d7a](https://github.com/synerise/synerise-design/commit/5d81d7ac6d4dc81b07de52a2343641ea34c2431b))
# [0.85.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.85.0) (2020-07-15)
### Bug Fixes
* **badge:** add badge only with outline white ([e7a6a72](https://github.com/synerise/synerise-design/commit/e7a6a7234a8643bd5bfa416ba68c8155c2a912d4))
* **badge:** chande styles of badge ([6dcb6c0](https://github.com/synerise/synerise-design/commit/6dcb6c0672b9ef8eb486e5b133136d0d2a073651))
* **card:** add option to show content of header ([dd7f20b](https://github.com/synerise/synerise-design/commit/dd7f20b5d38fe7ac9f37caf9a4fc4a35a8b4a2c1))
* **checkbox:** add `hasError` knob in group example ([69b5ee3](https://github.com/synerise/synerise-design/commit/69b5ee320f5dc6f32e168f3598f7d0e515aa562d))
* **checkbox:** fix styles ([ffcf6bc](https://github.com/synerise/synerise-design/commit/ffcf6bc7f3aa408c08e2fa319b358209baafa091))
* **date-picker:** changed icons, added placeholder ([b0bfd4a](https://github.com/synerise/synerise-design/commit/b0bfd4ab421634cb73eca4efc0701979a76029d3))
* **date-range-picker:** added missing components ([0c843ed](https://github.com/synerise/synerise-design/commit/0c843edca3cc9b94cc81d14e9ef60265408bb938))
* **date-range-picker:** added next chunk of types ([a7768ab](https://github.com/synerise/synerise-design/commit/a7768abbc706838f0643bd9ef8eb654d6d269ab4))
* **date-range-picker:** added partial types ([8de6c4f](https://github.com/synerise/synerise-design/commit/8de6c4ffe2e9de9dfc2c825e94158e0941c8c048))
* **date-range-picker:** added partial types ([bc9baa8](https://github.com/synerise/synerise-design/commit/bc9baa876c551429570674f581a269f849d4332e))
* **description:** update exmples ([7f85231](https://github.com/synerise/synerise-design/commit/7f85231036c33a41749de719b7580ca5f10e06f2))
* **description:** update stories, fix styles ([ebd1294](https://github.com/synerise/synerise-design/commit/ebd129411b6023fc940ed207f6a3da5e0cc32c17))
* **item-picker:** update example in storybook ([6cb8541](https://github.com/synerise/synerise-design/commit/6cb85415ac92a5c1e944ecbf01e6adcd7739d4b1))
* **menu:** added highlight of selected items, fixed rotating arrow ([60ff840](https://github.com/synerise/synerise-design/commit/60ff840d00a995c646d673cb3650ebe4737d983c))
* **menu:** changed styles of stories to disable selectable ([17cc250](https://github.com/synerise/synerise-design/commit/17cc250ce66d82be5ce72c7e3c26de40d9a8eae1))
* **navbar:** change to ghost white button ([7ff3f89](https://github.com/synerise/synerise-design/commit/7ff3f89a0d904bf26111032ac7d18e93747fc645))
* **search:** add text and filter dynamic keys for search objects ([8780b1e](https://github.com/synerise/synerise-design/commit/8780b1e49183f878d227d074134e80726010a845))
* **search:** add text config for lookup keys ([53ee393](https://github.com/synerise/synerise-design/commit/53ee393c1c39ba4a6f33c84f46276b8f24af3b9b))
* **sidebar:** change styles and add block to sidebar component ([354b2f0](https://github.com/synerise/synerise-design/commit/354b2f0a47cb143181935bb51ed91bc1daac2105))
* **tags:** add badge to preffix and suffix to tags ([83c0a30](https://github.com/synerise/synerise-design/commit/83c0a302a8947c8f81642a7463d1eaf0f81e428b))
### Features
* **date-range-picker:** added footer to the top picker ([aed4748](https://github.com/synerise/synerise-design/commit/aed4748cbac71bd8cc2e34f075e2acdb0771f10c))
* **date-range-picker:** resolved storybook start issues ([1a4a45e](https://github.com/synerise/synerise-design/commit/1a4a45ea3a08556dfcc3a01710b267ee916a59d0))
* **description:** add Description component ([6b91fde](https://github.com/synerise/synerise-design/commit/6b91fdefe64632c57378c1391ca7ceacb74404ea))
## [0.84.6](https://github.com/synerise/synerise-design/compare/[email protected]@0.84.6) (2020-07-15)
### Bug Fixes
* **search:** update width of input and update tests ([0305e65](https://github.com/synerise/synerise-design/commit/0305e65143caf5d6ea7ae256916d1d5e849f7d8f))
## [0.84.5](https://github.com/synerise/synerise-design/compare/[email protected]@0.84.5) (2020-07-13)
### Bug Fixes
* **search:** add minor fixes ([c7bbfd4](https://github.com/synerise/synerise-design/commit/c7bbfd491e70b652710ac91fb5f0999a94370717))
## [0.84.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.84.4) (2020-07-13)
**Note:** Version bump only for package portal
## [0.84.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.84.3) (2020-07-09)
### Bug Fixes
* **item-picker:** update example in storybook ([e1039a6](https://github.com/synerise/synerise-design/commit/e1039a60cdaf21ea352c7ab6cf26ec980323f4c4))
* **navbar:** add changes to suffixel ([7292a86](https://github.com/synerise/synerise-design/commit/7292a867cec0d834d0b2aff822eed99c0ae22527))
* **navbar:** add logo,button,avatar and changed icons ([412fc35](https://github.com/synerise/synerise-design/commit/412fc35d0330e9d060beec381cd5329a4ea0094f))
## [0.84.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.84.2) (2020-07-08)
### Bug Fixes
* **menu:** added option to disable ordering within submenu ([db6e97c](https://github.com/synerise/synerise-design/commit/db6e97c3803e8c6f9c9fa57185d74ab39ffb5c1b))
## [0.84.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.84.1) (2020-07-07)
### Bug Fixes
* **table:** fix columns prop types, add default layoutType ([568f9c2](https://github.com/synerise/synerise-design/commit/568f9c2aa77369f12170b50c30d2dd5a4352235b))
* **table:** fix onModal example ([37fade2](https://github.com/synerise/synerise-design/commit/37fade237a86cb233917c7c87d1fb227806e87d4))
# [0.84.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.84.0) (2020-07-07)
### Bug Fixes
* **badge:** add status with avatar and change styles in status ([16fff63](https://github.com/synerise/synerise-design/commit/16fff635890d7a7874f62a1d168f63d292f00bb9))
* **badge:** separate components flag with and add changes to badge ([1e0fabb](https://github.com/synerise/synerise-design/commit/1e0fabbeb4092106c7f7572ac159bc90cf620c39))
* **date-picker:** imporvements after ux review ([14caed8](https://github.com/synerise/synerise-design/commit/14caed88e2fdfba5380cd2319f12214a7a661550))
* **navbar:** change colors to pallet 600 and delete children navbar ([5fd7287](https://github.com/synerise/synerise-design/commit/5fd7287f0940040fd9b7a1dc5aaf6e5f01d17dc8))
* **navbar:** change colors to pallet 600 and delete children navbar ([7dce5ec](https://github.com/synerise/synerise-design/commit/7dce5ece862493a14c7182f64d7f53ea1fc8c8b8))
* **tags:** change names ([38e067c](https://github.com/synerise/synerise-design/commit/38e067c22fe2232359f782d02ebca6ce2dc2be60))
* **tags:** change size and margin of image ([89ba1d2](https://github.com/synerise/synerise-design/commit/89ba1d2556be269217a63c00c6a1a9b39376d332))
### Features
* **avatar-group:** add Modal with details about users ([4846398](https://github.com/synerise/synerise-design/commit/48463982030f2910bc8f841efd6482c456997241))
* **item-picker:** ItemPicker example in Storybook ([cbd7ecd](https://github.com/synerise/synerise-design/commit/cbd7ecdd9f724bf2a0798b18d937ab4854771d2d))
* **item-picker:** update ItemPicker example ([abfc753](https://github.com/synerise/synerise-design/commit/abfc753f6884dccca953d2eeffcf67cfe6618345))
* **item-picker:** update storybook example ([cf242e4](https://github.com/synerise/synerise-design/commit/cf242e49783099f0dd3864e4691da8af96fda3a2))
# [0.83.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.83.0) (2020-07-02)
### Bug Fixes
* **input:** change styles of labels ([0095789](https://github.com/synerise/synerise-design/commit/00957892877a5ba243a522c9faebf400fd740c33))
* **input:** changed story with prefixes ([48f90e8](https://github.com/synerise/synerise-design/commit/48f90e83ae5890b5a46edcc5b37428056e7270c1))
* **input:** set max length ([fd96438](https://github.com/synerise/synerise-design/commit/fd96438b60781c5d1321b61dcf827c3256931277))
* **input:** set max length and add knobs ([8467443](https://github.com/synerise/synerise-design/commit/8467443c453d99f0fc7227d0b5e603920bbf375d))
* **items-roll:** move examples to ItemsRoll section ([064250b](https://github.com/synerise/synerise-design/commit/064250b545b0ae3dd9c77a26b0b2e920068d4520))
* **menu:** added new story - with flags ([81622d5](https://github.com/synerise/synerise-design/commit/81622d59d19f34e30c4d1f33e199d885bd2ae626))
* **select:** changed texts ([28521e0](https://github.com/synerise/synerise-design/commit/28521e01fed7054f0baebcac76b3cdbcf9b06cd7))
* **select:** prefix and suffix stories fix ([32df241](https://github.com/synerise/synerise-design/commit/32df241c6127a8377e82ce5d763bec8bcebc68a8))
* **table:** fixed columns scrollable ([96a1712](https://github.com/synerise/synerise-design/commit/96a1712a02b9d3398f7986c64fcd9a06afee98ff))
* **table:** remove unused knobs from expandableVirtualTable ([6a886bb](https://github.com/synerise/synerise-design/commit/6a886bb0c6d89935a27a3edf48257c78b33be41e))
* **tags:** add changes to tags ([1d40b1f](https://github.com/synerise/synerise-design/commit/1d40b1fc37fb62d308007b567e58442a1170ff5f))
* **tags:** change tags into separate components and improve tags ([c319f5c](https://github.com/synerise/synerise-design/commit/c319f5c41eb05dffcefa4764d3d98b67d53f40f4))
### Features
* **table:** update default texts ([4fdb1b0](https://github.com/synerise/synerise-design/commit/4fdb1b0252f9445a12872cc7b16b0c3844238bd8))
# [0.82.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.82.0) (2020-06-29)
### Bug Fixes
* **card:** remove size prop, fix header styles ([2bc7e75](https://github.com/synerise/synerise-design/commit/2bc7e758df5531fc76d12937be62c2cc9b31e8ef))
### Features
* **table:** remove unused selection type ([522d874](https://github.com/synerise/synerise-design/commit/522d8742108b80c13e507e9fbe66e9c7e93830fc))
# [0.81.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.81.0) (2020-06-26)
### Features
* **table:** keep order of selection menu items ([a236e3a](https://github.com/synerise/synerise-design/commit/a236e3ae57d3daf84be8c7ffbfb5370a5d857f52))
# [0.80.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.80.0) (2020-06-26)
### Features
* **flag:** render flag as svg elemenet instead of img ([acce388](https://github.com/synerise/synerise-design/commit/acce38848668d8d2f1e02858fb373a9deb3414c1))
# [0.79.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.79.0) (2020-06-25)
### Bug Fixes
* **input:** added component Value and add improvments to inputs ([95d12b0](https://github.com/synerise/synerise-design/commit/95d12b00862aa384b16f2ff25a6e49eacf9b4bae))
* **input:** change styles of label in select, autocomplete ([5d17d08](https://github.com/synerise/synerise-design/commit/5d17d081b069e51bd8ff3ec721f92e5b1b1e64ae))
* **input:** change styles of labels ([ff97fd5](https://github.com/synerise/synerise-design/commit/ff97fd5a7953c9f625dcd51542201ca0c0154af4))
* **input:** change styles of labels ([7bc789f](https://github.com/synerise/synerise-design/commit/7bc789f03fe427eb0c4723ac06ef3d91dedea5b3))
* **input:** changed prefix rendering in stories ([cedd8aa](https://github.com/synerise/synerise-design/commit/cedd8aa3c5330935786bbe9df8c84c279191838d))
* **select:** resolving conflicts ([fe70f69](https://github.com/synerise/synerise-design/commit/fe70f69121e91bd871887aac395ae4ac5fdb8d24))
* **table:** fix example with expandable table ([35ecd57](https://github.com/synerise/synerise-design/commit/35ecd57614444a1082a0ddd238291890d6184d66))
### Features
* **table:** add support for expandable rows in virtualtable ([0a71ec9](https://github.com/synerise/synerise-design/commit/0a71ec9e3180446d2c91e66db783b8a51c2f8c7f))
* **table:** expandable row in virtual table ([b8ee297](https://github.com/synerise/synerise-design/commit/b8ee2970b88a15281198f08e9f6c6949e42c6b1f))
* **table:** expandable vitrualized table ([189a0d8](https://github.com/synerise/synerise-design/commit/189a0d8aaddef5e2ffc6bc7d1c487a90e7371943))
# [0.78.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.78.0) (2020-06-25)
### Bug Fixes
* **date-picker:** added input to the story ([69b3e19](https://github.com/synerise/synerise-design/commit/69b3e1945f06e377295d75fbe4aae8334fab784f))
* **date-picker:** added shortcut button for setting the current date ([5eee270](https://github.com/synerise/synerise-design/commit/5eee270e6902c3e15ca08d70c2f848d6e07ca632))
* **date-picker:** added typing for most of the elements ([6f345c7](https://github.com/synerise/synerise-design/commit/6f345c774d17b277266be257cffed009935279c7))
* **date-picker:** next types resolved ([4d5a6b0](https://github.com/synerise/synerise-design/commit/4d5a6b0a3b1f19e58cf71ff8150fa9e93245568b))
* **date-picker:** put picker into dropdown ([1b86143](https://github.com/synerise/synerise-design/commit/1b86143840f92485e6d48fa2d6ad720abc766b7b))
### Features
* **card:** change default background type ([cccf491](https://github.com/synerise/synerise-design/commit/cccf491877fe8d004c36c472bf5cdc58bc6b407a))
* **date-picker:** moved components from snrs-components ([06283ba](https://github.com/synerise/synerise-design/commit/06283ba3b8d61bd363126420a21b40ade15a547e))
* **table:** add headerButton to pass button in TableHeader ([1bb613a](https://github.com/synerise/synerise-design/commit/1bb613a3c674b5238d8d87bd9a4040a2aca6ef40))
* **table:** add hideGroupExpander & initialGroupsCollapsed props ([b57243b](https://github.com/synerise/synerise-design/commit/b57243bbb9f184a808221ee405f75b3e309d9f5e))
## [0.77.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.77.2) (2020-06-24)
### Bug Fixes
* **input:** added component input multivalue ([5a4c202](https://github.com/synerise/synerise-design/commit/5a4c2024c7ef9d9cb1e9e3cbc3f8faa6e3874ac4))
## [0.77.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.77.1) (2020-06-24)
### Bug Fixes
* **card:** icon position in compact header ([2f27275](https://github.com/synerise/synerise-design/commit/2f27275b7cbef9f53e2b682e0af1fd80197e9ea4))
* **card:** remove unused import ([06a1c9c](https://github.com/synerise/synerise-design/commit/06a1c9ca8f9c8bdf6f230ec8df9f96f6c3524216))
* **select:** added padding for prefix addon ([426e097](https://github.com/synerise/synerise-design/commit/426e097b62d30d27371bb0fba76cecdd2e0f01ee))
* **select:** changed multiselect story ([05da2d9](https://github.com/synerise/synerise-design/commit/05da2d93a2d7db18d45a6999697424746f548703))
* **tabs:** fix uniqe keys for hidden tabs ([ea01761](https://github.com/synerise/synerise-design/commit/ea01761af0292c9eb2950bbc0b407abf8525603c))
# [0.77.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.77.0) (2020-06-22)
### Bug Fixes
* **table:** fix filter in grouped example ([3165ddf](https://github.com/synerise/synerise-design/commit/3165ddf3348eba305d4d99034c3024e23fedd535))
* **table:** fix style of sorted & fixed columns ([50ddc44](https://github.com/synerise/synerise-design/commit/50ddc449a4451924db6a9219003aba2c2be0c186))
### Features
* **table:** add example of custom selection to all stories ([ba09d78](https://github.com/synerise/synerise-design/commit/ba09d781db1a632b86affd4ea2515596bf2a189c))
# [0.76.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.76.0) (2020-06-22)
### Bug Fixes
* **alert:** change hue of text from 700 to 600 except success and warn ([6db002f](https://github.com/synerise/synerise-design/commit/6db002fe7397be14be7694d0a01001ef69d8b6e2))
* **input:** fix styles and add validation with knobs and focus to inputs ([88b80a1](https://github.com/synerise/synerise-design/commit/88b80a11eeb5331909309fb5f6d30d1ea7725e25))
* **input-number:** fix styles, add validation with knobs,focus to inputs ([5be868c](https://github.com/synerise/synerise-design/commit/5be868cbff030feede33d1e6626b359abe414688))
* **select:** add placeholder and change width of input ([f33685f](https://github.com/synerise/synerise-design/commit/f33685fb8a53ce1373d9fde4dd43d27ecbfb1f14))
* **select:** add validation with knobs and focus, fix input styles ([6881b24](https://github.com/synerise/synerise-design/commit/6881b249dd23ad111984d3c4d6ed4d9f6dcaf04d))
* **select:** added custom search icon ([987484f](https://github.com/synerise/synerise-design/commit/987484f58e67baa3ec12319f9af8917bd41bb63d))
* **table:** add posibility to sort every column in group table example ([e5ef822](https://github.com/synerise/synerise-design/commit/e5ef822fff1319a5f57a05e341be177ac5aae3e2))
* **table:** clear groupSettings with clear filer selection ([169c7bb](https://github.com/synerise/synerise-design/commit/169c7bbbec36e26f65711747904424b3c1214d1a))
* **table:** items number in title bar, pagination ([15d2f43](https://github.com/synerise/synerise-design/commit/15d2f43e859668a922c39eabc49aab32f1ff072c))
### Features
* **card:** update Card stories ([d0b1206](https://github.com/synerise/synerise-design/commit/d0b12062d959012aeed0d733bf7b8cb482d29c1a))
* **flag:** add DSFlag component ([80e2d0e](https://github.com/synerise/synerise-design/commit/80e2d0e6f6fb2d3a9750bd57566c250f79684b7e))
* **table:** add placeholder to EditableCell ([5f8c4d5](https://github.com/synerise/synerise-design/commit/5f8c4d53855e5318691f3ef7efc2d5896d5b89f2))
* **table:** add props gapSize, contentAlign for ActionCell ([8a24a3a](https://github.com/synerise/synerise-design/commit/8a24a3a9fe9bf3f3231b8d518320d8e265a9832f))
* **table:** add search to GroupTable example ([78bb7d2](https://github.com/synerise/synerise-design/commit/78bb7d2ab9fc63aa8b9467c92472c0abec5bb86a))
# [0.75.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.75.0) (2020-06-17)
### Bug Fixes
* **modal:** changed button type in story ([334ff11](https://github.com/synerise/synerise-design/commit/334ff11070443cd4bc4a20938bc4491220199d9e))
* **select:** changed story ([8644686](https://github.com/synerise/synerise-design/commit/86446864c04533b6dcf7dceda1d6ff0282c2971d))
* **table:** fix eslint issues ([65b0701](https://github.com/synerise/synerise-design/commit/65b07018c540f25e9b54b5e005ae6094e45e0dbb))
* **table:** remove console.log from example ([9b0f4d0](https://github.com/synerise/synerise-design/commit/9b0f4d00bfbd6134b0cda27ddd46ad737676ecd1))
### Features
* **column-manager:** add support for group columns ([dceb5c4](https://github.com/synerise/synerise-design/commit/dceb5c474527a57d59cddb174eb3bb4133f83974))
* **column-manager:** update ColumnManager stories ([f5ec4ae](https://github.com/synerise/synerise-design/commit/f5ec4aef56d9ca9b4effefde97dc94226fb946b7))
* **column-manager:** update translations ([be156fc](https://github.com/synerise/synerise-design/commit/be156fc41965ec2bfed0ea4654a9fb10d4fe74a6))
* **table:** add example of grouping by value and interval ([612ede2](https://github.com/synerise/synerise-design/commit/612ede2454f4c3c44d1c3d9758f0d40eeecd2f59))
* **table:** add item from group, fix types ([bc140f2](https://github.com/synerise/synerise-design/commit/bc140f2246e8d2cc1601b7c2615255df63b4c9b7))
* **table:** adjcust GroupTable to current Table version ([54ad069](https://github.com/synerise/synerise-design/commit/54ad0691eda76a311ae0b5ecc856e38b118790a3))
* **table:** custom header ([17a6d1a](https://github.com/synerise/synerise-design/commit/17a6d1ae9413b91c62396ac7b2f8d12317cbf34b))
* **table:** group by date ([a4aa7d0](https://github.com/synerise/synerise-design/commit/a4aa7d0d76a0430e506b3db08257cf14ba6995c6))
* **table:** grouped rows selection ([896ff36](https://github.com/synerise/synerise-design/commit/896ff366873ddc63c3a8f8b54a958dcd3185196b))
* **table:** grouped table ([75a3b22](https://github.com/synerise/synerise-design/commit/75a3b22cf11255a677e19ba5dea95b232e4c58b3))
* **table:** sort subrows by column ([57dad0c](https://github.com/synerise/synerise-design/commit/57dad0c7822105009f08b8f037c7f24eba091809))
* **table:** update example of GroupTable ([ec8dc36](https://github.com/synerise/synerise-design/commit/ec8dc366b7bbb1129443cb3f457b3025e9c37f85))
* **table:** update stories with data grouping ([ccc84d5](https://github.com/synerise/synerise-design/commit/ccc84d5a3c7c950d851a63483b329851d33cbe82))
* **table:** use Table as common component to DefaultTable & GroupTable ([e8aa1af](https://github.com/synerise/synerise-design/commit/e8aa1af66e4d80a14d0c50235f502e3a70f96763))
# [0.74.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.74.0) (2020-06-16)
### Bug Fixes
* **autocomplete:** fix focus on validation state and fix cursor ([bb3eb9f](https://github.com/synerise/synerise-design/commit/bb3eb9f7a620d6b5b0dcaa76b907354e4d292c4d))
* **autocomplete:** fixes for default story ([b67434f](https://github.com/synerise/synerise-design/commit/b67434f9553eee173c0f8217a129be416303afc0))
* **autocomplete:** hide errors on focus ([72ab72b](https://github.com/synerise/synerise-design/commit/72ab72bb76a4ae03a0dc001cf173bbba032679ee))
* **input:** fixed error styles for prefix and suffix ([34540f7](https://github.com/synerise/synerise-design/commit/34540f7b121bc64b92afdb62363c79c8b7f4c180))
* **select:** added changes after code review ([c951991](https://github.com/synerise/synerise-design/commit/c951991e809b84d322a80ff5b1b5f0fe76d38899))
* **select:** added stories ([b1248b0](https://github.com/synerise/synerise-design/commit/b1248b04287118792ec6f20757449ce0ee3fcf2e))
### Features
* **input:** added prefix and suffix ([df157e2](https://github.com/synerise/synerise-design/commit/df157e2af0999c16f36a5acb2e8e3805617568d0))
* **input:** added prefixel and suffixel props ([8bc48fe](https://github.com/synerise/synerise-design/commit/8bc48fe8a90d2f1202fc126e9c1e0a3c3d517a5c))
* **select:** added prefix and suffix ([501ea11](https://github.com/synerise/synerise-design/commit/501ea11cae63f7bdf1881a637e30be902e49465b))
## [0.73.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.73.1) (2020-06-15)
### Bug Fixes
* **cascader:** added use effect to refresh selectedIds ([990c317](https://github.com/synerise/synerise-design/commit/990c3176ae7c4cbdf62cfaa804da7278a08c3831))
* **table:** fix font color in TreeTable example ([0ad0302](https://github.com/synerise/synerise-design/commit/0ad030206b286bda88819da7dd025670582d898f))
# [0.73.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.73.0) (2020-06-10)
### Features
* **table:** add icon to AvatarLabel cell type ([14c2918](https://github.com/synerise/synerise-design/commit/14c29182cb25f3ed13047b7d7ae2c8ba9ce8ac89))
## [0.72.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.72.1) (2020-06-10)
### Bug Fixes
* **table:** fix column-manager in table stories ([73dc9d1](https://github.com/synerise/synerise-design/commit/73dc9d137a129c207b3e257f46c7f19cc8321224))
* **table:** typo in stories ([fa1500d](https://github.com/synerise/synerise-design/commit/fa1500d9eb0af8cbc65ff4e118dc14bf5bc17e45))
* **table:** use MenuItemType=danger instead of danger prop in stories ([55580ae](https://github.com/synerise/synerise-design/commit/55580ae98621a4de62eeb8350b604586c5e44329))
# [0.72.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.72.0) (2020-06-09)
### Bug Fixes
* **column-manager:** fix selected filter in storybook ([5667b0d](https://github.com/synerise/synerise-design/commit/5667b0daa24f5b7565501ade224ca5579acb2c75))
* **table:** add hideTitlebar props ([23dad8b](https://github.com/synerise/synerise-design/commit/23dad8bbf365e0b9ff80641355257db15327972d))
* **table:** fix tree table example ([d7d30d4](https://github.com/synerise/synerise-design/commit/d7d30d41f4207cfd2f62a110b28cd15e847ebdbf))
### Features
* **table:** add CardHeader in example with Card ([518ddd1](https://github.com/synerise/synerise-design/commit/518ddd18054e4cc02da4a408df9411a3a5a07547))
* **table:** add Table on card example ([404cd46](https://github.com/synerise/synerise-design/commit/404cd466599e95560cc28cee3588cf30d254bb37))
* **table:** doesnt render TableTitle when title prop is not set ([31f0a52](https://github.com/synerise/synerise-design/commit/31f0a529809f507a2ba1a3cb78a54da47028477c))
# [0.71.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.71.0) (2020-06-08)
### Bug Fixes
* **input:** add missing stories ([3d01f26](https://github.com/synerise/synerise-design/commit/3d01f266f69069569a0aa9de9a61780cf3c0f300))
### Features
* **item-filter:** rename ItemFilter storybook example to ItemManager ([37bb17a](https://github.com/synerise/synerise-design/commit/37bb17a38ae3abc6c7277144ce49a569f3108a3b))
* **table:** add TreeTable ([cf1a829](https://github.com/synerise/synerise-design/commit/cf1a829de5cf16b302cbd14fb7c0d6acdd10e678))
* **table:** add TreeTable stories ([744c040](https://github.com/synerise/synerise-design/commit/744c0407f25988258a1233f62e35f7990042141f))
# [0.70.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.70.0) (2020-06-08)
### Bug Fixes
* **alert:** fix styles, stories ([bacd1e8](https://github.com/synerise/synerise-design/commit/bacd1e8931a1775b0850f5b3e33a2087fb0c3fb9))
* **input:** add missing export, fix stories ([7baaac3](https://github.com/synerise/synerise-design/commit/7baaac3d69b175bf6bd28a8baa59e7fdf261262e))
* **input:** remove console.log from input stories ([1252a2d](https://github.com/synerise/synerise-design/commit/1252a2da540f630922cc917d7ccd5ed3b6c34a68))
* **item-filter:** invalid date format in storybook examples ([b1cfb16](https://github.com/synerise/synerise-design/commit/b1cfb162a1abb66bbf8ffef790a3f07f9b908084))
* **table:** allow to pass null/undefined as selection type ([fdb1efa](https://github.com/synerise/synerise-design/commit/fdb1efae028fff9bd35fb9537fb1508d151bc967))
### Features
* **input:** add MaskedInput ([c2532b1](https://github.com/synerise/synerise-design/commit/c2532b186ad7136d057d24f8c5513c3074a4287f))
* **input:** set letter-spacing for MaskedInput ([8cdde8c](https://github.com/synerise/synerise-design/commit/8cdde8c4a98c2f711ab7775b71bc90f735cb7fe9))
* **input:** update examples ([96a1c0c](https://github.com/synerise/synerise-design/commit/96a1c0cc390cb4692e851b370ae585f724c9839a))
# [0.69.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.69.0) (2020-06-05)
### Bug Fixes
* **modal:** updated story with headers ([00608bc](https://github.com/synerise/synerise-design/commit/00608bc862db9feddff4bbd87d51d6619b7d1479))
### Features
* **table:** add empty table example ([a89cccb](https://github.com/synerise/synerise-design/commit/a89cccbddb50422ab05eab9ec13a3c8fd2575844))
## [0.68.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.68.1) (2020-06-05)
### Bug Fixes
* **menu:** copyable tooltip refactor, updated docs ([4e06d10](https://github.com/synerise/synerise-design/commit/4e06d10419e8384518ef7c91a3b22586b9d4312e))
# [0.68.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.68.0) (2020-06-03)
### Features
* **alert:** add examples in storybook ([fd75cf4](https://github.com/synerise/synerise-design/commit/fd75cf4a7f0ffe02be86e194ca3dbf6b72eab4a4))
* **alert:** bootstrap component ([6ef3099](https://github.com/synerise/synerise-design/commit/6ef3099679957e16795007de463217b0ee73bae9))
## [0.67.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.67.1) (2020-06-03)
### Bug Fixes
* **dropdown:** stories update ([2ac4030](https://github.com/synerise/synerise-design/commit/2ac403035e15e839436e35e49d304a1d37a02548))
* **modal:** added a new story, refactored stories ([214ee49](https://github.com/synerise/synerise-design/commit/214ee499ca52ee9c0cb2193a067033836bc43012))
* **modal:** added headers to the story ([80279fc](https://github.com/synerise/synerise-design/commit/80279fcf23e4bc1ce0fccf3128d2ffdee55807f7))
* **tabs:** added option to disable config button ([e62a22c](https://github.com/synerise/synerise-design/commit/e62a22cb0d766a424c9a9baeecc1d7ed2de88c5b))
# [0.67.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.67.0) (2020-06-02)
### Bug Fixes
* **item-filter:** fix docs, update storties ([8f4912e](https://github.com/synerise/synerise-design/commit/8f4912e3fd931d99d7f9245c278d7954a0e7def1))
* **item-filter:** update stories ([f6cafd3](https://github.com/synerise/synerise-design/commit/f6cafd32ea3074ba839e48728db6bad349a8eb06))
* **item-filter:** update stories ([310c9d0](https://github.com/synerise/synerise-design/commit/310c9d04763179ba86f3524130eb088863fa3fec))
* **table:** fix expandable row styles ([7804306](https://github.com/synerise/synerise-design/commit/7804306f99d5423d825164609ae833e2d9e14df5))
### Features
* **item-filter:** custom scrollbar + infinitescroll + virtualization ([a213e4f](https://github.com/synerise/synerise-design/commit/a213e4fe50f114f95aa713c3951cfa856d211c24))
* **item-filter:** use ds-scrollbar with infinite scroll mode ([728c32c](https://github.com/synerise/synerise-design/commit/728c32cee085fdd1138dd1b7f88574c40a70cc26))
* **scrollbar:** add custom styles for scrollbar wrapper, update story ([0f17aae](https://github.com/synerise/synerise-design/commit/0f17aae25cc6d91cf57515543b6a24b6dd54fe3e))
* **scrollbar:** add inifinite scroll ([d2e8ef2](https://github.com/synerise/synerise-design/commit/d2e8ef27fde732697d525d81c7ac3861a2efb2af))
* **table:** disable filter trigger ([d779c35](https://github.com/synerise/synerise-design/commit/d779c35fde07b19075a60c98b63c093afbe572a8))
## [0.66.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.66.1) (2020-06-02)
### Bug Fixes
* **button:** create cruds styles and cruds add tooltip in package json ([f976488](https://github.com/synerise/synerise-design/commit/f97648872adb1a894b967007135e15944f203411))
* **button:** fix in the build ([9e93889](https://github.com/synerise/synerise-design/commit/9e9388920d763b48619c6df3ff272c021c57c925))
* **button:** fix in the build and add Singlecrud component ([ef5b1c5](https://github.com/synerise/synerise-design/commit/ef5b1c56e1a3b5e60b966787ff17ec364b92f2de))
* **button:** remove disabled and made props optional ([5a2e832](https://github.com/synerise/synerise-design/commit/5a2e8324ec706b5c153150b9469ef69a432d9b39))
* **menu:** nested items style fixes ([0324e6e](https://github.com/synerise/synerise-design/commit/0324e6ea3bac44a07e431ee6551642617f384e9a))
* **search:** made tooltip optional, moved to static field ([ca8cbc9](https://github.com/synerise/synerise-design/commit/ca8cbc92e8b103b5269ab80503d89e40f6efe176))
* **search:** removed deps ([0393973](https://github.com/synerise/synerise-design/commit/0393973102ba9c5328c4518377dbae44822a9d92))
* dropdown ([4364c4c](https://github.com/synerise/synerise-design/commit/4364c4ca522daad1863ee48844f1a73459854aaa))
* dropdown: added story ([75b5c8c](https://github.com/synerise/synerise-design/commit/75b5c8c2173b9cecdfced729d82b4a1fd7e224c4))
# [0.66.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.66.0) (2020-05-28)
### Bug Fixes
* **button:** add custom color ghost ([04c994e](https://github.com/synerise/synerise-design/commit/04c994e013df96ef20a32bf3a78d515e42b08e88))
* **cascader:** moved cascader story into seperate view ([24b56e6](https://github.com/synerise/synerise-design/commit/24b56e6be13be377102b18910c48f6f4abda976e))
* **menu:** fixing test, used box shadow instead border in avatar ([fbadbfa](https://github.com/synerise/synerise-design/commit/fbadbfa7ec997258f1c7e8bd5f949a036f2eb129))
* **menu:** refactored stories, added focusing with arrow keys ([5af2fe4](https://github.com/synerise/synerise-design/commit/5af2fe42c01ba58a0211efd0ca3f1670e564d164))
### Features
* **tabs:** added block type for tabs ([6cf1486](https://github.com/synerise/synerise-design/commit/6cf1486e2b5bce6574adbcbcc0ccd16063e08d13))
## [0.65.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.65.2) (2020-05-26)
### Bug Fixes
* **cascader:** breadcrumb styles, added scrollbar ([254136f](https://github.com/synerise/synerise-design/commit/254136f93bd3dbccbd5272b5a50f6c526e9e3f06))
* **table:** fix row selection types ([2f84aa9](https://github.com/synerise/synerise-design/commit/2f84aa9446e81b424b514ddb56e8c1f9197f881d))
## [0.65.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.65.1) (2020-05-25)
### Bug Fixes
* **autocomplete:** add Error, Placeholder, getErrorText, change styles ([ca233e3](https://github.com/synerise/synerise-design/commit/ca233e37a318fc848a7ca3c8f1609f430574ba0c))
* **autocomplete:** delete has before label,description and placeholder ([92d9cb1](https://github.com/synerise/synerise-design/commit/92d9cb17567c7dd043b9519fa1c2fbe6a1325211))
* **cascader:** added width and height handling, added callbacks ([baaea36](https://github.com/synerise/synerise-design/commit/baaea368dfba6366de6e1935b8bf575738626794))
# [0.65.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.65.0) (2020-05-22)
### Bug Fixes
* **card:** removed redundant event listener from props ([2e2ff1c](https://github.com/synerise/synerise-design/commit/2e2ff1c8170166a2d328a4c2631faaddd01d6820))
* **cascader:** added data to story ([d7485ed](https://github.com/synerise/synerise-design/commit/d7485ed67178ed60e634f83eef7eec14d3387413))
* **cascader:** fixing navigation ([5e05e04](https://github.com/synerise/synerise-design/commit/5e05e040195ac1d8ac6a1ed5dc9d25a00669e483))
* **cascader:** improved searching of the routes ([17f2ffe](https://github.com/synerise/synerise-design/commit/17f2ffe61ab12dab353f409b44e8250bedcf7ac2))
* **cascader:** next changes after review ([826a4d1](https://github.com/synerise/synerise-design/commit/826a4d15052bc0b497c78ef2bb249a6363198f3c))
* **menu:** breadcrumb gradient overlay ([c06c150](https://github.com/synerise/synerise-design/commit/c06c150891408c498263818839d8166f99a285e4))
* **portal:** cleanup stories ([d9d0cc7](https://github.com/synerise/synerise-design/commit/d9d0cc7b94f8708679ec1787a6b91c96321ba1f0))
* **table:** fix min column width, fix table prop types ([0d5a3b3](https://github.com/synerise/synerise-design/commit/0d5a3b34470e49cab1b6b14b9531d1d5c9f93ec8))
* **table:** fix types ([5db086e](https://github.com/synerise/synerise-design/commit/5db086e08e4b7ad67f42c20e75c3b3a9fd4ccacb))
* **utils:** added utils for handling double click ([9129c5d](https://github.com/synerise/synerise-design/commit/9129c5d9b6898a4a9ad9de9251f0911437ff94f8))
### Features
* **cascader:** added cascader component ([e0fd82e](https://github.com/synerise/synerise-design/commit/e0fd82e7f81172951e95d3cbe821f590b62254c0))
* **cascader:** added handling of categories datatype ([342ce5a](https://github.com/synerise/synerise-design/commit/342ce5a4f9d04ae8b3d11704b5603ab5a4902539))
## [0.64.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.64.2) (2020-05-18)
### Bug Fixes
* **table:** fix column width on rerender ([d0eec73](https://github.com/synerise/synerise-design/commit/d0eec73d75ff8a39d5779e427336d93fc67da240))
## [0.64.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.64.1) (2020-05-18)
### Bug Fixes
* **input:** corrected types ([befdf18](https://github.com/synerise/synerise-design/commit/befdf182be1d72c84756220e737e887a78885af7))
* **menu:** added header, fixed breadcrumbs ([cff0a64](https://github.com/synerise/synerise-design/commit/cff0a64f1d356a608d03243f99607814272ef482))
# [0.64.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.64.0) (2020-05-15)
### Bug Fixes
* **icon:** stories ([241c2c9](https://github.com/synerise/synerise-design/commit/241c2c9183820e771e7331e54a99cc1071af42b5))
* **menu:** added indent level for tree item ([873dec2](https://github.com/synerise/synerise-design/commit/873dec21e44f128ba6dba090d41330ceb3614644))
* **menu:** fixed types ([928afe3](https://github.com/synerise/synerise-design/commit/928afe3751bb9a7a81d19d35138a1c560c29954a))
* **menu:** modified decorator ([b199516](https://github.com/synerise/synerise-design/commit/b199516e71a8060124bfbe04d91bff9fc7e48bcc))
* **menu:** removed redundant datasource dimension ([0f6f9d8](https://github.com/synerise/synerise-design/commit/0f6f9d8733748a180759318afa624c986043496d))
* **select:** fixed issues with smaller large select ([ad9b477](https://github.com/synerise/synerise-design/commit/ad9b477b73f49a48424eafc275d7a78dcb22c3af))
### Features
* **docs:** add home-page styles ([2d0dbf7](https://github.com/synerise/synerise-design/commit/2d0dbf7e1a4c4a7ec32c11f98ba4eaaf011f4c2b))
* **menu:** added breadcrumbs beta version ([0fcdd32](https://github.com/synerise/synerise-design/commit/0fcdd32dc822b6ae52304222d8afd3f5ef7b6dc3))
# [0.63.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.63.0) (2020-05-14)
### Bug Fixes
* **table:** fix stories ([e75c637](https://github.com/synerise/synerise-design/commit/e75c637ca237f6a84c58c3238f25389ad4d2a774))
### Features
* **icon:** add additional icons set ([5e18259](https://github.com/synerise/synerise-design/commit/5e182591c535489a8fc15955b7d466435078c669))
## [0.62.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.62.1) (2020-05-13)
### Bug Fixes
* **input:** fix error styles ([14ed650](https://github.com/synerise/synerise-design/commit/14ed6502f3276a6f26c5b8380078341abf1ce51c))
# [0.62.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.62.0) (2020-05-12)
### Bug Fixes
* **page-header:** removed knobs that leaked to other components ([3b7bd06](https://github.com/synerise/synerise-design/commit/3b7bd06e63003690d6907d6de206cfccb37803fa))
* **table:** expanded row styles ([ccd891e](https://github.com/synerise/synerise-design/commit/ccd891e1f9a649bab8c5963152f140e258a4eb17))
* **table:** fix selection columns styles ([23f218b](https://github.com/synerise/synerise-design/commit/23f218b0d160cda77797d5cb1c207bafb1bd594f))
### Features
* **column-manager:** update stories ([3daaf22](https://github.com/synerise/synerise-design/commit/3daaf22ac9900ca6a510828fdf2c7f54aa7dba07))
* **item-filter:** update stories ([ae411f9](https://github.com/synerise/synerise-design/commit/ae411f9f0d94663141d09d78d60b025dc257ba64))
* **table:** add column with checkbox ([9358018](https://github.com/synerise/synerise-design/commit/9358018cb5113fc345dac8c24d5b49f1aa420423))
* **table:** update stories ([504caaa](https://github.com/synerise/synerise-design/commit/504caaacf145f40996ebca875fdd5440fd72cc1f))
* **utils:** randomDate helper ([425619f](https://github.com/synerise/synerise-design/commit/425619f162e371ba98864a6bd35f0c55c9656b59))
## [0.61.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.61.1) (2020-05-11)
### Bug Fixes
* **manageable-list:** fixed expansion bug ([e58d5e5](https://github.com/synerise/synerise-design/commit/e58d5e5c77e2b61d0d8c486ed476f2a48857b2e3))
# [0.61.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.61.0) (2020-05-11)
### Bug Fixes
* **manageable-list:** added expand on mount prop ([9f854a2](https://github.com/synerise/synerise-design/commit/9f854a2112117a933033204ad7431b430ef9b116))
* **manageable-list:** added option to disable expander ([033964a](https://github.com/synerise/synerise-design/commit/033964af05ff81fd221ca9bdf59d4465b2ff591f))
* **manageable-list:** improved grabber item story style ([d297b0f](https://github.com/synerise/synerise-design/commit/d297b0f7f8fbde5e747fe4a5e6db3fb8db8192df))
### Features
* **manageable-list:** removed internal state for expandned items ([3e4cd20](https://github.com/synerise/synerise-design/commit/3e4cd20e2af9d50020cd3ca8ce9d4c54e16a16af))
* **manageable-list:** updated stories, added expand on click ([c7d3666](https://github.com/synerise/synerise-design/commit/c7d36666ffc10ae7bccfa076240d3a1218da9954))
# [0.60.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.60.0) (2020-05-08)
### Bug Fixes
* **button:** remove state from Button.expander ([2d398da](https://github.com/synerise/synerise-design/commit/2d398da89805fa3e94544116af10a9b85efe8ebf))
* **manageable-list:** styles update - outline style added ([f94d29e](https://github.com/synerise/synerise-design/commit/f94d29ed1d512f0e6dd67376f7df3fc5837adeaf))
* **table:** fix imports ([7405e77](https://github.com/synerise/synerise-design/commit/7405e77d1ca5292f5ebc66c91af7ca5f4fdd6c34))
* **table:** fix stories ([667d3eb](https://github.com/synerise/synerise-design/commit/667d3ebd2da1ca5cb0d985a89ab313c6e386693d))
* **table:** fix styles ([c539407](https://github.com/synerise/synerise-design/commit/c539407f51548964afb3aa8029e46d6d83a6a38e))
* **table:** fix table virtualization ([2c54e9b](https://github.com/synerise/synerise-design/commit/2c54e9b1867f695e037562571862436c3b24548b))
* **table:** fix types ([888a210](https://github.com/synerise/synerise-design/commit/888a21044f735776bd51b6a492019e8b37f7a960))
* **table:** update stories ([d821b8b](https://github.com/synerise/synerise-design/commit/d821b8b22fc3679abe380c5a9a770974ba959b8e))
### Features
* **table:** add ds-scrollbar to VirtualTable ([b510eac](https://github.com/synerise/synerise-design/commit/b510eac18a2abcc2ab9946941354688c1a19b581))
* **table:** add story with fixed columns ([1681d23](https://github.com/synerise/synerise-design/commit/1681d2326ef6370af4d8be5c6c0f480016e06a8c))
* **table:** expand on row click example ([8bbe78e](https://github.com/synerise/synerise-design/commit/8bbe78e95af56ed885a7bd88048556adef18a7f9))
## [0.59.7](https://github.com/synerise/synerise-design/compare/[email protected]@0.59.7) (2020-05-04)
### Bug Fixes
* **add-button:** removed addbutton story ([9e75377](https://github.com/synerise/synerise-design/commit/9e753773c5bc5eac93ef681299513622986e5a25))
* **search:** fixing lint errors and updating tests ([1c3422a](https://github.com/synerise/synerise-design/commit/1c3422a82dc8971868e572f0888977f648e3e7aa))
* **search:** styling changes in stories ([44b1558](https://github.com/synerise/synerise-design/commit/44b15585af66d3bd90960bba0383e5fc05d157e5))
* **search:** styling improvements ([2562333](https://github.com/synerise/synerise-design/commit/256233353b592c5aac9935bf8540e89601ecef9f))
## [0.59.6](https://github.com/synerise/synerise-design/compare/[email protected]@0.59.6) (2020-04-30)
**Note:** Version bump only for package portal
## [0.59.5](https://github.com/synerise/synerise-design/compare/[email protected]@0.59.5) (2020-04-30)
### Bug Fixes
* **items-roll:** add minor fixes ([e36be6a](https://github.com/synerise/synerise-design/commit/e36be6a04e4e890de781529162c11f3243024df8))
* **search:** moved scrollbar and changed width of the items in list ([8c359bd](https://github.com/synerise/synerise-design/commit/8c359bd344d0b093e49ebeee32a0b9c88cf0642f))
## [0.59.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.59.4) (2020-04-29)
### Bug Fixes
* **search:** added tests for focusWithArrowKeys utils ([187ca6b](https://github.com/synerise/synerise-design/commit/187ca6b9ff7d77a87a64e06da4c8f902a49993a7))
* **search:** extracted focusing with arrows to utils ([2eaf8c3](https://github.com/synerise/synerise-design/commit/2eaf8c37d25777f11e475c846e60927b6226c384))
* **tabs:** add hiddenHelpers to measure width of tabs ([2db3344](https://github.com/synerise/synerise-design/commit/2db33444b6d150017b36b685ef6c63759dd9e1b1))
## [0.59.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.59.3) (2020-04-29)
### Bug Fixes
* **items-roll:** add style fixes ([9a3dbef](https://github.com/synerise/synerise-design/commit/9a3dbef33d2ef4537c3c4ca97428a8d14cd95a07))
## [0.59.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.59.2) (2020-04-28)
**Note:** Version bump only for package portal
## [0.59.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.59.1) (2020-04-27)
### Bug Fixes
* **items-roll:** minor fixes ([51d9d07](https://github.com/synerise/synerise-design/commit/51d9d079fc61cba9f0b2278f5b659735309b165e))
* **table:** virtualization story ([fcca940](https://github.com/synerise/synerise-design/commit/fcca940bb9fea77a57200a5fd76f9125f54170bf))
# [0.59.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.59.0) (2020-04-27)
### Bug Fixes
* **table:** code review ([0d8429e](https://github.com/synerise/synerise-design/commit/0d8429ee1be27a605ef2b77106f8d58368c06a98))
* **table:** CR issues ([b51b574](https://github.com/synerise/synerise-design/commit/b51b5747a5c0e7cf57b109e2a9b66d69007ade9e))
* **table:** fix styles ([30309a0](https://github.com/synerise/synerise-design/commit/30309a0d9a9b2d5a32113521cb069a1899d80d2b))
### Features
* **column-manager:** update default translations ([c2f1660](https://github.com/synerise/synerise-design/commit/c2f1660139c31741d7c1701f3a68065bc3f80bab))
* **items-roll:** add items-roll component ([def8fe5](https://github.com/synerise/synerise-design/commit/def8fe576f893bf120fab89bad3397dba498838e))
* **table:** add search ([4e14210](https://github.com/synerise/synerise-design/commit/4e14210c513bf985ff502271f340a2086519c25b))
* **table:** add virtualized list ([4976607](https://github.com/synerise/synerise-design/commit/49766079297440f409f01a0d4523572ee8b8672c))
* **table:** example with ColumnManager ([cbf6a80](https://github.com/synerise/synerise-design/commit/cbf6a80e3ca7fca5d0eea103a0d61515123e2109))
* **table:** story with search ([db91a35](https://github.com/synerise/synerise-design/commit/db91a35bd7eb95285734d15556a688ccb698b1f0))
* **table:** table virtualization ([d68823e](https://github.com/synerise/synerise-design/commit/d68823eef53457f9d2815dc81116764e7fead6e4))
* **table:** update stories ([0fa960a](https://github.com/synerise/synerise-design/commit/0fa960a0b767421e0d2b174c84faa69f68375a90))
* **table:** update styles ([371aafc](https://github.com/synerise/synerise-design/commit/371aafc57bfffaace5a9233862c73fcd4f5f06fa))
* **table:** update styles ([e6b5245](https://github.com/synerise/synerise-design/commit/e6b5245786d1a3d4eba604a3866df7564b2f14fe))
* **table:** update table stories ([a0a4eb1](https://github.com/synerise/synerise-design/commit/a0a4eb1d29e65bb40c84561fbbb0e5d1df2e2ebc))
* **table:** update table stories ([ec2722f](https://github.com/synerise/synerise-design/commit/ec2722f6b46d182c71f09c849478621bc2e5f66e))
* **table:** use Expander button ([a5287ac](https://github.com/synerise/synerise-design/commit/a5287ac1050624636311eae7a9619333367d9aa3))
## [0.58.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.58.1) (2020-04-24)
### Bug Fixes
* **table:** fix virualtable ([00961a2](https://github.com/synerise/synerise-design/commit/00961a26418fce796477b1413f21a35f4f207db1))
# [0.58.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.58.0) (2020-04-24)
### Bug Fixes
* **button:** simplifed styles ([dc5e792](https://github.com/synerise/synerise-design/commit/dc5e792c4e483d3fd823a2ce57152fd2b92b39a9))
### Features
* **button:** added creator button ([48f1099](https://github.com/synerise/synerise-design/commit/48f1099df83282261e250a12cdfd6173a05b1516))
* **button:** added epxander ([63b443b](https://github.com/synerise/synerise-design/commit/63b443b9701b2a12b6c569c308cf3811ad7e8fa6))
* **button:** added expander ([d52b8a9](https://github.com/synerise/synerise-design/commit/d52b8a9d8e6208f621aa2e78004eebf6f033548e))
## [0.57.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.57.2) (2020-04-23)
### Bug Fixes
* **table:** fix virtualization ([238ecb7](https://github.com/synerise/synerise-design/commit/238ecb73b4a74aef19499b24358db340bf47aac8))
## [0.57.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.57.1) (2020-04-23)
### Bug Fixes
* **table:** calculation of virtual columns width ([1c39a9f](https://github.com/synerise/synerise-design/commit/1c39a9f346e4ec59543442197a6040696a32ae9c))
# [0.57.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.57.0) (2020-04-23)
### Features
* **table:** add table with virtualization ([4c0bc22](https://github.com/synerise/synerise-design/commit/4c0bc228ea6a3287854048cdb2762c155d0c16e0))
## [0.56.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.56.4) (2020-04-22)
### Bug Fixes
* **search:** changed placeholder texts ([d1c9c6d](https://github.com/synerise/synerise-design/commit/d1c9c6db5fdf0f7f9fc2b49b4a6c363383d9b275))
## [0.56.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.56.3) (2020-04-22)
### Bug Fixes
* **search:** added divider, fixed bugs with enter press ([a28fee6](https://github.com/synerise/synerise-design/commit/a28fee6eb2c78547c3c67dc03aad733224e664fb))
## [0.56.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.56.2) (2020-04-22)
### Bug Fixes
* **page-header:** fix stories, cleanup ([863e027](https://github.com/synerise/synerise-design/commit/863e02789202c68de8ece0c2ab2039113300ee9d))
## [0.56.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.56.1) (2020-04-22)
### Bug Fixes
* **search:** styles fixes, attaching custom styles to row renderer ([b99e60f](https://github.com/synerise/synerise-design/commit/b99e60f9d97d26e9121cb5a997d9cfb5a1c31adc))
# [0.56.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.56.0) (2020-04-22)
### Features
* **popconfirm:** add stories for confirm message ([882cd9c](https://github.com/synerise/synerise-design/commit/882cd9c9288495f5f050f2038d818dc6ac209227))
## [0.55.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.55.2) (2020-04-22)
### Bug Fixes
* **search:** added consts, simplifed callbacks deps ([46db54c](https://github.com/synerise/synerise-design/commit/46db54cdf8a82cb70d0535bdcb629fbb24eb9bfd))
* **search:** added renderers to props, fixed scrollbar ([1ba7972](https://github.com/synerise/synerise-design/commit/1ba797293619c449983f326f3a5537a0689fa4e3))
## [0.55.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.55.1) (2020-04-21)
### Bug Fixes
* **menu:** added highlighted item story ([50fdccd](https://github.com/synerise/synerise-design/commit/50fdccd0498a893e6c43cca5fa4f51ee2ff2629c))
* **portal:** logos ([e904646](https://github.com/synerise/synerise-design/commit/e9046468385b0e7155446a053f0018732238e736))
* **search:** added highlighting of menu item ([9206211](https://github.com/synerise/synerise-design/commit/9206211990732ef033eb3998e99f3b3e2225004c))
* **search:** added tests ([330484f](https://github.com/synerise/synerise-design/commit/330484f3edc43a5b3efdd8b79aadd4465660209c))
* **search:** before refactor ([2b9c86d](https://github.com/synerise/synerise-design/commit/2b9c86d5d2fe36a55ec8a85eb90a9aa47f421766))
* **search:** fixed serving suggestions ([808abbc](https://github.com/synerise/synerise-design/commit/808abbca86d0f3626d04834b58c26fff38a4090b))
* **search:** fixed type errors, updated tests ([7f1f676](https://github.com/synerise/synerise-design/commit/7f1f676e10c79dbb58a44507872950b8052af5f5))
* **search:** refactored - extracted input ([a31ead1](https://github.com/synerise/synerise-design/commit/a31ead144d8fcfb0bf72d3069fdf318e6e80d939))
* **search:** trying to fix animations ([7abe7d2](https://github.com/synerise/synerise-design/commit/7abe7d279062093338667e9bd14e42e814f4b887))
* **search:** updated tests, refactored naming, updated types ([c26f659](https://github.com/synerise/synerise-design/commit/c26f6597bbcbe22bbdc4af21051ac4bfe69c87f4))
# [0.55.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.55.0) (2020-04-15)
### Bug Fixes
* **menu:** changed width of the last story ([f372cf4](https://github.com/synerise/synerise-design/commit/f372cf4dad1c2a9419ffb7a6b291ff9163e93896))
* **menu,checkbox:** added new knobs to menu, changed checked icon ([123c049](https://github.com/synerise/synerise-design/commit/123c049b0075fc48e0e1fa4c4ff92ccdd11e8b10))
### Features
* **menu:** added new knobs ([c4c3ecc](https://github.com/synerise/synerise-design/commit/c4c3ecc207443ae58de38e26e796100a30476b40))
# [0.54.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.54.0) (2020-04-13)
### Features
* **column-manager:** add Drawer with header, search nad footer buttons ([a9daee7](https://github.com/synerise/synerise-design/commit/a9daee7560e4466f78d0100de8196a0f93e6f194))
* **column-manager:** add story with ItemFilter ([8c3b1fd](https://github.com/synerise/synerise-design/commit/8c3b1fddae63c57b69d6762ede1adcc5a9d8686f))
* **column-manager:** add translations ([2362085](https://github.com/synerise/synerise-design/commit/2362085d835f0ada054ccad03c8698d23412a101))
* **column-manager:** bootstrap component ([2115277](https://github.com/synerise/synerise-design/commit/211527798410d9d6271d7d0873ad195e24bc6fe5))
## [0.53.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.53.1) (2020-04-10)
### Bug Fixes
* **drawer:** ran prettier ([7372680](https://github.com/synerise/synerise-design/commit/73726803eaf62b72f7a248e6d56710a96d853a62))
* **drawer:** removed inline styles ([d0b9b87](https://github.com/synerise/synerise-design/commit/d0b9b874a47e024495772741cf282fc32154decc))
# [0.53.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.53.0) (2020-04-10)
### Features
* **menu:** MenuItems as Menu childs components ([e703360](https://github.com/synerise/synerise-design/commit/e7033606927f6c303bcbae835219b5528be09b05))
## [0.52.10](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.10) (2020-04-09)
### Bug Fixes
* **menu:** updated storybook ([635fd18](https://github.com/synerise/synerise-design/commit/635fd18292b562ee1def7ef4875c1b428595154e))
## [0.52.9](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.9) (2020-04-08)
### Bug Fixes
* **menu:** fixed focus,pressed and hover styles ([f3c3083](https://github.com/synerise/synerise-design/commit/f3c30831b71691817bcc9e0178d83f410b524f46))
## [0.52.8](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.8) (2020-04-07)
### Bug Fixes
* **select:** fix select styles ([0310dc7](https://github.com/synerise/synerise-design/commit/0310dc730e1f3fb037faec60733121d1d111c29d))
## [0.52.7](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.7) (2020-04-02)
### Bug Fixes
* **drawer:** added search filters ([0ab41f4](https://github.com/synerise/synerise-design/commit/0ab41f4feefeefcd4e89d9d2b03bef2aefb146ce))
## [0.52.6](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.6) (2020-04-01)
**Note:** Version bump only for package portal
## [0.52.5](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.5) (2020-03-31)
**Note:** Version bump only for package portal
## [0.52.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.4) (2020-03-30)
### Bug Fixes
* **inline-edit:** fix styles according to zeplin ([d9ffdb6](https://github.com/synerise/synerise-design/commit/d9ffdb66d3f5e1f1a4900fce85f3854c7717bd01))
## [0.52.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.3) (2020-03-30)
**Note:** Version bump only for package portal
## [0.52.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.2) (2020-03-30)
### Bug Fixes
* **icon-picker:** add frequently used icon into SB ([6e2c184](https://github.com/synerise/synerise-design/commit/6e2c184ef07fe42098ebc36738b4be050e0bc0e0))
## [0.52.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.1) (2020-03-27)
**Note:** Version bump only for package portal
# [0.52.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.52.0) (2020-03-26)
### Bug Fixes
* **time-picker:** fix onChange ([215b783](https://github.com/synerise/synerise-design/commit/215b783bceb2875bf5c4a28d756be18f3c5820d1))
### Features
* **time-picker:** update stories ([e7b08e1](https://github.com/synerise/synerise-design/commit/e7b08e1420211419aabc3e80c2df00e52e655a26))
## [0.51.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.51.1) (2020-03-25)
### Bug Fixes
* **input:** fix tooltip ([0bc13eb](https://github.com/synerise/synerise-design/commit/0bc13eb144577bd14fc08e74a3107b831e90ff20))
* **time-picker:** hide use12hourClock from knobs in storybook ([40ca40c](https://github.com/synerise/synerise-design/commit/40ca40c5e7497674084662bb617b6e1cc3c55e7f))
# [0.51.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.51.0) (2020-03-24)
### Features
* **tooltip:** add offset size props ([fca819a](https://github.com/synerise/synerise-design/commit/fca819ada15f340fded90c79f840ddc6011aba3c))
## [0.50.5](https://github.com/synerise/synerise-design/compare/[email protected]@0.50.5) (2020-03-24)
### Bug Fixes
* **tooltip:** fix knobs in stories ([97a15b5](https://github.com/synerise/synerise-design/commit/97a15b54595ef259c7e88a690691c035bfa75a36))
## [0.50.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.50.4) (2020-03-23)
### Bug Fixes
* **portal:** fix font paths ([f7fec1b](https://github.com/synerise/synerise-design/commit/f7fec1ba9e32f46c9ec073b89a04989c774ced97))
## [0.50.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.50.3) (2020-03-23)
### Bug Fixes
* **select:** showSearch props support ([9088ca8](https://github.com/synerise/synerise-design/commit/9088ca84c17aa9e2395628bb9bf2f4d87aa1c454))
* **tooltip:** fix styles, stories ([4c092bb](https://github.com/synerise/synerise-design/commit/4c092bb5b8c5b7c10241468823863aa4f38f9d21))
## [0.50.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.50.2) (2020-03-23)
**Note:** Version bump only for package portal
## [0.50.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.50.1) (2020-03-23)
### Bug Fixes
* **avatar-group:** fix stories ([64c548d](https://github.com/synerise/synerise-design/commit/64c548dfad71dcf9bf7cf0020f74c45de789b43a))
# [0.50.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.50.0) (2020-03-23)
### Features
* **tooltip:** add avatar type, update styles ([55f2647](https://github.com/synerise/synerise-design/commit/55f26471330f6311e5d3a404b2521b3636525513))
* **tooltip:** update stories ([374d9e9](https://github.com/synerise/synerise-design/commit/374d9e9599c68f8c577b347a82b1c6b9bc78b4d8))
## [0.49.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.49.3) (2020-03-20)
**Note:** Version bump only for package portal
## [0.49.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.49.2) (2020-03-19)
### Bug Fixes
* **avatar:** remove UserM icon as default avatar ([5e0d3b7](https://github.com/synerise/synerise-design/commit/5e0d3b7c7175f3b129485861a990446945f04491))
## [0.49.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.49.1) (2020-03-18)
**Note:** Version bump only for package portal
# [0.49.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.49.0) (2020-03-18)
### Features
* **icon-picker:** add icon picker component ([c29d318](https://github.com/synerise/synerise-design/commit/c29d31815e1da48d23396135bf5c53f6fdea71e3))
## [0.48.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.48.3) (2020-03-18)
### Bug Fixes
* **core:** allow side effects ([0fcca2b](https://github.com/synerise/synerise-design/commit/0fcca2b3476b539a60d6d21af5a43a7d32135868))
## [0.48.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.48.2) (2020-03-17)
**Note:** Version bump only for package portal
## [0.48.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.48.1) (2020-03-17)
### Bug Fixes
* **avatar-group:** fix stytles, update stories ([8ffaa93](https://github.com/synerise/synerise-design/commit/8ffaa93514b73ffea8be75dfca535cad49c842a1))
* **avatar-group:** move avatar-group stories to catagory 'avatar' ([d298304](https://github.com/synerise/synerise-design/commit/d298304e8216b0ba6b74f8c3bf52b8ed9fd0d9dc))
# [0.48.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.48.0) (2020-03-17)
### Features
* **avatar-group:** add tests ([69a1e35](https://github.com/synerise/synerise-design/commit/69a1e3547a36c0a15a64c7e12189258a589c2112))
* **avatar-group:** init component ([e853b0e](https://github.com/synerise/synerise-design/commit/e853b0ed0e9e2cefa0e9721af6217085b2c538ee))
* **avatar-group:** styles, stories ([f17ebb0](https://github.com/synerise/synerise-design/commit/f17ebb0394d820a969f4a95b9e839912d612c762))
## [0.47.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.47.4) (2020-03-13)
### Bug Fixes
* **avatar:** incon and color change ([d121fac](https://github.com/synerise/synerise-design/commit/d121fac25da56caeb3eb0934fc53db4309494c7d))
## [0.47.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.47.3) (2020-03-12)
**Note:** Version bump only for package portal
## [0.47.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.47.2) (2020-03-12)
### Bug Fixes
* **avatar:** ran prettier on the code ([59d5648](https://github.com/synerise/synerise-design/commit/59d5648db8c2d05eabf9c3a24e1950af0d5e0be4))
* **avatar:** resolving conflicts ([f50d008](https://github.com/synerise/synerise-design/commit/f50d00875b6fd6ad3b57fb4d074c053221a4fce8))
* **dashboards:** added placeholder icon inside avatar to avoid empty avatar circles ([3764bd8](https://github.com/synerise/synerise-design/commit/3764bd89e6b7e90330e589318778a11a4dc1cb16))
* **dashboards:** added placeholder icon inside avatar to avoid empty avatar circles ([0d05936](https://github.com/synerise/synerise-design/commit/0d05936880cb720921d673015881c11eddadfed2))
## [0.47.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.47.1) (2020-03-11)
**Note:** Version bump only for package portal
# [0.47.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.47.0) (2020-03-06)
### Bug Fixes
- **item-filter:** fix translations & icons ([65ebe04](https://github.com/synerise/synerise-design/commit/65ebe04685624528f44f810cb655ca469f2f836a))
### Features
- **item-filter:** use Avatar with tooltip ([f090c08](https://github.com/synerise/synerise-design/commit/f090c081740bae8f666ec1d96109b488fe1e9420))
# [0.46.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.46.0) (2020-03-02)
### Features
- **avatar:** avatar improvement ([098bfe1](https://github.com/synerise/synerise-design/commit/098bfe1fb6b88b9be1eead83425d4af16a4f8026))
# [0.45.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.45.0) (2020-02-28)
### Features
- **item-filter:** update docs ([a411237](https://github.com/synerise/synerise-design/commit/a4112374fdb77ae5884adcd3b76f17e1edd7d6e9))
- **item-filter:** update list item ([a5696db](https://github.com/synerise/synerise-design/commit/a5696db303a548756814f0dc8fe473ca1b60b300))
## [0.44.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.44.1) (2020-02-28)
**Note:** Version bump only for package portal
# [0.44.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.44.0) (2020-02-28)
### Features
- **input:** add label with tooltip component ([4359a43](https://github.com/synerise/synerise-design/commit/4359a43130b7d146d8f49a23da8aaed550865ac2))
# [0.43.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.43.0) (2020-02-26)
### Features
- **button:** custom-color type instead of danger, warning and success ([4479348](https://github.com/synerise/synerise-design/commit/447934862ea6ff1154bb1c38ac63e553c2bb4f92))
# [0.42.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.42.0) (2020-02-26)
### Features
- **add-button:** create AddButton component ([53fc502](https://github.com/synerise/synerise-design/commit/53fc50294a9133e4692313e4860e78a4cd0847fd))
## [0.41.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.41.1) (2020-02-26)
### Bug Fixes
- **deps:** update dependency antd to v3.26.12 ([690717d](https://github.com/synerise/synerise-design/commit/690717d06e322aee18f65644971ef1e0779d5d93))
# [0.41.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.41.0) (2020-02-25)
### Bug Fixes
- **button-group:** fix fullwidth ([ae11620](https://github.com/synerise/synerise-design/commit/ae1162003811100b6246b36e42b7ab1eb89cc8de))
### Features
- **button-group:** add buttonsPosition prop ([6466b4f](https://github.com/synerise/synerise-design/commit/6466b4f2cd238142599017f0d2306ea8674d361a))
# [0.40.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.40.0) (2020-02-24)
### Features
- **navbar:** update stories ([2f63d1a](https://github.com/synerise/synerise-design/commit/2f63d1a067c087ba0b9e09c604fce5544b43e2b0))
# [0.39.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.39.0) (2020-02-24)
### Bug Fixes
- **item-filter:** fix types ([6eec36c](https://github.com/synerise/synerise-design/commit/6eec36c928c810023c24f3ad026994c34c1d7618))
- **item-filter:** remove unused imports ([ffe2dfc](https://github.com/synerise/synerise-design/commit/ffe2dfc5bee613e3be33c30c6f719e49101d2dad))
### Features
- **item-filter:** add ItemFilter header and search ([e1ceeda](https://github.com/synerise/synerise-design/commit/e1ceeda39327ace0a52c6695b0fb3e724e574828))
- **item-filter:** add list of filters ([9db1087](https://github.com/synerise/synerise-design/commit/9db108782bebe4021c61790d1a4831010f25f0c0))
- **item-filter:** bootstrap component ([288f34a](https://github.com/synerise/synerise-design/commit/288f34ab4cad32ad43c257752625cf7a0d0d6fd8))
- **item-filter:** connect search with list of filters ([c21edc0](https://github.com/synerise/synerise-design/commit/c21edc08850322f5acc24f544f43dbf388977834))
- **item-filter:** selected item on top of list ([40585d1](https://github.com/synerise/synerise-design/commit/40585d1634f68b3f4d8d76d59d2cc02abbd269c5))
- **item-filter:** use Drawer with search bar ([4081dfb](https://github.com/synerise/synerise-design/commit/4081dfbc1cfe48259fd5e7b6f785c0c494cbab50))
- **search-bar:** add searchbar component ([e67c7cc](https://github.com/synerise/synerise-design/commit/e67c7cc0309beb49bf41b40eaf4a35ac71423053))
## [0.38.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.38.1) (2020-02-21)
### Bug Fixes
- **slider:** remove vertical variant from storybook ([91ae6d8](https://github.com/synerise/synerise-design/commit/91ae6d84ec30140cb3eb4d3d18d8941f8d72f2a5))
# [0.38.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.38.0) (2020-02-21)
### Features
- **result:** add noSearchResults prop, upadte styles ([d8021ea](https://github.com/synerise/synerise-design/commit/d8021ea2a80a7141b15d4074c3af69e3538b7c7a))
# [0.37.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.37.0) (2020-02-19)
### Features
- **slider:** add story with always visible labels ([ddd52e9](https://github.com/synerise/synerise-design/commit/ddd52e9509bb9b4e55651f6a71c8416154fd6b3e))
# [0.36.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.36.0) (2020-02-19)
### Bug Fixes
- **button:** rename props spinner -> loading ([7798910](https://github.com/synerise/synerise-design/commit/77989102abf853873cf27271da8746aa99c9de88))
- **drawer:** fix searchInput styles ([091c166](https://github.com/synerise/synerise-design/commit/091c1664ef22e19e0b7ed6d7ea5bacdc8e77e11f))
- **drawer:** fix searchInput styles ([0bb77bc](https://github.com/synerise/synerise-design/commit/0bb77bcf8c5230184ffd37f995d0dd3fe834e7c7))
### Features
- **drawer:** add Drawer with search ([4b95b61](https://github.com/synerise/synerise-design/commit/4b95b61de615537005cfb626c55a0e250ebbec8d))
# [0.35.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.35.0) (2020-02-18)
### Features
- **manageable-list:** add filter list item ([87cb274](https://github.com/synerise/synerise-design/commit/87cb274bdea02a038b3e19706ade22015f219aa7))
- **manageable-list:** move all labels, text, etc to 'texts' props ([7be555c](https://github.com/synerise/synerise-design/commit/7be555cef05d44a081f5f6c7794f584f8e952247))
## [0.34.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.34.1) (2020-02-17)
### Bug Fixes
- **popconfirm:** fix styles ([44bceea](https://github.com/synerise/synerise-design/commit/44bceea04e993c1e551e080bf12fd2bfebc78c9b))
# [0.34.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.34.0) (2020-02-13)
### Bug Fixes
- **modal:** update story ([c07f64f](https://github.com/synerise/synerise-design/commit/c07f64fde63932dde3d2f38b3021ad559da8b044))
- **result:** update default story ([2a59844](https://github.com/synerise/synerise-design/commit/2a5984424bd0a242b1a56aad211e3043d6fb91e9))
- **result:** update default story ([506fe53](https://github.com/synerise/synerise-design/commit/506fe53431e7f434ab8a1f00d95c4d5e7dbcd5bc))
### Features
- **modal:** add blank modal mode ([eaa2e04](https://github.com/synerise/synerise-design/commit/eaa2e04ff0bc0afd9fb118f6a7b9e9cf9627e287))
- **result:** add stories with Result on Modal ([ca75d1c](https://github.com/synerise/synerise-design/commit/ca75d1c87dd6735925d24b8cc40c9fdd9d317094))
- **result:** add story with textarea ([121d047](https://github.com/synerise/synerise-design/commit/121d047dc883bc57213769d5950b99dba618529b))
- **result:** add support for custom icons ([bf11e5d](https://github.com/synerise/synerise-design/commit/bf11e5df83c52736820407a0cac658fa40f43be3))
## [0.33.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.33.1) (2020-02-12)
### Bug Fixes
- **button:** update storybook ([551399e](https://github.com/synerise/synerise-design/commit/551399e0d8b5af642390bf603c65c3e7e0771599))
# [0.33.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.33.0) (2020-02-12)
### Bug Fixes
- **button:** button styles ([4632075](https://github.com/synerise/synerise-design/commit/4632075d3d231451d518f99fad1830591c438437))
- **button:** fix styles ([a6d956d](https://github.com/synerise/synerise-design/commit/a6d956d132ccfc109f9ed35aca019bebdc4903dd))
- **button:** hover state styles, colors ([a14b299](https://github.com/synerise/synerise-design/commit/a14b2996f56c02d96aab90c7d01b6643ada2d8bd))
- **button:** remove box-shadows on hover ([982fde4](https://github.com/synerise/synerise-design/commit/982fde4f822abbdc604e1dc761682948fe1bb50c))
- **button:** update storybook ([800c654](https://github.com/synerise/synerise-design/commit/800c654eccbe05db73e2bc9e306896d521d31f73))
- **button-group:** update storybook ([22c55e9](https://github.com/synerise/synerise-design/commit/22c55e956824c778ea7f09e1164d0aa169967e96))
- **buttons:** fix colors ([36b887f](https://github.com/synerise/synerise-design/commit/36b887f4bc4099304b6bfbb2e6b8d7c48cbcc17b))
### Features
- **button:** add large size of buttons ([8c79732](https://github.com/synerise/synerise-design/commit/8c797328ec3664be76f421918f20c06a074a5d67))
- **button:** add ripple animation on click ([92bc936](https://github.com/synerise/synerise-design/commit/92bc936dd8c6a3b1b34566084be078f25c70e66f))
- **button:** add spinner animation ([6259a60](https://github.com/synerise/synerise-design/commit/6259a609cfc15d9f83e27db8a24ea2219c29582a))
## [0.32.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.32.4) (2020-02-06)
### Bug Fixes
- **select:** fix empty list styles ([4ea770d](https://github.com/synerise/synerise-design/commit/4ea770def39cdd6c29a89152da042c08a6610ec0))
## [0.32.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.32.1) (2020-02-03)
### Bug Fixes
- **checkbox:** fix no animation on check ([ade4409](https://github.com/synerise/synerise-design/commit/ade4409d66f5b22887d9e98b605c8b18beaf5854))
# [0.32.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.32.0) (2020-01-30)
### Features
- **dropdown:** autofocus DropdownSearch ([b73327f](https://github.com/synerise/synerise-design/commit/b73327fbc3027dc588dc16d6cbc377c84b359040))
## [0.31.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.31.4) (2020-01-29)
### Bug Fixes
- **button:** spreading ([73eacd2](https://github.com/synerise/synerise-design/commit/73eacd2e0798555a226e9f7c248b63df5658b098))
## [0.31.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.31.2) (2020-01-27)
### Bug Fixes
- **list:** list padding corrected ([8b40531](https://github.com/synerise/synerise-design/commit/8b40531122869bd47a266e7bb396e2205a3bde5b))
## [0.31.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.31.1) (2020-01-24)
### Bug Fixes
- **button-group:** add size prop ([6ac3c52](https://github.com/synerise/synerise-design/commit/6ac3c52b93d718b0a25f07e8db101a606295a0ad))
# [0.31.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.31.0) (2020-01-23)
### Bug Fixes
- **avatar:** page header component fixes ([9beecdd](https://github.com/synerise/synerise-design/commit/9beecddeb37a8b44e4ada380421102d713ca19d2))
- **avatar:** resolve conflicts ([1584324](https://github.com/synerise/synerise-design/commit/15843244b160cbae3b0ce1cc9d635918fe67f62a))
### Features
- **tabs:** ability to disable underscore active ([1ce9665](https://github.com/synerise/synerise-design/commit/1ce96658168d02a9620f98d4d1d54b7d71e72261))
# [0.30.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.30.0) (2020-01-20)
### Features
- **progress-bar:** use strings instead of enums in props ([0076b66](https://github.com/synerise/synerise-design/commit/0076b6693f83eeb8e747177b86be3cce465a3273))
## [0.29.6](https://github.com/synerise/synerise-design/compare/[email protected]@0.29.6) (2020-01-16)
### Bug Fixes
- **progress-bar:** fix width of ant-progress-inner element ([ba47248](https://github.com/synerise/synerise-design/commit/ba4724895a4c8b0485dfbbc1f7fd53d956cbf1f5))
## [0.29.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.29.2) (2020-01-14)
### Bug Fixes
- **modal:** fix onClick method on close button ([60d3ce2](https://github.com/synerise/synerise-design/commit/60d3ce2452a3451a69598dc46335e25c134afa80))
- **navbar:** removed duplicated navbar ([2a7c038](https://github.com/synerise/synerise-design/commit/2a7c038ea7ebf1460c6f1882cc1992b99f8c168d))
## [0.29.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.29.1) (2020-01-13)
### Bug Fixes
- **list:** add divider list type solid ([83c89bd](https://github.com/synerise/synerise-design/commit/83c89bd8556c9d82602d5f713d42790979a96a0a))
- **list:** delete wraper on action element ([783624d](https://github.com/synerise/synerise-design/commit/783624dfbfb938eaaa013c396c4959beeea0fee2))
# [0.29.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.29.0) (2020-01-13)
### Features
- **slider:** allow add color map for slider ([6d34662](https://github.com/synerise/synerise-design/commit/6d346624b9c0548add47691a4523998557c39719))
# [0.28.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.28.0) (2020-01-10)
### Features
- **slider:** allow add color map for slider ([ccf6654](https://github.com/synerise/synerise-design/commit/ccf66542ef732f65fe374ea910de5a882ecb1d16))
## [0.27.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.27.1) (2020-01-02)
### Bug Fixes
- **icon:** add dynamic loading for icons in storybook ([fc277b8](https://github.com/synerise/synerise-design/commit/fc277b824728b200c979ecf234eb1f137be253e2))
# [0.27.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.27.0) (2019-12-30)
### Features
- **icon:** add custom block icons ([7fbbdc8](https://github.com/synerise/synerise-design/commit/7fbbdc815ab6dfcb83accbbf21b0291a00568121))
# [0.26.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.26.0) (2019-12-30)
### Bug Fixes
- **deps:** pin dependency antd to 3.26.3 ([ef5eb1f](https://github.com/synerise/synerise-design/commit/ef5eb1f3bcbd140fb8befcc7e49309a46980f340))
### Features
- **autocomplete:** add styles, docs and tests ([8810626](https://github.com/synerise/synerise-design/commit/88106266f47803e8ef2790242e3a2d82e95760ef))
## [0.25.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.25.2) (2019-12-23)
**Note:** Version bump only for package portal
## [0.25.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.25.1) (2019-12-18)
### Bug Fixes
- 🐛 Added missing icons, storybook update script ([c56a255](https://github.com/synerise/synerise-design/commit/c56a255fe015cd6a84e591249dda3f6d672b6c94))
- 🐛 Added missing icons, storybook update script ([e37101d](https://github.com/synerise/synerise-design/commit/e37101d4eddfa56c5c5b8e5bd8db5b4f0f42bed8))
# [0.25.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.25.0) (2019-12-17)
### Bug Fixes
- **result:** story button type ([e8fc5f3](https://github.com/synerise/synerise-design/commit/e8fc5f355f4102b708ca15d2bdcf3ce3b28879ed))
### Features
- **result:** add docs ([62a6335](https://github.com/synerise/synerise-design/commit/62a6335a6ca3ba649ae4d5a4754c3fc41092ae2f))
- **result:** structure for result component ([d9455b5](https://github.com/synerise/synerise-design/commit/d9455b5fc0196d02afb8e0096cac706fe684cc5f))
# [0.24.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.24.0) (2019-12-10)
### Features
- **icon:** add edit noline s icon ([f99b3ba](https://github.com/synerise/synerise-design/commit/f99b3ba5f939e709482436e8ddaa82fb7389eb4b))
# [0.23.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.23.0) (2019-12-06)
### Features
- update ant to 3.26.0 ([d67df46](https://github.com/synerise/synerise-design/commit/d67df4605844fb09680096df333886db40cb7c32))
## [0.22.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.22.1) (2019-12-06)
### Bug Fixes
- 🐛 Corrected error display logic ([d6597df](https://github.com/synerise/synerise-design/commit/d6597dfe93a251b54c9bb107264ec81dfc12b1df))
# [0.22.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.22.0) (2019-12-04)
### Features
- **radio:** Fix radio button style ([a798b8f](https://github.com/synerise/synerise-design/commit/a798b8f113869c2a7fb5dc571e8e105f1b79173d))
# [0.21.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.21.0) (2019-12-03)
### Features
- 🎸 Optional prop fileAmount ([36e3ceb](https://github.com/synerise/synerise-design/commit/36e3cebce4068527874dee756955da166a650b30))
# [0.20.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.20.0) (2019-11-22)
### Features
- **radio:** Enhance radio button ([343ab5b](https://github.com/synerise/synerise-design/commit/343ab5b3f7fc4e7f6d95084df941155823f7a14e))
## [0.19.5](https://github.com/synerise/synerise-design/compare/[email protected]@0.19.5) (2019-11-12)
### Bug Fixes
- **tabs:** html type button for container, ReactNode or string as label ([1167cad](https://github.com/synerise/synerise-design/commit/1167cad2f0607d91ade00790beddd30d8d063dff))
## [0.19.4](https://github.com/synerise/synerise-design/compare/[email protected]@0.19.4) (2019-11-12)
**Note:** Version bump only for package portal
## [0.19.3](https://github.com/synerise/synerise-design/compare/[email protected]@0.19.3) (2019-11-12)
**Note:** Version bump only for package portal
## [0.19.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.19.2) (2019-11-12)
### Bug Fixes
- **slider:** add styling fixes to slider ([3596448](https://github.com/synerise/synerise-design/commit/35964488a317c27e6ac184d3b7f3ab288ac0d87d))
## [0.19.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.19.1) (2019-11-09)
**Note:** Version bump only for package portal
# [0.19.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.19.0) (2019-11-06)
### Features
- **navbar:** add navbar ([d0ffc00](https://github.com/synerise/synerise-design/commit/d0ffc003ae64c39315e4a187c284fdb88dec07bc))
- **navbar:** add navbar ([6affab8](https://github.com/synerise/synerise-design/commit/6affab875d94e1bdcfc2c93a204795fa2c1e6388))
- **page-header:** add page-header component ([768cb8c](https://github.com/synerise/synerise-design/commit/768cb8c6e9af1def032ea8718285c101bb506ef1))
- **page-header:** add tests ([7b09db6](https://github.com/synerise/synerise-design/commit/7b09db60d66033feb54412f7c7ad16ea5cd1fb6f))
- **page-header:** write missed readme file, code refactor ([5dc1433](https://github.com/synerise/synerise-design/commit/5dc1433c0c9bd3a8dfd0f1d173b58c72f84fe72f))
- **popconfirm:** add standard antd popconfirm ([0244dfc](https://github.com/synerise/synerise-design/commit/0244dfc7694bf74930054a00af03fe996d5aa90a))
# [0.18.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.18.0) (2019-11-05)
### Bug Fixes
- **badge:** counter badge styles ([7ba3dd1](https://github.com/synerise/synerise-design/commit/7ba3dd10f8e5393b5f3921320b5803cadec0e934))
### Features
- **badge:** flag styles ([29a23bb](https://github.com/synerise/synerise-design/commit/29a23bb2d0c74388f7af0c7559e13707aaa4c092))
# [0.17.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.17.0) (2019-11-04)
### Bug Fixes
- add interface for stories config ([4929233](https://github.com/synerise/synerise-design/commit/4929233344f67874da841592d947ec6a99f792b6))
### Features
- storybook improvement with custom config ([ea325eb](https://github.com/synerise/synerise-design/commit/ea325ebefbb58c200482ef81d1ec91bb18faf21c))
- update stories to new scheme ([96ad5ab](https://github.com/synerise/synerise-design/commit/96ad5ab1f52bf15874affabb723e3de7fc2ddb5a))
- **message:** add message component ([a82fbae](https://github.com/synerise/synerise-design/commit/a82fbae03d79b6bbe09082f7e6b67992dcd62782))
# [0.16.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.16.0) (2019-10-30)
### Bug Fixes
- **avatar:** tests, storybook ([785820e](https://github.com/synerise/synerise-design/commit/785820e63437cf47a818e53388e37ccda8cf3fa3))
### Features
- **avatar:** add status badges position, hover styles ([a7fbdeb](https://github.com/synerise/synerise-design/commit/a7fbdeb88a48ed3d1852571e6c141cd10734e545))
# [0.15.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.15.0) (2019-10-30)
### Features
- **manageable-list:** add drag and drop ([786a1db](https://github.com/synerise/synerise-design/commit/786a1dbe49875add642861aeeb7912622b0d21fd))
- **manageable-list:** add styles ([f6db380](https://github.com/synerise/synerise-design/commit/f6db380cf3ab2a826b452da7902ab893dd179fe9))
- **manageable-list:** add styles for grey background ([55384e5](https://github.com/synerise/synerise-design/commit/55384e591675860c15e0e22ad999d740ce5cfe38))
- **manageable-list:** add support for content list ([d0730be](https://github.com/synerise/synerise-design/commit/d0730be07dab4bed07843300ab52fe658be571cc))
# [0.14.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.14.0) (2019-10-29)
### Features
- **input:** Fix error with jumping cursor ([e459585](https://github.com/synerise/synerise-design/commit/e45958570419ba172724bbd5a9e2a8224b5e8b8c))
# [0.13.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.13.0) (2019-10-24)
### Bug Fixes
- **manageable-list:** fix package name, import in storybook ([5d2f815](https://github.com/synerise/synerise-design/commit/5d2f81500fc26936678b3600ff8de1268e4b7865))
### Features
- **card-tabs:** add actions ([f16a670](https://github.com/synerise/synerise-design/commit/f16a6706685f35be59e4aa69674521c64ca5b7ef))
- **card-tabs:** add base componets ([4f4c754](https://github.com/synerise/synerise-design/commit/4f4c754976d8b6fe1dfc5ddd317d0726d993f0a7))
- **card-tabs:** add default example in storybook ([4795d78](https://github.com/synerise/synerise-design/commit/4795d78e4e51e3b0cb1123cdc26872d55f2be246))
- **card-tabs:** add documentation ([b9a3745](https://github.com/synerise/synerise-design/commit/b9a3745a6abb46b1481ecba3b605565fa8147ea3))
- **card-tabs:** add more examples in storybook ([6bc07a3](https://github.com/synerise/synerise-design/commit/6bc07a3dabe0acd97644e49397e8e0b986027e4b))
- **card-tabs:** add sortable tabs ([51f2f4d](https://github.com/synerise/synerise-design/commit/51f2f4d5d350db94f6e78f77efca9b8b523cbddb))
- **card-tabs:** add styles for active, hover, disabled, validate states ([16e46fa](https://github.com/synerise/synerise-design/commit/16e46fad5e3edb942575b6dd633943b156eac12b))
- **card-tabs:** add suffix single icon ([46bf7c5](https://github.com/synerise/synerise-design/commit/46bf7c58740f8f7c271166f4f8c5b62a83c144b3))
- **card-tabs:** add support for grey background ([cfdc2a4](https://github.com/synerise/synerise-design/commit/cfdc2a420613098516b6330ccf83aee11e3e65ee))
- **card-tabs:** add tab name inline edit ([05deb7d](https://github.com/synerise/synerise-design/commit/05deb7d3353c8f05e499137cf888a46111d6e282))
- **card-tabs:** examples in storybook ([a8125db](https://github.com/synerise/synerise-design/commit/a8125db4f59c6b53cc50174c216d252c1aafa1f4))
- **card-tabs:** refactor ([3142580](https://github.com/synerise/synerise-design/commit/3142580d2e8b6116ab921dcc7c3d3ef4339c8879))
- **card-tabs:** refactor ([fad9bf1](https://github.com/synerise/synerise-design/commit/fad9bf1c556b8cd040a6a28c99cb05c21d415c67))
- **manageablelist:** add component ([bcd1163](https://github.com/synerise/synerise-design/commit/bcd11633fb6ea9591f98bcc38a56ce4e9974a8c0))
- **manageablelist:** add tests ([41ff7c7](https://github.com/synerise/synerise-design/commit/41ff7c75bc10d59ae39692c507b1db68a9fb08fe))
- **manageablelist:** add toggle button ([9adc8d4](https://github.com/synerise/synerise-design/commit/9adc8d40d5425091c616e77138425fd66471474c))
- **manageablelist:** refactor ([954aeaa](https://github.com/synerise/synerise-design/commit/954aeaa810a64bae9a0109af29b9c8735de427f0))
- **manageablelist:** update storybook, fix minor issues ([e165a94](https://github.com/synerise/synerise-design/commit/e165a94307c6742830713ec75fe73f573cbe9865))
- **manageablelist:** update styles ([6d2c85a](https://github.com/synerise/synerise-design/commit/6d2c85abf07b0db49520521fcc37445703b4db05))
- **responsive-tabs:** restore basic tabs component ([49f300a](https://github.com/synerise/synerise-design/commit/49f300a384d3486c1fd3883255f26afde71a4712))
- **tabs:** add disabled tab state ([66ed546](https://github.com/synerise/synerise-design/commit/66ed5462b578bfb8f2ea0a1d26378a110e33633d))
- **tabs:** adds responsivity ([dbedaf8](https://github.com/synerise/synerise-design/commit/dbedaf8b44827fd82069ea6b30a0790dbb9de74c))
- **tabs:** create tabs component ([9477f10](https://github.com/synerise/synerise-design/commit/9477f10fdc2b3605064611043704892717bd11a0))
- **tabs:** fix issues from eslint ([5eccc5f](https://github.com/synerise/synerise-design/commit/5eccc5fc5810f3597b2fdb7289bc4f5e463bdf56))
- **tabs:** update styles ([d1f5cea](https://github.com/synerise/synerise-design/commit/d1f5ceacde4ef74c49033c20c0fb7505df62962b))
# [0.12.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.12.0) (2019-10-22)
### Features
- **input:** Add enhanced InputGroup ([d9fbfb1](https://github.com/synerise/synerise-design/commit/d9fbfb1))
## [0.11.2](https://github.com/synerise/synerise-design/compare/[email protected]@0.11.2) (2019-10-21)
**Note:** Version bump only for package portal
## [0.11.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.11.1) (2019-10-18)
### Bug Fixes
- **icon:** fix icon components ([c2f51df](https://github.com/synerise/synerise-design/commit/c2f51df))
# [0.11.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.11.0) (2019-10-18)
### Features
- **form:** add field set component ([a2a52ba](https://github.com/synerise/synerise-design/commit/a2a52ba))
## [0.10.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.10.1) (2019-10-18)
### Bug Fixes
- **input:** export raw inputs ([47e18b3](https://github.com/synerise/synerise-design/commit/47e18b3))
# [0.10.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.10.0) (2019-10-17)
### Bug Fixes
- **tags:** ability to disable single tag (storybook) ([e209237](https://github.com/synerise/synerise-design/commit/e209237))
- **tags:** disable entire group knob bug (storybook) ([fe17293](https://github.com/synerise/synerise-design/commit/fe17293))
- **tags:** remove disable single tag option (storybook) ([86c52d2](https://github.com/synerise/synerise-design/commit/86c52d2))
- **tags:** storybook changes ([6a4a7c3](https://github.com/synerise/synerise-design/commit/6a4a7c3))
- **tags:** styling ([030a100](https://github.com/synerise/synerise-design/commit/030a100))
- **tags:** styling for status & small shapes ([54879d6](https://github.com/synerise/synerise-design/commit/54879d6))
### Features
- **tags:** ability to add a tag, minor improvements ([00699f2](https://github.com/synerise/synerise-design/commit/00699f2))
- **tags:** add abilities ([e19eb38](https://github.com/synerise/synerise-design/commit/e19eb38))
- **tags:** add ability to create a tag ([0220b7c](https://github.com/synerise/synerise-design/commit/0220b7c))
- **tags:** add more knobs to storybook ([85897c7](https://github.com/synerise/synerise-design/commit/85897c7))
- **tags:** add more knobs to storybook ([de3c670](https://github.com/synerise/synerise-design/commit/de3c670))
- **tags:** add more knobs to storybook ([111bf8f](https://github.com/synerise/synerise-design/commit/111bf8f))
- **tags:** add status shapes to tag stories ([887cdb9](https://github.com/synerise/synerise-design/commit/887cdb9))
- **tags:** add support for images ([ce57e86](https://github.com/synerise/synerise-design/commit/ce57e86))
- **tags:** additional tag modes styling ([a0448ff](https://github.com/synerise/synerise-design/commit/a0448ff))
- **tags:** disable effects if tag is not actionable ([0d3147d](https://github.com/synerise/synerise-design/commit/0d3147d))
- **tags:** implement color effects ([a1980eb](https://github.com/synerise/synerise-design/commit/a1980eb))
- **tags:** implement removable tags ([06f1358](https://github.com/synerise/synerise-design/commit/06f1358))
- **tags:** initial dropdown support (add, create) ([8a45c0f](https://github.com/synerise/synerise-design/commit/8a45c0f))
- **tags:** initial tag component ([cbb1ca0](https://github.com/synerise/synerise-design/commit/cbb1ca0))
## [0.9.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.9.1) (2019-10-16)
### Bug Fixes
- **input:** allow for input margin reset ([caf9642](https://github.com/synerise/synerise-design/commit/caf9642))
# [0.9.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.9.0) (2019-10-16)
### Bug Fixes
- **card-select:** box-shadow on hover ([38f2454](https://github.com/synerise/synerise-design/commit/38f2454))
- **card-select:** box-shadow on hover ([ed5e3aa](https://github.com/synerise/synerise-design/commit/ed5e3aa))
- **card-select:** title margin ([438028b](https://github.com/synerise/synerise-design/commit/438028b))
- update package, changes into stories ([282bf75](https://github.com/synerise/synerise-design/commit/282bf75))
### Features
- **card:** support for icons and fixes to styling ([47fb462](https://github.com/synerise/synerise-design/commit/47fb462))
- **card-select:** add initial card-select component (WIP) ([cd02dda](https://github.com/synerise/synerise-design/commit/cd02dda))
- **card-select:** add initial card-select component (WIP) ([9ac3ad7](https://github.com/synerise/synerise-design/commit/9ac3ad7))
- **card-select:** add more examples, fix minor issues ([d86ae2c](https://github.com/synerise/synerise-design/commit/d86ae2c))
- **card-select:** add more examples, fix minor issues ([8baf643](https://github.com/synerise/synerise-design/commit/8baf643))
- **card-select:** new features and styling fixes ([201b4b1](https://github.com/synerise/synerise-design/commit/201b4b1))
- **card-select:** new features and styling fixes ([e62f5fe](https://github.com/synerise/synerise-design/commit/e62f5fe))
- **card-select:** new features and styling fixes ([a5b7229](https://github.com/synerise/synerise-design/commit/a5b7229))
- **card-select:** new features and styling fixes ([b6fbda3](https://github.com/synerise/synerise-design/commit/b6fbda3))
- **card-select:** onClick method and improvements ([4b4e8e3](https://github.com/synerise/synerise-design/commit/4b4e8e3))
- **card-select:** onClick method and improvements ([e61a38e](https://github.com/synerise/synerise-design/commit/e61a38e))
- **card-select:** refactor (WIP) ([08e8184](https://github.com/synerise/synerise-design/commit/08e8184))
- **card-select:** refactor (WIP) ([3083391](https://github.com/synerise/synerise-design/commit/3083391))
- **card-select:** small card anatomy ([2dc82f4](https://github.com/synerise/synerise-design/commit/2dc82f4))
- **card-select:** small card anatomy ([2f9ebbf](https://github.com/synerise/synerise-design/commit/2f9ebbf))
- **card-select:** storybook improvements ([68de601](https://github.com/synerise/synerise-design/commit/68de601))
- **card-select:** storybook improvements ([442baa3](https://github.com/synerise/synerise-design/commit/442baa3))
## [0.8.1](https://github.com/synerise/synerise-design/compare/[email protected]@0.8.1) (2019-10-16)
### Bug Fixes
- **inline-edit:** add hideIcon flag ([d089494](https://github.com/synerise/synerise-design/commit/d089494))
- **inline-edit:** fix onBlur ([670283f](https://github.com/synerise/synerise-design/commit/670283f))
# [0.8.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.8.0) (2019-10-16)
### Features
- **input:** fix styles ([25e5ed6](https://github.com/synerise/synerise-design/commit/25e5ed6))
# [0.7.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.7.0) (2019-10-15)
### Bug Fixes
- **card:** change storybook content bg color to white ([dac8f94](https://github.com/synerise/synerise-design/commit/dac8f94))
- **inline-edit:** typings, color palette config ([c7fedcc](https://github.com/synerise/synerise-design/commit/c7fedcc))
- **modal:** 'improvements' ([111b239](https://github.com/synerise/synerise-design/commit/111b239))
- **modal:** fix mask backdrop color and animation ([5f64ec5](https://github.com/synerise/synerise-design/commit/5f64ec5))
### Features
- **avatar:** enhance component according to zeplin ([f56fa40](https://github.com/synerise/synerise-design/commit/f56fa40))
- **badge:** create base structure and add stories example for component ([790a664](https://github.com/synerise/synerise-design/commit/790a664))
- **card:** add compact header type ([c48f281](https://github.com/synerise/synerise-design/commit/c48f281))
- **card:** add knob for size prop ([2da6e1c](https://github.com/synerise/synerise-design/commit/2da6e1c))
- **card:** add more knobs ([e7a74e0](https://github.com/synerise/synerise-design/commit/e7a74e0))
- **card:** add new sizes to storybook ([f465b34](https://github.com/synerise/synerise-design/commit/f465b34))
- **card:** add story for CardGroup component ([4104cef](https://github.com/synerise/synerise-design/commit/4104cef))
- **card:** initial card component ([d9d592c](https://github.com/synerise/synerise-design/commit/d9d592c))
- **divider:** add margin props ([1307887](https://github.com/synerise/synerise-design/commit/1307887))
- **dropdown:** add Dropdown elements ([2914b53](https://github.com/synerise/synerise-design/commit/2914b53))
- **list:** fix list styles and examples ([8936914](https://github.com/synerise/synerise-design/commit/8936914))
- **modal:** add ability to pick body background ([b7fe751](https://github.com/synerise/synerise-design/commit/b7fe751))
- **modal:** add ability to render w/o footer, pass down button props ([f2bf3ab](https://github.com/synerise/synerise-design/commit/f2bf3ab))
- **slider:** add slider component ([1a5e444](https://github.com/synerise/synerise-design/commit/1a5e444))
# [0.6.0](https://github.com/synerise/synerise-design/compare/[email protected]@0.6.0) (2019-10-09)
### Bug Fixes
- **modal:** loading state when using custom footer (storybook) ([fb7b7d2](https://github.com/synerise/synerise-design/commit/fb7b7d2))
- **tooltip:** add styling fixes to tooltip ([242f7fd](https://github.com/synerise/synerise-design/commit/242f7fd))
### Features
- **button-group:** add button group component ([46f485c](https://github.com/synerise/synerise-design/commit/46f485c))
- **button-group:** add more button customization (storybook) ([0b34223](https://github.com/synerise/synerise-design/commit/0b34223))
- **button-group:** initial button-group component ([faef5a0](https://github.com/synerise/synerise-design/commit/faef5a0))
- **dropdown:** Add overlay helper components ([d4a0e6b](https://github.com/synerise/synerise-design/commit/d4a0e6b))
- **icon:** add icon component ([e84fc24](https://github.com/synerise/synerise-design/commit/e84fc24))
- **modal:** add a custom footer example to storybook ([1076eb1](https://github.com/synerise/synerise-design/commit/1076eb1))
- **modal:** add example with header actions to storybook ([9370bef](https://github.com/synerise/synerise-design/commit/9370bef))
- **modal:** add size support ([dc76464](https://github.com/synerise/synerise-design/commit/dc76464))
- **modal:** customizing modal & styling ([85c798e](https://github.com/synerise/synerise-design/commit/85c798e))
- **progress-bar:** add progress-bar component ([78b04a3](https://github.com/synerise/synerise-design/commit/78b04a3))
- **progress-bar:** add progress-bar tests ([9616cb0](https://github.com/synerise/synerise-design/commit/9616cb0))
- **progress-bar:** CR fixes ([aad9d16](https://github.com/synerise/synerise-design/commit/aad9d16))
- **progress-bar:** refactor ([f510421](https://github.com/synerise/synerise-design/commit/f510421))
- **progress-bar:** use Progress component from antd ([cb8465e](https://github.com/synerise/synerise-design/commit/cb8465e))
- **select:** add error, label and description + additional styles ([8f58a29](https://github.com/synerise/synerise-design/commit/8f58a29))
# 0.5.0 (2019-10-03)
### Bug Fixes
- fix less paths ([344b097](https://github.com/synerise/synerise-design/commit/344b097))
- **tooltip:** fix tests ([bfdd8d3](https://github.com/synerise/synerise-design/commit/bfdd8d3))
### Features
- **button:** button ([b2a6f5f](https://github.com/synerise/synerise-design/commit/b2a6f5f))
- **checkbox:** create checkbox component ([c616c93](https://github.com/synerise/synerise-design/commit/c616c93))
- **checkbox:** styles ([f6f18a5](https://github.com/synerise/synerise-design/commit/f6f18a5))
- **divider:** add divider component ([fb0a04b](https://github.com/synerise/synerise-design/commit/fb0a04b))
- **dropdown:** add basic component ([5c338fb](https://github.com/synerise/synerise-design/commit/5c338fb))
- **input:** add input text field ([7099f19](https://github.com/synerise/synerise-design/commit/7099f19))
- **input-number:** Add component ([56b9f36](https://github.com/synerise/synerise-design/commit/56b9f36))
- **layout:** add layout component ([ca125d2](https://github.com/synerise/synerise-design/commit/ca125d2))
- **modal:** add modal component ([80b30ad](https://github.com/synerise/synerise-design/commit/80b30ad))
- **page-header:** add new component ([3f2e12c](https://github.com/synerise/synerise-design/commit/3f2e12c))
- **portal:** add color palette ([4b214bc](https://github.com/synerise/synerise-design/commit/4b214bc))
- **portal:** add colors palette ([8e320f6](https://github.com/synerise/synerise-design/commit/8e320f6))
- **radio:** add radio button ([826f69e](https://github.com/synerise/synerise-design/commit/826f69e))
- **radio:** enhance and style radio input ([75f389f](https://github.com/synerise/synerise-design/commit/75f389f))
- **select:** add select component ([97ae77e](https://github.com/synerise/synerise-design/commit/97ae77e))
- **table:** add new component ([b860b24](https://github.com/synerise/synerise-design/commit/b860b24))
- **table:** add search input and styles for checkbox ([565eb99](https://github.com/synerise/synerise-design/commit/565eb99))
- **table:** add selection menu feature ([f44142f](https://github.com/synerise/synerise-design/commit/f44142f))
- **table:** add title and subtitle support ([e84c201](https://github.com/synerise/synerise-design/commit/e84c201))
- **tooltip:** add tooltip component ([b7b47b5](https://github.com/synerise/synerise-design/commit/b7b47b5))
- **tooltip:** PR fixes ([f0dd422](https://github.com/synerise/synerise-design/commit/f0dd422))
- **typography:** add styled-components macros ([e62d35f](https://github.com/synerise/synerise-design/commit/e62d35f))
# 0.4.0 (2019-09-24)
### Bug Fixes
- fix less paths ([344b097](https://github.com/Synerise/synerise-designcommit/344b097))
- **tooltip:** fix tests ([bfdd8d3](https://github.com/Synerise/synerise-designcommit/bfdd8d3))
### Features
- **button:** button ([b2a6f5f](https://github.com/Synerise/synerise-designcommit/b2a6f5f))
- **checkbox:** create checkbox component ([c616c93](https://github.com/Synerise/synerise-designcommit/c616c93))
- **checkbox:** styles ([f6f18a5](https://github.com/Synerise/synerise-designcommit/f6f18a5))
- **dropdown:** add basic component ([5c338fb](https://github.com/Synerise/synerise-designcommit/5c338fb))
- **input:** add input text field ([7099f19](https://github.com/Synerise/synerise-designcommit/7099f19))
- **layout:** add layout component ([ca125d2](https://github.com/Synerise/synerise-designcommit/ca125d2))
- **modal:** add modal component ([80b30ad](https://github.com/Synerise/synerise-designcommit/80b30ad))
- **page-header:** add new component ([3f2e12c](https://github.com/Synerise/synerise-designcommit/3f2e12c))
- **portal:** add color palette ([4b214bc](https://github.com/Synerise/synerise-designcommit/4b214bc))
- **portal:** add colors palette ([8e320f6](https://github.com/Synerise/synerise-designcommit/8e320f6))
- **radio:** add radio button ([826f69e](https://github.com/Synerise/synerise-designcommit/826f69e))
- **radio:** enhance and style radio input ([75f389f](https://github.com/Synerise/synerise-designcommit/75f389f))
- **select:** add select component ([97ae77e](https://github.com/Synerise/synerise-designcommit/97ae77e))
- **table:** add new component ([b860b24](https://github.com/Synerise/synerise-designcommit/b860b24))
- **table:** add search input and styles for checkbox ([565eb99](https://github.com/Synerise/synerise-designcommit/565eb99))
- **table:** add selection menu feature ([f44142f](https://github.com/Synerise/synerise-designcommit/f44142f))
- **table:** add title and subtitle support ([e84c201](https://github.com/Synerise/synerise-designcommit/e84c201))
- **tooltip:** add tooltip component ([b7b47b5](https://github.com/Synerise/synerise-designcommit/b7b47b5))
- **tooltip:** PR fixes ([f0dd422](https://github.com/Synerise/synerise-designcommit/f0dd422))
- **typography:** add styled-components macros ([e62d35f](https://github.com/Synerise/synerise-designcommit/e62d35f))
| 56.52732 | 202 | 0.776485 | eng_Latn | 0.106578 |
f4c4dd8174eb94a020316368d4dc6597764a9a0a | 646 | md | Markdown | 2014/CVE-2014-4199.md | sei-vsarvepalli/cve | fbd9def72dd8f1b479c71594bfd55ddb1c3be051 | [
"MIT"
] | 4 | 2022-03-01T12:31:42.000Z | 2022-03-29T02:35:57.000Z | 2014/CVE-2014-4199.md | sei-vsarvepalli/cve | fbd9def72dd8f1b479c71594bfd55ddb1c3be051 | [
"MIT"
] | null | null | null | 2014/CVE-2014-4199.md | sei-vsarvepalli/cve | fbd9def72dd8f1b479c71594bfd55ddb1c3be051 | [
"MIT"
] | 1 | 2022-03-29T02:35:58.000Z | 2022-03-29T02:35:58.000Z | ### [CVE-2014-4199](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4199)
### Description
vm-support 0.88 in VMware Tools, as distributed with VMware Workstation through 10.0.3 and other products, allows local users to write to arbitrary files via a symlink attack on a file in /tmp.
### POC
#### Reference
- http://seclists.org/fulldisclosure/2014/Aug/71
#### Github
No GitHub POC found.
| 35.888889 | 193 | 0.739938 | eng_Latn | 0.445353 |
f4c552878b0d127b3665638ad379afa5952446e7 | 1,092 | md | Markdown | README.md | mauri-medina/peoplemanagement | de7bf4ba0b6aaf9eb92dd2b099ea1d7448bc24e4 | [
"Apache-2.0"
] | 7 | 2020-01-07T20:06:38.000Z | 2020-06-05T23:35:58.000Z | README.md | mauri-medina/peoplemanagement | de7bf4ba0b6aaf9eb92dd2b099ea1d7448bc24e4 | [
"Apache-2.0"
] | 14 | 2020-01-24T14:24:18.000Z | 2020-04-23T01:56:04.000Z | README.md | swnat/peoplemanagement | fafc8bde3e2c7847525a91763edb752c1dbf5108 | [
"Apache-2.0"
] | 4 | 2020-01-24T14:11:23.000Z | 2020-06-05T23:03:39.000Z | # People Management
Human resources recruitment monitoring system. It enables record keeping for candidates interviews and technical challenges.\
For the front end project, we use Angular 7.1.4 and Bootstrap 4. \
For the back end project, we use Spring boot 2.0 and Flowable BPM for modeler processes.
## This is our general architecture.
## Installation
First, you need to clone the project and follow steps for installation.\
[README Front end project](https://github.com/swnat/peoplemanagement/blob/master/front-end/README.md)\
[README Back end project](https://github.com/swnat/peoplemanagement/blob/master/back-end/README.md)\
[README Docker project](https://github.com/swnat/peoplemanagement/blob/master/Docker/README.md)
## Contributing
To contribute please read the CONTRIBUTING file of each project.
[CONTRIBUTING Front end project](https://github.com/swnat/peoplemanagement/blob/master/front-end/CONTRIBUTING.md)\
[CONTRIBUTING Back end project](https://github.com/swnat/peoplemanagement/blob/master/back-end/CONTRIBUTING.md)
| 47.478261 | 125 | 0.795788 | eng_Latn | 0.577616 |
f4c5b11587ca9418c2ad1a4180bcede97c192cbe | 2,614 | md | Markdown | _posts/2018-11-02-episode-19-unsung-heroes.md | TheCloudArch/thecloudarch.github.io | 5952e5a0db19250142e902b77e4d3fd727794ae1 | [
"MIT"
] | 2 | 2020-01-08T10:03:54.000Z | 2021-07-30T05:13:58.000Z | _posts/2018-11-02-episode-19-unsung-heroes.md | TheCloudArch/thecloudarch.github.io | 5952e5a0db19250142e902b77e4d3fd727794ae1 | [
"MIT"
] | null | null | null | _posts/2018-11-02-episode-19-unsung-heroes.md | TheCloudArch/thecloudarch.github.io | 5952e5a0db19250142e902b77e4d3fd727794ae1 | [
"MIT"
] | null | null | null | ---
author: chris
title: 'Episode 19: Unsung Heroes'
slug: episode-19-unsung-heroes
id: 223
date: '2018-11-02 14:54:15'
layout: post
categories:
- Interviews
---
Documentation is something we all rely on, especially in today's rapidly changing cloud world where the only constant seems to be change. Perhaps I'm a little obsessive, but I constantly use Microsoft's documentation to confirm things, even when I already know the answer. Like many people though, I never really considered what goes into making sure I have something to refer to and keeping it up to date with all the change going on. Nicolas and I had the pleasure of sitting down with Brenda Carter and Joe Davies from the Microsoft Documentation Team at Ignite recently to talk about how they do what they do, how you can help and what it takes to be a technical writer.
{:style="float: left;margin-right: 10px;margin-top: 10px;" height="150px" width="150px"} Brenda Carter is a Principal Technical Writer at Microsoft. Brenda works on enterprise and solution architecture across Microsoft's cloud platforms and services, from Office 365 to Azure. Recent focus areas include security and access management for Office 365 and other SaaS services, including protection for identities, devices, and files.
{:style="float: left;margin-right: 10px;margin-top: 10px;" height="150px" width="150px"} Joe Davies is a Senior Technical Writer at Microsoft. Throughout his career as an instructor, course developer, and technical writer, his driving concern has been presenting technical information in a way that enables someone to go from total ignorance to comfortable understanding as efficiently as possible.
If you have an feedback, questions or comments for the documentation team, you can reach them at [email protected]
<p><iframe width="100%" height="300" scrolling="no" frameborder="no" allow="autoplay" src="https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/523708998&color=%23ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false&show_teaser=true&visual=true"></iframe></p>
This Episode is brought to you by KEMP TECHNOLOGIES. Choose KEMP to optimize your multi-cloud application deployments and simplify multi-cloud application management. A single pane-of-glass for application delivery, KEMP provides a 360 degree view of your entire application environment, and even third-party ADCs. Download KEMP360 [for free today at kemptechnologies.com](https://kempte.ch/2MYXjew)
| 113.652174 | 674 | 0.796098 | eng_Latn | 0.994443 |
f4c5c55551c811eed74211cf0ce86176d5d36a8f | 4,105 | md | Markdown | README.md | brandonfancher/react-redux-talk | 96c944c5ee460385dd7cf9fe8ff2b4f4e8daadce | [
"MIT"
] | 1 | 2016-06-23T00:26:35.000Z | 2016-06-23T00:26:35.000Z | README.md | brandonfancher/react-redux-talk | 96c944c5ee460385dd7cf9fe8ff2b4f4e8daadce | [
"MIT"
] | null | null | null | README.md | brandonfancher/react-redux-talk | 96c944c5ee460385dd7cf9fe8ff2b4f4e8daadce | [
"MIT"
] | null | null | null | # react-redux-talk
**just another react redux talk**
_but with counters and colors!_
We'll review state, props, react-router, and more.
We'll talk about the pain redux aims to alleviate.
We'll talk about how it alleviates that pain.
We'll alleviate that pain.
## Commands to get started
**Clone this repo**
```
git clone https://github.com/brandonfancher/react-redux-talk.git
```
**Install**
```
npm install
```
**Start the application in dev mode with hot-module-replacement**
```
npm start
```
**To follow along with the talk, check out the first commit**
```
git checkout cd897cd
```
**Then follow along!**
# Some documentation
**What each commit covers**
* `cd897cd`: Initial Commit. The Counter and Color components work, but the CounterHistory and ColorHistory components aren't hooked up yet.
* `de2819d`: Get the CounterHistory and ColorHistory components to work by pushing the Counter and Color state higher and passing down props.
* `b781afd`: The CounterHistory and ColorHistory components are working with the Counter and Color components properly now, but those dashboards
lose their state if you leave them. We want state to persist when changing routes. This is where we set the foundation to push the state even higher.
* `4cc7ba2`: Push all app state and handlers (actionCreators) higher into parent App component that doesn't unmount. Stuff starts getting weird. Maybe there's a better way?
* `d730f06`: Enter redux. Configure and migrate to react-redux.
* `774a9e9`: Check out the redux dev tools chrome browser extension!
* `e5ef1d8`: Separate out concerns a bit: Separate state for each dashboard into separate reducer files.
**Mapping out our initial component hierarchy, state and props**
Component | Has State | Receives Props
--- | --- | ---
**Root** | -- | `history` (object)
-->**Routes** | -- | --
-->-->**App** | -- | `children` (object)
-->-->-->**Header** | -- | --
-->-->-->**Home** | -- | --
-->-->-->**DashboardCounter** | `countEntries` (array) | --
-->-->-->-->**Counter** | `counter` (number) | --
-->-->-->-->**CounterHistory** | -- | `countEntries` (array)
-->-->-->**DashboardColor** | `colorEntries` (array) | --
-->-->-->-->**Color** | `color` (string) | --
-->-->-->-->**ColorHistory** | -- | `colorEntries` (array)
# Resources
* Free course from redux' creator--Dan Abramov (30 videos): https://github.com/tayiorbeii/egghead.io_redux_course_notes
* Community notes on that course on github: https://github.com/tayiorbeii/egghead.io_redux_course_notes
* New course (27 videos) from Dan: [Building React Applications with Idiomatic Redux](https://egghead.io/courses/building-react-applications-with-idiomatic-redux)
* Free 20-video course by Wes Bos: [Learn Redux](https://learnredux.com/)
* Redux documentation: http://redux.js.org/index.html
* Redux documentation for react specifically: http://redux.js.org/docs/basics/UsageWithReact.html
* Boilerplate for quickly getting a react project started. See Below.
# Cool stuff from the boilerplate that serves as the foundation for this app:
I started this app by cloning another repository, _react-kickstart_, which is a react + webpack boilerplate.
That way, I didn't have to spend a ton of time getting everything set up the way I wanted it.
## This boilerplate has lots of cool features
* webpack + vanilla hot-module-replacement
* Stateless functional components
* redux
* [css-modules](https://github.com/css-modules/css-modules/) + [PostCSS](https://github.com/postcss/postcss)
* basic routing setup with react-router (you most likely need routing in your app)
* [babeljs](https://babeljs.io/)
* unit tests ([ava](https://github.com/sindresorhus/ava) + [sinon](http://sinonjs.org/)) examples with both [shallow-rendering](https://facebook.github.io/react/docs/test-utils.html#shallow-rendering) and [jsdom](https://github.com/tmpvar/jsdom)
* code coverage with [nyc](https://github.com/bcoe/nyc)
* development and production build
If you want to use the boilerplate repo as the foundation for another project, check out the README here: https://github.com/vesparny/react-kickstart
| 44.619565 | 245 | 0.724239 | eng_Latn | 0.904253 |
f4c5da1fa1c037f1a63bc6f5fb12b79b0fb19de6 | 3,985 | md | Markdown | api/extension-guides/markdown-extension.md | jruales/vscode-docs | 40b2fe6b17454c64f003a68efce5501702b19886 | [
"CC-BY-3.0",
"MIT"
] | 1 | 2022-03-04T03:21:24.000Z | 2022-03-04T03:21:24.000Z | api/extension-guides/markdown-extension.md | jruales/vscode-docs | 40b2fe6b17454c64f003a68efce5501702b19886 | [
"CC-BY-3.0",
"MIT"
] | null | null | null | api/extension-guides/markdown-extension.md | jruales/vscode-docs | 40b2fe6b17454c64f003a68efce5501702b19886 | [
"CC-BY-3.0",
"MIT"
] | null | null | null | ---
# DO NOT TOUCH — Managed by doc writer
ContentId: 1664249a-ba7a-4a53-b3f0-9d757cff7d27
DateApproved: 3/3/2022
# Summarize the whole topic in less than 300 characters for SEO purpose
MetaDescription: Learn how to extend Visual Studio Code's built-in Markdown preview.
---
# Markdown Extension
Markdown extensions allow you to extend and enhance Visual Studio Code's built-in Markdown preview. This includes changing the look of the preview or adding support for new Markdown syntax.
## Changing the look of the Markdown preview with CSS
Extensions can contribute CSS to change the look or layout of the Markdown preview. Stylesheets are registered using the `markdown.previewStyles` [Contribution Point](/api/references/contribution-points) in the extension's `package.json`:
```json
"contributes": {
"markdown.previewStyles": [
"./style.css"
]
}
```
`"markdown.previewStyles"` is a list of files relative to the extension's root folder.
Contributed styles are added after the built-in Markdown preview styles but before a user's `"markdown.styles"`.
The [Markdown Preview GitHub Styling](https://marketplace.visualstudio.com/items?itemName=bierner.markdown-preview-github-styles) extension is a good example that demonstrates using a stylesheet to make the Markdown preview look like GitHub's rendered Markdown. You can review the extension's source code on [GitHub](https://github.com/mjbvz/vscode-github-markdown-preview-style).
## Adding support for new syntax with markdown-it plugins
The VS Code Markdown preview supports the [CommonMark specification](https://spec.commonmark.org). Extensions can add support for additional Markdown syntax by contributing a [markdown-it plugin.](https://github.com/markdown-it/markdown-it#syntax-extensions)
To contribute a markdown-it plugin, first add a `"markdown.markdownItPlugins"` contribution in your extension's `package.json`:
```json
"contributes": {
"markdown.markdownItPlugins": true
}
```
Then, in the extension's main `activation` function, return an object with a function named `extendMarkdownIt`. This function takes the current markdown-it instance and must return a new markdown-it instance:
```ts
import * as vscode from 'vscode';
export function activate(context: vscode.ExtensionContext) {
return {
extendMarkdownIt(md: any) {
return md.use(require('markdown-it-emoji'));
}
};
}
```
To contribute multiple markdown-it plugins, return multiple `use` statements chained together:
```ts
return md.use(require('markdown-it-emoji')).use(require('markdown-it-hashtag'));
```
Extensions that contribute markdown-it plugins are activated lazily, when a Markdown preview is shown for the first time.
The [markdown-emoji](https://marketplace.visualstudio.com/items?itemName=bierner.markdown-emoji) extension demonstrates using a markdown-it plugin to add emoji support to the markdown preview. You can review the Emoji extension's source code on [GitHub](https://github.com/mjbvz/vscode-markdown-emoji).
You may also want to review:
- [Guidelines](https://github.com/markdown-it/markdown-it/blob/master/docs/development.md) for markdown-it plugin developers
- [Existing markdown-it plugins](https://www.npmjs.com/browse/keyword/markdown-it-plugin)
## Adding advanced functionality with scripts
For advanced functionality, extensions may contribute scripts that are executed inside of the Markdown preview.
```json
"contributes": {
"markdown.previewScripts": [
"./main.js"
]
}
```
Contributed scripts are loaded asynchronously and reloaded on every content change.
The [Markdown Preview Mermaid Support](https://marketplace.visualstudio.com/items?itemName=bierner.markdown-mermaid) extension demonstrates using scripts to add [mermaid](https://knsv.github.io/mermaid/index.html) diagrams and flowchart support to the markdown preview. You can review the Mermaid extension's source code on [GitHub](https://github.com/mjbvz/vscode-markdown-mermaid).
| 45.284091 | 383 | 0.77591 | eng_Latn | 0.775784 |
f4c5df668e4e4121cd728b349db552fac739f06f | 1,039 | md | Markdown | Projects/1-Beginner/Notes-App.md | guerra08/app-ideas | c6e31c9f672d8c5f7c78803f7c7376c68161fe45 | [
"MIT"
] | 52,710 | 2019-02-26T21:33:50.000Z | 2022-03-31T23:42:26.000Z | Projects/1-Beginner/Notes-App.md | guerra08/app-ideas | c6e31c9f672d8c5f7c78803f7c7376c68161fe45 | [
"MIT"
] | 164 | 2019-03-03T07:56:13.000Z | 2022-03-23T09:22:36.000Z | Projects/1-Beginner/Notes-App.md | guerra08/app-ideas | c6e31c9f672d8c5f7c78803f7c7376c68161fe45 | [
"MIT"
] | 8,154 | 2019-02-28T23:43:43.000Z | 2022-03-31T19:27:10.000Z | # Notes App
**Tier:** 1-Beginner
Create and store your notes for later purpose!
## User Stories
- [ ] User can create a note
- [ ] User can edit a note
- [ ] User can delete a note
- [ ] When closing the browser window the notes will be stored and when the User returns, the data will be retrieved
## Bonus features
- [ ] User can create and edit a note in Markdown format. On save it will convert Markdown to HTML
- [ ] User can see the date when he created the note
## Useful links and resources
- [localStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage)
- [Markdown Guide](https://www.markdownguide.org/basic-syntax/)
- [Marked - A markdown parser](https://github.com/markedjs/marked)
## Example projects
- [Markdown Notes built with Angular on Codepen](https://codepen.io/nickmoreton/full/gbyygq)
- [Markdown Notes built with React](https://github.com/email2vimalraj/notes-app)
- [Markdown Notes built with Angular 7 and bootstrap 4](https://github.com/omdnaik/angular-ui)
| 34.633333 | 118 | 0.719923 | eng_Latn | 0.872836 |
f4c60071df01325676b4d947296d754d8f0b3000 | 4,810 | md | Markdown | doc/main.md | manuel-fischer/IXO | db978d9ce397ae0bf8b486afefb34031b91cffab | [
"MIT"
] | null | null | null | doc/main.md | manuel-fischer/IXO | db978d9ce397ae0bf8b486afefb34031b91cffab | [
"MIT"
] | null | null | null | doc/main.md | manuel-fischer/IXO | db978d9ce397ae0bf8b486afefb34031b91cffab | [
"MIT"
] | null | null | null | # The IXO Input-Output Library Documentation
## Hello World example - Reading
**test.json**
```json
{
"name": "Alice",
"age": 42
}
```
**main.c**
```c
#include <IXO/IXO.h>
#include <stdint.h> // -> uint64_t
#include <stdio.h> // -> FILE
typedef struct Person
{
char* name; // Needs to be freed
uint64_t age;
} Person;
IXO_STRUCTDEF(Person,
(name, &IXO_string_class),
(age, &IXO_uint64_class)
);
int main()
{
TST_Person the_person = {0};
if(!IXO_Read("test.json", &the_person, &Person_class))
{
printf("Object couldn't be read completely\n");
}
else
{
printf("%s is %" PRIu64 " years old\n", the_person.name, the_person.age);
}
free(the_person.name);
}
```
### Step by step explanation
#### 1. Inclusion of `IXO.h`
```c
#include <IXO/IXO.h>
```
When installing library files with `install.py`, the header files are
placed to the `IXO/` directory in the include directory
It is sufficient to include `IXO.h` to use the library, specialized files like
`IXO_classdef.h` could be included in files that only define type information
but do not read/write any objects.
#### 2. Defining the type information
```c
IXO_STRUCTDEF(Person,
(name, &IXO_string_class),
(age, &IXO_uint64_class)
);
```
To deserialize or serialize objects, type information needs to be defined.
This is done by various macros like `IXO_STRUCTDEF`, `IXO_TUPLEDEF`,
`IXO_BITDEF`, `IXO_ENUMDEF`.
Each macro defines type information in a variable of type `IXO_Class`. The name
itself is the name of the given type appended with `_name`. This means in the
example above, the variable `Person_class` is defined.
The Macros takes the name of the type as the first parameter, that should be
one token, after that a variable number of tuples follows. Each tuple has
a specific number of arguments. Here the name of a struct type is given as
the first parameter to `IXO_STRUCTDEF`. `IXO_STRUCTDEF` accepts tuples with
two arguments, the first element is the name of the member in the struct, and
the second element is a pointer the IXO-class, which is used do deserialize
the given field itself.
There are some builtin classes for primitive numeric types:
```
IXO_uint8_class
IXO_uint16_class
IXO_uint32_class
IXO_uint64_class
IXO_int8_class
IXO_int16_class
IXO_int32_class
IXO_int64_class
IXO_float_class
IXO_double_class
```
And also there is a class for zero terminated strings, corresponding to the
`char*` type:
```
IXO_string_class
```
It dynamically allocates the string with `malloc` (or related), so the
string needs to be cleaned with `free`.
**For headerfiles**
To declare the class without implementing it, the macro `IXO_DECLARE_CLASS`
can be used with the type name. Here it would be `IXO_DECLARE_CLASS(Person);`.
Note the trailing semicolon, semicolons are needed after any of these macros.
#### 3. Reading the object
```c
TST_Person the_person = {0};
if(!IXO_Read("test.json", &the_person, &Person_class))
{
printf("Object couldn't be read completely\n");
}
else
{
printf("%s is %" PRIu64 " years old\n", the_person.name, the_person.age);
}
```
To read an object from a file, the function `IXO_Read` is called.
The first parameter is the filename. The second
is a pointer to the object that gets filled with data. The last parameter
is the class that provides type information of the object.
The function auto-detects the file type from the filename, that is
corresponding to the enum value `IXO_JSON`.
The object itself should be filled with the default values.
The function `IXO_Read_FILE` takes a `FILE*` instead of a filename. The file
type cannot be detected in this case, so an additional `IXO_FileType` parameter
should be passed.
### Structs vs Tuples
There are two ways to define the class for a struct type. These correspond to
the macros `IXO_STRUCTDEF` and `IXO_TUPLEDEF`. The difference is the
JSON-representation. `IXO_STRUCTDEF` defines the type information that is
needed to load an object from a JSON-object (denoted by `{` and `}`).
A string for each member is stored.
`IXO_TUPLEDEF` defines the type information that is needed to load an object
from a JSON-array (denoted by `[` and `]`). No strings for the members are
created. The elements are loaded sequencially in the order in which the
members are defined in the macro. Using a tuple instead of a struct might be
useful for coordinates/vectors or repeated elements like table rows.
Reading/writing objects as tuples from/to json might be more efficient than
reading/writing as structs(JSON-objects), because the name of each field
is not stored and is not looked up to find the type information of that
specific member. On the other side using structs is more portable when the
order of elements changes or elements are removed or added.
| 30.0625 | 81 | 0.745114 | eng_Latn | 0.998739 |
f4c6223b0f11564b00719183496f01146c8484a3 | 2,670 | md | Markdown | vendor/github.com/docker/docker/docs/swarm/swarm-tutorial/create-swarm.md | Pooja-S-Rao/docker-machine-oneview | 7af1e668d4831b5f5118eed80e69b513200a3334 | [
"Apache-2.0"
] | 27 | 2015-11-17T23:24:38.000Z | 2018-10-31T13:16:48.000Z | vendor/github.com/docker/docker/docs/swarm/swarm-tutorial/create-swarm.md | Pooja-S-Rao/docker-machine-oneview | 7af1e668d4831b5f5118eed80e69b513200a3334 | [
"Apache-2.0"
] | 42 | 2015-11-04T21:13:45.000Z | 2017-06-11T17:59:06.000Z | vendor/github.com/docker/docker/docs/swarm/swarm-tutorial/create-swarm.md | Pooja-S-Rao/docker-machine-oneview | 7af1e668d4831b5f5118eed80e69b513200a3334 | [
"Apache-2.0"
] | 22 | 2015-11-03T22:13:48.000Z | 2021-06-07T07:52:18.000Z | <!--[metadata]>
+++
title = "Create a swarm"
description = "Initialize the swarm"
keywords = ["tutorial, cluster management, swarm mode"]
[menu.main]
identifier="initialize-swarm"
parent="swarm-tutorial"
weight=12
+++
<![end-metadata]-->
# Create a swarm
After you complete the [tutorial setup](index.md) steps, you're ready
to create a swarm. Make sure the Docker Engine daemon is started on the host
machines.
1. Open a terminal and ssh into the machine where you want to run your manager
node. For example, the tutorial uses a machine named `manager1`.
2. Run the following command to create a new swarm:
```bash
docker swarm init --advertise-addr <MANAGER-IP>
```
In the tutorial, the following command creates a swarm on the `manager1`
machine:
```bash
$ docker swarm init --advertise-addr 192.168.99.100
Swarm initialized: current node (dxn1zf6l61qsb1josjja83ngz) is now a manager.
To add a worker to this swarm, run the following command:
docker swarm join \
--token SWMTKN-1-49nj1cmql0jkz5s954yi3oex3nedyz0fb0xx14ie39trti4wxv-8vxv8rssmk743ojnwacrr2e7c \
192.168.99.100:2377
To add a manager to this swarm, run the following command:
docker swarm join \
--token SWMTKN-1-61ztec5kyafptydic6jfc1i33t37flcl4nuipzcusor96k7kby-5vy9t8u35tuqm7vh67lrz9xp6 \
192.168.99.100:2377
```
The `--advertise-addr` flag configures the manager node to publish its
address as `192.168.99.100`. The other nodes in the swarm must be able
to access the manager at the IP address.
The output incudes the commands to join new nodes to the swarm. Nodes will
join as managers or workers depending on the value for the `--swarm-token`
flag.
2. Run `docker info` to view the current state of the swarm:
```bash
$ docker info
Containers: 2
Running: 0
Paused: 0
Stopped: 2
...snip...
Swarm: active
NodeID: dxn1zf6l61qsb1josjja83ngz
Is Manager: true
Managers: 1
Nodes: 1
...snip...
```
3. Run the `docker node ls` command to view information about nodes:
```bash
$ docker node ls
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS
dxn1zf6l61qsb1josjja83ngz * manager1 Ready Active Leader
```
The `*` next to the node id indicates that you're currently connected on
this node.
Docker Engine swarm mode automatically names the node for the machine host
name. The tutorial covers other columns in later steps.
## What's next?
In the next section of the tutorial, we'll [add two more nodes](add-nodes.md) to
the cluster.
| 29.021739 | 103 | 0.68839 | eng_Latn | 0.973531 |
f4c6320a898365bb850375f57496c5e5d1f23758 | 242 | md | Markdown | README.md | k3cman/eslint-config-angular | 6878fcc7ea8efd626c042c0725bbac1c3ef866d9 | [
"MIT"
] | null | null | null | README.md | k3cman/eslint-config-angular | 6878fcc7ea8efd626c042c0725bbac1c3ef866d9 | [
"MIT"
] | null | null | null | README.md | k3cman/eslint-config-angular | 6878fcc7ea8efd626c042c0725bbac1c3ef866d9 | [
"MIT"
] | null | null | null | # eslint-config-angular
## Installation
`
npm install -D eslint-config-k3cman-angular
@angular-eslint/builder @angular-eslint/eslint-plugin @angular-eslint/eslint-plugin-template @angular-eslint/schematics @angular-eslint/template-parser
`
| 26.888889 | 151 | 0.805785 | cat_Latn | 0.102194 |
f4c65b0d3fc576777f605fe7c5d5afe76bccf738 | 24,020 | md | Markdown | docset/winserver2012-ps/netsecurity/Set-NetFirewallSetting.md | pahuijbr/windows-powershell-docs | 5c367612c6b744743237843ba867feac02964313 | [
"CC-BY-4.0",
"MIT"
] | 292 | 2017-03-21T07:51:46.000Z | 2022-03-29T17:01:09.000Z | docset/winserver2012-ps/netsecurity/Set-NetFirewallSetting.md | edsonsbo04/windows-powershell-docs | 348e6fd7da6472e4d6b03eab587bae9970bc8e92 | [
"CC-BY-4.0",
"MIT"
] | 2,496 | 2017-03-02T21:37:40.000Z | 2022-03-31T16:49:37.000Z | docset/winserver2012-ps/netsecurity/Set-NetFirewallSetting.md | edsonsbo04/windows-powershell-docs | 348e6fd7da6472e4d6b03eab587bae9970bc8e92 | [
"CC-BY-4.0",
"MIT"
] | 530 | 2017-02-21T19:10:56.000Z | 2022-03-26T17:13:01.000Z | ---
external help file: NetSecurity_Function.xml
Module Name: NetSecurity
online version: https://docs.microsoft.com/powershell/module/netsecurity/set-netfirewallsetting?view=windowsserver2012-ps&wt.mc_id=ps-gethelp
schema: 2.0.0
---
# Set-NetFirewallSetting
## SYNOPSIS
Modifies the global firewall settings of the target computer.
## SYNTAX
### UNNAMED_PARAMETER_SET_1
```
Set-NetFirewallSetting [-AllowIPsecThroughNAT <IPsecThroughNAT>] [-AsJob] [-CertValidationLevel <CRLCheck>]
[-CimSession <CimSession[]>] [-EnablePacketQueuing <PacketQueuing>] [-EnableStatefulFtp <GpoBoolean>]
[-EnableStatefulPptp <GpoBoolean>] [-Exemptions <TrafficExemption>] [-GPOSession <String>]
[-KeyEncoding <KeyEncoding>] [-MaxSAIdleTimeSeconds <UInt32>] [-PassThru] [-PolicyStore <String>]
[-RemoteMachineTransportAuthorizationList <String>] [-RemoteMachineTunnelAuthorizationList <String>]
[-RemoteUserTransportAuthorizationList <String>] [-RemoteUserTunnelAuthorizationList <String>]
[-RequireFullAuthSupport <GpoBoolean>] [-ThrottleLimit <Int32>] [-Confirm] [-WhatIf]
```
### UNNAMED_PARAMETER_SET_2
```
Set-NetFirewallSetting [-AllowIPsecThroughNAT <IPsecThroughNAT>] [-AsJob] [-CertValidationLevel <CRLCheck>]
[-CimSession <CimSession[]>] [-EnablePacketQueuing <PacketQueuing>] [-EnableStatefulFtp <GpoBoolean>]
[-EnableStatefulPptp <GpoBoolean>] [-Exemptions <TrafficExemption>] [-KeyEncoding <KeyEncoding>]
[-MaxSAIdleTimeSeconds <UInt32>] [-PassThru] [-RemoteMachineTransportAuthorizationList <String>]
[-RemoteMachineTunnelAuthorizationList <String>] [-RemoteUserTransportAuthorizationList <String>]
[-RemoteUserTunnelAuthorizationList <String>] [-RequireFullAuthSupport <GpoBoolean>] [-ThrottleLimit <Int32>]
-InputObject <CimInstance[]> [-Confirm] [-WhatIf]
```
## DESCRIPTION
The **Set-NetFirewallSetting** cmdlet configures properties that apply to the firewall and IPsec settings, regardless of which network profile is currently in use.
This cmdlet allows the administrator to specify global firewall behavior.
## EXAMPLES
### EXAMPLE 1
```
PS C:\>$nfSetting = Get-NetFirewallSetting -PolicyStore corp.contoso.com/gpo_name
PS C:\>Set-NetFirewallSetting -Exemptions RouterDiscovery -InputObject $nfSetting
This cmdlet can be run using only the pipeline.
PS C:\>Get-NetFirewallSetting -PolicyStore corp.contoso.com/gpo_name | Set-NetFirewallSetting -Exemptions RouterDiscovery
```
This example modifies the global firewall settings of a particular GPO policy store.
### EXAMPLE 2
```
PS C:\>$computers = New-Object -Typename System.Security.Principal.NTAccount ("corp.contoso.com" "SecureMachineName1")
PS C:\>$SIDofSecureComputerGroup = $computers.Translate([System.Security.Principal.SecurityIdentifier]).Value
PS C:\>$SecureMachineGroupSDDL = "D:(A;;CC;;; $SIDofSecureComputerGroup)"
PS C:\>$nfSetting = Get-NetFirewallSetting -PolicyStore corp.contoso.com/gpo_name
PS C:\>Set-NetFirewallSetting -RemoteMachineTunnelAuthorizationList $SecureMachineGroupSDDL -InputObject $nfSetting
This cmdlet can be run using only the pipeline.
PS C:\>Get-NetFirewallSetting -PolicyStore corp.contoso.com/gpo_name | Set-NetFirewallSetting -RemoteMachineTunnelAuthorizationList $SecureMachineGroupSDDL
```
This example allows authorization to override the per-rule basis and to be done at the IPsec layer in a GPO.
## PARAMETERS
### -AllowIPsecThroughNAT
Specifies that IPsec configures a security association (SA) when one or both computers involved are behind a network address translation (NAT) device.
This setting indicates on which side NAT traversal should be attempted.
The acceptable values for this parameter are: None, Server, Both, or NotConfigured.
-- None: Specifies that an SA cannot be negotiated if the server or client computer is behind a NAT device.
-- Server: Specifies that an SA can be negotiated if only the server is on a private subnet behind a NAT device.
-- Both: Specifies that an SA can be negotiated if the client or server or both of the computers are on private subnets behind one or more NAT devices.
-- NotConfigured: Valid only when configuring a GPO.
Removes the setting from the GPO, which results in the policy not changing the value on the computer when the policy is applied.
The default value is None.
When managing a GPO, the default setting is NotConfigured.
```yaml
Type: IPsecThroughNAT
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -AsJob
ps_cimcommon_asjob
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -CertValidationLevel
Specifies that IPsec checks the certificates used in authentication against a certificate revocation list (CRL), and how IPsec reacts to a certificate that is found to be on a CRL.
The acceptable values for this parameter are: None, AttemptCrlCheck, RequireCrlCheck, or NotConfigured.
-- None: Specifies that IPsec does not perform any CRL checking.
-- AttemptCrlCheck: Specifies that IPsec authentication fails only if the certificate is found to be revoked.
-- RequireCrlCheck: Specifies that IPsec authentication fails if there is any error during CRL checking, including a failure to retrieve the CRL.
-- NotConfigured: Valid only when configuring a GPO.
Removes the setting from the GPO, which results in the policy not changing the value on the computer when the policy is applied.
The default value is None.
When managing a GPO, the default setting is NotConfigured.
```yaml
Type: CRLCheck
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -CimSession
Runs the cmdlet in a remote session or on a remote computer.
Enter a computer name or a session object, such as the output of a New-CimSessionhttp://go.microsoft.com/fwlink/p/?LinkId=227967 or Get-CimSessionhttp://go.microsoft.com/fwlink/p/?LinkId=227966 cmdlet.
The default is the current session on the local computer.
```yaml
Type: CimSession[]
Parameter Sets: (All)
Aliases: Session
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -EnablePacketQueuing
Specifies how the Windows Firewall with Advanced Security handles packet queuing.
This parameter enables inbound or forward packet queuing independently, allowing the computer is able to evenly distribute CPU load to multiple CPUs for site-to-site IPsec tunnel scenarios.
The acceptable values for this parameter are: None, Inbound, Forward, or NotConfigured.
-- None: The firewall tracks the port numbers specified in PORT command requests and in the responses to PASV requests, and then allows the incoming FTP data traffic entering on the requested port number.
-- Inbound: Inbound packet queuing is enabled.
-- Forward: Forward packet queuing is enabled.
-- NotConfigured: Valid only when configuring a GPO.
Removes the setting from the GPO, which results in the policy not changing the value on the computer when the policy is applied.
The default value when managing a computer running Windows Server® 2012 is None.
When managing a Group Policy Object (GPO), the default setting is NotConfigured.
```yaml
Type: PacketQueuing
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -EnableStatefulFtp
Configures how Windows Firewall with Advanced Security handles FTP traffic that uses an initial connection on one port to request a data connection on a different port.
This affects both active and passive FTP.
If active FTP is used, then the client initiates a connection to the server on TCP port 21 and includes a PORT command that indicates to the FTP server the port number on which it should respond.
A typical firewall on the client would block this new connection as unsolicited inbound traffic since the packets to the new port are not in response to a request from that port.
If passive FTP is used, then the client initiates a connection to the server on TCP port 21 and includes the PASV command.
The server responds on TCP port 21 with a port number that the client must use for subsequent data transfer.
The client then initiates a connection to the server on the specified port.
A typical firewall on the FTP server would block this new incoming data connection as unsolicited inbound traffic since the packets received at the new port are not in response to a request from that port.
When this parameter is True, the firewall examines the PORT and PASV requests for these other port numbers and then allows the corresponding data connection to the port number that was requested.
-- True: The firewall tracks the port numbers specified in PORT command requests and in the responses to PASV requests, and then allows the incoming FTP data traffic entering on the requested port number.
-- False: The firewall does not track outgoing PORT commands or PASV responses, and so incoming data connections on the PORT or PASV requested port is blocked as an unsolicited incoming connection.
- NotConfigured: Valid only when configuring a GPO.
Removes the setting from the GPO, which results in the policy not changing the value on the computer when the policy is applied.
The default value is False.
The default value when managing a computer running firstref_vista or firstref_client_7 is True.
The default value when managing a computer running firstref_longhorn or firstref_server_7 is False.
When managing a Group Policy Object (GPO), the default value is NotConfigured.
```yaml
Type: GpoBoolean
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -EnableStatefulPptp
Configures how Windows Firewall with Advanced Security handles PPTP traffic.
If a connection is made through TCP port 1723 in nextref_vista, then Windows Firewall recognizes the connection as being established through PPTP.
By default, Windows Firewall uses a stateful PPTP protocol analyzer to determine whether it can receive packets through the TCP port 1723 connection.
Therefore, the stateful PPTP protocol analyzer may reject as not valid any traffic that uses a protocol other than PPTP.
-- True: The firewall examines the packets from port 1723 and determines whether the traffic is valid PPTP traffic.
-- False: The firewall does not examine the packets from port 1723 to determine whether the traffic is valid PPTP traffic.
-- NotConfigured: Valid only when configuring a GPO.
Removes the setting from the GPO, which results in the policy not changing the value on the computer when the policy is applied.
The default value is False.
When managing a GPO, the default value is NotConfigured.
```yaml
Type: GpoBoolean
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -Exemptions
Specifies the protocols to be exempted from IPsec requirements.
The acceptable values for this parameter are: None, NeighborDiscovery, Icmp, RouterDiscovery, Dhcp, or NotConfigured.
-- None: No protocols are exempted.
-- NeighborDiscovery: Exempt IPv6 Neighbor Discovery protocol traffic.
-- Icmp: Exempt ICMP, for both IPv4 and IPv6, protocol traffic.
This option is available on computers that are running Windows® 7 or nextref_server_7.
-- RouterDiscovery: Exempt router discovery traffic.
-- Dhcp: Exempt DHCP, for both IPv4 and IPv6, protocol traffic.
This option is available on computers that are running Windows® 7 or nextref_server_7.
The default value when managing a local computer that is running Windows® 7 or nextref_server_7 is NeighborDiscovery,Dhcp.
The default value when managing a local computer that is running nextref_vista, nextref_longhorn, Windows XP®, or Windows Server® 2003 is NeighborDiscovery.
The default value when managing a GPO is NotConfigured.
```yaml
Type: TrafficExemption
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -GPOSession
Specifies the network GPO from which to retrieve the rules to be modified.
This parameter is used in the same way as the **PolicyStore** parameter.
When modifying GPOs in Windows PowerShell®, each change to a GPO requires the entire GPO to be loaded, modified, and saved back.
On a busy Domain Controller (DC), this can be a slow and resource-heavy operation.
A GPO Session loads a domain GPO onto the local computer and makes all changes in a batch, before saving it back.
This reduces the load on the DC and speeds up the Windows PowerShell cmdlets.
To load a GPO Session, use the Open-NetGPO cmdlet.
To save a GPO Session, use the Save-NetGPO cmdlet.
```yaml
Type: String
Parameter Sets: UNNAMED_PARAMETER_SET_1
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -InputObject
Specifies the input to this cmdlet.
You can use this parameter, or you can pipe the input to this cmdlet.
```yaml
Type: CimInstance[]
Parameter Sets: UNNAMED_PARAMETER_SET_2
Aliases:
Required: True
Position: Named
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: False
```
### -KeyEncoding
Specifies the type of key encoding to be used.
The acceptable values for this parameter are: UTF16 or UTF8.
The default value is UTF8.
```yaml
Type: KeyEncoding
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -MaxSAIdleTimeSeconds
Specifies the number of minutes that a security association (SA) can stay idle before being deleted.
Once deleted, a new SA must be established before computers under the scope of the original SA can communicate again.
The acceptable values for this parameter are: 300 through 3600 seconds, or NotConfigured.
-- A non-zero value, including 300 through 3600, specifies the desired lifetime.
-- NotConfigured: Valid only when configuring a GPO.
Removes the setting from the GPO, which results in the policy not changing the value on the computer when the policy is applied.
Note: This parameter value is case-sensitive and NotConfigured can only be specified using dot-notation.
The default value when managing a local computer is 300 seconds (5 minutes).
When managing a GPO, the default value is NotConfigured.
```yaml
Type: UInt32
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -PassThru
Returns an object representing the item with which you are working.
By default, this cmdlet does not generate any output.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -PolicyStore
Specifies the policy store from which to retrieve the rules to be modified.
A policy store is a container for firewall and IPsec policy.
The acceptable values for this parameter are:
-- PersistentStore: Sometimes called static rules, this store contains the persistent policy for the local computer.
This policy is not from GPOs, and has been created manually or programmatically (during application installation) on the computer.
Rules created in this store are attached to the ActiveStore and activated on the computer immediately.
-- ActiveStore: This store contains the currently active policy, which is the sum of all policy stores that apply to the computer.
This is the resultant set of policy (RSOP) for the local computer (the sum of all GPOs that apply to the computer), and the local stores (the PersistentStore, the static Windows service hardening (WSH), and the configurable WSH).
---- GPOs are also policy stores.
Computer GPOs can be specified as follows.
------ `-PolicyStore hostname`.
---- Active Directory GPOs can be specified as follows.
------ `-PolicyStore domain.fqdn.com\GPO_Friendly_Namedomain.fqdn.comGPO_Friendly_Name`.
------ Such as the following.
-------- `-PolicyStore localhost`
-------- `-PolicyStore corp.contoso.com\FirewallPolicy`
---- Active Directory GPOs can be created using the New-GPO cmdlet or the Group Policy Management Console.
-- RSOP: This read-only store contains the sum of all GPOs applied to the local computer.
-- SystemDefaults: This read-only store contains the default state of firewall rules that ship with Windows Server 2012.
-- StaticServiceStore: This read-only store contains all the service restrictions that ship with Windows Server 2012.
Optional and product-dependent features are considered part of Windows Server 2012 for the purposes of WFAS.
-- ConfigurableServiceStore: This read-write store contains all the service restrictions that are added for third-party services.
In addition, network isolation rules that are created for Windows Store application containers will appear in this policy store.
The default value is PersistentStore.
Note: The Set-NetFirewallRule cmdlet cannot be used to add an object to a policy store.
An object can only be added to a policy store at creation time with the Copy-NetFirewallRule cmdlet or with the New-NetFirewallRule cmdlet.
```yaml
Type: String
Parameter Sets: UNNAMED_PARAMETER_SET_1
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -RemoteMachineTransportAuthorizationList
Specifies the computer accounts that are authorized to establish transport connections to the local computer that match this rule.
Authorization can override the per-rule basis and be done at the IPsec layer.
The acceptable values for this parameter are:
-- None: Specifies that access to the tunnel is not restricted based on computer account.
-- \<SDDL string\>: A string that identifies accounts and the permissions granted or denied to those accounts.
This parameter value is valid on computers that are running Windows® 7, nextref_server_7, and Windows Server 2012 only, and is ignored on earlier versions of Windows.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -RemoteMachineTunnelAuthorizationList
Specifies the computer accounts that are authorized to establish tunnel connections to the local computer that match this rule.
Authorization can override the per-rule basis and be done at the IPsec layer.
The acceptable values for this parameter are:
-- None: Specifies that access to the tunnel is not restricted based on computer account.
-- \<SDDL string\>: A string that identifies accounts and the permissions granted or denied to those accounts.
This parameter value is valid on computers that are running Windows® 7, nextref_server_7, and Windows Server 2012 only, and is ignored on earlier versions of Windows.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -RemoteUserTransportAuthorizationList
Specifies the user accounts that are authorized to establish transport connections to the local computer that match this rule.
Authorization can override the per-rule basis and be done at the IPsec layer.
The acceptable values for this parameter are:
-- None: Specifies that access to the tunnel is not restricted based on computer account.
-- \<SDDL string\>: A string that identifies accounts and the permissions granted or denied to those accounts.
This parameter value is valid on computers that are running Windows® 7, nextref_server_7, and Windows Server 2012 only, and is ignored on earlier versions of Windows.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -RemoteUserTunnelAuthorizationList
Specifies the user accounts that are authorized to establish tunnel connections to the local computer that match this rule.
Authorization can override the per-rule basis and be done at the IPsec layer.
The acceptable values for this parameter are:
-- None: Specifies that access to the tunnel is not restricted based on computer account.
-- \<SDDL string\>: A string that identifies accounts and the permissions granted or denied to those accounts.
This parameter value is valid on computers that are running Windows® 7, nextref_server_7, and Windows Server 2012 only, and is ignored on earlier versions of Windows.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -RequireFullAuthSupport
Ignores key modules that do not support all of the authentication types present in a rule.
If this parameter is set to True, then the behavior is the same as nextref_vista and Windows® 7, that the key modules that do not support the entire authentication set will be ignored.
If this parameter is set to False, then the keying modules will try with the subset of configured authentication types that are allowed.
```yaml
Type: GpoBoolean
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -ThrottleLimit
Specifies the maximum number of concurrent operations that can be established to run the cmdlet.
If this parameter is omitted or a value of `0` is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer.
The throttle limit applies only to the current cmdlet, not to the session or to the computer.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### -Confirm
Prompts you for confirmation before running the cmdlet.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```
### -WhatIf
Shows what would happen if the cmdlet runs.
The cmdlet is not run.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```
## INPUTS
### Microsoft.Management.Infrastructure.CimInstance#root\StandardCimv2\NetFirewallSetting[]
The `Microsoft.Management.Infrastructure.CimInstance` object is a wrapper class that displays Windows Management Instrumentation (WMI) objects.
The path after the pound sign (`#`) provides the namespace and class name for the underlying WMI object.
## OUTPUTS
### Microsoft.Management.Infrastructure.CimInstance#root\StandardCimv2\MSFT_NetServiceFilter[]
The `Microsoft.Management.Infrastructure.CimInstance` object is a wrapper class that displays Windows Management Instrumentation (WMI) objects.
The path after the pound sign (`#`) provides the namespace and class name for the underlying WMI object.
## NOTES
## RELATED LINKS
[Copy-NetIPsecRule](./Copy-NetIPsecRule.md)
[Get-NetFirewallSetting](./Get-NetFirewallSetting.md)
[New-NetIPsecRule](./New-NetIPsecRule.md)
[Open-NetGPO](./Open-NetGPO.md)
[Save-NetGPO](./Save-NetGPO.md)
[Set-NetIPsecRule](./Set-NetIPsecRule.md)
[New-GPO](../grouppolicy/New-GPO.md)
| 36.504559 | 230 | 0.78801 | eng_Latn | 0.991614 |
f4c708487c70952d2f4091a7a15f78f37b470f78 | 2,308 | md | Markdown | docs/1-template-overview.md | Jackie-Zhong/cumulus-workshop-master | f4149de084fc3a38190941473076f3f09bcc9825 | [
"MIT"
] | null | null | null | docs/1-template-overview.md | Jackie-Zhong/cumulus-workshop-master | f4149de084fc3a38190941473076f3f09bcc9825 | [
"MIT"
] | null | null | null | docs/1-template-overview.md | Jackie-Zhong/cumulus-workshop-master | f4149de084fc3a38190941473076f3f09bcc9825 | [
"MIT"
] | 1 | 2021-01-23T05:18:17.000Z | 2021-01-23T05:18:17.000Z | # 平行链收集者模板
熟悉[Substrate Node Template](https://github.com/substrate-developer-hub/substrate-node-template)的开发者将会发现平行链模板很熟悉。
它们具有相同的通用结构，包括`节点`，`运行时逻辑`，以及 `托盘` 目录。它们的运行时间是相似的，并具有许多相同的托盘。
除了一些新的特性，托盘本身基本上是相同的。许多[Substrate devhub tutorials](https://substrate.dev/tutorials/)可以在平行链模板上通过少量的的修改而被使用。
这两个模板之间的相似性应该会给您带来信心，如果您已经构建一个Substrate链，那么您构建一个平行链就没有问题了！
## 节点模板的不同
然而，这两个模板之间有一些重要的区别，值得从一开始就观察。
### 平行链信息托盘
这个托盘被设计的目的是将有关平行链的注册注入到它自己的运行时逻辑中，目前它只注入链注册的平行链id。这使得运行时逻辑可以知道哪些跨链消息是针对它的。
### 消息代理托盘
这个托盘负责将通过网络接收的块链消息分发到它们要用的托盘上。如果您打算接收跨链消息，您应该可以使用这个托盘。
### 代币商托盘
这个托盘可以作为发送和接收跨链消息的示例。他是实现我们前面看到的[跨链代币转账](../4-cross-chain/1-downward.md)。
如果您想要接收DOTs或者来自国外的链的资产，您应该使用这个托盘或者使用它的代码作为灵感。
### `register_validate_block!` 宏
每一个平行链必须向中继链提供一个`validate_block`函数，表示作为一个wasm blob。节点模板没有提供这个函数，但是平行链模板有。
多亏了cumulus，为Substrate运行时逻辑创建这个函数就像在运行时底部添加一行代码一样简单：
```rust
cumulus_runtime::register_validate_block!(Block, Executive);
```
### 没有Aura托盘
许多流行的Substrate运行时逻辑，像Polkadot，包含了consensus-related托盘和runtime-apis。这个节点模板以Aura托盘及其相关运行时逻辑的`AuraApi`为特色。
两者都是在平行链模板中缺失的。
这是因为收集者节点的authors区块在一个规则的间隔，而不是使用更复杂的共识引擎，如Aura，Babe，或者PoW。
在未来，这个authoring的行为可能是可配置的，并且运行时逻辑的这些部分可能会被重新引入。关于这方面的进展，请访问：
- https://github.com/paritytech/cumulus/issues/166
- https://github.com/paritytech/cumulus/issues/36
- https://github.com/paritytech/cumulus/issues/115
- https://github.com/paritytech/cumulus/issues/116
### 没有GRANDPA托盘
许多流行的Substrate运行时逻辑，包括节点模板，都有一个与finality-related相关的`GrandpaApi`。
这两者都是平行链模板中确实的。
Many popular Substrate runtimes including the node template feature a finality-related GRANDPA
pallet and its associated `GrandpaApi`. These are both missing from the parachain template.
这是因为平行链跟随的是中继链的最终性而不是运行它们自己的最终行的工具。这是基本的Polkadot的架构，而且不会改变。
### 服务
收集者节点的服务与节点模板的服务是完全不同的。虽然您可以找到相似之处，但是入伍的架构却大不相同。这个新的服务是cumulus提供的主要变化。
> 当使用Cumulus去修改现有的Substrate链时，通常最好是从模板中复制服务代码。
> service code from the template.
## 使用模板
下面几节中的说明将使用平行链模板简单的处理一些基本的练习。它们可以按照任何顺序被遵循，而不是建立在彼此之上。要了解Substrate开发的更多的彻底的入门，搜索[Substrate Developer Hub](https://substrate.dev)。
这些指令假设您已经在本地系统[compiled the parachain template](../1-prep/1-compiling.md)上编译了。如果您没有，请返回去做。
如果您是一个github用户，可以从分支
If you're a github user, begin by[forking the parachain template](https://github.com/substrate-developer-hub/substrate-pallet-template)开始，然后在您的fork中使用。 | 27.807229 | 151 | 0.830589 | yue_Hant | 0.666634 |
f4c7369369ba165d8d25419a7c9805f6daa055ba | 516 | md | Markdown | docs/core/tutorials/aspnet-core.md | GeiGeiLa/docs.zh-tw | 88f98d80c8afc37c430f79fb76c5e14f11dce957 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/core/tutorials/aspnet-core.md | GeiGeiLa/docs.zh-tw | 88f98d80c8afc37c430f79fb76c5e14f11dce957 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/core/tutorials/aspnet-core.md | GeiGeiLa/docs.zh-tw | 88f98d80c8afc37c430f79fb76c5e14f11dce957 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: ASP.NET Core 使用者入門
description: 透過 ASP.NET Core 文件中的教學課程深入了解 ASP.NET Core。
author: tdykstra
ms.author: mairaw
ms.date: 06/20/2016
ms.openlocfilehash: d3749152197997575022dea4828a62393369fd83
ms.sourcegitcommit: 586dbdcaef9767642436b1e4efbe88fb15473d6f
ms.translationtype: HT
ms.contentlocale: zh-TW
ms.lasthandoff: 10/06/2018
ms.locfileid: "48840507"
---
# <a name="getting-started-with-aspnet-core"></a>ASP.NET Core 使用者入門
如需開發 ASP.NET Core Web 應用程式的教學課程，請參閱 [ASP.NET Core 教學課程](/aspnet/core/tutorials)。
| 30.352941 | 80 | 0.794574 | yue_Hant | 0.674791 |
f4c7c8d1fc4257e938bb523b1f7f28aa1b39b64b | 2,997 | md | Markdown | docs/t-sql/statements/drop-service-transact-sql.md | Jteve-Sobs/sql-docs.de-de | 9843b0999bfa4b85e0254ae61e2e4ada1d231141 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/t-sql/statements/drop-service-transact-sql.md | Jteve-Sobs/sql-docs.de-de | 9843b0999bfa4b85e0254ae61e2e4ada1d231141 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/t-sql/statements/drop-service-transact-sql.md | Jteve-Sobs/sql-docs.de-de | 9843b0999bfa4b85e0254ae61e2e4ada1d231141 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: DROP SERVICE (Transact-SQL)
title: DROP SERVICE (Transact-SQL) | Microsoft-Dokumentation
ms.custom: ''
ms.date: 03/06/2017
ms.prod: sql
ms.prod_service: sql-database
ms.reviewer: ''
ms.technology: t-sql
ms.topic: language-reference
f1_keywords:
- DROP_SERVICE_TSQL
- DROP SERVICE
dev_langs:
- TSQL
helpviewer_keywords:
- deleting services
- services [Service Broker], removing
- dropping services
- DROP SERVICE statement
- removing services
ms.assetid: 2351bba7-0f2a-4cda-b3b2-6a88b8747c53
author: CarlRabeler
ms.author: carlrab
ms.openlocfilehash: 0c44273578fff67bed075dea4f60fc6314902dcc
ms.sourcegitcommit: e700497f962e4c2274df16d9e651059b42ff1a10
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 08/17/2020
ms.locfileid: "88415806"
---
# <a name="drop-service-transact-sql"></a>DROP SERVICE (Transact-SQL)
[!INCLUDE [SQL Server - ASDBMI](../../includes/applies-to-version/sql-asdbmi.md)]
Löscht einen vorhandenen Dienst.
 [Transact-SQL-Syntaxkonventionen](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
## <a name="syntax"></a>Syntax
```syntaxsql
DROP SERVICE service_name
[ ; ]
```
[!INCLUDE[sql-server-tsql-previous-offline-documentation](../../includes/sql-server-tsql-previous-offline-documentation.md)]
## <a name="arguments"></a>Argumente
*service_name*
Der Name des zu löschenden Diensts. Server-, Datenbank- und Schemaname können nicht angegeben werden.
## <a name="remarks"></a>Bemerkungen
Sie können einen Dienst nicht löschen, wenn Konversationsprioritäten darauf verweisen.
Durch das Löschen eines Dienstes werden alle Nachrichten aus der Warteschlange gelöscht, die von diesem Dienst verwendet werden. [!INCLUDE[ssSB](../../includes/sssb-md.md)] sendet einen Fehler an die Remoteseite offener Konversationen, die diesen Dienst verwenden.
## <a name="permissions"></a>Berechtigungen
Standardmäßig verfügen der Besitzer des Dients, Mitglieder der festen Datenbankrollen db_ddladmin und db_owner sowie Mitglieder der festen Serverrolle sysadmin über die Berechtigung zum Löschen eines Dients.
## <a name="examples"></a>Beispiele
Im folgenden Beispiel wird der Dienst `//Adventure-Works.com/Expenses` gelöscht.
```
DROP SERVICE [//Adventure-Works.com/Expenses] ;
```
## <a name="see-also"></a>Weitere Informationen
[ALTER BROKER PRIORITY (Transact-SQL)](../../t-sql/statements/alter-broker-priority-transact-sql.md)
[ALTER SERVICE (Transact-SQL)](../../t-sql/statements/alter-service-transact-sql.md)
[CREATE SERVICE (Transact-SQL)](../../t-sql/statements/create-service-transact-sql.md)
[DROP BROKER PRIORITY (Transact-SQL)](../../t-sql/statements/drop-broker-priority-transact-sql.md)
[EVENTDATA (Transact-SQL)](../../t-sql/functions/eventdata-transact-sql.md)
| 39.434211 | 267 | 0.744411 | deu_Latn | 0.465163 |
f4c83810e4469d7940c095714de7c311f01d6606 | 5,357 | md | Markdown | docs/tools/dta/lesson-3-using-the-dta-command-prompt-utility.md | JasperLian0715/sql-docs.zh-tw | 34167797c0a9e46a5d114c3c1b14e7e40c371345 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/tools/dta/lesson-3-using-the-dta-command-prompt-utility.md | JasperLian0715/sql-docs.zh-tw | 34167797c0a9e46a5d114c3c1b14e7e40c371345 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/tools/dta/lesson-3-using-the-dta-command-prompt-utility.md | JasperLian0715/sql-docs.zh-tw | 34167797c0a9e46a5d114c3c1b14e7e40c371345 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 使用 dta 命令提示字元公用程式
description: 除 SQL Server Database Engine Tuning Advisor 提供的功能之外，亦請了解 dta 命令提示公用程式提供的功能。
ms.custom: seo-lt-2019
ms.date: 03/14/2017
ms.prod: sql
ms.prod_service: sql-tools
ms.technology: performance
ms.topic: conceptual
helpviewer_keywords:
- Database Engine [SQL Server], tutorials
ms.assetid: 30f27f4d-8852-4b12-ba62-57f63e496f1d
author: markingmyname
ms.author: maghan
ms.reviewer: ''
ms.openlocfilehash: 3afc39516bc50a6a4f1a2fb7ad67d7b0c3602e7e
ms.sourcegitcommit: a9f16d7819ed0e2b7ad8f4a7d4d2397437b2bbb2
ms.translationtype: HT
ms.contentlocale: zh-TW
ms.lasthandoff: 08/21/2020
ms.locfileid: "88713736"
---
# <a name="lesson-3-using-the-dta-command-prompt-utility"></a>第 3 課：使用 dta 命令提示字元公用程式
[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
除了 Database Engine Tuning Advisor 所提供的功能，**dta** 命令提示字元公用程式還提供額外的功能。
您可以利用您愛用的 XML 工具和 Database Engine Tuning Advisor XML 結構描述來建立這個公用程式的輸入檔。 這個結構描述會在您安裝 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 時一併安裝，並且位於：C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\schemas\sqlserver\2004\07\dta\dtaschema.xsd。
您也可以透過 [Microsoft 網站](https://go.microsoft.com/fwlink/?linkid=43100&clcid=0x409)，線上取得 Database Engine Tuning Advisor XML 結構描述。
在微調選項的設定上，Database Engine Tuning Advisor XML 結構描述非常靈活。 例如，它可讓您進行「假設」分析。 「假設」分析包括針對您要微調的資料庫來指定一組現有的實體設計結構和假設的實體設計結構，再利用 Database Engine Tuning Advisor 來分析它，以了解這個假設的實體設計是否能改進查詢處理效能。 這類分析的好處是既能夠評估新的組態，又免除了實際實作的負擔。 如果假設的實體設計所改進的效能不符需求，您很容易改變它，再分析它，直到產生的結果符合需求的組態出現為止。
此外，在使用 Database Engine Tuning Advisor XML 結構描述和 **dta** 命令提示字元公用程式時，您也可以將 Database Engine Tuning Advisor 功能納入指令碼中，再搭配其他資料庫設計工具來使用它。
如何使用 Database Engine Tuning Advisor 的 XML 輸入功能不在這個課程的範圍內。
這項工作會帶您逐步啟動 **dta** 公用程式、檢視它的說明，再從命令提示字元之下，使用它來微調工作負載。 它會使用您針對 Database Engine Tuning Advisor 圖形化使用者介面 (GUI) [微調工作負載](lesson-2-using-database-engine-tuning-advisor.md#tuning-a-workload)練習所建立的 MyScript.sql 工作負載
本教學課程使用 AdventureWorks2017 範例資料庫。 基於安全性的考量，依預設，不會安裝範例資料庫。 若要安裝範例資料庫，請參閱＜ [安裝 SQL Server 範例和範例資料庫](../../samples/adventureworks-install-configure.md)＞。
下列工作將帶您逐步開啟命令提示字元、啟動 **dta** 命令提示字元公用程式、檢視其語法說明，以及微調您在 [微調工作負載](./lesson-2-using-database-engine-tuning-advisor.md?view=sql-server-ver15)中所建立的簡單工作負載 MyScript.sql。
## <a name="prerequisites"></a>必要條件
若要完成本教學課程，您需要 SQL Server Management Studio、執行 SQL Server 伺服器的存取權，以及 AdventureWorks 資料庫。
- 安裝 [SQL Server 2017 Developer Edition](https://www.microsoft.com/sql-server/sql-server-downloads)。
- 下載 [AdventureWorks2017 範例資料庫](../../samples/adventureworks-install-configure.md) \(機器翻譯\)。
如需在 SSMS 中還原資料庫的指示，請參閱：[還原資料庫。](../../relational-databases/backup-restore/restore-a-database-backup-using-ssms.md?view=sql-server-2017)
>[!NOTE]
> 本教學課程適用於熟悉使用 SQL Server Management Studio 與基本資料庫管理工作的使用者。
## <a name="access-dta-command-prompt-utility-help-menu"></a>存取 DTA 命令提示字元公用程式說明功能表
1. 在 [開始] 功能表上，依序指向 [所有程式] 和 [附屬應用程式]，再按一下 [命令提示字元]。
2. 在命令提示字元之下，輸入下列字串，再按 ENTER 鍵：
```
dta -? | more
```
這個命令的 `| more` 部份是選擇性的。 不過，您可以利用它來逐頁閱讀公用程式的語法說明。 按 ENTER 鍵會在說明文字中，每次前進一行，按空白鍵則會每次前進一頁。
## <a name="tune-simple-workload-using-the-dta-command-prompt-utility"></a>使用 DTA 命令提示字元公用程式來微調簡易的工作負載
1. 在命令提示字元之下，導覽到儲存 MyScript.sql 檔的目錄。
2. 在命令提示字元之下，輸入下列字串，再按 ENTER 鍵來執行命令，以及啟動微調工作階段 (請注意，當剖析命令時，這個公用程式會區分大小寫)：
```
dta -S YourServerName\YourSQLServerInstanceName -E -D AdventureWorks2012 -if MyScript.sql -s MySession2 -of MySession2OutputScript.sql -ox MySession2Output.xml -fa IDX_IV -fp NONE -fk NONE
```
其中 `-S` 指定您的伺服器名稱以及安裝了 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 資料庫的 [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)] 執行個體。 `-E` 設定值指定您要使用執行個體的信任連接，當您利用 Windows 網域帳戶來連接時，適合採用這個方式。 `-D` 設定值指定您要微調的資料庫， `-if` 指定工作負載檔案， `-s` 指定工作階段名稱， `-of` 指定工具要將 [!INCLUDE[tsql](../../includes/tsql-md.md)] 建議指令碼寫入其中的檔案， `-ox` 指定工具要將 XML 格式的建議寫入其中的檔案。 最後三個參數依照下列方式來指定微調選項： `-fa IDX_IV` 指定 Database Engine Tuning Advisor 只應考慮加入索引 (叢集和非叢集) 和索引檢視； `-fp NONE` 指定在分析期間，完全不應考慮任何資料分割策略； `-fk NONE` 指定 Database Engine Tuning Advisor 在產生建議時，不需要保留資料庫中任何現有的實體設計結構。
3. 在 Database Engine Tuning Advisor 微調好工作負載之後，它會顯示一則訊息，指出微調工作階段已順利完成。 您可以利用 [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] 來開啟 MySession2OutputScript.sql 和 MySession2Output.xml 檔，以檢視微調結果。 另外，您也可以在 Database Engine Tuning Advisor GUI 中開啟 MySession2 微調工作階段，依照 [檢視微調建議](./lesson-2-using-database-engine-tuning-advisor.md?view=sql-server-ver15) 和 [檢視微調報表](./lesson-2-using-database-engine-tuning-advisor.md?view=sql-server-ver15)中的相同方式來檢視其建議和報表。
## <a name="after-you-finish-this-tutorial"></a>完成這個教學課程之後
完成這個教學課程中的課程之後，請參閱下列主題，以取得有關 Database Engine Tuning Advisor 的詳細資訊：
- ＜[Database Engine Tuning Advisor](../../relational-databases/performance/database-engine-tuning-advisor.md) ＞提供如何利用這個工具來執行工作的描述。
- ＜[dta Utility](../../tools/dta/dta-utility.md) ＞提供有關命令提示字元公用程式的參考資料，以及可用來控制公用程式作業的選擇性 XML 檔案。
若要返回教學課程的起始處，請參閱[教學課程：Database Engine Tuning Advisor](../../tools/dta/tutorial-database-engine-tuning-advisor.md)。
## <a name="see-also"></a>另請參閱
[Database Engine 教學課程](../../relational-databases/database-engine-tutorials.md)
| 53.57 | 576 | 0.759754 | yue_Hant | 0.735162 |
f4c86cf2332019222cdfb6d9a891ae9b3c6d1d93 | 9,031 | md | Markdown | articles/logic-apps/logic-apps-scenario-social-serverless.md | bergano65/azure-docs.ru-ru | 8baaa0e3e952f85f7a3b5328960f0d0d3e52db07 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/logic-apps/logic-apps-scenario-social-serverless.md | bergano65/azure-docs.ru-ru | 8baaa0e3e952f85f7a3b5328960f0d0d3e52db07 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/logic-apps/logic-apps-scenario-social-serverless.md | bergano65/azure-docs.ru-ru | 8baaa0e3e952f85f7a3b5328960f0d0d3e52db07 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Создать панель мониторинга Customer Insights
description: Управление отзывами от клиентов, данными социальных сетей и многим другим путем создания панели мониторинга клиента с помощью Azure Logic Apps и Функций Azure
services: logic-apps
ms.suite: integration
author: jeffhollan
ms.author: jehollan
ms.reviewer: estfan, logicappspm
ms.topic: article
ms.date: 03/15/2018
ms.openlocfilehash: ebc1d449cdb8702a984304e92697d4b7c778daaa
ms.sourcegitcommit: 76b48a22257a2244024f05eb9fe8aa6182daf7e2
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 12/03/2019
ms.locfileid: "74792903"
---
# <a name="create-a-streaming-customer-insights-dashboard-with-azure-logic-apps-and-azure-functions"></a>Создание панели мониторинга потоковой передачи сведений о клиентах с помощью Функций Azure и Azure Logic Apps.
Azure предлагает средства [Бессерверные приложения в Azure](https://azure.microsoft.com/solutions/serverless/) для быстрого создания и размещения приложений в облаке, не задумываясь об инфраструктуре. В этом руководстве мы создадим панель мониторинга, которая будет запускаться при получении отзывов от клиентов, анализировать отзывы с помощью машинного обучения и публиковать аналитику в источник, например Power BI или Azure Data Lake.
Для этого решения вы используете такие ключевые компоненты Azure для бессерверных приложений: [Функции Azure](https://azure.microsoft.com/services/functions/) и [Azure Logic Apps](https://azure.microsoft.com/services/logic-apps/).
Azure Logic Apps представляет беcсерверный обработчик рабочего процесса в облаке, поэтому вы можете создавать оркестрации бессерверных компонентов и подключаться к более чем 200 службам и API. Функции Azure предоставляют беcсерверные вычисления в облаке. В этом решении Функции Azure используются для пометки пользовательских твитов на основе предопределенных ключевых слов.
В этом случае вы создаете приложение логики, которое запускает поиск отзывов клиентов. К некоторым соединителям, которые помогают реагировать на отзывы от клиентов, относятся Outlook.com, Office 365, Survey Monkey, Twitter и [HTTP-запрос из веб-формы](https://blogs.msdn.microsoft.com/logicapps/2017/01/30/calling-a-logic-app-from-an-html-form/). Рабочий процесс, который вы создаете, отслеживает хэштег в Twitter.
Вы можете [создать все решение в Visual Studio](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md) и [развернуть решение с помощью шаблона Azure Resource Manager](../logic-apps/logic-apps-deploy-azure-resource-manager-templates.md). Пошаговые инструкции по созданию этого решения см. [в этом видео Channel 9](https://aka.ms/logicappsdemo).
## <a name="trigger-on-customer-data"></a>Триггер, срабатываемый при получении данных клиента
1. На портале Azure или в Visual Studio создайте пустое приложение логики.
Если вы не знакомы с приложениями логики, перейдите к [краткому руководству по его созданию на портале Azure](../logic-apps/quickstart-create-first-logic-app-workflow.md) или [в Visual Studio](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md).
2. В конструкторе приложений логики найдите и добавьте триггер Twitter, в котором есть действие **When a new tweet is posted** (При публикации нового твита).
3. Настройте триггер для прослушивания твитов по ключевому слову или хэштегу.
Свойство повторения определяет, как часто приложение логики будет проверять наличие новых элементов с помощью триггеров на основе опроса, таких как триггер Twitter.
![Пример триггера Twitter][1]
Это приложение логики реагирует на все новые твиты. Затем вы можете взять и проанализировать данные твита, чтобы лучше понять настроение отзыва.
## <a name="analyze-tweet-text"></a>Анализ текста твита
Чтобы понять настроение исходя из текста, вы можете использовать [Azure Cognitive Services](https://azure.microsoft.com/services/cognitive-services/).
1. В конструкторе приложений логики выберите для созданного триггера пункт **Новый шаг**.
2. Найдите соединитель **Текстовая аналитика**.
3. Выберите действие **Detect Sentiment** (Определение тональности).
4. При запросе введите допустимый ключ Cognitive Services для службы текстовой аналитики.
5. В разделе **Текст запроса** выберите поле **Текст твита**, которое содержит текст в качестве входных данных для анализа.
После того, как вы получите данные твита и его аналитику, можно использовать несколько других соответствующих соединителей и их действия:
* **Power BI. Добавление строк в набор данных потоковой передачи**. Входящие твиты можно просматривать на панели мониторинга Power BI.
* **Azure Data Lake. Добавление файла**. Данные клиента добавляются в набор данных Azure Data Lake для включения в задания аналитики.
* **SQL. Добавление строк**. Данные можно сохранить в базе данных для последующего извлечения.
* **Slack. Отправка сообщения**. Канал Slack получает оповещение об отрицательном отзыве, для которого нужно предпринять действие.
Можно также создать Функцию Azure, чтобы иметь возможность выполнять пользовательскую обработку данных.
## <a name="process-data-with-azure-functions"></a>Обработка данных с помощью Функций Azure
Перед созданием функции создайте приложение-функцию в вашей подписке Azure. Кроме того, чтобы ваше приложение логики могло непосредственно вызывать функцию, она должна иметь привязку триггера HTTP, например, используйте шаблон **HttpTrigger**. Узнайте, [как создать свое первое приложение-функцию и функцию на портале Azure](../azure-functions/functions-create-first-azure-function-azure-portal.md).
Для этого сценария используйте текст твита в качестве текста запроса для вашей функции Azure. В коде функции задайте логику, определяющую, что содержит текст твита: ключевое слово или фразу. Используйте простую или сложную функцию в зависимости от реализуемого сценария.
В конце функции верните в приложение логики ответ с данными, например, простое логическое значение, такое как `containsKeyword`, или cоставной объект.
> [!TIP]
> При доступе к сложному ответу от функции в приложении логики **используйте действие "Анализ JSON"** .
Когда вы закончите, сохраните функцию, а затем добавьте ее в качестве действия в приложение логики, которое вы создаете.
## <a name="add-azure-function-to-logic-app"></a>Добавление функции Azure в приложение логики
1. В конструкторе приложений логики в действии **Определить тональность** выберите **Новый шаг**.
2. Найдите соединитель **Функции Azure**, а затем выберите созданную функцию.
3. В поле **Текст запроса** выберите **Текст твита**.
![Настройка шага Функции Azure][2]
## <a name="run-and-monitor-your-logic-app"></a>Запуск и мониторинг приложения логики
Чтобы просмотреть текущие или предыдущие запуски приложения логики, вы можете использовать расширенные возможности отладки и мониторинга, которые Azure Logic Apps предоставляет на портале Azure, в Visual Studio или с помощью интерфейсов API и пакетов SDK для Azure REST.
Чтобы легко протестировать приложение логики, в конструкторе приложений логики выберите **Запустить триггер**. Триггер выполняет опрос твитов на основе указанного расписания, пока не будет найден твит, который соответствует указанным критериям. Конструктор отображает актуальное представление этого запуска в ходе его выполнения.
Чтобы просмотреть предыдущие журналы запусков в Visual Studio или на портале Azure:
* Откройте Visual Studio Cloud Explorer. Найдите ваше приложение логики и откройте контекстное меню приложения. Щелкните **Открыть журнал запусков**.
> [!TIP]
> Если у вас нет этой команды в Visual Studio 2019, убедитесь, что установлены последние обновления для Visual Studio.
* Найдите приложение логики на портале Azure. В меню приложения логики щелкните **Обзор**.
## <a name="create-automated-deployment-templates"></a>Создание шаблонов для автоматического развертывания
После создания решения приложения логики вы можете сохранить и развернуть его в качестве [шаблона Azure Resource Manager](../azure-resource-manager/template-deployment-overview.md) в любом регионе Azure в мире. Вы можете использовать эту возможность, чтобы изменить параметры как для создания различных версий вашего приложения, так и для интеграции вашего решения в Azure Pipelines. Функции Azure также можно включить в шаблон развертывания таким образом, чтобы всем решением вместе со всеми зависимостями можно было управлять как одним шаблоном. Узнайте, как [автоматизировать развертывание приложений логики](logic-apps-azure-resource-manager-templates-overview.md).
Пример шаблона развертывания с функцией Azure можно найти в [репозитории шаблонов быстрого запуска Azure](https://github.com/Azure/azure-quickstart-templates/tree/master/101-function-app-create-dynamic).
## <a name="next-steps"></a>Дальнейшие действия
* [Распространенные сценарии, примеры, учебники и пошаговые руководства для Azure Logic Apps](logic-apps-examples-and-scenarios.md)
<!-- Image References -->
[1]: ./media/logic-apps-scenario-social-serverless/twitter.png
[2]: ./media/logic-apps-scenario-social-serverless/function.png
| 76.533898 | 669 | 0.808327 | rus_Cyrl | 0.959758 |
f4c89bd05e26d404f4f479edf928f13857d5aa57 | 1,788 | md | Markdown | README.md | collaide/rails-log-viewer | 213d9892778e06b3ac5766a360eb01afd9200741 | [
"MIT"
] | 2 | 2017-10-20T11:46:41.000Z | 2020-04-24T18:22:09.000Z | README.md | collaide/rails-log-viewer | 213d9892778e06b3ac5766a360eb01afd9200741 | [
"MIT"
] | null | null | null | README.md | collaide/rails-log-viewer | 213d9892778e06b3ac5766a360eb01afd9200741 | [
"MIT"
] | null | null | null | # Rails Log viewer
With the help of logstash, elasticsearch, kibana and lograge, it is now realy easy to view log of a rails app locally.
This solution has the adventage that it doesn't require any remote server to run.
What it does is to fetch the remote logs to your locale machine and start logstash with kibana if needed
## Installation
Install the gem:
$ gem install rails-log-viewer
Install logstash:
1. Download the latest logstash
2. uncompress the archive
## Usage
#### Configure
First, start to configure the gem, run:
$ fetch-log config
And provide the required informations. By now, you need to setup a ssh publickey to access to your remote machine. The password option is not working. Then, run:
$ read-log config
And provide your logstash executable (usually under: `logstash-1.x.x/bin/logstash`)
Now you can run logstash: ` read-log ` and then fetch the log: ` fetch-log `. Each times the logs has changed and you want to read it, run. ` fetch-log `.
Go to ` localhost:9292 ` to view your logs !
When you are done, run: ` read-log quit `
If you delete the log file to the server and want to parse it from the beginning, run: `read-log reset`
Every created files by this gem are under `$HOME/.log-parser`. Config files are .config for server access and .config-read for logstash executable
To configure lograge go to his github repo. Otherwise is a good idea to read the logstash doc!
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
| 32.509091 | 161 | 0.740492 | eng_Latn | 0.993229 |
f4c8e67cd917087c8712f048f605c81717d710fe | 1,253 | md | Markdown | src/scripts/README.md | martyzz1/circleci-slack-notifier | 1faf9fb36f0e3bf1c4ae8d109c28a1c1c0b4be5b | [
"MIT"
] | null | null | null | src/scripts/README.md | martyzz1/circleci-slack-notifier | 1faf9fb36f0e3bf1c4ae8d109c28a1c1c0b4be5b | [
"MIT"
] | null | null | null | src/scripts/README.md | martyzz1/circleci-slack-notifier | 1faf9fb36f0e3bf1c4ae8d109c28a1c1c0b4be5b | [
"MIT"
] | null | null | null | # scripts/
This is where any scripts you wish to include in your orb can be kept. This is encouraged to ensure your orb can have all aspects tested, and is easier to author, since we sacrifice most features an editor offers when editing scripts as text in YAML.
As a part of keeping things seperate, it is encouraged to use environment variables to pass through parameters, rather than using the `<< parameter. >>` syntax that CircleCI offers.
# Including Scripts
Utilizing the `circleci orb pack` CLI command, it is possible to import files (such as _shell scripts_), using the `<<include(scripts/script_name.sh)>>` syntax in place of any config key's value.
```yaml
# commands/greet.yml
description: >
This command echos "Hello World" using file inclusion.
parameters:
to:
type: string
default: "World"
description: "Hello to who?"
steps:
- run:
environment:
PARAM_TO: <<parameters.to>
name: Hello <<parameters.to>
command: <<include(scripts/greet.sh)>>
```
```shell
# scripts/greet.sh
Greet() {
echo Hello ${PARAM_TO}
}
# Will not run if sourced from another script. This is done so this script may be tested.
# View src/tests for more information.
if [[ "$_" == "$0" ]]; then
Greet
fi
```
| 30.560976 | 250 | 0.709497 | eng_Latn | 0.997873 |
f4c9469f42d7201b8e64ae397da96479623fac5c | 5,150 | md | Markdown | src/pages/blog/2019-06-23-big-o-notation.md | amit-shahi/amitshahi.dev | 76e660d671f9b089aae3fc436b4c451d411c0daa | [
"MIT"
] | null | null | null | src/pages/blog/2019-06-23-big-o-notation.md | amit-shahi/amitshahi.dev | 76e660d671f9b089aae3fc436b4c451d411c0daa | [
"MIT"
] | 1 | 2022-02-22T04:48:42.000Z | 2022-02-22T04:48:42.000Z | src/pages/blog/2019-06-23-big-o-notation.md | amit-shahi/amitshahi.dev | 76e660d671f9b089aae3fc436b4c451d411c0daa | [
"MIT"
] | null | null | null | ---
templateKey: blog-post
title: Big 'O' Notation
date: 2019-06-23T07:32:00.000Z
description: >+
Big O notation is used in Computer Science to describe the performance or
complexity of an algorithm. Big O specifically describes the worst-case
scenario and can be used to describe the execution time required or the space
used (e.g. in memory or on disk) by an algorithm.
featuredpost: false
featuredimage: /img/bigonotation.png
tags:
- Big 'O' Notation
- Big 'O'
- Space Complexity
- Time Complexity
- Worst-Case Scenario
---
## O(1) - Constant Running Time
O(1) describes an algorithm that will always execute in the same time (or space) regardless of the size of the input data set.
```
bool IsFirstElementNull(List<string> elements)
{
return elements[0] == null;
}
```
## O(log N) - Logarithmic Running Time
Logarithmic O(log N) — narrows down the search by repeatedly halving the dataset until you find the target value.
Using binary search — which is a form of logarithmic algorithm, finds the median in the array and compares it to the target value. The algorithm will traverse either upwards or downwards depending on the target value being higher than, lower than or equal to the median.
```C#
public class BinarySearch<T>
{
public int Search(T[] array, T target)
{
if (!String.IsNullOrEmpty(target.ToString()))
return SearchHelper(array, target, 0, array.Length - 1);
return -1;
}
private int SearchHelper(T[] array, T target, int left, int right)
{
while (left <= right)
{
// left + ((right - left) / 2) prevents integer flow.
int middle = left + ((right - left) / 2);
var currentItem = array[middle];
Comparer<T> comparer = Comparer<T>.Default;
if (comparer.Compare(currentItem, target) == 0)
return middle;
else if (comparer.Compare(currentItem, target) > 0)
right = middle - 1;
else
left = middle + 1;
}
return -1;
}
}
```
## O(N) - Linear Running Time
O(N) describes an algorithm whose performance will grow linearly and in direct proportion to the size of the input data set. The example below also demonstrates how Big O favours the worst-case performance scenario; a matching string could be found during any iteration of the for loop and the function would return early, but Big O notation will always assume the upper limit where the algorithm will perform the maximum number of iterations.
```
bool ContainsValue(List<string> elements, string value)
{
foreach (var element in elements)
{
if (element == value) return true;
}
return false;
}
```
## O( N (log N) ) - Quasilinear time/ log-linear / Linearithmic Time
This is the time complexity of divide and conquer sorting algorithms.
In O(N log N), N is the input size (or number of elements).
log N is actually logarithm to the base 2
In divide and conquer approach, we divide the problem into sub problems(divide) and solve them separately and then combine the solutions(conquer).
**When the list of input size n is divided into two halves, we get the log n time complexity.**
That’s why **Merge sort’s** time complexity is O(n log n).
Binary search’s time complexity(which is not divide and conquer approach but divides the list into two halves) which is O(log n)
***
An algorithm with worst-case time complexity W(n) ∊ O(n log n) scales very well. The logarithm function grows very slowly:
log2 1,000 ≈ 10,
log2 1,000,000 ≈ 20,
log2 1,000,000,000 ≈ 30.
In fact, O(n log n) time complexity is close to linear: it takes roughly twice the time to solve a problem twice as big.
## O(N2) - Quadratic (type of Polynomial) Running Time
O(N2) represents an algorithm whose performance is directly proportional to the square of the size of the input data set. This is common with algorithms that involve nested iterations over the data set. Deeper nested iterations will result in O(N3), O(N4) etc.
```
bool ContainsDuplicates(List<string> elements)
{
for (var outer = 0; outer < elements.Count; outer++)
{
for (var inner = 0; inner < elements.Count; inner++)
{
// Don't compare with self
if (outer == inner) continue;
if (elements[outer] == elements[inner]) return true;
}
}
return false;
}
```
## O(2^N) - Exponential Running Time
O(2^N) denotes an algorithm whose growth doubles with each addition to the input data set. The growth curve of an O(2^N) function is exponential - starting off very shallow, then rising meteorically. An example of an O(2N) function is the recursive calculation of Fibonacci numbers:
```
int Fibonacci(int number)
{
if (number <= 1) return number;
return Fibonacci(number - 2) + Fibonacci(number - 1);
}
```
| 33.660131 | 443 | 0.675728 | eng_Latn | 0.992287 |
f4c95e25615bb2d6daa51523722e28661a598b72 | 2,956 | md | Markdown | docs/integration-services/lesson-2-adding-looping-with-ssis.md | kuniteru/sql-docs.ja-jp | 3fe27875882b987f4dc2f7a402859a754ed1a6bb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/integration-services/lesson-2-adding-looping-with-ssis.md | kuniteru/sql-docs.ja-jp | 3fe27875882b987f4dc2f7a402859a754ed1a6bb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/integration-services/lesson-2-adding-looping-with-ssis.md | kuniteru/sql-docs.ja-jp | 3fe27875882b987f4dc2f7a402859a754ed1a6bb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'レッスン 2: SSIS でのループの追加 | Microsoft Docs'
ms.custom: ''
ms.date: 01/03/2019
ms.prod: sql
ms.prod_service: integration-services
ms.reviewer: ''
ms.technology: integration-services
ms.topic: tutorial
ms.assetid: 01f2ed61-1e5a-4ec6-b6a6-2bd070c64077
author: chugugrace
ms.author: chugu
ms.openlocfilehash: f8a7cb05ea7768877ad15ba0d71c5f7636ac8d58
ms.sourcegitcommit: c8e1553ff3fdf295e8dc6ce30d1c454d6fde8088
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 07/22/2020
ms.locfileid: "86920393"
---
# <a name="lesson-2-add-looping-with-ssis"></a>レッスン 2: SSIS でのループの追加
[!INCLUDE[sqlserver-ssis](../includes/applies-to-version/sqlserver-ssis.md)]
「[レッスン 1: SSIS によるプロジェクトと基本パッケージの作成](../integration-services/lesson-1-create-a-project-and-basic-package-with-ssis.md)」で、1 つのフラット ファイル ソースからデータを抽出するパッケージを作成しました。 抽出されたデータは参照変換を使用して変換されます。 最後に、パッケージによって、**AdventureWorksDW2012** サンプル データベースの **FactCurrencyRate** ファクト テーブルのコピーにそのデータが読み込まれます。
抽出、変換、読み込み (ETL) プロセスでは通常、複数のフラット ファイル ソースからデータが抽出されます。 複数のソースからデータを抽出するには、反復型の制御フローが必要となります。 [!INCLUDE[msCoName](../includes/msconame-md.md)] [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] では、繰り返しやループをパッケージに簡単に追加できます。
[!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] には、パッケージ全体をループさせる 2 種類のコンテナーがあります。1 つは Foreach ループ コンテナー、もう 1 つは For ループ コンテナーです。 Foreach ループ コンテナーではループに列挙子が使用されるのに対して、For ループ コンテナーでは通常、変数式が使用されます。 このレッスンでは Foreach ループ コンテナーを使用します。
パッケージで Foreach ループ コンテナーを使用すれば、指定した列挙子の各メンバーについて、制御フローを繰り返すことができます。 Foreach ループ コンテナーでは、次のものを列挙できます。
- ADO レコードセット行
- ADO .Net スキーマ情報
- ファイル構造とディレクトリ構造
- システム変数、パッケージ変数、ユーザー変数
- 変数の列挙可能なオブジェクト
- コレクション内のアイテム
- XML パス言語 (XPath) 式内のノード
- [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] 管理オブジェクト (SMO)
このレッスンでは、Foreach ループ コンテナーを使用するようにレッスン 1 のサンプル ETL パッケージを変更し、そのパッケージにユーザー定義のパッケージ変数を設定します。 サンプル フォルダーで一致するファイルを反復処理する際、その変数が使用されます。
このレッスンでは、データ フローは変更せずに、制御フローのみを変更します。
> [!NOTE]
> まだ行っていない場合は、[レッスン 1 の前提条件](../integration-services/lesson-1-create-a-project-and-basic-package-with-ssis.md#prerequisites)を参照してください。
## <a name="lesson-tasks"></a>このレッスンの作業
このレッスンの内容は次のとおりです。
- [ステップ 1:レッスン 1 のパッケージをコピーする](../integration-services/lesson-2-1-copying-the-lesson-1-package.md)
- [手順 2:Foreach ループ コンテナーの追加および構成](../integration-services/lesson-2-2-adding-and-configuring-the-foreach-loop-container.md)
- [ステップ 3:フラット ファイル接続マネージャーの変更](../integration-services/lesson-2-3-modifying-the-flat-file-connection-manager.md)
- [手順 4:レッスン 2 で作成したチュートリアル パッケージのテスト](../integration-services/lesson-2-4-testing-the-lesson-2-tutorial-package.md)
## <a name="start-the-lesson"></a>レッスンの開始
[ステップ 1:レッスン 1 のパッケージをコピーする](../integration-services/lesson-2-1-copying-the-lesson-1-package.md)
## <a name="see-also"></a>関連項目
[For ループ コンテナー](../integration-services/control-flow/for-loop-container.md)
| 38.894737 | 291 | 0.75406 | yue_Hant | 0.377386 |
f4ca31ddcb54b4cc982c418c9a2eb3e6015af008 | 40 | md | Markdown | Research Files/Control Board/readme.md | CrashOverrideProductions/Ender_3_Pro-Dual-Extruder | c99d0a75840e11e097eb22fb3c0c942b1c7a37ba | [
"CC0-1.0"
] | 1 | 2021-08-25T01:09:38.000Z | 2021-08-25T01:09:38.000Z | Research Files/Control Board/readme.md | CrashOverrideProductions/Ender_3_Pro-Dual-Extruder | c99d0a75840e11e097eb22fb3c0c942b1c7a37ba | [
"CC0-1.0"
] | null | null | null | Research Files/Control Board/readme.md | CrashOverrideProductions/Ender_3_Pro-Dual-Extruder | c99d0a75840e11e097eb22fb3c0c942b1c7a37ba | [
"CC0-1.0"
] | null | null | null | ## Control Board Research Files Go HEre
| 20 | 39 | 0.775 | eng_Latn | 0.506592 |
f4ca7bed3a13a3965fd897869bd22affc5390f4b | 4,947 | md | Markdown | docs/backend-api/resources/tracking/status/index.md | ka1ash/navixy-api | 53195a81fca62d290c336b01c353dd1e3048c5da | [
"Apache-2.0"
] | null | null | null | docs/backend-api/resources/tracking/status/index.md | ka1ash/navixy-api | 53195a81fca62d290c336b01c353dd1e3048c5da | [
"Apache-2.0"
] | null | null | null | docs/backend-api/resources/tracking/status/index.md | ka1ash/navixy-api | 53195a81fca62d290c336b01c353dd1e3048c5da | [
"Apache-2.0"
] | null | null | null | ---
title: Status
description: Status
---
# Status
Statuses used to track current activity for employees (in fact, of tracking devices owned by employees).
The simplest example is "busy" | "not busy". This is a status listing consisting of two elements. Different trackers
can be assigned different status lists.
API base path: `/status/`
## Status object structure
```json
{
"id": 5,
"label": "Busy",
"color": "E57373"
}
```
* `id` - int. A unique identifier of the status. Read-only.
* `label` - string. Human-readable label for the status.
* `color` - string. Hex-representation of RGB color used to display this status.
## Status listing object structure
```json
{
"id": 1,
"label": "Taxi driver statuses",
"employee_controlled": true,
"supervisor_controlled": false,
"entries": [ 5, 2, 1, 4, 6]
}
```
* `id` - int. A unique identifier of this status listing. Read-only.
* `label` - string. Human-readable label for the status listing.
* `employee_controlled` - boolean. If `true` employees can change their own status, e.g. using mobile tracking app.
* `supervisor_controlled` - boolean. If `true` supervisors can change status, e.g. using mobile monitoring app.
* `entries` - int array. List of IDs of statuses which belong to this listing. Order matters, and is preserved.
### create
Creates new possible status for the specified status listing.
**required sub-user rights:** `tracker_update`
#### parameters
| name | description | type|
| :------ | :------ | :----- |
| listing_id | ID of the listing for this status to attach to. | int |
| status | Status object without ID field. | JSON object |
#### examples
=== "cURL"
```shell
curl -X POST '{{ extra.api_example_url }}/status/create' \
-H 'Content-Type: application/json' \
-d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "listing_id": 12345, "status": {"label": "Busy", "color": "E57373"}}'
```
#### response
```json
{
"success": true,
"id": 111
}
```
* `id` - int. ID of the created status.
#### errors
* 201 (Not found in the database) – if listing with the specified ID does not exist.
* 236 (Feature unavailable due to tariff restrictions) – if there are no trackers with "statuses" tariff feature
available.
* 268 (Over quota) – if the user's quota for statuses exceeded.
### delete
Deletes status entry.
**required sub-user rights:** `tracker_update`
#### parameters
| name | description | type|
| :------ | :------ | :----- |
| status_id | ID of the status belonging to authorized user. | int |
#### examples
=== "cURL"
```shell
curl -X POST '{{ extra.api_example_url }}/status/delete' \
-H 'Content-Type: application/json' \
-d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "status_id": 123}'
```
=== "HTTP GET"
```
{{ extra.api_example_url }}/status/delete?hash=a6aa75587e5c59c32d347da438505fc3&status_id=123
```
#### response
```json
{ "success": true }
```
#### errors
* 201 (Not found in the database) – if status with the specified ID does not exist.
* 236 (Feature unavailable due to tariff restrictions) – if there are no trackers with "statuses" tariff feature
available.
### list
Gets statuses belonging to the specified status listing.
#### parameters
| name | description | type|
| :------ | :------ | :----- |
| listing_id | ID of the listing for this status to attach to. | int |
#### examples
=== "cURL"
```shell
curl -X POST '{{ extra.api_example_url }}/status/list' \
-H 'Content-Type: application/json' \
-d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "listing_id": 12345}'
```
=== "HTTP GET"
```
{{ extra.api_example_url }}/status/list?hash=a6aa75587e5c59c32d347da438505fc3&listing_id=12345
```
#### response
```json
{
"success": true,
"list":[{
"id": 5,
"label": "Busy",
"color": "E57373"
},{
"id": 6,
"label": "Free",
"color": "A27373"
}]
}
```
* `list` - ordered array of <status> objects.
#### errors
* 236 (Feature unavailable due to tariff restrictions) – if there are no trackers with "statuses" tariff
feature available.
### update
Updates status properties.
**required sub-user rights:** `tracker_update`
#### parameters
| name | description | type|
| :------ | :------ | :----- |
| status | Status object with ID field. | JSON object |
#### examples
=== "cURL"
```shell
curl -X POST '{{ extra.api_example_url }}/status/update' \
-H 'Content-Type: application/json' \
-d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "status": {"id": 5, "label": "Busy", "color": "E57373"}}'
```
#### response
```json
{ "success": true }
```
#### errors
* 201 (Not found in the database) – if status with the specified ID does not exist.
* 236 (Feature unavailable due to tariff restrictions) – if there are no trackers with "statuses"
tariff feature available.
| 23.557143 | 126 | 0.63675 | eng_Latn | 0.855271 |
f4ca9532d7e516274eee8b0a3237c3e4bd555825 | 718 | md | Markdown | vendor/zendframework/zend-stdlib/README.md | nofandiyan/c-bodas | 6660f0aef8cb48777c93a22e855220901a6860de | [
"MIT"
] | 6 | 2019-02-27T11:19:08.000Z | 2021-10-14T12:44:04.000Z | vendor/zendframework/zend-stdlib/README.md | nofandiyan/c-bodas | 6660f0aef8cb48777c93a22e855220901a6860de | [
"MIT"
] | 14 | 2019-12-29T21:05:44.000Z | 2022-03-24T13:38:11.000Z | vendor/zendframework/zend-stdlib/README.md | backlineint/brian-perry-interactive-drupal | 95d5ca75db4196ebf505ba3ce8edc1c47ff46395 | [
"MIT"
] | 3 | 2017-07-05T23:30:07.000Z | 2017-12-13T02:48:19.000Z | # zend-stdlib
[](https://secure.travis-ci.org/zendframework/zend-stdlib)
[](https://coveralls.io/r/zendframework/zend-stdlib?branch=master)
`Zend\Stdlib` is a set of components that implements general purpose utility
class for different scopes like:
- array utilities functions;
- json serializable interfaces;
- general messaging systems;
- string wrappers;
- etc.
---
- File issues at https://github.com/zendframework/zend-stdlib/issues
- Documentation is at http://framework.zend.com/manual/current/en/index.html#zend-stdlib
| 37.789474 | 162 | 0.781337 | kor_Hang | 0.317344 |
f4cbf0eb7cf3f77cf1a784c60295a61d784a46d5 | 6,760 | md | Markdown | source/documentation/iTin.Export.Documentation/Documentation/T_iTin_Export_Model_CommentModel.md | iAJTin/iExportEngine | b81fb64c4fd8ebe2f2c22957c9c2f676074054cb | [
"MIT"
] | 40 | 2016-10-25T14:01:03.000Z | 2021-12-07T15:40:54.000Z | source/documentation/iTin.Export.Documentation/Documentation/T_iTin_Export_Model_CommentModel.md | iAJTin/iExportEngine | b81fb64c4fd8ebe2f2c22957c9c2f676074054cb | [
"MIT"
] | 1 | 2021-10-08T12:09:38.000Z | 2021-10-08T12:09:38.000Z | source/documentation/iTin.Export.Documentation/Documentation/T_iTin_Export_Model_CommentModel.md | iAJTin/iExportEngine | b81fb64c4fd8ebe2f2c22957c9c2f676074054cb | [
"MIT"
] | 5 | 2018-02-01T03:34:30.000Z | 2021-08-16T07:19:23.000Z | # CommentModel Class
Additional header content
Represents a comment. Includes comment text, format, including font face, size, and style attributes.
## Inheritance Hierarchy
System.Object<br /> <a href="T_iTin_Export_Model_BaseModel_1">iTin.Export.Model.BaseModel</a>(CommentModel)<br /> iTin.Export.Model.CommentModel<br />
**Namespace:** <a href="N_iTin_Export_Model">iTin.Export.Model</a><br />**Assembly:** iTin.Export.Core (in iTin.Export.Core.dll) Version: 2.0.0.0 (2.0.0.0)
## Syntax
**C#**<br />
``` C#
[SerializableAttribute]
public class CommentModel : BaseModel<CommentModel>,
ICloneable
```
**VB**<br />
``` VB
<SerializableAttribute>
Public Class CommentModel
Inherits BaseModel(Of CommentModel)
Implements ICloneable
```
The CommentModel type exposes the following members.
## Constructors
<table><tr><th></th><th>Name</th><th>Description</th></tr><tr><td></td><td><a href="M_iTin_Export_Model_CommentModel__ctor">CommentModel</a></td><td>
Initializes a new instance of the CommentModel class.</td></tr></table>
<a href="#commentmodel-class">Back to Top</a>
## Properties
<table><tr><th></th><th>Name</th><th>Description</th></tr><tr><td></td><td><a href="P_iTin_Export_Model_CommentModel_Font">Font</a></td><td>
Gets or sets the font model.</td></tr><tr><td></td><td><a href="P_iTin_Export_Model_CommentModel_IsDefault">IsDefault</a></td><td>
Gets a value indicating whether this instance is default.
(Overrides BaseModel.IsDefault.)</td></tr><tr><td></td><td><a href="P_iTin_Export_Model_BaseModel_1_Properties">Properties</a></td><td>
Gets or sets a reference to user-defined property list for this element.
(Inherited from <a href="T_iTin_Export_Model_BaseModel_1">BaseModel(T)</a>.)</td></tr><tr><td></td><td><a href="P_iTin_Export_Model_CommentModel_Show">Show</a></td><td>
Gets or sets a value indicating whether displays a comment that contains the original value of the field.</td></tr><tr><td></td><td><a href="P_iTin_Export_Model_CommentModel_Text">Text</a></td><td>
Gets or sets the comment text.</td></tr></table>
<a href="#commentmodel-class">Back to Top</a>
## Methods
<table><tr><th></th><th>Name</th><th>Description</th></tr><tr><td></td><td><a href="M_iTin_Export_Model_CommentModel_Clone">Clone</a></td><td>
Clones this instance.</td></tr><tr><td></td><td><a href="M_iTin_Export_Model_CommentModel_Combine">Combine</a></td><td>
Combines this instance with reference parameter.</td></tr><tr><td></td><td>Equals</td><td> (Inherited from Object.)</td></tr><tr><td></td><td>Finalize</td><td> (Inherited from Object.)</td></tr><tr><td></td><td>GetHashCode</td><td> (Inherited from Object.)</td></tr><tr><td></td><td><a href="M_iTin_Export_Model_BaseModel_1_GetStaticBindingValue">GetStaticBindingValue</a></td><td>
Gets the static binding value by reflection.
(Inherited from <a href="T_iTin_Export_Model_BaseModel_1">BaseModel(T)</a>.)</td></tr><tr><td></td><td>GetType</td><td> (Inherited from Object.)</td></tr><tr><td></td><td>MemberwiseClone</td><td> (Inherited from Object.)</td></tr><tr><td></td><td><a href="M_iTin_Export_Model_BaseModel_1_SaveToFile">SaveToFile(String)</a></td><td>
Saves to file.
(Inherited from <a href="T_iTin_Export_Model_BaseModel_1">BaseModel(T)</a>.)</td></tr><tr><td></td><td><a href="M_iTin_Export_Model_BaseModel_1_SaveToFile_1">SaveToFile(String, Exception)</a></td><td>
Serializes current BaseModel object into file
(Inherited from <a href="T_iTin_Export_Model_BaseModel_1">BaseModel(T)</a>.)</td></tr><tr><td></td><td><a href="M_iTin_Export_Model_BaseModel_1_Serialize">Serialize</a></td><td>
Serializes current BaseModel object into an Xml document.
(Inherited from <a href="T_iTin_Export_Model_BaseModel_1">BaseModel(T)</a>.)</td></tr><tr><td></td><td><a href="M_iTin_Export_Model_BaseModel_1_ToString">ToString</a></td><td>
Returns a string that represents the current object.
(Inherited from <a href="T_iTin_Export_Model_BaseModel_1">BaseModel(T)</a>.)</td></tr></table>
<a href="#commentmodel-class">Back to Top</a>
## Remarks
**ITEE Object Element Usage**<br />
``` XML
<Comment>
<Text/>
<Font/>
</Comment>
```
<strong>Attributes</strong><table><tr><th>Attribute</th><th>Optional</th><th>Description</th></tr><tr><td><a href="P_iTin_Export_Model_CommentModel_Show">Show</a></td><td align="center">Yes</td><td>Determines whether displays a comment that contains the original value of the field. The default is <a href="T_iTin_Export_Model_YesNo">Yes</a>.</td></tr></table><strong>Elements</strong>
<table><tr><th>Element</th><th>Description</th></tr><tr><td><a href="P_iTin_Export_Model_CommentModel_Font">Font</a></td><td>Represents a font. Defines a particular format for text, including font face, size, and style attributes.</td></tr><tr><td><a href="P_iTin_Export_Model_CommentModel_Text">Text</a></td><td>Represents comment text.</td></tr></table>
<strong>Compatibility table with native writers.</strong><table><tr><th>Comma-Separated Values<br /><a href="T_iTin_Export_Writers_CsvWriter">CsvWriter</a></th><th>Tab-Separated Values<br /><a href="T_iTin_Export_Writers_TsvWriter">TsvWriter</a></th><th>SQL Script<br /><a href="T_iTin_Export_Writers_SqlScriptWriter">SqlScriptWriter</a></th><th>XML Spreadsheet 2003<br /><a href="T_iTin_Export_Writers_Spreadsheet2003TabularWriter">Spreadsheet2003TabularWriter</a></th></tr><tr><td align="center">No has effect</td><td align="center">No has effect</td><td align="center">No has effect</td><td align="center">X</td></tr></table> A <strong>`X`</strong> value indicates that the writer supports this element.
## See Also
#### Reference
<a href="N_iTin_Export_Model">iTin.Export.Model Namespace</a><br /> | 80.47619 | 706 | 0.740237 | yue_Hant | 0.499236 |
f4cbf4ab6ee7f22e06cfae2e6917945db0040b97 | 6,378 | md | Markdown | README.md | JingweiToo/Machine-Learning-Toolbox-Python | e8cec16e46b02e205fefbc6269ed62b9191c47a2 | [
"BSD-3-Clause"
] | null | null | null | README.md | JingweiToo/Machine-Learning-Toolbox-Python | e8cec16e46b02e205fefbc6269ed62b9191c47a2 | [
"BSD-3-Clause"
] | null | null | null | README.md | JingweiToo/Machine-Learning-Toolbox-Python | e8cec16e46b02e205fefbc6269ed62b9191c47a2 | [
"BSD-3-Clause"
] | 1 | 2021-05-09T19:26:19.000Z | 2021-05-09T19:26:19.000Z | # Jx-MLT : A Machine Learning Toolbox for Classification
[](https://github.com/JingweiToo/Machine-Learning-Toolbox-Python/blob/main/LICENSE)
[](https://github.com/JingweiToo/Machine-Learning-Toolbox-Python)
---
> "Toward Talent Scientist: Sharing and Learning Together"
> --- [Jingwei Too](https://jingweitoo.wordpress.com/)
---
## Introduction
* This toolbox contains 6 widely used machine learning algorithms
* The `Demo_KNN` and `Demo_LDA` provide the examples of how to use these methods on benchmark dataset
## Usage
You may switch the algorithm by changing the `knn` in `from ML.knn import jkfold` to [other abbreviations](/README.md#list-of-available-machine-learning-methods)
* If you wish to use linear discriminate analysis ( LDA ) classifier then you may write
```code
from ML.lda import jkfold
```
* If you want to use naive bayes ( NB ) classifier then you may write
```code
from ML.nb import jkfold
```
## Input
* *`feat`* : feature vector matrix ( Instance *x* Features )
* *`label`* : label matrix ( Instance *x* 1 )
* *`opts`* : parameter settings
+ *`ho`* : ratio of testing data in hold-out validation
+ *`kfold`* : number of folds in *k*-fold cross-validation
## Output
* *`mdl`* : Machine learning model ( It contains several results )
+ *`acc`* : classification accuracy
+ *`con`* : confusion matrix
+ *`r`* : precision and recall
## How to choose the validation scheme?
There are three types of performance validations. These validation strategies are listed as following ( *KNN* is adopted as an example ).
+ Hold-out cross-validation
```code
from ML.knn import jho
```
+ *K*-fold cross-validation
```code
from ML.knn import jkfold
```
+ Leave-one-out cross-validation
```code
from ML.knn import jloo
```
### Example 1 : *K*-nearest neighbor ( KNN ) with *k*-fold cross-validation
```code
import numpy as np
import pandas as pd
# change this to switch algorithm & types of validation (jho, jkfold, jloo)
from ML.knn import jkfold
import matplotlib.pyplot as plt
import seaborn as sns
# load data
data = pd.read_csv('ionosphere.csv')
data = data.values
feat = np.asarray(data[:, 0:-1])
label = np.asarray(data[:, -1])
# parameters
k = 5
kfold = 10
opts = {'k':k, 'kfold':kfold}
# KNN with k-fold
mdl = jkfold(feat, label, opts)
# overall accuracy
accuracy = mdl['acc']
# confusion matrix
confmat = mdl['con']
print(confmat)
# precision & recall
result = mdl['r']
print(result)
# plot confusion matrix
uni = np.unique(label)
# Normalise
con = confmat.astype('float') / confmat.sum(axis=1)[:, np.newaxis]
fig, ax = plt.subplots()
sns.heatmap(con, annot=True, fmt='.2f', xticklabels=uni, yticklabels=uni, cmap="YlGnBu")
plt.ylabel('Actual')
plt.xlabel('Predicted')
plt.title('KNN')
plt.show()
```
### Example 2 : Support vector machine ( SVM ) with hold-out validation
```code
import numpy as np
from sklearn import datasets
# change this to switch algorithm & types of validation (jho, jkfold, jloo)
from ML.svm import jho
import matplotlib.pyplot as plt
import seaborn as sns
iris = datasets.load_iris()
feat = iris.data
label = iris.target
# parameters
ho = 0.3 # 30% testing set
kernel = 'rbf'
opts = {'ho':ho, 'kernel':kernel}
# machine learning
mdl = jho(feat, label, opts)
# overall accuracy
accuracy = mdl['acc']
# confusion matrix
confmat = mdl['con']
print(confmat)
# precision & recall
result = mdl['r']
print(result)
# plot confusion matrix
uni = np.unique(label)
# Normalise
con = confmat.astype('float') / confmat.sum(axis=1)[:, np.newaxis]
fig, ax = plt.subplots()
sns.heatmap(con, annot=True, fmt='.2f', xticklabels=uni, yticklabels=uni, cmap="YlGnBu")
plt.ylabel('Actual')
plt.xlabel('Predicted')
plt.title('SVM')
plt.show()
```
### Example 3 : Linear Discriminate Analysis ( LDA ) with leave-one-out validation
```code
import numpy as np
from sklearn import datasets
# change this to switch algorithm & types of validation (jho, jkfold, jloo)
from ML.lda import jloo
import matplotlib.pyplot as plt
import seaborn as sns
iris = datasets.load_iris()
feat = iris.data
label = iris.target
# parameters
opts = {}
# machine learning
mdl = jloo(feat, label, opts)
# overall accuracy
accuracy = mdl['acc']
# confusion matrix
confmat = mdl['con']
print(confmat)
# precision & recall
result = mdl['r']
print(result)
# plot confusion matrix
uni = np.unique(label)
# Normalise
con = confmat.astype('float') / confmat.sum(axis=1)[:, np.newaxis]
fig, ax = plt.subplots()
sns.heatmap(con, annot=True, fmt='.2f', xticklabels=uni, yticklabels=uni, cmap="YlGnBu")
plt.ylabel('Actual')
plt.xlabel('Predicted')
plt.title('LDA')
plt.show()
```
## Requirement
* Python 3
* Numpy
* Pandas
* Scikit-learn
* Matplotlib
* Seaborn
## List of available machine learning methods
* Click on the name of algorithm to check the parameters
* Use the *`opts`* to set the specific parameters
* If you do not set extra parameters then the algorithm will use default setting in [here](/Description.md)
| No. | Abbreviation | Name | Support |
|-----|--------------|-----------------------------------------------------------------------------------|--------------|
| 06 | `knn` | [*K*-nearest Neighbor](/Description.md#k-nearest-neighbor-knn) | Multi-class |
| 05 | `svm` | [Support Vector Machine](/Description.md#support-vector-machine-svm) | Multi-class |
| 04 | `dt` | Decision Tree | Multi-class |
| 03 | `lda` | Linear Discriminate Analysis | Multi-class |
| 02 | `nb` | Naive Bayes | Multi-class |
| 01 | `rf` | [Random Forest](Description.md#random-forest-rf) | Multi-class |
| 28.473214 | 170 | 0.64064 | eng_Latn | 0.768325 |
f4cc4c8925d102ccef7b52ed6c889e8e45012e30 | 287 | md | Markdown | R/docs/SearchResultHits.md | openlattice/api-clients | 1d5be9861785b295089b732f37464e31bf80c8ca | [
"Apache-2.0"
] | null | null | null | R/docs/SearchResultHits.md | openlattice/api-clients | 1d5be9861785b295089b732f37464e31bf80c8ca | [
"Apache-2.0"
] | 1 | 2021-01-20T00:20:01.000Z | 2021-01-20T00:20:01.000Z | R/docs/SearchResultHits.md | openlattice/api-clients | 1d5be9861785b295089b732f37464e31bf80c8ca | [
"Apache-2.0"
] | null | null | null | # openlattice::SearchResultHits
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**propertyTypes** | [**array[PropertyType]**](PropertyType.md) | | [optional]
**entitySet** | [**EntitySet**](EntitySet.md) | | [optional]
| 28.7 | 79 | 0.522648 | yue_Hant | 0.142747 |
f4cc87359e68931baad00268f30bd8887859f9c6 | 11,340 | md | Markdown | articles/azure-monitor/alerts/alerts-metric.md | KreizIT/azure-docs.fr-fr | dfe0cb93ebc98e9ca8eb2f3030127b4970911a06 | [
"CC-BY-4.0",
"MIT"
] | 43 | 2017-08-28T07:44:17.000Z | 2022-02-20T20:53:01.000Z | articles/azure-monitor/alerts/alerts-metric.md | KreizIT/azure-docs.fr-fr | dfe0cb93ebc98e9ca8eb2f3030127b4970911a06 | [
"CC-BY-4.0",
"MIT"
] | 676 | 2017-07-14T20:21:38.000Z | 2021-12-03T05:49:24.000Z | articles/azure-monitor/alerts/alerts-metric.md | KreizIT/azure-docs.fr-fr | dfe0cb93ebc98e9ca8eb2f3030127b4970911a06 | [
"CC-BY-4.0",
"MIT"
] | 153 | 2017-07-11T00:08:42.000Z | 2022-01-05T05:39:03.000Z | ---
title: Créer, afficher et gérer des alertes de métrique avec Azure Monitor
description: Découvrez comment utiliser le portail Azure ou l’interface CLI pour créer, afficher et gérer des règles d’alerte de métrique.
author: harelbr
ms.author: harelbr
ms.topic: conceptual
ms.date: 09/09/2021
ms.openlocfilehash: 7a76b4b37760e5e320ab62c2660e97c9fcabdbb0
ms.sourcegitcommit: 0770a7d91278043a83ccc597af25934854605e8b
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 09/13/2021
ms.locfileid: "124815693"
---
# <a name="create-view-and-manage-metric-alerts-using-azure-monitor"></a>Créer, afficher et gérer des alertes de métrique à l’aide d’Azure Monitor
Dans Azure Monitor, les alertes de métrique vous avertissent quand l’une de vos métriques dépasse un certain seuil. Les alertes de métrique fonctionnent sur toute une gamme de métriques de plateforme multidimensionnelles, de métriques personnalisées, mais aussi de métriques standard et personnalisées d’Application Insights. Dans cet article, nous allons décrire comment créer, afficher et gérer des règles d’alerte de métrique par le biais du portail Azure et d’Azure CLI. Vous pouvez également créer des règles d’alerte de métrique à l’aide de modèles Azure Resource Manager, qui sont décrits dans [un autre article](./alerts-metric-create-templates.md).
Vous pouvez en savoir plus sur le fonctionnement des alertes de métrique dans la [vue d’ensemble des alertes de métrique](./alerts-metric-overview.md).
## <a name="create-with-azure-portal"></a>Créer avec le Portail Azure
La procédure suivante décrit comment créer une règle d’alerte de métrique dans le portail Azure :
1. Dans le [portail Azure](https://portal.azure.com), cliquez sur **Moniteur**. Le panneau Moniteur consolide tous vos paramètres et données de supervision dans une même vue.
2. Cliquez sur **Alertes**, puis sur **+ Nouvelle règle d’alerte**.
> [!TIP]
> La plupart des panneaux de ressources incluent également l’option **Alertes** dans leur menu de ressources, sous **Supervision**. Vous pouvez créer des alertes à partir de là également.
3. Cliquez sur **Sélectionner une cible** dans le volet contextuel qui se charge, puis sélectionnez une ressource cible sur laquelle définir une alerte. Utilisez les listes déroulantes **Abonnement** et **Type de ressource** pour rechercher la ressource à surveiller. Vous pouvez également utiliser la barre de recherche pour rechercher votre ressource.
4. Si la ressource sélectionnée dispose de métriques pour lesquelles vous pouvez créer des alertes, la zone des **signaux disponibles** dans la partie inférieure droite inclura des métriques. Vous pouvez afficher la liste complète des types de ressources pris en charge pour les alertes de métrique dans cet [article](./alerts-metric-near-real-time.md#metrics-and-dimensions-supported).
5. Une fois que vous avez sélectionné une ressource cible, cliquez sur **Ajouter une condition**.
6. Vous verrez alors une liste des signaux pris en charge pour la ressource. Sélectionnez la métrique sur laquelle vous souhaitez créer une alerte.
7. Vous verrez un graphique de la métrique pendant les six dernières heures. Utilisez la liste déroulante **Période du graphique** pour voir un historique plus long de la métrique.
8. Si la métrique a des dimensions, une table dimensions s’affiche. Sélectionnez une ou plusieurs valeurs par dimension.
- Les valeurs de dimension affichées sont basées sur les données de métriques couvrant le dernier jour.
- Si la valeur de dimension que vous recherchez n’apparaît pas, cliquez sur « Ajouter une valeur personnalisée » pour ajouter une valeur de dimension personnalisée.
- Vous pouvez également **Sélectionner toutes les valeurs actuelles et futures** pour les dimensions. Cette option permet de mettre à l’échelle la sélection de manière dynamique en fonction de toutes les valeurs actuelles et futures pour une dimension.
La règle d’alerte de métrique évaluera la condition pour toutes les combinaisons de valeurs sélectionnées. [En savoir plus sur le fonctionnement de la génération d’alertes sur les métriques multidimensionnelles](./alerts-metric-overview.md).
> [!NOTE]
> L’utilisation de « Tous » comme valeur de dimension équivaut à sélectionner « Toutes les valeurs actuelles et futures ».
9. Sélectionnez le type de **Seuil**, l’**Opérateur** et le **Type d’agrégation**. Cela permet de déterminer la logique que la règle d’alerte de métrique évaluera.
- Si vous utilisez un seuil **Statique**, définissez une **Valeur du seuil**. Le graphique de métrique peut aider à déterminer un seuil raisonnable.
- Si vous utilisez un seuil **Dynamique**, définissez la **Sensibilité du seuil**. Le graphique de métriques affiche les seuils calculés en fonction des données récentes. [Découvrez-en plus sur le type de condition des seuils dynamiques et les options de sensibilité](../alerts/alerts-dynamic-thresholds.md).
10. Si vous le souhaitez, affinez la condition en réglant **Précision d’agrégation** et **Fréquence d’évaluation**.
11. Cliquez sur **Done**.
12. Si vous le souhaitez, ajoutez un autre critère pour surveiller une règle d’alerte complexe. Actuellement, les utilisateurs peuvent avoir des règles d’alerte avec un critère Seuils dynamiques en tant que critère unique.
13. Renseignez les **détails de l’alerte** (**Nom de règle d’alerte**, **Description** et **Gravité** par exemple).
14. Ajoutez un groupe d’actions à l’alerte, soit en sélectionnant un groupe d’actions existant, soit en créant un nouveau groupe d’actions.
15. Cliquez sur **Terminé** pour enregistrer la règle d’alerte de métrique.
## <a name="view-and-manage-with-azure-portal"></a>Afficher et gérer avec le Portail Azure
Vous pouvez afficher et gérer les règles d’alerte de métrique à l’aide du panneau Gérer les règles, sous Alertes. La procédure suivante vous explique comment afficher vos règles d’alerte de métrique et comment en modifier une.
1. Dans le portail Azure, accédez à **Moniteur**.
2. Cliquez sur **Alertes** et **Gérer les règles**.
3. Dans le panneau **Gérer les règles**, vous pouvez afficher toutes vos règles d’alerte dans tous les abonnements. Vous pouvez filtrer davantage les règles à l’aide des options **Groupe de ressources**, **Type de ressource** et **Ressource**. Si vous souhaitez afficher uniquement les alertes de métrique, sélectionnez le **type de signal** Métriques.
> [!TIP]
> Dans le panneau **Gérer les règles**, vous pouvez sélectionner plusieurs règles d’alerte et les activer/désactiver. Cela peut être utile lorsque certaines ressources cibles doivent être mises en maintenance.
4. Cliquez sur le nom de la règle d’alerte de métrique que vous souhaitez modifier.
5. Dans Modifier la règle, cliquez sur le **critère d’alerte** que vous souhaitez modifier. Vous pouvez modifier la métrique, la condition de seuil et les autres champs en fonction des besoins
> [!NOTE]
> Vous ne pouvez pas modifier le **nom de la règle d’alerte** une fois la règle d’alerte de métrique créée.
6. Cliquez sur **Terminé** pour enregistrer vos modifications.
## <a name="with-azure-cli"></a>Avec l’interface de ligne de commande Azure
Les sections précédentes décrivaient comment créer, afficher et gérer des règles d’alerte de métrique à l’aide du portail Azure. Cette section décrit comment faire de même à l’aide de l’[interface de ligne de commande Azure](/cli/azure/get-started-with-azure-cli) multiplateforme. Le plus rapide pour commencer à utiliser Azure CLI est de s’appuyer sur [Azure Cloud Shell](../../cloud-shell/overview.md). Pour cet article, nous utiliserons Cloud Shell.
1. Accédez au portail Azure, puis cliquez sur **Cloud Shell**.
2. À l’invite, vous pouvez utiliser des commandes avec l’option ``--help`` pour en savoir plus sur la commande et comment l’utiliser. Par exemple, la commande suivante vous montre la liste des commandes disponibles pour la création, l’affichage et la gestion des alertes de métrique.
```azurecli
az monitor metrics alert --help
```
3. Vous pouvez créer une seule règle d’alerte de métrique qui surveille si le pourcentage d’UC moyen sur une machine virtuelle est supérieur à 90
```azurecli
az monitor metrics alert create -n {nameofthealert} -g {ResourceGroup} --scopes {VirtualMachineResourceID} --condition "avg Percentage CPU > 90" --description {descriptionofthealert}
```
4. Vous pouvez afficher toutes les alertes de métrique dans un groupe de ressources à l’aide de la commande suivante.
```azurecli
az monitor metrics alert list -g {ResourceGroup}
```
5. Vous pouvez voir les détails d’une règle d’alerte de métrique spécifique en utilisant le nom ou l’ID de ressource de la règle.
```azurecli
az monitor metrics alert show -g {ResourceGroup} -n {AlertRuleName}
```
```azurecli
az monitor metrics alert show --ids {RuleResourceId}
```
6. Vous pouvez désactiver une règle d’alerte de métrique à l’aide de la commande suivante.
```azurecli
az monitor metrics alert update -g {ResourceGroup} -n {AlertRuleName} --enabled false
```
7. Vous pouvez supprimer une règle d’alerte de métrique à l’aide de la commande suivante.
```azurecli
az monitor metrics alert delete -g {ResourceGroup} -n {AlertRuleName}
```
## <a name="with-powershell"></a>Avec PowerShell
Les règles d’alerte de métrique disposent de cmdlets PowerShell dédiées :
- [Add-AzMetricAlertRuleV2](/powershell/module/az.monitor/add-azmetricalertrulev2) : Créez une nouvelle règle d'alerte de métrique ou mettez-en à jour une existante.
- [Get-AzMetricAlertRuleV2](/powershell/module/az.monitor/get-azmetricalertrulev2) : Obtenez une ou plusieurs règles d’alerte de métrique.
- [Remove-AzMetricAlertRuleV2](/powershell/module/az.monitor/remove-azmetricalertrulev2) : Supprimez une règle d’alerte de métrique.
## <a name="with-rest-api"></a>Avec l’API REST
- [Créer ou mettre à jour](/rest/api/monitor/metricalerts/createorupdate) : Créez une nouvelle règle d'alerte de métrique ou mettez-en à jour une existante.
- [Obtenir](/rest/api/monitor/metricalerts/get) : Obtenez une règle d’alerte de métrique spécifique.
- [Lister par groupe de ressources](/rest/api/monitor/metricalerts/listbyresourcegroup) : Obtenez la liste des règles d’alerte de métrique dans un groupe de ressources spécifique.
- [Lister par abonnement](/rest/api/monitor/metricalerts/listbysubscription) : Obtenez la liste des règles d’alerte de métrique dans un abonnement spécifique.
- [Mettre à jour](/rest/api/monitor/metricalerts/update) : Mettez à jour une règle d’alerte de métrique.
- [Supprimer](/rest/api/monitor/metricalerts/delete) : Supprimez une règle d’alerte de métrique.
## <a name="next-steps"></a>Étapes suivantes
- [Créer des alertes de métrique à l’aide de modèles Azure Resource Manager](./alerts-metric-create-templates.md)
- [Comprendre le fonctionnement des alertes de métrique](./alerts-metric-overview.md)
- [Comprendre le fonctionnement des alertes de métrique avec la condition Seuils dynamiques](../alerts/alerts-dynamic-thresholds.md)
- [Comprendre le schéma des webhooks pour les alertes de métrique](./alerts-metric-near-real-time.md#payload-schema)
- [Résolution des problèmes liés aux alertes de métrique](./alerts-troubleshoot-metric.md)
| 70 | 657 | 0.771781 | fra_Latn | 0.987509 |
f4cd1e5824828b2b748b03314f98f89241a08aad | 722 | md | Markdown | js/airdate/README.md | Dvionst/vvfy | 36b668c862c1f38f34228a5c24ac87f3822584a4 | [
"Apache-2.0"
] | null | null | null | js/airdate/README.md | Dvionst/vvfy | 36b668c862c1f38f34228a5c24ac87f3822584a4 | [
"Apache-2.0"
] | null | null | null | js/airdate/README.md | Dvionst/vvfy | 36b668c862c1f38f34228a5c24ac87f3822584a4 | [
"Apache-2.0"
] | null | null | null | # Air Datepicker
Lightweight customizable cross-browser jQuery datepicker, built with es5 and css-flexbox. Works in all modern browsers.
## Install
```
bower i --save air-datepicker
```
## Usage
```javascript
$('.my-datepicker').datepicker([options])
```
## Demo and docs
* [In English](http://t1m0n.name/air-datepicker/docs/)
* [In Russian](http://t1m0n.name/air-datepicker/docs/index-ru.html)
## Change log
### v1.2.0
* add `range` feature
* improve keyboard navigation (fixed two focused cells)
### v1.1.0
* add keyboard navigation
* add `classes` option to add custom classes
* add `altField` option
* bug fixes
| 23.290323 | 119 | 0.721607 | eng_Latn | 0.465747 |
f4cd33456e910605ea754872ff620340184eddec | 47 | md | Markdown | README.md | varundeep2005/jarvis2000 | 03e2cbd11000151d81c158e45768198f930c365b | [
"MIT"
] | null | null | null | README.md | varundeep2005/jarvis2000 | 03e2cbd11000151d81c158e45768198f930c365b | [
"MIT"
] | null | null | null | README.md | varundeep2005/jarvis2000 | 03e2cbd11000151d81c158e45768198f930c365b | [
"MIT"
] | 1 | 2020-10-01T04:45:29.000Z | 2020-10-01T04:45:29.000Z | # Jarvis 2000
> A voice assistant for the web
| 11.75 | 31 | 0.723404 | eng_Latn | 0.949673 |
f4cd477608ead5b939c616bcd4dc198eca5bf548 | 4,931 | md | Markdown | content/id/docs/concepts/scheduling/kube-scheduler.md | lezeroq/website | a78456d87ca911adeaa73298b5792e7632c8c477 | [
"CC-BY-4.0"
] | 1 | 2021-04-09T16:25:53.000Z | 2021-04-09T16:25:53.000Z | content/id/docs/concepts/scheduling/kube-scheduler.md | lezeroq/website | a78456d87ca911adeaa73298b5792e7632c8c477 | [
"CC-BY-4.0"
] | null | null | null | content/id/docs/concepts/scheduling/kube-scheduler.md | lezeroq/website | a78456d87ca911adeaa73298b5792e7632c8c477 | [
"CC-BY-4.0"
] | 3 | 2020-08-08T13:26:59.000Z | 2022-02-10T08:19:22.000Z | ---
title: Penjadwal Kubernetes
content_type: concept
weight: 50
---
<!-- overview -->
Dalam Kubernetes, _scheduling_ atau penjadwalan ditujukan untuk memastikan
{{< glossary_tooltip text="Pod" term_id="pod" >}} mendapatkan
{{< glossary_tooltip text="Node" term_id="node" >}} sehingga
{{< glossary_tooltip term_id="kubelet" >}} dapat menjalankannya.
<!-- body -->
## Ikhtisar Penjadwalan {#penjadwalan}
Sebuah penjadwal mengawasi Pod yang baru saja dibuat dan belum ada Node yang
dialokasikan untuknya. Untuk setiap Pod yang ditemukan oleh penjadwal, maka
penjadwal tersebut bertanggung jawab untuk menemukan Node terbaik untuk
menjalankan Pod. Penjadwal dapat menetapkan keputusan penempatan ini dengan
mempertimbangkan prinsip-prinsip penjadwalan yang dijelaskan di bawah ini.
Jika kamu ingin memahami mengapa Pod ditempatkan pada Node tertentu, atau jika
kamu berencana untuk mengimplementasikan penjadwal kustom sendiri, halaman ini
akan membantu kamu belajar tentang penjadwalan.
## Kube-scheduler
[_Kube-scheduler_](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/)
adalah penjadwal standar untuk Kubernetes dan dijalankan sebagai bagian dari
{{< glossary_tooltip text="_control plane_" term_id="control-plane" >}}.
_Kube-scheduler_ dirancang agar jika kamu mau dan perlu, kamu bisa menulis
komponen penjadwalan kamu sendiri dan menggunakannya.
Untuk setiap Pod yang baru dibuat atau Pod yang tak terjadwal lainnya,
_kube-scheduler_ memilih Node yang optimal untuk menjalankannya. Namun, setiap
kontainer masuk Pod memiliki persyaratan sumber daya yang berbeda dan setiap Pod
juga memiliki persyaratan yang berbeda juga. Oleh karena itu, Node yang ada
perlu dipilih sesuai dengan persyaratan khusus penjadwalan.
Dalam sebuah Klaster, Node yang memenuhi persyaratan penjadwalan untuk suatu Pod
disebut Node _feasible_. Jika tidak ada Node yang cocok, maka Pod tetap tidak
terjadwal sampai penjadwal yang mampu menempatkannya.
Penjadwal menemukan Node-Node yang layak untuk sebuah Pod dan kemudian
menjalankan sekumpulan fungsi untuk menilai Node-Node yang layak dan mengambil
satu Node dengan skor tertinggi di antara Node-Node yang layak untuk menjalankan
Pod. Penjadwal kemudian memberi tahu server API tentang keputusan ini dalam
proses yang disebut dengan _binding_.
Beberapa faktor yang perlu dipertimbangkan untuk keputusan penjadwalan termasuk
persyaratan sumber daya individu dan kolektif, aturan kebijakan / perangkat keras /
lunak, spesifikasi persamaan dan anti-persamaan, lokalitas data, interferensi
antar Workloads, dan sebagainya.
### Pemilihan node pada kube-scheduler {#kube-scheduler-implementation}
_Kube-scheduler_ memilih node untuk pod dalam 2 langkah operasi:
1. Filtering
2. Scoring
Langkah _filtering_ menemukan sekumpulan Nodes yang layak untuk menjadwalkan
Pod. Misalnya, penyarin PodFitsResources memeriksa apakah Node kandidat
memiliki sumber daya yang cukup untuk memenuhi permintaan spesifik sumber daya dari
Pod. Setelah langkah ini, daftar Node akan berisi Node-node yang sesuai;
seringkali, akan terisi lebih dari satu. Jika daftar itu kosong, maka Pod itu
tidak (belum) dapat dijadwalkan.
Pada langkah _scoring_, penjadwal memberi peringkat pada Node-node yang tersisa
untuk memilih penempatan paling cocok untuk Pod. Penjadwal memberikan skor
untuk setiap Node yang sudah tersaring, memasukkan skor ini pada aturan
penilaian yang aktif.
Akhirnya, _kube-scheduler_ memberikan Pod ke Node dengan peringkat tertinggi.
Jika ada lebih dari satu node dengan skor yang sama, maka _kube-scheduler_
memilih salah satunya secara acak.
Ada dua cara yang didukung untuk mengkonfigurasi perilaku penyaringan dan
penilaian oleh penjadwal:
1. [Aturan Penjadwalan](/docs/reference/scheduling/policies) yang memungkinkan
kamu untuk mengkonfigurasi _Predicates_ untuk pemfilteran dan _Priorities_
untuk penilaian.
1. [Profil Penjadwalan](/docs/reference/scheduling/profiles) yang memungkinkan
kamu mengkonfigurasi _Plugin_ yang menerapkan tahapan penjadwalan berbeda,
termasuk: `QueueSort`, `Filter`, `Score`, `Bind`, `Reserve`, `Permit`, dan
lainnya. Kamu juga bisa mengonfigurasi _kube-scheduler_ untuk menjalankan
profil yang berbeda.
## {{% heading "whatsnext" %}}
* Baca tentang [penyetelan performa penjadwal](/docs/concepts/scheduling/scheduler-perf-tuning/)
* Baca tentang [pertimbangan penyebarang topologi pod](/docs/concepts/workloads/pods/pod-topology-spread-constraints/)
* Baca [referensi dokumentasi](/docs/reference/command-line-tools-reference/kube-scheduler/) untuk _kube-scheduler_
* Pelajari tentang [mengkonfigurasi beberapa penjadwal](/docs/tasks/administer-cluster/configure-multiple-schedulers/)
* Pelajari tentang [aturan manajemen topologi](/docs/tasks/administer-cluster/topology-manager/)
* Pelajari tentang [pengeluaran tambahan Pod](/docs/concepts/configuration/pod-overhead/)
| 47.413462 | 118 | 0.812208 | ind_Latn | 0.982681 |
f4cd6f4b3a79ce20f2ba07018ad0bef9fcba4c4a | 77 | md | Markdown | README.md | sz4ni5z/Open-Lyrics-Converter | 34c182c730d2edee5f4531073495c3714caa37fe | [
"MIT"
] | null | null | null | README.md | sz4ni5z/Open-Lyrics-Converter | 34c182c730d2edee5f4531073495c3714caa37fe | [
"MIT"
] | null | null | null | README.md | sz4ni5z/Open-Lyrics-Converter | 34c182c730d2edee5f4531073495c3714caa37fe | [
"MIT"
] | null | null | null | # Open-Lyrics-Converter
An application to create importable songs for OpenLP
| 25.666667 | 52 | 0.831169 | eng_Latn | 0.874043 |
f4cdc0cdbea283be3057b398c8511eb60d98d4b1 | 435 | md | Markdown | README.md | reymont/SimpleK8sWeb | b918883dc33d92b4cb3dbbf0d81a8a4e32e82d73 | [
"Apache-2.0"
] | null | null | null | README.md | reymont/SimpleK8sWeb | b918883dc33d92b4cb3dbbf0d81a8a4e32e82d73 | [
"Apache-2.0"
] | null | null | null | README.md | reymont/SimpleK8sWeb | b918883dc33d92b4cb3dbbf0d81a8a4e32e82d73 | [
"Apache-2.0"
] | null | null | null | # SimpleK8sWeb
## 安装及启动
```sh
npm install
npm install -g webpack webpack-cli
npm install --global --production windows-build-tools ### for windows
npm start
```
## 注意：
1. 部署的主机需要支持kubectl命令，能够访问k8s的资源。配置/root/.kube/config与/etc/kubernetes/admin/conf一致
2. 在app.js，修改你想要的kubectl命令
```js
app.post('/terminals', function (req, res) {
...
term.write('kubectl exec -it -n test02 '+pod+' bash\r');
...
``` | 19.772727 | 83 | 0.645977 | yue_Hant | 0.23385 |
f4ce067eb8439cd0edd3f64cf99204503932538f | 1,319 | md | Markdown | README.md | IncentroBA/DatagridFixFirstColumn | 740ffb976b43f5c8863ae8d51432ef59fa286b6b | [
"MIT"
] | 1 | 2021-09-06T06:21:32.000Z | 2021-09-06T06:21:32.000Z | README.md | IncentroBA/DatagridFixFirstColumn | 740ffb976b43f5c8863ae8d51432ef59fa286b6b | [
"MIT"
] | 1 | 2021-09-06T06:21:53.000Z | 2021-09-08T11:33:10.000Z | README.md | IncentroBA/DatagridFixFirstColumn | 740ffb976b43f5c8863ae8d51432ef59fa286b6b | [
"MIT"
] | null | null | null | # DatagridFixFirstColumn
## Description
Datagrid with fixed first column and a horizontal scroll.
## Typical usage scenario
By default, a datagrid keeps al information inside the screen. Which is a good thing until there are so many columns in the screen that it becomes hard to read the data (even on a HD screen).
This is where a horizontal scroll comes in handy.
## Features and limitations
### Features
View more data than fits your screen while the first column stays fixed as you scroll through the datagrid.
### Limitations
Force the datagrid to become larger than your screen width by giving most columns a fixed width in pixels. This can best be a value that matches the amount of content inside for most situations. If the datagrid is kept in width units in percentages, not much will happen. Fixing the first column doesn't do anything without a scroll.
The widget is not compatible with the new Datagrid 2 widgets!
## Dependencies
Vertical scrolling is based on a Mendix default layout and placement inside the 'region-content' (which results in the used class: 'mx-scrollcontainer-center').
## Installation
Install the widget and place after the desired datagrid.
## Configuration
Add a class name to the datagrid and tell the widget to listen to this class.
## Bugs
none known at this moment. | 39.969697 | 333 | 0.78696 | eng_Latn | 0.999584 |
f4ce06f01eb3131260ae84bca4af383565a2e961 | 1,727 | md | Markdown | source/includes/_cartValue.md | ahead123/slate | c5f937fee8605dac9f25922e9ec8a04d461e034f | [
"Apache-2.0"
] | null | null | null | source/includes/_cartValue.md | ahead123/slate | c5f937fee8605dac9f25922e9ec8a04d461e034f | [
"Apache-2.0"
] | null | null | null | source/includes/_cartValue.md | ahead123/slate | c5f937fee8605dac9f25922e9ec8a04d461e034f | [
"Apache-2.0"
] | null | null | null | # Cart Value
## mapCartValue()
```javascript
mapCartValue = (arrayOfSelectors = [], currencySymbol = "$") => {
let cartVal = null;
let aA = arrayOfSelectors;
for (let i = 0; i < aA.length; i++) {
if (document.querySelector(aA[i])) {
cartVal = document.querySelector(aA[i]).textContent.trim();
cartVal = cartVal.indexOf(currencySymbol) > -1 ? /[0-9,.]+/.exec(cartVal)[0] : null;
}
}
return cartVal
};
mapCartValue(["Enter comma separated css selectors here"], "Enter currency - unless USD ")
//example
mapCartValue(["div.basketrow > div.total_cell", "table.order-summary > tr.subtotal"], "$")
shcv: "445.00"
```
The mapCartValue function expects an array of comma separated CSS selectors, and a currency symbol.
The mapCartValu function returns a single value string without any commas or currency symbols.
> copy the code block below to use in pixel dashboard
```javascript
mapCartValue = (arrayOfSelectors = [], currencySymbol = "$") => { let cartVal = null; let aA = arrayOfSelectors; for (let i = 0; i < aA.length; i++) { if (document.querySelector(aA[i])) { cartVal = document.querySelector(aA[i]).textContent.trim(); cartVal = cartVal.indexOf(currencySymbol) > -1 ? /[0-9,.]+/.exec(cartVal)[0] : null; } } return cartVal };mapCartValue(["Enter comma separated css selectors here"], "Enter currency - unless USD ")
```
### Parameters
Parameter | Default | Description
--------- | ------- | -----------
arrayOfSelectors | minimum of one CSS selector inside an array | single or multiple css path(s) to an html element containing some text i.e. a <code>```<p class="subtotal">```</code> element.
currencySymbol | $ - USD | the currency symbol to check for to be removed
| 39.25 | 444 | 0.67458 | eng_Latn | 0.752734 |
f4ce2873892720308ea32e0f80bfe7737939c3d9 | 4,867 | md | Markdown | ru/tracker/user/default-filters.md | k0t3n/docs | c56671784cfbd1978e1fe11834fef65539014d84 | [
"CC-BY-4.0"
] | null | null | null | ru/tracker/user/default-filters.md | k0t3n/docs | c56671784cfbd1978e1fe11834fef65539014d84 | [
"CC-BY-4.0"
] | null | null | null | ru/tracker/user/default-filters.md | k0t3n/docs | c56671784cfbd1978e1fe11834fef65539014d84 | [
"CC-BY-4.0"
] | null | null | null | ---
__system: {"dislikeVariants":["Нет ответа на мой вопрос","Рекомендации не помогли","Содержание не соответсвует заголовку","Другое"]}
---
# Найти мои задачи
Чтобы найти задачи, с которыми вы работаете, используйте предустановленные _системные фильтры_. Фильтры выводят списки задач, в которых вы указаны как исполнитель, автор и так далее. Для поиска задач в списке используйте [быструю фильтрацию](#quick-filters) или [добавьте условия поиска](#add-condition).
## Использовать системные фильтры {#sys_filters}
Чтобы найти ваши задачи, на верхней панели {{ tracker-name }} нажмите **Задачи** → **Мои задачи** и выберите один из фильтров:
- **Мои задачи** – задачи, для которых вы являетесь автором, исполнителем или наблюдателем.
- **Избранные задачи** – задачи, которые вы [добавили в избранное](favourites.md#section_thz_1n5_jz).
- **Я автор** – задачи, которые вы создали.
- **Я исполнитель** – задачи, в которых вы назначены исполнителем.
- **Я наблюдатель** – задачи, на обновления которых вы [подписались](subscribe.md#section_xt5_xrv_jz).
- **Ждёт ответа** – задачи, в которых вас [призвали в комментарии](comments.md#section_nl2_1qv_tz).
На странице фильтра вы увидите выбранный список задач. Вы можете добавить условия фильтрации, настроить внешний вид списка или сохранить список в файл:
- Для поиска задач в списке используйте [быструю фильтрацию](#quick-filters) или [добавьте условия поиска](#add-condition).
- Чтобы отобразить или скрыть параметры задач, справа над списком нажмите **Настроить столбцы**, выберите параметры и нажмите кнопку **Сохранить**.
- Чтобы сгруппировать задачи по определенному параметру, справа над списком нажмите **Без группировки** и выберите параметр.
- Чтобы построить для списка задач [диаграмму Гантта](../manager/gantt.md), в правом верхнем углу страницы нажмите значок .
- Чтобы сохранить список задач, справа над списком нажмите значок  и выберите формат файла для загрузки или скопируйте список в буфер обмена.
- Чтобы свернуть левую панель со списком фильтров, вверху панели нажмите кнопку .
## Быстрая фильтрация {#quick-filters}
Чтобы отфильтровать список задач и оставить в нем только задачи с выбранными параметрами, используйте быстрые фильтры. Кнопки быстрой фильтрации расположены над списком задач:
* Фильтр по резолюции. Выберите одну из опций:
- **Все** — на странице отображаются все задачи, независимо от наличия резолюции.
- **Без резолюции** — на странице отображаются только задачи без резолюции (не решенные).
- **С резолюцией** — на странице отображаются только задачи с резолюцией (решенные).
* Группа фильтров для поиска задач по вашей роли. Вы можете включить несколько фильтров одновременно:
- **Я автор**.
- **Я исполнитель**.
- **Я наблюдатель**.
В результате в списке останутся только те задачи, которые удовлетворяют выбранным фильтрам.
## Добавить условия поиска {#add-condition}
#### Поиск по параметрам
Чтобы найти в списке задачи по параметрам, которые нельзя задать с помощью быстрых фильтров, добавьте условия поиска:
1. Над списком задач нажмите кнопку **Добавить условие**.
1. Выберите параметр задачи, затем задайте его значение.
В списке останутся только задачи, параметры которых удовлетворяют заданному условию.
1. Если нужно уточнить условия поиска, добавьте еще несколько параметров.
1. Чтобы отменить заданные условия поиска, над списком задач нажмите **Сбросить**.
Например, вы можете искать задачи по названию или описанию:
- Чтобы найти задачи, название которых содержит заданную фразу, добавьте в условия поиска параметр **Задача** и введите текст для поиска.
- Чтобы найти задачи, описание которых содержит заданную фразу, добавьте в условия поиска параметр **Описание** и введите текст для поиска.
{% note info %}
Если вы зададите несколько условий поиска, будут найдены только те задачи, которые удовлетворяют всем условиям одновременно.
{% endnote %}
#### Язык запросов
Если условия поиска не удается задать с помощью параметров задачи, используйте запрос:
1. В правом верхнем углу страницы нажмите кнопку **Язык запросов**. Все параметры поиска, которые вы задали с помощью быстрых фильтров и условий, отобразятся в строке запроса.
1. Добавьте в строку условия с помощью [языка запросов](query-filter.md).
1. Нажмите кнопку **Применить**.
В списке останутся только задачи, параметры которых удовлетворяют заданному условию.
#### Сохранить фильтр
Чтобы сохранить условия поиска задач в виде фильтра, над списком задач нажмите кнопку **Сохранить фильтр как** и задайте имя фильтра. Сохраненный фильтр появится в списке на левой панели.
| 43.070796 | 304 | 0.765975 | rus_Cyrl | 0.988889 |
f4ce33c49bd094060865d4ca4dc5287b621ef3ec | 3,607 | md | Markdown | articles/service-bus-messaging/service-bus-quickstart-topics-subscriptions-portal.md | Myhostings/azure-docs.tr-tr | 536eaf3b454f181f4948041d5c127e5d3c6c92cc | [
"CC-BY-4.0",
"MIT"
] | 16 | 2017-08-28T08:29:36.000Z | 2022-01-02T16:46:30.000Z | articles/service-bus-messaging/service-bus-quickstart-topics-subscriptions-portal.md | Ahmetmaman/azure-docs.tr-tr | 536eaf3b454f181f4948041d5c127e5d3c6c92cc | [
"CC-BY-4.0",
"MIT"
] | 470 | 2017-11-11T20:59:16.000Z | 2021-04-10T17:06:28.000Z | articles/service-bus-messaging/service-bus-quickstart-topics-subscriptions-portal.md | Ahmetmaman/azure-docs.tr-tr | 536eaf3b454f181f4948041d5c127e5d3c6c92cc | [
"CC-BY-4.0",
"MIT"
] | 25 | 2017-11-11T19:39:08.000Z | 2022-03-30T13:47:56.000Z | ---
title: Service Bus konuları ve abonelikleri oluşturmak için Azure portal kullanın
description: 'Hızlı başlangıç: Bu hızlı başlangıçta, Azure portal kullanarak bu konuya bir Service Bus konu ve abonelik oluşturmayı öğreneceksiniz.'
author: spelluru
ms.author: spelluru
ms.date: 06/23/2020
ms.topic: quickstart
ms.custom:
- mode-portal
ms.openlocfilehash: 25b0579f05c1f7669a8dfc1df02e9a1f575ea066
ms.sourcegitcommit: 49b2069d9bcee4ee7dd77b9f1791588fe2a23937
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 04/16/2021
ms.locfileid: "107537140"
---
# <a name="use-the-azure-portal-to-create-a-service-bus-topic-and-subscriptions-to-the-topic"></a>Azure portalını kullanarak Service Bus konusunu ve konunun aboneliklerini oluşturma
Bu hızlı başlangıçta, bir Service Bus konu oluşturmak ve ardından bu konuya abonelikler oluşturmak için Azure portal kullanın.
## <a name="what-are-service-bus-topics-and-subscriptions"></a>Service Bus konuları ve abonelikleri nelerdir?
Service Bus konuları ve abonelikleri *publish/subscribe* mesajlaşma iletişim modelini destekler. Konular ve abonelikler kullanıldığında, dağıtılmış uygulamanın bileşenleri birbirleriyle doğrudan iletişim kurmazlar; bunun yerine bir aracı gibi davranan bir konu aracılığıyla iletileri değiş tokuş eder.
Her iletinin tek bir tüketici tarafından işlendiği Service Bus kuyruklarının aksine, konular ve abonelikler, Yayımla/abone ol ' u kullanarak bire çok bir iletişim biçimi sağlar. Bir konuya birden fazla abonelik kaydedilebilir. Bir konuya ileti gönderildiğinde, bundan sonra, bağımsız olarak ele almak/işlemek amacıyla her abonelik için kullanılabilir hale getirilir. Bir konuya abone olunması, konuya gönderilmiş olan iletilerin kopyaların alan sanal kuyruğa benzer. İsteğe bağlı olarak, bir konu için filtre kurallarını abonelik başına temelinde kaydedebilirsiniz. Bu, hangi konu aboneliklerinin hangi konuyla ilgili olduğunu filtrelemenizi veya kısıtlamanıza olanak sağlar.
Service Bus konuları ve abonelikleri, çok sayıda kullanıcı ve uygulama genelinde çok sayıda iletiyi işlemek için ölçeklendirmenize olanak tanır.
[!INCLUDE [service-bus-create-namespace-portal](../../includes/service-bus-create-namespace-portal.md)]
[!INCLUDE [service-bus-create-topics-three-subscriptions-portal](../../includes/service-bus-create-topics-three-subscriptions-portal.md)]
> [!NOTE]
> Service Bus kaynaklarını [Service Bus Explorer](https://github.com/paolosalvatori/ServiceBusExplorer/)ile yönetebilirsiniz. Service Bus gezgin, kullanıcıların bir Service Bus ad alanına bağlanmasına ve mesajlaşma varlıklarını kolay bir şekilde yönetmesine olanak tanır. Araç içeri/dışarı aktarma işlevselliği gibi gelişmiş özellikler ya da konu, kuyruk, abonelik, geçiş Hizmetleri, Bildirim Hub 'ları ve Olay Hub 'larını test etme yeteneği sağlar.
## <a name="next-steps"></a>Sonraki adımlar
Bu makalede bir Service Bus ad alanı, ad alanında bir konu ve konuya üç abonelik oluşturdunuz. Konuya ileti yayımlamayı ve bir abonelikten iletileri abone olmayı öğrenmek için, **Iletileri Yayımla ve abone ol** bölümünde aşağıdaki hızlı başlangıçlardan birine bakın.
- [.NET](service-bus-dotnet-how-to-use-topics-subscriptions.md)
- [Java](service-bus-java-how-to-use-topics-subscriptions.md)
- [JavaScript](service-bus-nodejs-how-to-use-topics-subscriptions.md)
- [Python](service-bus-python-how-to-use-topics-subscriptions.md)
- [PHP](service-bus-php-how-to-use-topics-subscriptions.md)
- [Ruby](service-bus-ruby-how-to-use-topics-subscriptions.md)
| 80.155556 | 675 | 0.816745 | tur_Latn | 0.99919 |
f4ce76c7f6d61837d28c79fdee250dfb63ba7c97 | 196 | md | Markdown | pages.es/linux/snake4scores.md | stautonico/tldr | bebfa4e965256c2e7fefa0aabf1d775a92c4fb3a | [
"CC-BY-4.0"
] | 2 | 2021-06-01T13:47:41.000Z | 2021-07-30T20:18:00.000Z | pages.es/linux/snake4scores.md | stautonico/tldr | bebfa4e965256c2e7fefa0aabf1d775a92c4fb3a | [
"CC-BY-4.0"
] | 3 | 2021-05-20T15:47:33.000Z | 2021-05-20T16:12:50.000Z | pages.es/linux/snake4scores.md | stautonico/tldr | bebfa4e965256c2e7fefa0aabf1d775a92c4fb3a | [
"CC-BY-4.0"
] | 1 | 2021-05-19T17:07:38.000Z | 2021-05-19T17:07:38.000Z | # snake4scores
> Muestra las máximas puntuaciones del juego snake4.
> Más información: <https://manpages.debian.org/snake4/snake4.6.en.html>.
- Muestra las máximas puntuaciones:
`snake4scores`
| 21.777778 | 73 | 0.770408 | spa_Latn | 0.857586 |
f4ce9cc97168a198ed25c1c021dbd1c330d8d05f | 16,928 | md | Markdown | app/enterprise/2.5.x/admin-api/event-hooks/reference.md | pastine/docs.konghq.com | 305348e2f0117f3465a5e9e978606716215becbf | [
"MIT"
] | 109 | 2018-08-21T04:48:09.000Z | 2022-03-30T22:09:54.000Z | app/enterprise/2.5.x/admin-api/event-hooks/reference.md | pastine/docs.konghq.com | 305348e2f0117f3465a5e9e978606716215becbf | [
"MIT"
] | 2,857 | 2018-06-21T12:58:04.000Z | 2022-03-31T16:25:47.000Z | app/enterprise/2.5.x/admin-api/event-hooks/reference.md | pastine/docs.konghq.com | 305348e2f0117f3465a5e9e978606716215becbf | [
"MIT"
] | 402 | 2018-06-23T11:45:59.000Z | 2022-03-26T07:47:01.000Z | ---
title: Event Hooks Reference
book: event-hooks
---
## Introduction
{:.important}
> **Important:** Before you can use event hooks for the first time, Kong needs to be
reloaded.
{% include /md/enterprise/event-hooks-intro.md %}
{:.note}
> **Note:** Event hooks do not work with Konnect Cloud yet.
## List all event hooks
**Endpoint**
<div class="endpoint get">/event-hooks</div>
**Response**
```json
{
"data": [
{
"config": {
"body": null,
"body_format": true,
"headers": {
"content-type": "application/json"
},
"headers_format": false,
"method": "POST",
"payload": {
"text": "{% raw %}Admin account \`{{ entity.username }}\` {{ operation}}d; email address set to \`{{ entity.email }}\`{% endraw %}"
},
"payload_format": true,
"secret": null,
"ssl_verify": false,
"url": "https://hooks.slack.com/services/foo/bar/baz"
},
"created_at": 1627588552,
"event": "admins",
"handler": "webhook-custom",
"id": "937df175-3db2-4e6d-8aa1-d95c94a76089",
"on_change": null,
"snooze": null,
"source": "crud"
},
{
"config": {
"headers": {},
"secret": null,
"ssl_verify": false,
"url": "https://webhook.site/a1b2c3-d4e5-g6h7-i8j9-k1l2m3n4o5p6"
},
"created_at": 1627581575,
"event": "consumers",
"handler": "webhook",
"id": "c57340ab-9fed-40fd-bb7e-1cef8d37c2df",
"on_change": null,
"snooze": null,
"source": "crud"
},
{
"config": {
"functions": [
"return function (data, event, source, pid)\n local user = data.entity.username\n error(\"Event hook on consumer \" .. user .. \"\")\nend\n"
]
},
"created_at": 1627595513,
"event": "consumers",
"handler": "lambda",
"id": "c9fdd58d-5416-4d3a-9467-51e5cfe4ca0e",
"on_change": null,
"snooze": null,
"source": "crud"
}
],
"next": null
}
```
## List all sources
Sources are the actions that trigger the event hook. The `/sources` JSON output follows the following pattern:
- 1st level = The source, which is the action that triggers the event hook.
- 2nd level = The event, which is the Kong entity the event hook will listen to for events.
- 3rd level = The available template parameters for use in webhook-custom payloads.
For instance, in the example below `balancer` is the source, `health` is the event, and `upstream_id`,
`ip`, `port`, `hostname`, and `health` are the available template parameters.
**Endpoint**
<div class="endpoint get">/event-hooks/sources/</div>
**Response**
```json
{
"data": {
"balancer": {
"health": {
"fields": [
"upstream_id",
"ip",
"port",
"hostname",
"health"
]
}
},
"crud": {
"acls": {
"fields": [
"operation",
"entity",
"old_entity",
"schema"
]
},
. . .
"rate-limiting-advanced": {
"rate-limit-exceeded": {
"description": "Run an event when a rate limit has been exceeded",
"fields": [
"consumer",
"ip",
"service",
"rate",
"limit",
"window"
],
"unique": [
"consumer",
"ip",
"service"
]
}
}
}
}
```
{:.note}
> **Note:** The response has been shortened because it is too long to include in its entirety.
The ellipsis in the center of the response represents the missing content.
## List all events for a source
Events are the Kong entities the event hook will listen to for events. With this endpoint you
can list all of the events associated with a particular source.
<div class="endpoint get">/event-hooks/sources/{source}/</div>
The following response lists all of the events for the `dao:crud` source.
**Response**
```json
{
"data": {
"create": {
"fields": [
"operation",
"entity",
"old_entity",
"schema"
]
},
"delete": {
"fields": [
"operation",
"entity",
"old_entity",
"schema"
]
},
"update": {
"fields": [
"operation",
"entity",
"old_entity",
"schema"
]
}
}
}
```
## Add a webhook
**Endpoint**
<div class="endpoint post">/event-hooks</div>
**Request Body**
| Attribute | Description |
| ---------: | -------- |
| `event`<br>*optional* | A string describing the Kong entity the event hook will listen to for events. |
| `handler`<br>*required* | A string describing one of four handler options: webhook, webhook-custom, log, or lambda. |
| `source`<br>*required* | A string describing the action that triggers the event hook. |
| `snooze`<br>*optional* | An optional integer describing the time in seconds to delay an event trigger to avoid spamming an integration. |
| `on_change`<br>*optional* | An optional boolean indicating whether to trigger an event when key parts of a payload have changed. |
| `config.url`<br>*required* | The URL the JSON POST request is made to with the event data as the payload. |
| `config.headers`<br>*optional* | An object defining additional HTTP headers to send in the webhook request, for example `{"X-Custom-Header": "My Value"}`.|
| `config.secret`<br>*optional* | An optional string used to sign the remote webhook for remote verification. When set, Kong will sign the body of the event hook with HMAC-SHA1 and include it in a header, `x-kong-signature`, to the remote endpoint. |
| `config.ssl_verify`<br>*optional* | A boolean indicating whether to verify the SSL certificate of the remote HTTPS server where the event hook will be sent. The default is `false`. |
**Response**
```json
{
"config": {
"headers": {},
"secret": null,
"ssl_verify": false,
"url": "https://webhook.site/a1b2c3-d4e5-g6h7-i8j9-k1l2m3n4o5p6"
},
"created_at": 1627581575,
"event": "consumers",
"handler": "webhook",
"id": "c57340ab-9fed-40fd-bb7e-1cef8d37c2df",
"on_change": null,
"snooze": null,
"source": "crud"
}
```
## Add a custom webhook
**Endpoint**
<div class="endpoint post">/event-hooks</div>
**Request Body**
| Attribute | Description |
| ---------: | -------- |
| `event`<br>*optional* | A string describing the Kong entity the event-hook will listen to for events. |
| `handler`<br>*required* | A string describing one of four handler options: webhook, webhook-custom, log, or lambda. |
| `source`<br>*required* | A string describing the action that triggers the event hook. |
| `snooze`<br>*optional* | An optional integer describing the time in seconds to delay an event trigger to avoid spamming an integration. |
| `on_change`<br>*optional* | An optional boolean indicating whether to trigger an event when key parts of a payload have changed. |
| `config.url`<br>*required* | The URL the JSON POST request is made to with the event data as the payload. |
| `config.method`<br>*required* | The HTTP method used to create the custom webhook. |
| `config.payload`<br>*optional* | An object that includes key/value pairs that describe the configurable payload body. Supports templating. The full list of available template parameters can be found in the `/sources` API output, under the `fields` JSON object. |
| `config.payload_format`<br>*optional* | A optional boolean (defaults to `true`) indicating whether to format the `config.payload` with resty templating. When set to `false`, the payload is sent as a raw object. |
| `config.body`<br>*optional* | An optional string sent in the remote request. |
| `config.body_format`<br>*optional* | An optional boolean (defaults to `true`) indicating whether to format the `config.body` with resty templating. When set to `false`, the body is sent as a raw object. To see all the available parameters defined for a specific `source`, check the source fields displayed by the `/event-hooks/source` endpoint. |
| `config.headers` | An object defining additional HTTP headers to send in the webhook request, for example `{"Content-type": "application/json", "X-Custom-Header": "My Value"}`. |
| `config.headers_format`<br>*optional* | An optional boolean (defaults to `false`) indicating whether to format the `config.headers` with resty templating. When set to `true`, the `config.headers` value will be treated as a template. To see all the available parameters defined for a specific `source`, check the source fields displayed by the `/event-hooks/sources` endpoint. |
| `config.secret`<br>*optional* | An optional string used to sign the remote webhook for remote verification. When set, Kong will sign the body of the event hook with HMAC-SHA1 and include it in a header, `x-kong-signature`, to the remote endpoint. |
| `config.ssl_verify`<br>*optional* | A boolean indicating whether to verify the SSL certificate of the remote HTTPS server where the event hook will be sent. The default value is `false`. |
**Response**
```json
{
"config": {
"body": null,
"body_format": true,
"headers": {
"content-type": "application/json"
},
"headers_format": false,
"method": "POST",
"payload": {
"text": "Admin account `{{ entity.username }}` {{ operation }}d; email address set to `{{ entity.email }}`"
},
"payload_format": true,
"secret": null,
"ssl_verify": false,
"url": "https://hooks.slack.com/services/foo/bar/baz"
},
"created_at": 1627588552,
"event": "admins",
"handler": "webhook-custom",
"id": "937df175-3db2-4e6d-8aa1-d95c94a76089",
"on_change": null,
"snooze": null,
"source": "crud"
}
```
## Add a log event hook
**Endpoint**
<div class="endpoint post">/event-hooks</div>
**Request Body**
| Attribute | Description |
| ---------: | -------- |
| `event`<br>*optional* | A string describing the Kong entity the event hook will listen to for events. |
| `handler`<br>*required* | A string describing one of four handler options: webhook, webhook-custom, log, or lambda. |
| `source`<br>*required* | A string describing the action that triggers the event hook. |
| `snooze`<br>*optional* | An optional integer describing the time in seconds to delay an event trigger to avoid spamming an integration. |
| `on_change`<br>*optional* | An optional boolean indicating whether to trigger an event when key parts of a payload have changed. |
**Response**
```json
{
"config": {},
"on_change": null,
"created_at": 1627346155,
"snooze": null,
"id": "13a16f91-68b6-4384-97f7-d02763a551ac",
"handler": "log",
"source": "crud",
"event": "routes"
}
```
## Add a lambda event hook
**Endpoint**
<div class="endpoint post">/event-hooks</div>
**Request Body**
| Attribute | Description |
| ---------: | -------- |
| `event`<br>*optional* | A string describing the Kong entity the event hook will listen to for events. |
| `handler`<br>*required* | A string describing one of four handler options: webhook, webhook-custom, log, or lambda. |
| `source`<br>*required* | A string describing the action that triggers the event hook. |
| `snooze`<br>*optional* | An optional integer describing the time in seconds to delay an event trigger to avoid spamming an integration. |
| `on_change`<br>*optional* | An optional boolean indicating whether to trigger an event when key parts of a payload have changed. |
| `config.functions`<br>*required* | An array of Lua code functions to execute on the event hook. |
**Response**
```json
{
"config": {
"functions": [
"return function (data, event, source, pid)\n local user = data.entity.username\n error(\"Event hook on consumer \" .. user .. \"\")\nend\n"
]
},
"created_at": 1627595513,
"event": "consumers",
"handler": "lambda",
"id": "c9fdd58d-5416-4d3a-9467-51e5cfe4ca0e",
"on_change": null,
"snooze": null,
"source": "crud"
}
```
## Test an event hook
It's useful to manually trigger an event hook without provoking the event to be triggered.
For instance, you might want to test the integration, or see if your hook's service is receiving a payload from Kong.
POST any data to `/event-hooks/:id-of-hook/test`, and the `/test` endpoint executes the with the provided data as the event payload.
**Endpoint**
<div class="endpoint post">/event-hooks/{event-hook-id}/test</div>
**Response**
```json
{
"data": {
"consumer": {
"username": "Jane Austen"
},
"event": "consumers",
"source": "crud"
},
"result": {
"body": "",
"headers": {
"Cache-Control": "no-cache, private",
"Content-Type": "text/plain; charset=UTF-8",
"Date": "Fri, 30 Jul 2021 16:07:09 GMT",
"Server": "nginx/1.14.2",
"Transfer-Encoding": "chunked",
"Vary": "Accept-Encoding",
"X-Request-Id": "f1e703a5-d22c-435c-8d5d-bc9c561ead4a",
"X-Token-Id": "1cc1c53b-f613-467f-a5c9-20d276405104"
},
"status": 200
}
}
```
## Ping a webhook event hook
**Endpoint**
<div class="endpoint get">/event-hooks/{event-hook-id}/ping</div>
**Response**
```json
{
"source": "kong:event_hooks",
"event_hooks": {
"source": "crud",
"id": "c57340ab-9fed-40fd-bb7e-1cef8d37c2df",
"on_change": null,
"event": "consumers",
"handler": "webhook",
"created_at": 1627581575,
"config": {
"headers": {
"content-type": "application/json"
},
"ssl_verify": false,
"url": "https://webhook.site/a1b2c3-d4e5-g6h7-i8j9-k1l2m3n4o5p6",
"secret": null
},
"snooze": null
},
"event": "ping"
}
```
| 39.367442 | 379 | 0.510397 | eng_Latn | 0.919227 |
f4cf4e64852c61048e667d0cf0afe7efeeb1582e | 50,331 | md | Markdown | Exchange-Server-2013/what-s-new-in-exchange-2013-exchange-2013-help.md | v-bhmakwn/OfficeDocs-Exchange-Test-pr.de-de | d39b524813fe6ad43490ab8f7e73340f4cc887c9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange-Server-2013/what-s-new-in-exchange-2013-exchange-2013-help.md | v-bhmakwn/OfficeDocs-Exchange-Test-pr.de-de | d39b524813fe6ad43490ab8f7e73340f4cc887c9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange-Server-2013/what-s-new-in-exchange-2013-exchange-2013-help.md | v-bhmakwn/OfficeDocs-Exchange-Test-pr.de-de | d39b524813fe6ad43490ab8f7e73340f4cc887c9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Neuerungen in Exchange 2013: Exchange 2013 Help'
TOCTitle: Neuerungen in Exchange 2013
ms:assetid: 97501135-2149-4590-8373-98e638ac8eb1
ms:mtpsurl: https://technet.microsoft.com/de-de/library/JJ150540(v=EXCHG.150)
ms:contentKeyID: 50476274
ms.date: 04/24/2018
mtps_version: v=EXCHG.150
ms.translationtype: HT
---
# Neuerungen in Exchange 2013
_**Gilt für:** Exchange Server 2013_
_**Letztes Änderungsdatum des Themas:** 2016-12-09_
Informieren Sie sich über die neuesten Funktionen in Exchange 2013.
Microsoft Exchange Server 2013 erweitert die Exchange Server-Produktlinie um eine umfangreiche Sammlung neuer Technologien, Funktionen und Dienste. Ziel ist es, Benutzer und Organisationen bei der Änderung ihrer Arbeitsgewohnheiten zu unterstützen, deren Schwerpunkt sich von auf der Kommunikation weiter auf die Zusammenarbeit verlagert. Zugleich hilft Exchange Server 2013, die Gesamtbetriebskosten zu senken – ob bei einer lokalen Bereitstellung von Exchange 2013 oder einer Bereitstellung Ihrer Postfächer in der Cloud. Neue Features und Funktionen in Exchange 2013 wurden für die folgenden Zwecke konzipiert:
- **Unterstützen einer Mitarbeiterschaft mehrerer Generationen** Ein soziales Miteinander und das schnelle Finden von Personen sind für Benutzer wichtig. Die Funktion *Intelligente Suche* wertet das Kommunikations- und Zusammenarbeitsverhalten aus, um Suchergebnisse im Exchange zu verbessern und mit Prioritäten zu versehen. Mithilfe von Exchange 2013 können Benutzer außerdem Kontakte aus mehreren Quellen zusammenführen, um eine einzelne Sicht auf eine Person zu schaffen, für die aus mehreren Stellen abgerufene Kontaktinformationen miteinander verknüpft werden.
- **Neue optimierte Oberfläche** Microsoft Outlook 2013 und Microsoft Outlook Web App haben eine neue aktualisierte Benutzeroberfläche. Outlook Web App bietet eine verbesserte Benutzeroberfläche, die auch die Verwendung von Touchscreens unterstützt, wodurch die Nutzung von Exchange auf mobilen Geräten optimiert wird.
- **Integration mit SharePoint und Lync** Exchange 2013 bietet mithilfe von Websitepostfächern und Compliance-eDiscovery eine bessere Integration mit Microsoft SharePoint 2013 und Microsoft Lync 2013. Zusammen bieten diese Produkte eine breite Palette an Features, die Szenarien wie Unternehmens-eDiscovery und Zusammenarbeit mit Websitepostfächern ermöglichen.
- **Hilfe bei der Erfüllung wachsender Anforderungen hinsichtlich Compliance** Compliance und eDiscovery stellen für viele Organisationen eine Herausforderung dar. Exchange 2013 hilft Ihnen nicht nur beim Suchen und Finden von Daten in Exchange, sondern in der gesamten Organisation. Dank verbesserter Such- und Indexfunktionen können Sie Exchange 2013, Lync 2013, SharePoint 2013 und Windows-Dateiserver durchsuchen. Mit den Funktionen zur Verhinderung von Datenverlust (Data Loss Prevention, DLP) können Organisationen auch verhindern, dass Benutzer versehentlich vertrauliche Informationen an nicht autorisierte Personen senden. DLP ermöglicht Ihnen das Bestimmen, Überwachen und Schützen vertraulicher Daten mittels einer eingehenden Inhaltsanalyse.
- **Bereitstellung einer ausfallsicheren Lösung** Exchange 2013 baut auf der Architektur von Exchange Server 2010 auf und wurde hinsichtlich Einfachheit für Skalierung, Hardwarenutzung und Fehlerisolierung neu gestaltet.
Informationen zu den an Exchange Server 2013 seit der RTM-Version (Release to Manufacturing) erfolgten Änderungen finden Sie unter [Updates für Exchange 2013](updates-for-exchange-2013-exchange-2013-help.md).
In den folgenden Themen finden Sie weitere Informationen zu den Neuerungen in Exchange 2013:
Exchange-Verwaltungskonsole
Exchange 2013-Architektur
Setup
Messagingrichtlinie und -kompatibilität
Schutz vor Schadsoftware
Nachrichtenübermittlung
Empfänger
Freigabe und Zusammenarbeit
Integration in SharePoint und Lync
Clients und mobile Funktionen
Unified Messaging
Batchverschiebungen von Postfächern
[Hohe Verfügbarkeit und Ausfallsicherheit von Standorten](high-availability-and-site-resilience-exchange-2013-help.md)
Verwaltung von Exchange-Arbeitsauslastungen
> [!NOTE]
> Weitere Informationen zu Funktionen in Vorgängerversionen von Exchange, die in Exchange Server 2013 entfernt, eingestellt oder ersetzt wurden, finden Sie unter <A href="what-s-discontinued-in-exchange-2013-exchange-2013-help.md">In Exchange 2013 nicht mehr unterstützte Funktionen</A>. Darüber hinaus sind die <A href="release-notes-for-exchange-2013-exchange-2013-help.md">Versionshinweise zu Exchange 2013</A> für Sie möglicherweise interessant.
## Exchange-Verwaltungskonsole
Exchange 2013 bietet eine zentrale vereinheitlichte und benutzerfreundliche Verwaltungskonsole, die für die Verwaltung von lokalen, Online- und Hybridbereitstellungen optimiert wurde. Die *Exchange-Verwaltungskonsole* in Exchange 2013 ersetzt die Exchange 2010-Verwaltungskonsole und die Exchange-Systemsteuerung (ECP). ("ECP" ist aber immer noch der Name des virtuellen Verzeichnisses, das von der Exchange-Verwaltungskonsole verwendet wird.) Zu den Funktionen der Exchange-Verwaltungskonsole zählen u. a.:
- **Listenansicht** Die Listenansicht der Exchange-Verwaltungskonsole weist wesentliche Einschränkungen der Exchange-Systemsteuerung nicht mehr auf. In der Exchange-Systemsteuerung konnten nur bis zu 500 Objekte angezeigt werden, und um Objekte anzuzeigen, die im Detailbereich nicht aufgeführt wurden, mussten Sie mithilfe von Such- und Filterfunktionen nach diesen Objekten suchen. In Exchange 2013 können in der Listenansicht der Exchange-Verwaltungskonsole gut 20.000 Objekte angezeigt werden. Nachdem die Exchange-Verwaltungskonsole die Ergebnisse zurückgegeben hat, führt der dazugehörige Client die Such- und Sortiervorgänge aus, wodurch im Vergleich zur Exchange-Systemsteuerung in Exchange 2010 deutliche Leistungsverbesserungen zu verzeichnen sind. Darüber hinaus können Sie die Ergebnisse seitenweise anzeigen. Sie können auch die Seitengröße konfigurieren und Daten in eine CSV-Datei exportieren.
- **Hinzufügen/Entfernen von Spalten in der Empfängerlistenansicht** Sie können festlegen, welche Spalten angezeigt werden sollen, und mithilfe lokaler Cookies können Sie Ihre benutzerdefinierten Listenansichten, über die Sie auf die Exchange-Verwaltungskonsole zugreifen, computerbezogen speichern.
- **Absichern des virtuellen Verzeichnisses der Exchange-Systemsteuerung** Sie können den Zugriff über das Internet und Intranets innerhalb des virtuellen IIS-Verzeichnisses der Exchange-Systemsteuerung partitionieren, um Verwaltungsfunktionen zuzulassen oder zu sperren. Mit dieser Funktion können Sie den Zugriff für Benutzer zulassen oder verweigern, die von außerhalb Ihrer Organisationsumgebung über das Internet auf die Exchange-Verwaltungskonsole zugreifen möchten. Gleichzeitig können Sie den Zugriff auf die Outlook Web App-Optionen eines Endbenutzers weiterhin zulassen.
- **Verwaltung öffentlicher Ordnern** In Exchange 2010 und Exchange 2007 wurden öffentliche Ordner über die Verwaltungskonsole für öffentliche Ordner verwaltet. Öffentliche Ordner befinden sich nun in der Exchange-Verwaltungskonsole, und Sie benötigen kein separates Tool mehr für deren Verwaltung.
- **Benachrichtigungen** In Exchange 2013 weist die Exchange-Verwaltungskonsole eine Benachrichtigungsanzeige auf, sodass Sie den Status lang dauernder Prozesse anzeigen können und, falls gewünscht, per E-Mail darüber benachrichtigt werden, sobald ein Prozess abgeschlossen ist.
- **Benutzereditor für die rollenbasierte Zugriffssteuerung** In Exchange 2010 konnte der Benutzereditor für die rollenbasierte Zugriffssteuerung in der Exchange Toolbox verwendet werden, um Benutzer zu Verwaltungsrollengruppen hinzuzufügen. In Exchange 2013 ist die Funktionalität des Benutzereditors für die rollenbasierte Zugriffssteuerung nun in die Exchange-Verwaltungskonsole integriert, sodass kein separates Tool zur Verwaltung der rollenbasierten Zugriffssteuerung erforderlich ist.
- **Unified Messaging-Tools** In Exchange 2010 konnten die Anrufstatistik und die Benutzeranrufprotokolle verwendet werden, um UM-Statistiken und -Informationen zu bestimmten Anrufen für einen UM-aktivierten Benutzer abzurufen. In Exchange 2013 sind die Anrufstatistik und die Benutzeranrufprotokolle nun in die Exchange-Verwaltungskonsole integriert, sodass kein separates Tool erforderlich ist, um diese Informationen zu verwalten.
- **Verbesserungen für Gruppen** In der Exchange-Verwaltungskonsole können nun im Fenster **Gruppen**, **Mitglieder auswählen** bis zu 10.000 Empfänger angezeigt werden. Standardmäßig werden bis zu 500 Empfänger zurückgegeben, wenn Sie das Fenster **Mitglieder auswählen** öffnen. Durch Klicken auf **Alle Ergebnisse abrufen** unter der Empfängerliste können Sie jedoch bis zu 10.000 Empfänger auflisten. Unterstützt wird nun auch das Durchsuchen von mehr als 500 Empfängern mithilfe der Bildlaufleiste. Außerdem bieten wir optimierte Suchfunktionen, mit deren Hilfe Sie die in der Empfängerliste enthaltenen Empfänger filtern können. Sie können filtern nach:
- Ort
- Firma
- Land/Region
- Abteilung
- Büro
- Titel
Weitere Informationen finden Sie unter [Exchange Admin Center in Exchange 2013](exchange-admin-center-in-exchange-2013-exchange-2013-help.md).
## Exchange 2013-Architektur
Vorgängerversionen von Exchange wurden gemäß der technischen Möglichkeiten zur jeweiligen Zeit entwickelt und optimiert. Während der Entwicklung von Exchange 2007 war beispielsweise die CPU-Leistung eine der wesentlichsten Einschränkungen. Zum Umgehen dieser Einschränkung wurde Exchange 2007 in verschiedene Serverrollen aufgeteilt, die eine horizontale Skalierung durch Servertrennung ermöglichten. Jedoch waren die Serverfunktionen in Exchange 2007 und Exchange 2010 eng gekoppelt. Die enge Kopplung der Rollen hatte mehrere Nachteile, z. B. Versionsabhängigkeit, geografische Affinität (alle Rollen muss sich an einem bestimmten Standort befinden), Sitzungsaffinität (ein teurer hardwaregestützter Layer 7-Lastenausgleich war erforderlich) und Namespacekomplexität.
Mittlerweile ist CPU-Leistung viel günstiger zu haben und kein einschränkender Faktor mehr. Nach dem Überwinden dieser Einschränkung war das primäre Entwicklungsziel für Exchange 2013 die Einfachheit von Skalierung, Hardwarenutzung und Fehlerisolierung. Für Exchange 2013 wurde die Anzahl der Serverrollen auf drei reduziert: Clientzugriff, Postfach und Edge-Transport.
Der Postfachserver umfasst alle traditionellen Serverkomponenten aus Exchange 2010: Clientzugriffsprotokolle, Transportdienst, Postfachdatenbanken und Unified Messaging. Der Postfachserver verarbeitet alle Vorgänge für die aktiven Postfächer auf diesem Server. Der Clientzugriffsserver bietet eine Authentifizierung, begrenzte Umleitung und Proxydienste. Der Clientzugriffsserver führt kein Datenrendering durch. Der Clientzugriffsserver ist ein zustandsloser Thin Server. Auf einem Clientzugriffsserver werden keine Daten gespeichert oder in Warteschlangen gestellt. Der Clientzugriffsserver bietet alle üblichen Clientzugriffsprotokolle: HTTP, POP und IMAP und SMTP.
Bei dieser neuen Architektur sind der Clientzugriffs- und der Postfachserver nur noch "lose gekoppelt". Verarbeitungsvorgänge und Aktivitäten für ein bestimmtes Postfach erfolgen auf dem Postfachserver, der die aktive Datenbankkopie hostet, in der sich das Postfach befindet. Alle Datenrender- und -transformationsvorgänge erfolgen lokal für die aktive Datenbankkopie, sodass Bedenken hinsichtlich der Versionskompatibilität zwischen Clientzugriffs- und Postfachserver aus dem Weg geräumt werden.
Mit Exchange 2013 Service Pack 1 haben wir erneut die Edge-Transport-Serverrolle eingeführt. Die Edge-Transport-Serverrolle wird normalerweise in Ihrem Umkreisnetzwerk außerhalb der internen Active Directory-Gesamtstruktur bereitgestellt und wurde entwickelt, um die Angriffsfläche Ihrer Exchange-Bereitstellung zu minimieren. Durch die Verarbeitung des gesamten E-Mail-Flusses in das Internet werden außerdem weitere Nachrichtenschutz- und Sicherheitsebenen gegen Viren und Spam hinzugefügt, und es können Transportregeln zum Steuern des Nachrichtenflusses angewendet werden. Weitere Informationen zur Serverrolle **Edge-Transport** finden Sie unter [Edge-Transport-Server](edge-transport-servers-exchange-2013-help.md).
Die Exchange 2013-Architektur bietet die folgenden Vorzüge:
- **Flexibilität beim Versionsupgrade** Keine starren Upgradeanforderungen mehr. Ein Upgrade eines Clientzugriffsservers kann unabhängig und in beliebiger Reihenfolge in Relation zum Postfachserver stattfinden.
- **Sitzungsindifferenz** Bei Exchange 2010 war für mehrere Protokolle Sitzungsaffinität zur Clientzugriffsserver-Rolle erforderlich. In Exchange 2013 befinden sich die Clientzugriffs- und Postfachkomponenten auf demselben Postfachserver. Da der Clientzugriffsserver alle Verbindungen eines Benutzers per Proxy an einen bestimmten Postfachserver weiterleitet, ist auf den Clientzugriffsservern keine Sitzungsaffinität erforderlich. Dadurch kann für eingehende Verbindungen für Clientzugriffsserver ein Lastenausgleich mithilfe von Methoden wie "Geringste Anzahl von Verbindungen" oder "Round-Robin" erfolgen.
- **Einfachheit der Bereitstellung** Bei einem Exchange 2010-Entwurf für ausfallsichere Standorte benötigten Sie bis zu acht verschiedene Namespaces: zwei Internet Protocol-Namespaces, zwei für Outlook Web App-Fallback, einen für die AutoErmittlung, zwei für den RPC-Clientzugriff und einen für SMTP. Für ein Upgrade von Exchange 2003 oder Exchange 2007 war zudem ein Legacynamespace erforderlich. Bei Exchange 2013 sinkt die Mindestanzahl von Namespaces auf zwei. Bei einer Koexistenzlösung mit Exchange 2007 müssen Sie dennoch einen Legacyhostnamen erstellen. Doch bei einer Koexistenzlösung mit Exchange 2010 oder Installation einer neuen Exchange 2013-Organisation benötigen Sie nur zwei Namespaces: einen für Clientprotokolle und einen für die AutoErmittlung. Möglicherweise benötigen Sie auch einen SMTP-Namespace.
Aufgrund dieser Architekturänderungen gab es Änderungen in Bezug auf die Clientkonnektivität. Erstens wird RPC nicht länger als Protokoll für den Direktzugriff unterstützt. Dies bedeutet, dass sämtliche Outlook-Verbindungen mithilfe von RPC über HTTP (auch als Outlook Anywhere bekannt) erfolgen müssen. Auf den ersten Blick scheint dies eine Einschränkung zu sein, doch tatsächlich ergeben sich einige zusätzliche Vorteile. Der offenkundigste Vorteil ist, dass der RPC-Clientzugriffsdienst sich nicht auf dem Clientzugriffsserver befinden muss. Dies resultiert zu einer Verringerung um zwei Namespaces, die normalerweise für eine ausfallsichere Lösung für Standorte erforderlich wären. Darüber hinaus muss keine Affinität mehr für den RPC-Clientzugriffsdienst bereitgestellt werden.
Zweitens greifen Outlook-Clients nicht mehr wie in allen Vorversionen von Exchange auf den vollqualifizierten Domänennamen (FQDN) eines Servers zu. Outlook verwendet die AutoErmittung zum Erstellen eines neuen Verbindungspunkts, der aus einer Postfach-GUID, dem Symbol "@" und dem Domänenteil der primären SMTP-Adresse des Benutzers besteht. Diese einfache Änderung führt zu einer fast vollständigen Einstellung der unwillkommenen Nachricht "Ihr Administrator hat eine Änderung an Ihrem Postfach vorgenommen. Bitte starten Sie neu." Nur Outlook 2007 und höhere Versionen werden von Exchange 2013 unterstützt.
Das Modell für Hochverfügbarkeit der Postfachkomponente hat sich seit Exchange 2010 nicht wesentlich geändert. Die Einheit für Hochverfügbarkeit ist weiter die Database Availability Group (DAG). Für die DAG wird immer noch Windows Server-Failoverclustering verwendet. Für die fortlaufende Replikation werden weiter sowohl die Dateimodus- als auch die Blockmodusreplikation unterstützt. Jedoch gibt es einige Verbesserungen. Failoverzeiten wurden verkürzt, und zwar als Ergebnis von verbessertem Transaktionsprotokollcode und umfassender Überprüfungen der passiven Datenbanken. Der Exchange-Speicherdienst wurde in verwaltetem Code neu geschrieben (siehe den Abschnitt "Verwalteter Speicher" weiter unten in diesem Kapitel). Jede Datenbank wird nun in einem eigenen Prozess ausgeführt, was die Isolierung von Speicherproblemen auf eine einzelne Datenbank ermöglicht.
## Verwalteter Speicher
In Exchange 2013 ist *Verwalteter Speicher* der Name der neu gestalteten Informationsspeicherprozesse ("Microsoft.Exchange.Store.Service.exe" und "Microsoft.Exchange.Store.Worker.exe"). Der neue verwaltete Speicher ist in C\# geschrieben und eng in den Microsoft Exchange-Replikationsdienst (MSExchangeRepl.exe) integriert, um eine verbesserte Resilienz und damit eine höhere Verfügbarkeit bereitzustellen. Darüber hinaus ermöglicht die Architektur des verwalteten Speichers eine präzisere Verwaltung der Ressourcennutzung und schnellere Ursachenanalyse durch eine verbesserte Diagnose.
Der verwaltete Speicher arbeitet mit dem Microsoft Exchange-Replikationsdienst bei der Verwaltung von Postfachdatenbanken zusammen, für die weiterhin ESE (Extensible Storage Engine) als Datenbankmodul verwendet wird. Exchange 2013 weist wesentliche Änderungen am Schema von Postfachdatenbanken auf, die im Vergleich zu früheren Exchange-Versionen viele Optimierungen bieten. Zusätzlich zu diesen Änderungen ist der Microsoft Exchange-Replikationsdienst für die Verfügbarkeit sämtlicher Dienste für Postfachserver zuständig. Aufgrund der Architekturänderungen sind ein schnelleres Datenbankfailover und ein besserer Umgang mit dem Ausfall physischer Datenträger möglich.
Der verwaltete Speicher ist außerdem mit dem Search Foundation-Suchmodul integriert (das auch von SharePoint 2013 verwendet wird), um im Vergleich zur Microsoft-Suche in früheren Versionen von Exchange zuverlässigere Indizierungs- und Suchfunktionen zu bieten.
Weitere Informationen finden Sie unter [Hohe Verfügbarkeit und Ausfallsicherheit von Standorten](high-availability-and-site-resilience-exchange-2013-help.md).
## Zertifikatverwaltung
Das Verwalten digitaler Zertifikate ist eine der wichtigsten Aufgaben in Bezug auf Sicherheit in Ihrer Exchange-Organisation. Die Sicherstellung, dass Zertifikate ordnungsgemäß konfiguriert sind, ist der Schlüssel zu einer sicheren Messaginginfrastruktur für das Unternehmen. In Exchange 2010 war die Exchange-Verwaltungskonsole das Hauptinstrument zum Verwalten von Zertifikaten. In Exchange 2013 erfolgt die Zertifikatverwaltung auch mithilfe der neu gestalteten Exchange 2013-Verwaltungskonsole für Administratoren.
Die Vorgaben für Exchange 2013 in Bezug auf Zertifikate waren schwerpunktmäßig die Minimierung der Anzahl von Zertifikaten, die ein Administrator verwalten muss, und der Interaktion des Administrators mit Zertifikaten sowie das Ermöglichen einer zentralen Zertifikatverwaltung. Aus den Änderungen bei der Zertifikatverwaltung ergeben sich die folgenden Vorteile:
- Die Zertifikatverwaltung kann auf dem Clientzugriffs- oder Postfachserver erfolgen. Für den Postfachserver ist standardmäßig ein selbstsigniertes Zertifikat installiert. Der Clientzugriffsserver vertraut dem selbstsignierten Zertifikat auf dem Exchange 2013-Postfachserver automatisch, weshalb Clients keine Warnungen zu einem selbstsignierten Zertifikat erhalten, dem nicht vertraut wird. Voraussetzung ist allerdings, dass der Exchange 2013-Clientzugriffsserver über ein nicht selbstsigniertes Zertifikat von entweder einer Windows-Zertifizierungsstelle oder einem vertrauenswürdigen Drittanbieter verfügt.
- In früheren Exchange-Versionen war es schwierig zu erkennen, wann sich ein digitales Zertifikat dem Ablauf näherte. In Exchange 2013 zeigt das Benachrichtigungscenter Warnungen an, wenn ein auf einem Server mit Exchange 2013 gespeichertes Zertifikat vor dem Ablauf steht. Administratoren können diese Benachrichtigungen wahlweise auch per E-Mail erhalten.
Weitere Informationen finden Sie unter [Digitale Zertifikate und SSL](digital-certificates-and-ssl-exchange-2013-help.md).
## Setup
Setup wurde komplett neu gestaltet, sodass das Installieren von Exchange 2013 und Sicherstellen, dass Sie über die neuesten Produktrollups und Sicherheitsfixes verfügen, nun einfacher als je zuvor ist. Hier einige der Verbesserungen, die wir vorgenommen haben:
- **Setup greift stets auf aktuelle Informationen zu** Wenn Sie den Setup-Assistenten ausführen, können Sie die neuesten Produktrollups, Sicherheitsfixes und Sprachpakete herunterladen und nutzen. Über diese Option werden nicht nur die Dateien aktualisiert, die zum Ausführen von Exchange dienen, sondern Setup selbst kann aktualisiert werden. Auf diese Weise können wir Setup im Anschluss an die Produktveröffentlichung weiter verbessern und Überprüfungen der Bereitschaft aktualisieren, sobald Anforderungen aktualisiert oder geändert werden.
Wenn Sie den unbeaufsichtigten Setupmodus verwenden, können Updates nicht automatisch heruntergeladen werden. Sie können dennoch weiter in den Genuss der Ausführung der neuesten Version von Setup kommen, indem Sie die neuesten Updates vorher herunterladen und den Parameter `/UpdatesDir: <path>` angeben, damit Setup sich vor Beginn des Installationsvorgangs selbst aktualisiert.
- **Verbesserte Überprüfungen der Bereitschaft** Überprüfungen der Bereitschaft stellen sicher, dass Ihr Computer und Ihre Organisation für Exchange 2013 bereit sind. Nachdem Sie Setup die benötigten Informationen zu Ihrer Installation bereitgestellt haben, werden die Überprüfungen der Bereitschaft vor Beginn der Installation ausgeführt. Das neue Modul für Überprüfungen der Bereitschaft durchläuft nun sämtliche Überprüfungen, bevor Ihnen gemeldet wird, welche Aktionen Sie durchführen müssen, damit Setup fortgesetzt werden kann. Dieser Vorgang erfolgt so schnell wie nie zuvor. Wie bei Vorgängerversionen von Exchange können Sie Setup auffordern, die hierfür benötigten Windows-Funktionen zu installieren, damit Sie dies nicht manuell ausführen müssen.
- **Vereinfachter und moderner Assistent** Wir haben sämtliche Schritte im Setup-Assistenten entfernt, die für die Installation von Exchange nicht unbedingt erforderlich sind. Übrig geblieben ist ein einfach zu durchlaufender Assistent, der Sie nacheinander durch alle Schritte des Installationsprozesses begleitet.
Weitere Informationen finden Sie unter [Planung und Bereitstellung](planning-and-deployment-for-exchange-2013-installation-instructions.md).
## Messagingrichtlinie und -kompatibilität
Es gibt zwei neue Nachrichtenrichtlinien- und Kompatibilitätsfeatures in Exchange 2013: Verhinderung von Datenverlust und Microsoft Rights Management-Verbindungsdienst
DLP-Funktionen zur *Verhinderung von Datenverlust* helfen Ihnen dabei, Ihre vertraulichen Daten zu schützen und Benutzer über interne Richtlinien und Vorschriften zu informieren. Mit DLP können Sie in Ihrer Organisation verhindern, dass Benutzer versehentlich vertrauliche Informationen an nicht autorisierte Personen senden. DLP ermöglicht Ihnen das Bestimmen, Überwachen und Schützen vertraulicher Daten mittels einer eingehenden Inhaltsanalyse.Exchange 2013 bietet vordefinierte DLP-Richtlinien basierend auf diversen Bestimmungen wie beispielsweise PII (persönlich identifizierbare Informationen) und PCI-DSS (Payment Card Industry Data Security Standard) und kann erweitert werden, um weitere für Ihr Unternehmen wichtige Richtlinien zu unterstützen. Darüber hinaus ermöglicht die neue Funktion der Richtlinientipps in Outlook 2013 Ihnen, Ihre Benutzer über mögliche Richtlinienverletzungen zu informieren, bevor vertrauliche Daten gesendet werden.
Der Microsoft Rights Management-Verbindungsdienst (RMS-Verbindungsdienst) ist eine optionale Anwendung, die den Datenschutz für Ihren Exchange 2013-Server mithilfe von cloudbasierten Rechteverwaltungsdiensten (Microsoft Rights Management-Diensten) verbessert. Nachdem Sie den RMS-Verbindungsdienst installiert haben, bietet er kontinuierlichen Datenschutz während der gesamten Lebensspanne der Informationen. Da diese Dienste anpassbar sind, können Sie das gewünschte Sicherheitsniveau festlegen. Sie können beispielsweise den E-Mail-Nachrichtenzugriff auf bestimmte Benutzer beschränken oder für bestimmte Nachrichten nur Leserechte festlegen.
Hier erfahren Sie mehr über diese Funktionen:
[Verhinderung von Datenverlust](technical-overview-of-dlp-data-loss-prevention-in-exchange.md)
[Rights Management-Verbindungsdienst](https://go.microsoft.com/fwlink/p/?linkid=330432)
## Compliance-Archivierung, Aufbewahrung und eDiscovery
Exchange 2013 bietet die folgenden Verbesserungen für Compliance-Archivierung, Aufbewahrung und eDiscovery, damit Ihre Organisation ihre Anforderungen an die Richtlinientreue besser erfüllen kann:
- **Compliance-Archiv** Ein neues einheitliches Archivmodell, mit dessen Hilfe Sie gesetzliche Archivierungsvorschriften in den folgenden Szenarien erfüllen können:
- Aufbewahren der Ergebnisse der Abfrage (abfragebasierte Aufbewahrung), wodurch eine bereichsbasierte Unveränderbarkeit postfachübergreifend ermöglicht wird.
- Definieren einer zeitbasierten Aufbewahrung (Sie können beispielsweise alle Elemente in einem Postfach sieben Jahre aufbewahren. Für dieses Szenario mussten in Exchange 2010 die Funktionen "Wiederherstellung einzelner Elemente/Aufbewahrungszeit für gelöschte Elemente" verwendet werden).
- Dauerhaftes Platzieren eines Postfachs in einem Archiv (ähnlich dem Beweissicherungsverfahren in Exchange 2010).
- Platzieren eines Benutzerpostfachs in mehreren Archiven, um die Anforderungen verschiedener Untersuchungen zu erfüllen.
- **Compliance-eDiscovery** Compliance-eDiscovery ermöglicht autorisierten Benutzern das Durchsuchen von Postfachdaten in sämtlichen Postfächern und Compliance-Archiven einer Exchange 2013-Organisation und das Kopieren von Nachrichten zur Überprüfung in ein Discoverypostfach. In Exchange 2013 wurde Compliance-eDiscovery verbessert, um zuständigen Mitarbeitern effizientere Such- und Archivierungsvorgänge zu ermöglichen. Diese Verbesserungen umfassen:
- Über eine **Sammelsuche** können Daten in mehreren Datenspeichern durchsucht und beibehalten werden. In Exchange 2013 können Sie Compliance-eDiscovery-Suchen übergreifend in Exchange, SharePoint 2013 und Lync 2013 durchführen. Im eDiscovery Center in SharePoint 2013 können Sie Compliance-eDiscovery-Such- und Archivierungsvorgänge durchführen.
- Ein **abfragebasiertes Compliance-Archiv** ermöglicht das Speichern der Ergebnisse der Abfrage, wodurch eine bereichsbasierte Unveränderbarkeit postfachübergreifend ermöglicht wird.
- **Export von Suchergebnissen** Discoverymanager können über die SharePoint 2013-eDiscovery-Konsole Postfachinhalte in eine PST-Datei exportieren. Cmdlets für das Anfordern des Exports von Postfächern sind nicht mehr erforderlich, um ein Postfach in eine PST-Datei zu exportieren.
- **Schlüsselwortstatistik** Suchstatistiken werden suchbegriffsbezogen bereitgestellt. Dadurch kann ein Discoverymanager schnell intelligente Entscheidungen zur weiteren Optimierung der Suchabfrage treffen, um bessere Ergebnisse zu erzielen. eDiscovery-Suchergebnisse werden nach Relevanz sortiert.
- **KQL-Syntax** Discoverymanager können in Suchabfragen KQL-Syntax (Keyword Query Language) verwenden. KQL ähnelt AQS (Advanced Query Syntax), die für Discoverysuchvorgänge in Exchange 2010 verwendet wurde.
- **Assistent für Compliance-eDiscovery und -Archiv** Discoverymanager können mit diesem neuen Assistenten Compliance-eDiscovery- und -Archiv-Vorgänge durchführen.
> [!NOTE]
> Wenn SharePoint 2013 nicht verfügbar ist, steht in der Exchange-Verwaltungskonsole eine eingeschränkte eDiscovery-Funktionalität zur Verfügung.
- **Durchsuchen aller primären und Archivpostfächer in Outlook Web App** Benutzer können in Outlook Web App alle ihre primären und Archivpostfächer durchsuchen. Zwei getrennte Suchvorgänge sind nicht mehr notwendig.
- **Archivieren von Lync-Inhalten** Exchange 2013 unterstützt die Archivierung von Lync 2013-Inhalten in einem Benutzerpostfach. Sie können mithilfe der Funktion "Compliance-Archiv" Lync-Inhalte in Archivpostfächern platzieren und mit der Funktion "Compliance-eDiscovery" in Exchange archivierte Lync-Inhalte durchsuchen.
- **Aufbewahrungsrichtlinien** Mithilfe von Aufbewahrungsrichtlinien kann Ihre Organisation Risiken im Zusammenhang mit E-Mail und anderen Kommunikationsmitteln verringern und E-Mail-Aufbewahrungsanforderungen erfüllen. Die Aufbewahrungsrichtlinien wurden in folgenden Bereichen verbessert:
- **Unterstützung von Aufbewahrungstags für "Kalender" und "Aufgaben"** Sie können Aufbewahrungsrichtlinientags für die Standardordner "Kalender" und "Aufgaben" erstellen, damit Elemente in diesen Ordnern ablaufen. Elemente in diesen Ordnern werden außerdem basierend auf den für das Postfach geltenden Archivrichtlinieneinstellungen in das Archiv des Benutzers verschoben.
- **Optimierte Fähigkeit zur Aufbewahrung von Elementen für einen angegebenen Zeitraum** Sie können mithilfe einer Aufbewahrungsrichtlinie und eines zeitbasierten Compliance-Archivs die Aufbewahrung von Elementen für einen festgelegten Zeitraum erzwingen.
Weitere Informationen finden Sie unter [Messagingrichtlinie und -kompatibilität](messaging-policy-and-compliance-exchange-2013-help.md).
## Transportregeln
Transportregeln in Exchange Server 2013 sind eine Weiterentwicklung der in Exchange Server 2010 verfügbaren Funktionen. Es sind jedoch einige Verbesserungen an den Transportregeln in Exchange 2013 erfolgt. Die wichtigste Änderung ist die Unterstützung der Verhinderung von Datenverlust (Data Loss Prevention, DLP). Ferner sind neue Prädikate und Aktionen sowie eine verbesserte Überwachung verfügbar und einige Architekturänderungen erfolgt.
Ausführliche Informationen finden Sie unter [Neuerungen bei Transportregeln](what-s-new-for-transport-rules-exchange-2013-help.md).
## Verwaltung von Informationsrechten
Information Rights Management (IRM) ist kompatibel mit dem Kryptografiemodus 2, einem AD RMS-Kryptografiemodus (Active Directory Rights Management), der eine stärkere Verschlüsselung unterstützt und Ihnen die Verwendung von 2048-Bit-Schlüsseln für RSA und 256-Bit-Schlüsseln für SHA-1 ermöglicht. Darüber hinaus ermöglicht der Kryptografiemodus 2 die Verwendung des SHA-2-Hashalgorithmus. Weitere Informationen zu Kryptografiemodi in AD RMS finden Sie unter [AD RMS-Kryptografiemodi](https://go.microsoft.com/fwlink/p/?linkid=263219).
## Überwachung
Exchange 2013 bietet die folgenden Verbesserungen an der Überwachung:
- **Überwachungsberichte** Die Exchange-Verwaltungskonsole bietet Überwachungsfunktionen, sodass Sie Berichte erstellen oder Einträge aus dem Postfachüberwachungsprotokoll oder Administratorüberwachungsprotokoll exportieren können. Im Postfachüberwachungsprotokoll werden alle Postfachzugriffe erfasst, die von Personen vorgenommen werden, bei denen es sich nicht um den Besitzer des Postfachs handelt. Dadurch können Sie ermitteln, wer auf ein Postfach zugegriffen hat und welche Aktionen ausgeführt wurden. Im Administratorüberwachungsprotokoll werden (auf der Grundlage eines Exchange Verwaltungsshell-Cmdlets) alle Aktionen aufgezeichnet, die von einem Administrator ausgeführt wurden. Diese Informationen können Sie zum Behandeln von Konfigurationsproblemen sowie zum Ermitteln der Ursache von Sicherheits- oder Richtlinientreueproblemen heranziehen. Weitere Informationen finden Sie unter [Exchange-Überwachungsberichte](exchange-auditing-reports-exchange-2013-help.md).
- **Anzeigen des Administratorüberwachungsprotokolls** Anstatt das Administratorüberwachungsprotokoll zu exportieren, dessen Empfang in einer E-Mail-Nachricht bis zu 24 Stunden dauern kann, können Sie Einträge im Administratorüberwachungsprotokoll in der Exchange-Verwaltungskonsole anzeigen. Wählen Sie **Verwaltung der Richtlinientreue** \> **Überwachung** aus, und klicken Sie anschließend auf **Administratorüberwachungsprotokoll anzeigen**. Es können bis zu 1.000 Einträge auf mehreren Seiten angezeigt werden. Um die Suche einzuschränken, können Sie einen Datumsbereich angeben. Weitere Informationen finden Sie unter [Anzeigen des Administratorüberwachungsprotokolls](view-the-administrator-audit-log-exchange-2013-help.md).
## Schutz vor Schadsoftware
Die integrierten Filterfunktionen für Schadsoftware in Exchange 2013 dienen zum Schutz Ihres Netzwerks vor Schadsoftware, die durch E-Mail-Nachrichten übertragen wird. Alle von Ihrem Server mit Exchange gesendeten und empfangenen Nachrichten werden auf Schadsoftware (Viren und Spyware) überprüft. Sobald Schadsoftware erkannt wird, wird die Nachricht gelöscht. Wenn eine infizierte Nachricht gelöscht und nicht übermittelt wird, können auch Benachrichtigungen an Absender oder Administratoren gesendet werden. Sie können auch infizierte Anlagen durch entweder Standard- oder benutzerdefinierte Nachrichten ersetzen, die die Empfänger über erkannte Schadsoftware informieren.
Weitere Informationen zum Schutz vor Schadsoftware finden Sie unter [Antischadsoftwareschutz](anti-malware-protection-exchange-2013-help.md).
## Nachrichtenübermittlung
Exchange 2013 weist wesentliche Änderungen hinsichtlich der Übermittlung von Nachrichten durch eine Organisation und ihrer Verarbeitung auf. Es folgt eine kurze Übersicht der Änderungen:
- **Transportpipeline** An der Transportpipeline in Exchange 2013 sind nun mehrere Dienste beteiligt: der Front-End-Transport-Dienst auf Clientzugriffsservern, der Transportdienst auf Postfachservern und der Postfachtransportdienst auf Postfachservern. Weitere Informationen finden Sie unter [Nachrichtenübermittlung](mail-flow-exchange-2013-help.md).
- **Routing** Beim Routing von E-Mail in Exchange 2013 werden DAG-Grenzen und Active Directory-Standortgrenzen erkannt. Darüber hinaus wurde das E-Mail-Routing so verbessert, dass Nachrichten für interne Empfänger direkter in Warteschlangen abgelegt werden. Weitere Informationen finden Sie unter [E-Mail-Routing](mail-routing-exchange-2013-help.md).
- **Connectors** Die standardmäßige maximale Nachrichtengröße für einen Sende- oder Empfangsconnector gemäß dem Parameter *MaxMessageSize* wurde von 10 MB auf 25 MB erhöht. Weitere Informationen zum Festlegen von Parametern für einen Connector finden Sie unter [Set-SendConnector](https://technet.microsoft.com/de-de/library/aa998294\(v=exchg.150\)) und [Set-ReceiveConnector](https://technet.microsoft.com/de-de/library/bb125140\(v=exchg.150\)).
Sie können mithilfe des Parameters *FrontEndProxyEnabled* des Cmdlets **Set-SendConnector** einen Sendeconnector im Transportdienst eines Postfachservers auf das Routing von ausgehender E-Mail durch einen Front-End-Transportserver am lokalen Active Directory-Standort festlegen. Dadurch können Sie bestimmen, wie das Routing von E-Mail durch den Transportdienst erfolgt.
- **Edge-Transport** Sie können optional einen Edge-Transport-Server in Ihrem Umkreisnetzwerk installieren, um die Angriffsfläche zu verkleinern und Nachrichtenschutz und -sicherheit zu bieten. Weitere Informationen finden Sie unter [Edge-Transport-Server](edge-transport-servers-exchange-2013-help.md).
## Empfänger
In diesem Abschnitt werden die Verbesserungen bei der Verwaltung von Empfängern in Exchange 2013 beschrieben:
- **Gruppenbenennungsrichtlinie** Administratoren können nun in der Exchange-Verwaltungskonsole eine *Gruppenbenennungsrichtlinie* erstellen, mit deren Hilfe Sie die Namen von Verteilergruppen standardisieren und verwalten können, die von Benutzern in Ihrer Organisation erstellt werden. Sie können festlegen, dass dem Namen der Verteilergruppe bei der Erstellung ein bestimmtes Präfix und Suffix hinzugefügt werden muss, und Sie können die Verwendung bestimmter Wörter unterbinden. Dadurch können Sie die Verwendung ungeeigneter Wörter in Gruppennamen eindämmen.
Weitere Informationen finden Sie unter [Erstellen einer Benennungsrichtlinie für Verteilergruppen](create-a-distribution-group-naming-policy-exchange-2013-help.md).
- **Nachrichtenverfolgung** Administratoren können in der Exchange-Verwaltungskonsole auch Zustellungsoptionen für E-Mail-Nachrichten nachverfolgen, die von Benutzern in Ihrer Organisation gesendet oder empfangen werden. Sie wählen nur ein Postfach aus und suchen dann nach Nachrichten, die an einen anderen Benutzer gesendet oder von diesem empfangen wurden. Sie können die Suche eingrenzen, indem Sie in der Betreffzeile nach bestimmten Wörtern suchen. Im sich ergebenden Zustellungsbericht wird eine Nachricht während des Zustellungsprozesses nachverfolgt und angegeben, ob die Nachricht erfolgreich zugestellt wurde, ob die Zustellung noch aussteht oder ob sie nicht zugestellt wurde.
Weitere Informationen finden Sie unter [Nachverfolgen von Nachrichten mit Zustellungsberichten](track-messages-with-delivery-reports-exchange-2013-help.md).
## Freigabe und Zusammenarbeit
In diesem Abschnitt werden die Verbesserungen bei Freigabe und Zusammenarbeit in Exchange 2013 beschrieben.
- **Öffentliche Ordner** Öffentliche Ordner kommen nun in den Genuss der vorhandenen Hochverfügbarkeits- und Speichertechnologien des Postfachspeichers. Die Architektur für öffentliche Ordner verwendet speziell entworfene Postfächer, um sowohl die Hierarchie als auch die Inhalte öffentlicher Ordner zu speichern. Dieser neue Entwurf bedeutet auch, dass es keine Öffentliche Ordner-Datenbank mehr gibt. Für die Replikation öffentlicher Ordner wird jetzt das Modell der fortlaufenden Replikation eingesetzt. Hochverfügbarkeit für die Hierarchie- und Inhaltspostfächer wird von der DAG bereitgestellt. Durch diesen Entwurf erfolgt ein Wechsel weg von einem Multimaster- hin zu einem Einzelmasterreplikationsmodell.
Outlook Web App-Benutzer in Ihrer Organisation haben jetzt die Möglichkeit, öffentliche Ordner zu ihren Favoriten hinzuzufügen oder aus ihren Favoriten zu entfernen. Zuvor konnte dies nur in Outlook durchgeführt werden.
Weitere Informationen finden Sie unter [Öffentliche Ordner](public-folders-exchange-2013-help.md).
- **Websitepostfächer** E-Mails und Dokumente werden herkömmlicherweise in zwei voneinander getrennten Datenrepositorys gespeichert. Die meisten Teams verwenden bei der Zusammenarbeit normalerweise beide Medien. Die Herausforderung liegt darin, dass auf E-Mails und Dokumente mit unterschiedlichen Clients zugegriffen wird. Dies reduziert üblicherweise sowohl die Benutzerfreundlichkeit als auch die Benutzerproduktivität.
Das *Websitepostfach* ist ein neues Konzept in Exchange 2013, mit dem diese Probleme gelöst werden sollen. Websitepostfächer verbessern die Zusammenarbeit und Benutzerproduktivität, indem sie den Zugriff auf SharePoint-Websitedokumente und E-Mail-Nachrichten in Outlook 2013 über die gleiche Clientbenutzeroberfläche ermöglichen. Ein Websitepostfach besteht funktional aus der Mitgliedschaft in einer SharePoint-Website (Besitzer und Mitglieder), gemeinsam genutztem Speicher in einem Exchange-Postfach für E-Mail-Nachrichten und einer SharePoint-Website für Dokumente sowie einer Verwaltungsoberfläche für Bereitstellungs- und Lebenszyklusanforderungen.
Weitere Informationen finden Sie unter [Websitepostfächer](site-mailboxes-exchange-2013-help.md).
- **Freigegebene Postfächer** In Vorgängerversionen von Exchange mussten zum Erstellen eines freigegebenen Postfachs mehrere Schritte ausgeführt werden, wobei Stellvertretungsberechtigungen über die Exchange-Verwaltungsshell festgelegt wurden. In Exchange 2013 können Sie nun in der Exchange-Verwaltungskonsole ein freigegebenes Postfach erstellen. Navigieren Sie in der Exchange-Verwaltungskonsole zu **Empfänger** \> **Freigegebene Postfächer**, um ein freigegebenes Postfach zu erstellen. Ein freigegebenes Postfach ist nun ein Empfängertyp, weshalb Sie auf der Benutzeroberfläche oder über die Shell ganz einfach nach freigegebenen Postfächern suchen können.
Weitere Informationen finden Sie unter [Freigegebene Postfächer](shared-mailboxes-exchange-2013-help.md).
## Integration in SharePoint und Lync
Exchange 2013 bietet eine bessere Integration mit SharePoint 2013 und Lync 2013. Vorteile dieser verbesserten Integration sind u. a.:
- Exchange 2013 ist mit SharePoint 2013 integriert, damit Benutzer mithilfe von Websitepostfächern effektiver zusammenarbeiten können.
- Lync Server 2013 ermöglicht die Archivierung von Inhalten in Exchange 2013 und Nutzung von Exchange 2013 als Kontaktspeicher.
- Discoverymanager können Compliance-eDiscovery- und Compliance-Archiv-Suchvorgänge auf sämtliche Daten in SharePoint 2013, Exchange 2013 und Lync 2013 anwenden.
- Die Oauth-Authentifizierung ermöglicht Anwendungen von Partnern die Authentifizierung als Dienst oder bei Bedarf das Annehmen der Identität von Benutzern.
Weitere Informationen finden Sie unter [Integration in SharePoint und Lync](integration-with-sharepoint-and-lync-exchange-2013-help.md).
## Clients und mobile Funktionen
Die Outlook Web App-Benutzeroberfläche ist neu und für Tablets und Smartphones sowie für Desktop- und Laptopcomputer optimiert. Zu den neuen Funktionen gehören Apps für Outlook, die Benutzern und Administratoren die Erweiterung der Funktionsmöglichkeiten von Outlook Web App erlauben: die Verknüpfung von Kontakten, die Möglichkeit für Benutzer, Kontakte aus ihre LinkedIn-Konten hinzuzufügen, und Aktualisierungen des Aussehens und der Funktionen des Kalenders.
Weitere Informationen finden Sie unter [Neuerungen bei Outlook Web App in Exchange 2013](what-s-new-for-outlook-web-app-in-exchange-2013-exchange-2013-help.md).
## Unified Messaging
Unified Messaging in Exchange 2013 bietet im Wesentlichen dieselben Voicemailfunktionen wie Exchange 2010. Diese vorhandenen Funktionen wurden jedoch durch einige neue und weiterentwickelte Funktionen ergänzt. Wichtiger ist der Hinweis, dass Architekturänderungen an Exchange 2013 Unified Messaging zu Komponenten, Diensten und Funktionalität geführt haben, die von der Unified Messaging-Serverrolle in Exchange 2010 geboten wurden und nun in Exchange 2013 auf die Clientzugriffs- und Postfachserverrolle aufgeteilt sind.
Weitere Informationen finden Sie unter [Neues in Exchange 2013 Unified Messaging](what-s-new-for-unified-messaging-in-exchange-2013-exchange-2013-help.md).
## Batchverschiebungen von Postfächern
In Exchange 2013 wurde das Konzept von Batchverschiebungen eingeführt. Die neue Verschiebungsarchitektur basiert auf der des Postfachreplikationsdiensts und bietet verbesserte Verwaltungsfunktionen. Die neue Architektur für Batchverschiebungen weist die folgenden Verbesserungen auf:
- Möglichkeit, mehrere Postfächer in großen Batches zu verschieben.
- E-Mail-Benachrichtigung bei Verschiebung mit Berichterstellung.
- Automatische Wiederholung und automatische Priorisierung von Verschiebungen.
- Primäre und persönliche Archivpostfächer können zusammen oder einzeln verschoben werden.
- Option zum manuellen Abschließen der Verschiebungsanforderung, sodass Sie eine Verschiebung überprüfen können, ehe Sie sie abschließen.
- Regelmäßige inkrementelle Synchronisierungen zum Migrieren der Änderungen.
Weitere Informationen finden Sie unter [Verwalten von lokalen Verschiebungen](manage-on-premises-moves-exchange-2013-help.md).
## Hohe Verfügbarkeit und Ausfallsicherheit von Standorten
Exchange 2013 verwendet DAGs, Postfachdatenbankkopien und weitere Funktionen, wie z. B. die Wiederherstellung einzelner Elemente, Aufbewahrungsrichtlinien und verzögerte Datenbankkopien, um Hochverfügbarkeit, Ausfallsicherheit für Standorte und einen systemeigenen Exchange-Datenschutz bereitzustellen. Sowohl die Hochverfügbarkeitsplattform als auch der Exchange-Informationsspeicher und das ESE-Modul (Extensible Storage Engine) wurden erweitert und bieten mehr Verfügbarkeit, eine vereinfachte Verwaltung und die Möglichkeit zur Kosteneinsparung. Diese Verbesserungen umfassen:
- **Verwaltete Verfügbarkeit** Bei der verwalteten Verfügbarkeit werden eine interne Überwachung und wiederherstellungsorientierte Funktionen eng miteinander verzahnt, um Ausfälle zu vermeiden, Dienste proaktiv wiederherzustellen, ein Serverfailover automatisch einzuleiten oder den Administrator zu benachrichtigen, damit dieser entsprechende Maßnahmen ergreift. Der Schwerpunkt liegt eher auf der Überwachung und Verbesserung des Endbenutzererlebnisses als darauf, nur den Betrieb von Servern und Komponenten sicherzustellen, damit die Dienste ohne Unterbrechung verfügbar sind.
- **Verwalteter Speicher** Als verwalteter Speicher werden die neu gestalteten Informationsspeicherprozesse in Exchange 2013 bezeichnet. Der neue verwaltete Speicher ist in C\# geschrieben und eng in den Microsoft Exchange-Replikationsdienst (MSExchangeRepl.exe) integriert, um eine verbesserte Resilienz und damit eine höhere Verfügbarkeit bereitzustellen.
- **Unterstützung für mehrere Datenbanken pro Datenträger** Exchange 2013 bietet Verbesserungen, die Ihnen die Unterstützung mehrerer Datenbanken (eine Kombination aus aktiven und passiven Kopien) auf demselben Datenträger ermöglichen, wodurch größere Datenträger in Bezug auf Kapazität und E/A pro Sekunde effizienter genutzt werden können.
- **Automatisches erneutes Seeding** Ermöglicht das schnelle Wiederherstellen von Datenbankredundanz nach einem Datenträgerausfall. Wenn ein Datenträger ausfällt, wird die auf diesem Datenträger gespeicherte Datenbankkopie aus der aktiven Datenbankkopie auf einen Ersatzdatenträger auf demselben Server kopiert. Wenn mehrere Datenbankkopien auf dem fehlerhaften Datenträger gespeichert waren, kann für diese automatisch ein erneutes Seeding auf einem Ersatzdatenträger ausgeführt werden. Damit kann das erneute Seeding schneller ausgeführt werden, da die aktiven Datenbanken sich wahrscheinlich auf mehreren Servern befinden und die Daten parallel kopiert werden können.
- **Automatische Wiederherstellung nach Speicherfehlern** Eine Weiterentwicklung der in Exchange 2010 eingeführten Funktion, die es dem System erlaubt, nach Ausfällen mit Auswirkung auf Resilienz oder Redundanz eine automatische Wiederherstellung durchzuführen. Zusätzlich zur Fehlerprüfung von Exchange 2010 bietet Exchange 2013 weitere Wiederherstellungsfunktionen bei langen E/A-Zeiten, übermäßige Speicherbelegungen durch "MSExchangeRepl.exe" und für gravierende Fälle, bei denen das System sich in einem so schlechten Zustand befindet, dass keine Threads geplant werden können.
- **Verbesserungen in Bezug auf verzögerte Kopien** Verzögerte Kopien können sich mithilfe der automatischen Protokollwiedergabe jetzt bis zu einem gewissen Grad selbst verwalten. Verzögerte Kopien geben in verschiedenen Situationen automatisch Protokolldateien wieder, wie z. B. beim Wiederherstellen einzelner Seite und in Szenarien mit wenig Speicherplatz. Wenn das System ermittelt, dass für eine verzögerte Kopie ein Seitenpatching erforderlich ist, werden die Protokolle automatisch in die verzögerte Kopie wiedergegeben, um das Seitenpatching auszuführen. Verzögerte Kopien rufen die automatische Wiedergabefunktion auch auf, wenn ein Schwellenwert bezüglich zu wenig Speicherplatz erreicht wird und wenn die verzögerte Kopie während eines bestimmten Zeitraums die einzige verfügbare Kopie ist. Darüber hinaus nutzen verzögerte Kopien die Funktion "Sicherheitsnetz", mit der die Wiederherstellung oder Aktivierung wesentlich vereinfacht wird. *Sicherheitsnetz* ist der Name einer verbesserten Funktionalität in Exchange 2013, die auf dem Transportdumpster von Exchange 2010 basiert.
- **Verbesserte Warnung zu einzelnen Kopien** Die in Exchange 2010 eingeführte Warnung zu einzelnen Kopien wird nicht länger als separat geplantes Skript zur Verfügung gestellt. Es wurde in die Systemkomponenten für verwaltete Verfügbarkeit integriert und ist jetzt eine systemeigene Funktion von Exchange.
- **Automatische Konfiguration von DAG-Netzwerken** DAG-Netzwerke können basierend auf Konfigurationseinstellungen automatisch vom System konfiguriert werden. DAGs bieten nicht nur manuelle Konfigurationsoptionen, sondern können auch zwischen MAPI- und Replikationsnetzwerken unterscheiden und DAG-Netzwerke automatisch konfigurieren.
Weitere Informationen zu diesen beiden Funktionen finden Sie unter [Hohe Verfügbarkeit und Ausfallsicherheit von Standorten](high-availability-and-site-resilience-exchange-2013-help.md) und [Änderungen bei hoher Verfügbarkeit und Ausfallsicherheit im Vergleich zu früheren Versionen](changes-to-high-availability-and-site-resilience-over-previous-versions-exchange-2013-help.md)
## Verwaltung von Exchange-Arbeitsauslastungen
Bei Exchange-Arbeitsauslastungen handelt es sich um Exchange-Serverfunktionen, -protokolle oder -dienste, die explizit zum Zweck der Exchange-Systemressourcenverwaltung definiert wurden. Jede Exchange-Arbeitsauslastung nutzt Systemressourcen (z. B. CPU, Postfachdatenbankvorgänge oder Active Directory-Anforderungen), um Benutzeranforderungen oder Hintergrundaufgaben auszuführen. Beispiele für Exchange-Arbeitsauslastungen sind Outlook Web App, Exchange ActiveSync, Postfachmigrationen und der Postfach-Assistenten.
Es gibt zwei Möglichkeiten zum Verwalten von Exchange-Arbeitsauslastungen in Exchange 2013:
- **Überwachen des Status bestimmter Systemressourcen** Die Verwaltung von Arbeitsauslastungen basierend auf dem Status bestimmter Systemressourcen ist neu in Exchange 2013.
- **Steuern der Nutzung von Ressourcen durch einzelne Benutzer** Das Steuern der Nutzung von Ressourcen durch einzelne Benutzer war in Exchange 2010 möglich (und wurde als Benutzereinschränkung bezeichnet). Diese Funktionalität wurde für Exchange 2013 erweitert.
Weitere Informationen zu diesen Funktionen finden Sie unter [Verwaltung von Exchange-Arbeitsauslastungen](exchange-workload-management-exchange-2013-help.md).
| 133.859043 | 1,093 | 0.838628 | deu_Latn | 0.999092 |
f4cfd2bcdfdcbb7dbf11e3058b94dc8e6323e46d | 6,517 | md | Markdown | docs/getting-started.md | theclaw33/material-components | 1331fd7989e6c4f19bc417866968c16827f65889 | [
"CC-BY-4.0"
] | null | null | null | docs/getting-started.md | theclaw33/material-components | 1331fd7989e6c4f19bc417866968c16827f65889 | [
"CC-BY-4.0"
] | null | null | null | docs/getting-started.md | theclaw33/material-components | 1331fd7989e6c4f19bc417866968c16827f65889 | [
"CC-BY-4.0"
] | null | null | null | <!--docs:
title: "Getting Started"
layout: landing
section: docs
path: /docs/getting-started/
-->
# Getting Started
This getting started guide walks you through how to [install MDC Web Node modules](https://www.npmjs.com/org/material), and bundle the Sass and JavaScript from those Node modules in your [Webpack](https://webpack.js.org/) configuration.
> Note: This guide assumes you have npm installed locally.
### Step 1: Webpack with Sass
We’re going to use webpack-dev-server to demonstrate how webpack bundles our Sass and JavaScript. First create a package.json that looks like this:
```json
{
"scripts": {
"start": "webpack-dev-server"
}
}
```
You’ll need all of these Node dependencies:
- [webpack](https://www.npmjs.com/package/webpack): Bundles Sass and JavaScript
- [webpack-dev-server](https://www.npmjs.com/package/webpack-dev-server): Development server
- [sass-loader](https://www.npmjs.com/package/sass-loader): Loads a Sass file and compiles it to CSS
- [node-sass](https://www.npmjs.com/package/node-sass): Provides binding for Node.js to Sass, peer dependency to sass-loader
- [css-loader](https://www.npmjs.com/package/css-loader): Resolves CSS @import and url() paths
- [extract-loader](https://github.com/peerigon/extract-loader): Extracts the CSS into a .css file
- [file-loader](https://github.com/webpack-contrib/file-loader): Serves the .css file as a public URL
You can install all of them by running this command:
```
npm install --save-dev webpack@3 webpack-dev-server@2 css-loader sass-loader node-sass extract-loader file-loader
```
> Note: We recommend using Webpack 3, because we're still investigating using Webpack 4. We also recommend you use webpack-dev-server 2, because this works with Webpack 3.
In order to demonstrate how webpack bundles our Sass, you’ll need an index.html. This HTML file needs to include CSS. The CSS is generated by sass-loader, which compiles Sass files into CSS. The CSS is extracted into a .css file by extract-loader. Create this simple 'hello world' index.html:
```html
<html>
<head>
<link rel="stylesheet" href="bundle.css">
</head>
<body>Hello World</body>
</html>
```
And create a simple Sass file called app.scss:
```scss
body {
color: blue;
}
```
Then configure webpack to convert app.scss into bundle.css. For that you need a new webpack.config.js file:
```js
module.exports = [{
entry: './app.scss',
output: {
// This is necessary for webpack to compile
// But we never use style-bundle.js
filename: 'style-bundle.js',
},
module: {
rules: [{
test: /\.scss$/,
use: [
{
loader: 'file-loader',
options: {
name: 'bundle.css',
},
},
{ loader: 'extract-loader' },
{ loader: 'css-loader' },
{ loader: 'sass-loader' },
]
}]
},
}];
```
To test your webpack configuration, run:
```
npm start
```
And open localhost:8080 from a browser. You should see a blue “Hello World”.
### Step 2: Include CSS for a component
Now that you have webpack configured to compile Sass into CSS, let's include the Sass files for the Material Design button. First install the Node dependency:
```
npm install @material/button
```
We need to tell our app.scss to import the Sass files for @material/button. We can also use Sass mixins to customize the button. Replace your “hello world” version of app.scss with this code:
```scss
@import "@material/button/mdc-button";
.foo-button {
@include mdc-button-ink-color(teal);
@include mdc-states(teal);
}
```
@material/button has [documentation](../packages/mdc-button/README.md) about the required HTML of a button. Update your index.html to include this HTML, and add the foo-button class onto the element:
```html
<body>
<button class="foo-button mdc-button">
Button
</button>
</body>
```
You also need to configure the sass-loader to understand the @material syntax. Update your webpack.config.js by changing `{ loader: 'sass-loader' }` to:
```javascript
{
loader: 'sass-loader',
options: {
includePaths: ['./node_modules']
}
}
```
Now run npm start again and open localhost:8080. You should see the a Material Design button!
### Step 3: Webpack with ES2015
We need to configure webpack to bundle ES2015 JavaScript into standard JavaScript, through [babel](https://babeljs.io). You’ll need all of these dependencies:
- [babel-core](https://www.npmjs.com/package/babel-core)
- [babel-loader](https://www.npmjs.com/package/babel-loader): Compiles JavaScript files using babel
- [babel-preset-es2015](https://www.npmjs.com/package/babel-preset-es2015): Preset for compiling es2015
You can install all of them by running this command:
```
npm install --save-dev babel-core babel-loader babel-preset-es2015
```
In order to demonstrate how webpack bundles our JavaScript, you’ll need to update index.html to include JavaScript. The JavaScript file is generated by babel-loader, which compiles ES2015 files into JavaScript. Add this script tag to index.html:
```html
<script src="bundle.js" async></script>
```
And create a simple ES2015 file called app.js:
```javascript
console.log('hello world');
```
Then configure webpack to convert app.js into bundle.js. For that you need to add this code to the webpack.config.js file:
```javascript
module.exports.push({
entry: "./app.js",
output: {
filename: "bundle.js"
},
module: {
loaders: [{
test: /\.js$/,
loader: 'babel-loader',
query: {
presets: ['es2015']
}
}]
},
});
```
Now run npm start again and open localhost:8080. You should see a “hello world” in the console.
### Step 4: Include JavaScript for a component
Now that you have webpack configured to compile ES2015 into JavaScript, let's include the ES2015 files from the Material Design ripple. First install the Node dependency:
```
npm install @material/ripple
```
We need to tell our app.js to import the ES2015 file for @material/ripple. You also need to initialize an MDCRipple with a DOM element. Replace your 'hello world' version of app.js with this code:
```javascript
import {MDCRipple} from '@material/ripple';
const ripple = new MDCRipple(document.querySelector('.foo-button'));
```
Now run npm start again and open localhost:8080. You should see a Material Design ripple on the button!
TODO: Write a getting started guide for our CDN users
| 30.740566 | 292 | 0.711217 | eng_Latn | 0.90669 |
f4d02fa9b39da11c7f2a4251068be46b23631033 | 976 | md | Markdown | docs/windows-ml/custom-operators/IMLOperatorTensor_GetTensorDataType.md | hyoshioka0128/windows-ai-docs.ja-JP | ff8c8ee4df0963b2335d484b32fe44ed47d7db79 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/windows-ml/custom-operators/IMLOperatorTensor_GetTensorDataType.md | hyoshioka0128/windows-ai-docs.ja-JP | ff8c8ee4df0963b2335d484b32fe44ed47d7db79 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/windows-ml/custom-operators/IMLOperatorTensor_GetTensorDataType.md | hyoshioka0128/windows-ai-docs.ja-JP | ff8c8ee4df0963b2335d484b32fe44ed47d7db79 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Imloperatorの場合は、GetTensorDataType メソッド
description: のデータ型を取得します。
ms.date: 4/1/2019
ms.topic: article
keywords: windows 10、windows machine learning、WinML、カスタム演算子、GetTensorDataType
ms.localizationpriority: medium
topic_type:
- APIRef
api_type:
- NA
api_name:
- IMLOperatorTensor.GetTensorDataType
api_location:
- MLOperatorAuthor.h
ms.openlocfilehash: 4b6e08cd66c903f0bd170a4555318cc131da92c7
ms.sourcegitcommit: 577942041c1ff4da60d22af96543c11f5d5fe401
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 08/29/2019
ms.locfileid: "70156872"
---
# <a name="imloperatortensorgettensordatatype-method"></a>Imloperatorの場合は、GetTensorDataType メソッド
のデータ型を取得します。
```cpp
MLOperatorTensorDataType GetTensorDataType()
```
## <a name="requirements"></a>要件
| | |
|-|-|
| **サポートされている最低限のクライアント** | Windows 10、ビルド17763 |
| **サポートされている最小サーバー** | デスクトップエクスペリエンスを備えた Windows Server 2019 |
| **項目** | MLOperatorAuthor. h |
[!INCLUDE [help](../../includes/get-help.md)]
| 24.4 | 96 | 0.782787 | yue_Hant | 0.253594 |
f4d0e1782fc4786bd5bbf7587cba5985d4a048f5 | 95 | md | Markdown | README.md | kaunghtet466/phatsayar | f1e6046447a1f56353b648c6011ada4c002e9a89 | [
"MIT"
] | null | null | null | README.md | kaunghtet466/phatsayar | f1e6046447a1f56353b648c6011ada4c002e9a89 | [
"MIT"
] | null | null | null | README.md | kaunghtet466/phatsayar | f1e6046447a1f56353b648c6011ada4c002e9a89 | [
"MIT"
] | null | null | null | # phatsayar
mini library for user
This, phatsayar, is my first repo. I have to do many things.
| 23.75 | 60 | 0.757895 | eng_Latn | 0.999439 |
f4d0e33cb1769bf7f4e49591f7f8a9ece7c80f4b | 1,024 | md | Markdown | README.md | BradHuang1999/Battle-Tetromino | c2390a53245e941e14432401a1ff010c71c8d85e | [
"Apache-2.0"
] | 11 | 2017-01-08T08:10:24.000Z | 2022-02-08T07:41:08.000Z | README.md | BradHuang1999/Battle-Tetromino | c2390a53245e941e14432401a1ff010c71c8d85e | [
"Apache-2.0"
] | null | null | null | README.md | BradHuang1999/Battle-Tetromino | c2390a53245e941e14432401a1ff010c71c8d85e | [
"Apache-2.0"
] | 2 | 2018-07-07T19:03:56.000Z | 2019-02-14T11:20:23.000Z | # Battle Tetromino
Battle Tetromino is a spin on the classic Tetris game where various powerups can be employed to wreck havoc on the opponent's game board.
<img src="https://github.com/BradHuang1999/Battle-Tetromino/blob/master/screenshots/Login.png?raw=true" height="210px"></img></br>
Features:
1. Local Player vs Player
2. Local Player vs AI
3. Online Multiplayer and Chatroom
4. AI Demo Play
5. Single Player
## Genetic Algorithm
The machine modes were trained with ~ 30 generations using a **genetic algorithm** which assessed children from generation x with a fitness function and mutation operator using **supervised heuristic optimization**.
<img src="https://github.com/BradHuang1999/Battle-Tetromino/blob/master/screenshots/MachineAlgo.png" height="420px"></img></br>
<sup>_Machine Algorithm after 24 hours: reached score of 61,000,000 and cleared 7000 lines_</sup>
## Websocket Multiplayer
Used a **low-latency message queue optimization** on the websocket connection to eliminate 95% of game play delays
| 46.545455 | 215 | 0.785156 | eng_Latn | 0.939717 |
f4d0ff0b67d643bcfe3c67fd8f75d2503bcb549e | 1,663 | md | Markdown | windows-driver-docs-pr/kernel/object-directories.md | Ryooooooga/windows-driver-docs.ja-jp | c7526f4e7d66ff01ae965b5670d19fd4be158f04 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-driver-docs-pr/kernel/object-directories.md | Ryooooooga/windows-driver-docs.ja-jp | c7526f4e7d66ff01ae965b5670d19fd4be158f04 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-driver-docs-pr/kernel/object-directories.md | Ryooooooga/windows-driver-docs.ja-jp | c7526f4e7d66ff01ae965b5670d19fd4be158f04 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: オブジェクト ディレクトリ
description: オブジェクト ディレクトリ
ms.assetid: b0e0d077-6736-4a54-b1eb-a30962442942
keywords:
- オブジェクトディレクトリ WDK カーネル
- 名前付きオブジェクト WDK カーネル
- ディレクトリ WDK オブジェクト
- 最上位レベルのオブジェクトディレクトリ WDK カーネル
ms.date: 06/16/2017
ms.localizationpriority: medium
ms.openlocfilehash: cc6247d159e47de931911ae75ae5cce0540d2269
ms.sourcegitcommit: 4b7a6ac7c68e6ad6f27da5d1dc4deabd5d34b748
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 10/24/2019
ms.locfileid: "72827769"
---
# <a name="object-directories"></a>オブジェクト ディレクトリ
*オブジェクトディレクトリ*は、他の名前付きオブジェクトを格納するためだけに使用される名前付きオブジェクトです。 たとえば、 **\\デバイス**オブジェクトディレクトリには、ドライバーによって作成された名前付きデバイスオブジェクトが格納されます。
オブジェクトディレクトリとファイルシステムディレクトリを混同しないようにしてください。 オブジェクトディレクトリは、オブジェクトマネージャー内にのみ存在し、ディスク上のディレクトリには対応していません。 (実際にはファイルシステムディレクトリは、ファイルオブジェクトとして表されます)。
次に示すのは、ドライバーが作成または使用する可能性のあるオブジェクトが含まれている最上位レベルのオブジェクトディレクトリの一覧です。
- **\\コールバック**
システムは、このディレクトリに標準コールバックオブジェクトを作成します。 詳細については、「[システム定義のコールバックオブジェクトの使用](using-a-system-defined-callback-object.md)」を参照してください。
- **\\デバイス**
ドライバーは、このディレクトリに名前付きデバイスオブジェクトを作成します。 詳細については、「[名前付きデバイスオブジェクト](named-device-objects.md)」を参照してください。
- **\\KernelObjects**
システムによって、このディレクトリに標準イベントオブジェクトが作成されます。 詳細については、「[標準イベントオブジェクト](standard-event-objects.md)」を参照してください。
- **\\DosDevices**
このディレクトリには、デバイスの MS-DOS デバイス名が、対応するデバイスオブジェクトへのシンボリックリンクとして格納されます。 詳細については、「 [MS-DOS デバイス名](ms-dos-device-names.md)」を参照してください。
システムは、他の最上位レベルのディレクトリを作成しますが、システムで使用するために予約されています。
ドライバーは、 [**Zwcreatedirectoryobject**](https://docs.microsoft.com/windows-hardware/drivers/ddi/wdm/nf-wdm-zwcreatedirectoryobject)ルーチンを呼び出すことによって、新しいオブジェクトディレクトリを作成できます。
| 28.672414 | 168 | 0.809381 | yue_Hant | 0.683972 |
f4d155a202a7a5fffd278e95ceec858d77d0f85c | 1,877 | markdown | Markdown | _posts/2013-08-06-linker_13.markdown | freetonik/freetonik.github.io | 77b4a79611828ae1e21f5dca03015e5e46ce29ed | [
"MIT"
] | 2 | 2016-05-16T19:42:28.000Z | 2018-04-28T19:34:13.000Z | _posts/2013-08-06-linker_13.markdown | freetonik/freetonik.github.io | 77b4a79611828ae1e21f5dca03015e5e46ce29ed | [
"MIT"
] | 1 | 2016-03-15T12:22:47.000Z | 2017-08-04T15:55:26.000Z | _posts/2013-08-06-linker_13.markdown | freetonik/freetonik.github.io | 77b4a79611828ae1e21f5dca03015e5e46ce29ed | [
"MIT"
] | 3 | 2016-02-03T10:14:41.000Z | 2020-09-24T11:25:23.000Z | ---
layout: post
title: "Ссылкомат #13"
category: Linker
---
### Музыка
1. Расслабьтесь. [Air – La Femme D'argent](http://www.youtube.com/watch?v=Ls9aiN4QEDw).
2. У португальского языка есть удивительная способность звучать сказочно мягко. [Astrud Gilberto, João Gilberto and Stan Getz – The Girl from Ipanema](http://www.youtube.com/watch?v=c5QfXjsoNe4).
3. Джимми Фаллон, The Roots и Робин Тике [исполняют](http://www.youtube.com/watch?v=YOZjaqHioro) хоть уже и немного попсовую, но клевую песню Blurred Lines.
### Программирование
1. Джастин Абрамс, программист-самоучка, [объясняет Big-O](http://justin.abrah.ms/computer-science/big-o-notation-explained.html).
2. Новый доклад восхитительного Брета Виктора – [Будущее программирования](http://vimeo.com/71278954).
### Видео
1. [Сравнение реального секса и секса в порнофильмах](https://www.youtube.com/watch?v=q64hTNEj6KQ). На примере еды.
2. Как выглядела [ампутация во времена наполеоновских войн](http://www.youtube.com/watch?v=ctKKpBTWwwo). Слабонервным смотреть и жалеть.
3. Майк Роув показывает [крутейший трюк](http://www.youtube.com/watch?v=J4LhdU3a1KM): он слушает запись и повторяет ее в реальном времени. Если вам кажется что тут ничего такого – попробуйте сами.
4. [Классный веб-сериал](http://www.helpingyoumaintain.com/episodes) про клиентов чувака, который развозит травку по Нью-Йорку.
5. [Таймлапс в аэропорту Хитроу](http://www.youtube.com/watch?v=fgHjVvqLXV8). Бесконечный поток самолетов!
6. Выступление знаменитого [Бёрдимана на TED](http://www.youtube.com/watch?v=dIh8KBOOkYU). Не люблю битбокс, но Бёрдимана или, например, Реджи Уоттса – обожаю.
7. [Язык тела кошек](http://www.youtube.com/watch?v=bvsfB7sf4QU). В принципе, ничего неожиданного, но интересно.
8. Люблю смотреть на мастеров. Вот, например, [столяр делает скамейку](http://www.youtube.com/watch?v=p7l3_THa-Yk).
| 69.518519 | 197 | 0.763985 | rus_Cyrl | 0.774021 |
f4d191519170455f89f3eb7f1080cc3842cf76e3 | 850 | md | Markdown | ISSUE_TEMPLATE.md | kkostritsynax/Harpy | d9a899f28de78a09d11724c69bfe5d83f4b1c882 | [
"MIT"
] | null | null | null | ISSUE_TEMPLATE.md | kkostritsynax/Harpy | d9a899f28de78a09d11724c69bfe5d83f4b1c882 | [
"MIT"
] | null | null | null | ISSUE_TEMPLATE.md | kkostritsynax/Harpy | d9a899f28de78a09d11724c69bfe5d83f4b1c882 | [
"MIT"
] | null | null | null | ======
Before posting an issue, please make sure your issue has not already been resolved or answered elsehwere.
Common Issue #1:
> "Error retrieving iOS version number as there was no data returned."
Check if your app is available in the US App Store, otherwise add the corresponding country code when setting up Siren: https://github.com/ArtSabintsev/Siren/blob/master/Siren/Siren.swift#L198
Common Issue #2:
> "Support for macOS App Store."
Siren does not and will not support the macOS App Store.
Common Issue #3:
> "Support for prompting TestFlight users to update to the newest beta build."
Siren does not support this functionality. There is no publicly accessible TstFlight API akin to that of the public App Store API that Siren can utilize to provide this functionality.
Please delete this text before submitting a new issue.
======
| 40.47619 | 192 | 0.778824 | eng_Latn | 0.99489 |
f4d19f3239c3b95ab54cfdab2c1ff5a1e56b0689 | 505 | md | Markdown | README.md | zainarbani/unluac_miwifi | 8fc326b30c50d1a9fe95723a7d9175e819d28b1c | [
"MIT"
] | 38 | 2020-06-14T16:27:09.000Z | 2022-03-14T01:42:48.000Z | README.md | zainarbani/unluac_miwifi | 8fc326b30c50d1a9fe95723a7d9175e819d28b1c | [
"MIT"
] | null | null | null | README.md | zainarbani/unluac_miwifi | 8fc326b30c50d1a9fe95723a7d9175e819d28b1c | [
"MIT"
] | 29 | 2020-06-20T09:14:07.000Z | 2022-03-24T08:17:00.000Z | # unluac for MiWifi
Xiaomi Router encrypts its lua files in models AC2100, AX3600, R4.
They modified the Lua interpreter, which introduces string encryption, shifted opcode order, and customized opcodes.
This unluac is imported from upstream unluac at 2020.6.14
Credits:
- @lvqier for the initial port from https://github.com/lvqier/unluac
- unluac team for a brilliant luac decompiler
| 36.071429 | 116 | 0.79604 | eng_Latn | 0.92407 |
f4d1f5c250e7968f5cba93a4e1a6638869ddaa1f | 5,100 | md | Markdown | _posts/2016-03-30-batch.md | hausdorff/hausdorff.github.com | 0358eeffc4598d6d27d2a1cbfd16416d05781fbc | [
"MIT"
] | null | null | null | _posts/2016-03-30-batch.md | hausdorff/hausdorff.github.com | 0358eeffc4598d6d27d2a1cbfd16416d05781fbc | [
"MIT"
] | null | null | null | _posts/2016-03-30-batch.md | hausdorff/hausdorff.github.com | 0358eeffc4598d6d27d2a1cbfd16416d05781fbc | [
"MIT"
] | null | null | null | ---
layout: post
title: "How bad is the Windows command line really?"
permalink: batch.html
comments: true
analysis: ■
---
Kevin Gallo just announced Bash support on Windows.
If you have never had to interact with the Windows Batch language, this might not seem like such a big deal. Surely Batch could not be substantially worse than Bash, right?
Bash: a language that was neither designed, nor evolved. An adequate solution to a problem that has since become orders of magnitude harder. As arcane as it is useful, as dangerous as it is ubiquitous, Bash: the language that asks how much we are willing to give up for convenience's sake?
Sure, Bash could be worse. But _substantially_ worse? Bash had one value proposition: it was _just good enough_. It is difficult to imagine that it would have flourished as it has, if that had that not been true.
But the truth is what it is. Batch _is_ substantially worse. And how much worse sort of beggars belief. Look:
* The time a batch script takes to execute is at least O(n*(n-1)/2) (aka O(n^2)) in the LENGTH OF THE FILE, INCLUDING COMMENTS. The reason is that the batch engine reads the entire file, then executes a line, then reads the file again, then executes another line, and so on.
* It is therefore customary to use a GOTO to skip over sizable comment blocks, so that you don't have to "execute" them.
* The lines inside "lexical" blocks like those of the `for` loop are not interpreted separately. They are CONCATENATED TOGETHER AND INTERPRETED ALL AT ONCE, meaning that if do something as innocuous as adding a `::` comment inside a `for` loop or an `if` block, the terminating `)` will go missing and batch will not know what to do. It will think that you forgot to add a `)` to close the `for` loop.
* Never comment out code. If you, do bad things will eventually happen. For example, on some Windows systems, the `REM`-style comment, `REM Ensure > true`, will actually pipe the "output" of the comment to a file called `true`. Since comments have no output, the effect is to generate an empty file called `true`.
* Variable expansion occurs at PARSE TIME, not evaluation time. This is particularly bad in the case of blocks like `for` and `if`, because all the lines in the block are concatenated together and parsed at once. So, normally if you call something like `findstr` inside a `for` block, you would expect `%errorlevel%` to be set to indicate whether there was an error. But, it's not. The variable `%errorlevel%` is never updated, because it was assigned whatever value it had when Batch PARSED THE `for` BLOCK. The statement `if %errorlevel% neq 0` is therefore completely meaningless inside a `for` block.
* If you add 2 `::` comments in a `for` block, you will get errors that claim `The system cannot find the drive specified` and there is a possibility that your script will exit with error code 123. This happens because (in spite of popular guidance that you _should_ use `::` as a comment) it turns out that the `::` comment syntax is actually not a comment at all, but a LABEL, and in label syntax, `::` must be at the beginning of the line with no leading whitespace, and two consecutive labels causes batch to freak out, because batch concatenated them together into the same line.
And the list goes on and on.
When I was in college a few years ago, I thought that PowerShell was a fun take on what a modern shell could look like. It is not. PowerShell is the cure for polio, and Jeffrey Snover is the Jonas Salk of the Windows ecosystem.
Batch is like an alien device that has appeared on the earth, and at first you think it's a gift, but then you realize it is a machine of destruction, here to raze your society to the ground, and the only viable solution is to find a way to rid yourself of it completely.
Like the Necronomicon or some other Satanic book, Batch does not seem so bad at first, but when the correct medium (in this case, the computer) reads the words, you find that a portal to hell has opened and suddenly the trees are coming alive and you're being sucked into your computer screen you're thinking about how 10 minutes ago your biggest problem was whether you were going to get to the store in time tonight to grab that macaroni you like, and now, as you are floating through the demon portal, you're just wondering why this thing didn't come with a warning on this side or something like that.
Bash is like the neighbor who seems nice and sweet, but maybe they don't have a life you'd want to have personally. They have some pretty serious character flaws and obviously make mistakes, but in the end they are a nice person who tries hard to make sure the people that depend on them are doing ok.
Batch is the guy who looks like that neighbor, but then turns out to be a serial killer.
So, here we are. This is the reality of the Windows world. Yesterday, your choice was Batch or PowerShell. Today your choice is Batch, PowerShell, or Bash. (Well, it's not really as simple as that, but you get my point.)
And as you make your choice, it's worth visiting the graves of the fallen.
| 121.428571 | 605 | 0.770392 | eng_Latn | 0.999938 |
f4d24ebd4634ebde835d3b511938253b434c08d9 | 6,257 | md | Markdown | CHANGELOG.md | dandycoding/ice_cube | 768aef21c384b312e1be6591a393ca25a26a295f | [
"MIT"
] | 2 | 2015-12-04T07:27:08.000Z | 2020-05-28T12:58:48.000Z | CHANGELOG.md | dandycoding/ice_cube | 768aef21c384b312e1be6591a393ca25a26a295f | [
"MIT"
] | 8 | 2015-03-16T20:51:29.000Z | 2021-06-25T15:40:57.000Z | CHANGELOG.md | dnrce/ice_cube | 2028392b2f216557bb7aaa0f7e18a5351d6f2890 | [
"MIT"
] | 3 | 2015-10-01T19:21:04.000Z | 2021-03-17T18:02:35.000Z | # Changelog
## 0.12.1 / 2014-07-04
* [FEATURE] Deprecation message improvements
* [FEATURE] Added support for deserialization of times via Time.parse
* [FEATURE] Added interval validations
* [FEATURE] Coerce validation intervals to Fixnum
* [BUGFIX] Fix YAML serialization on blank values in ActiveRecord (#231)
* [BUGFIX] Yearly interval should return self like others
## 0.12.0 / 2014-04-06
* [FEATURE] Rename to `start_time` as a hash key (see UPGRADING) (#102)
* [FEATURE] Notify of deprecated usage (#219)
* [BUGFIX] Skip double occurrences over DST (#189)
* [BUGFIX] Avoid symbolizing hash keys from input
* [BUGFIX] Ensure time comparisons are done in schedule time zone (#209)
* [BUGFIX] Occurrence#overnight? now works on the last day of the month (#218)
## 0.11.3 / 2014-02-07
* [BUGFIX] Fix a StopIteration leak
## 0.11.2 / 2014-01-25
* [ENHANCEMENT] Use Enumerator for schedule occurrences
* [BUGFIX] Fix high CPU usage on minutely schedules
## 0.11.1 / 2013-10-28
* [ENHANCEMENT] Move deprecated into IceCube namespace
* [ENHANCEMENT] Standardize the exceptions that we raise
* [BUGFIX] Fix ActiveSupport edge case restoring serialized TZ
## 0.11.0 / 2013-06-13
* [FEATURE] `schedule.last(n)` method (#117)
* [FEATURE] `previous_occurrence` & `previous_occurrences` methods (#170)
* [BUGFIX] Occurrence `to_s` accepts format to comply with Rails
## 0.10.1 / 2013-05-17
* [BUGFIX] Match time zone from schedule when finding times (#152)
* [BUGFIX] Reliably calculate distance to same day in next month (#171)
* [ENHANCEMENT] Accept arrays in multiparameter DSL methods (#139)
* [BUGFIX] Updating interval on a rule shouldn't leave duplicate validations (#158) (#157)
* [BUGFIX] Allow Occurrence to work transparently with Arel (#168)
* [BUGFIX] Raise errors for invalid input (#139)
## 0.10.0 / 2013-02-25
* [BUGFIX] Fix monthly intervals to not skip short months (#105)
* [FEATURE] Add support for `week_start` (@masquita) (#75)
* [BUGFIX] Fix `occurring_between?` for zero-length occurrences at start boundary (#147)
* [ENHANCEMENT] Add block initialization, new schedule yields itself (#146)
* [ENHANCEMENT] Warn on use of DateTime and convert to local Time (#144)
* [BUGFIX] Bug fix for count limit across multiple rules (#149)
* [BUGFIX] Fix occurrences in DST transition (#150)
* [ENHANCEMENT] Start time counts as an implicit occurrence (no more empty schedule) (#135)
* [FEATURE] Schedule occurrences have end times (#119)
## 0.9.3 / 2013-01-03
* [BUGFIX] Match the subseconds of `start_time` when finding occurrences (#89)
* [FEATURE] Duration is dependent upon `end_time` (#120)
* [ENHANCEMENT] Duration defaults to 0
* [BUGFIX] Avoid microseconds when comparing times (#83)
* [BUGFIX] Handle DateTime's lack of subseconds
## 0.9.2 / 2012-12-08
* [FEATURE] Allow passing Time, Date, or DateTime to all calls
## 0.9.1 / 2012-10-19
* [BUGFIX] A fix for removing `until` validations (#106)
* [BUGFIX] A DST edge fix
## 0.9.0 / 2012-10-12
* [FEATURE] Fix the effect on `end_time` on IceCube::Schedule (#99)
* [ENHANCEMENT] Remove `end_time` from `to_s` (#99)
* [BUGFIX] Single recurrences now work properly with `conflict_with?` (#71)
* [BUGFIX] Fix a bug with interval > 1 when using `occurrences_between` (#92)
* [BUGFIX] Allow count, until removal by setting to nil (#94)
* [FEATURE] Allow deserialization of string structures easily (#93)
* [BUGFIX] Ignore usecs when creating Time.now for `*_occurrences` (#84)
* [BUGFIX] DST bug fix (#98)
* [FEATURE] Added `occurring_between?` (#88)
## 0.8.0
* Added support for WEEKST (thanks @devwout)
## 0.7.9
* Added INTERVAL to `to_ical` for all interval validations
## 0.7.8
* Bug fixes
## 0.7.7
* Added "Weekends" and "Weekdays" to day's `to_s`
## 0.7.6
* Support for `terminating?` and `conflicts_with?`
## 0.7.5
* Fix an issue with `occurrences_between` when using count (#54)
## 0.7.4
* NameError when serializing schedule with `end_time` (thanks @digx)
## 0.7.3
* Fix for time interval buckets (affects hour, minute, sec)
## 0.7.2
* Fix for interval to/from YAML issue
## 0.7.1
* Fix for comparing rules with nil
## 0.7.0
* Large rewrite, fixing a few small bugs and including some large optimizations to the spidering algo
* Support for `each_occurrence` which iterates as it builds forever
## 0.6.15
* Deserialize `until_date` properly in `to_hash` and `to_yaml` (thanks @promisedlandt)
## 0.6.14
* Fixed a skipping issue around DST ending
## 0.6.13
* Fix by Ben Fyvie for daily rule crossing over a year boundary
* Additional accessor methods on validations and rules for easy use in microformats (thanks @jamesarosen)
* Fix for changing start date affecting schedules without reloading
* Fix for typo in `active_support_occurs_between`? causing load issues with ActiveSupport (thanks @carlthuringer)
## 0.6.12
* Be able to set the `start_date` and duration after creating a schedule
## 0.6.11
* Added the ability to add and remove rdates, rrules, exdates, and exrules from a schedule
## 0.6.10
* UNTIL date now serialized with time information
## 0.6.9
* Added support for `Schedule#occurs_between?`
## 0.6.5
* Added a `:start_date_override` option to `from_hash` / `from_yaml` (@sakrafd)
## 0.6.4
* Fixed bug where `next_occurrence` wouldn't actually grab the correct next occurrence with schedules that had more than one recurrence rule and/or a recurrence rule and a recurrence date
* Added `next_occurrences` function to schedule, allowing you to get the next _N_ occurrences after a given date
## 0.6.3
* Change how `active_support_occurs_on` works
* Fixed bug where `next_occurrence` wouldn't work if no `end_date` was set
## 0.6.2
* Patch release for `to_yaml` performance issue
## 0.6.1
* Lessen the amount of info we store in yaml on the time zone
## 0.6.0
* Changed how time serialization is done to preserve TimeWithZone when appropriate. (#8)
* Backward compatibility is intact, but bumping the minor version for the YAML format change.
* Fixed next occurrence to work on never-ending schedules (#11)
| 32.087179 | 187 | 0.70577 | eng_Latn | 0.976988 |
f4d30b3ad2eef48fa362bcdaabedecfa9f52b97a | 384 | md | Markdown | windows.networking.connectivity/lanidentifierdata.md | stefb965/winrt-api | 89da6197d3c4c09e3bbb4966b984a6da790614f3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows.networking.connectivity/lanidentifierdata.md | stefb965/winrt-api | 89da6197d3c4c09e3bbb4966b984a6da790614f3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows.networking.connectivity/lanidentifierdata.md | stefb965/winrt-api | 89da6197d3c4c09e3bbb4966b984a6da790614f3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
-api-id: T:Windows.Networking.Connectivity.LanIdentifierData
-api-type: winrt class
---
<!-- Class syntax.
public class LanIdentifierData : Windows.Networking.Connectivity.ILanIdentifierData
-->
# Windows.Networking.Connectivity.LanIdentifierData
## -description
Represents the port specific data that enables LAN locality capabilities.
## -remarks
## -examples
## -see-also | 20.210526 | 83 | 0.773438 | yue_Hant | 0.41617 |
f4d3102629b82dd3ee5d71d443bf9b7ae486bc31 | 10,202 | md | Markdown | README.md | TakuKobayashi/dotnet-env | 13fea8df41aad516c780ba8d1eac939b838ca491 | [
"MIT"
] | 1 | 2021-04-29T19:09:57.000Z | 2021-04-29T19:09:57.000Z | README.md | TakuKobayashi/dotnet-env | 13fea8df41aad516c780ba8d1eac939b838ca491 | [
"MIT"
] | null | null | null | README.md | TakuKobayashi/dotnet-env | 13fea8df41aad516c780ba8d1eac939b838ca491 | [
"MIT"
] | null | null | null | [](https://ci.appveyor.com/project/rogusdev/dotnet-env)
[](LICENSE)
[](https://www.nuget.org/packages/DotNetEnv)
# dotnet-env
A .NET library to load environment variables from .env files. Supports .NET Core and .NET Framework
## Installation
Available on [NuGet](https://www.nuget.org/packages/DotNetEnv/)
Visual Studio:
```powershell
PM> Install-Package DotNetEnv
```
.NET Core CLI:
```bash
dotnet add package DotNetEnv
```
## Usage
### Load env file
`Load()` will automatically look for a `.env` file in the current directory by default,
or any higher parent/ancestor directory if given the option flag via TraversePath()
```csharp
DotNetEnv.Env.Load();
DotNetEnv.Env.TraversePath().Load();
```
Or you can specify the path directly to the `.env` file,
amd as above, with `TraversePath()`, it will start looking there
and then look in higher dirs from there if not found.
```csharp
DotNetEnv.Env.Load("./path/to/.env");
```
It's also possible to load the (text) file as a `Stream` or `string` or multiple files in sequence
```csharp
using (var stream = File.OpenRead("./path/to/.env"))
{
DotNetEnv.Env.Load(stream);
}
DotNetEnv.Env.LoadContents("OK=GOOD\nTEST=\"more stuff\"");
// will use values in later files over values in earlier files
// NOTE: NoClobber will reverse this, it will use the first value encountered!
DotNetEnv.Env.LoadMulti(new[] {
".env",
".env2",
});
```
### Accessing environment variables
The variables in the `.env` can then be accessed through the `System.Environment` class
```csharp
System.Environment.GetEnvironmentVariable("IP");
```
Or through one of the helper methods:
```csharp
DotNetEnv.Env.GetString("A_STRING");
DotNetEnv.Env.GetBool("A_BOOL");
DotNetEnv.Env.GetInt("AN_INT");
DotNetEnv.Env.GetDouble("A_DOUBLE");
```
The helper methods also have an optional second argument which specifies what value to return if the variable is not found:
```csharp
DotNetEnv.Env.GetString("THIS_DOES_NOT_EXIST", "Variable not found");
```
### Additional arguments
You can also pass a `LoadOptions` object arg to all `DotNetEnv.Env.Load` variants to affect the Load/Parse behavior:
```csharp
new DotNetEnv.LoadOptions(
setEnvVars: true,
clobberExistingVars: true,
onlyExactPath: true
)
```
However the recommended approach is with a fluent syntax for turning flags off such as:
```csharp
DotNetEnv.Env.NoEnvVars().NoClobber().TraversePath().Load();
```
All parameters default to true, which means:
1. `setEnvVars`, first arg: `true` in order to actually update env vars.
Setting it `false` allows consumers of this library to process the .env file
but use it for things other than updating env vars, as a generic configuration file.
The Load methods all return an `IEnumerable<KeyValuePair<string,string>> for this, but
there is an extension method ToDictionary to get a dict with the last value for each key.
```env
KEY=value
```
```csharp
var kvps = DotNetEnv.Env.Load(
options: new DotNetEnv.Env.LoadOptions(
setEnvVars: false
)
)
// or the recommended, cleaner (fluent) approach:
var dict = DotNetEnv.Env.NoEnvVars().Load().ToDictionary();
// not "value" from the .env file
null == System.Environment.GetEnvironmentVariable("KEY")
"KEY" == kvps.First().Key
"value" == kvps.First().Value
```
2. `clobberExistingVars`, second arg: `true` to always set env vars,
`false` would leave existing env vars alone.
```env
KEY=value
```
```csharp
System.Environment.SetEnvironmentVariable("KEY", "really important value, don't overwrite");
DotNetEnv.Env.Load(
options: new DotNetEnv.Env.LoadOptions(
clobberExistingVars: false
)
)
// or the recommended, cleaner (fluent) approach:
DotNetEnv.Env.NoClobber().Load();
// not "value" from the .env file
"really important value, don't overwrite" == System.Environment.GetEnvironmentVariable("KEY")
```
3. `exactPathOnly`, third arg: `true` to require .env to be
in the current directory if not specified, or to match the exact path passed in,
`false` would traverse the parent directories above the current or given path
to find the nearest `.env` file or whatever name was passed in.
This option only applies to Env.Load that takes a string path.
See `DotNetEnvTraverse.Tests` for examples.
```csharp
// the recommended, cleaner (fluent) approach:
DotNetEnv.Env.TraversePath().Load();
```
## .env file structure
All lines must be valid assignments or empty lines (with optional comments).
A minimal valid assignment looks like:
```
KEY=value
```
There can optionally be one of a few export or equivalent keywords at the beginning
and there can be a comment at the end, values can be quoted to include whitespace,
and interpolated references can be included (unquoted values as well as double quoted,
with optional braces in both cases -- but often more useful in unquoted), like:
```
export KEY="extra $ENVVAR value" # comment
set KEY2=extra${ENVVAR}value # comment
```
The options for the export keyword are:
export # bash
set # windows cmd
SET # windows cmd
set -x # fish
This allows the `.env` file itself to be `source`-d like `. .env`
to load the env vars into a terminal session directly.
The options for quoting values are:
1. `""` double: can have everything: interpolated variables, plus whitespace, escaped chars, and byte code chars
1. `''` single: can have whitespace, but no interpolation, no escaped chars, no byte code chars -- notably not even escaped single quotes inside -- single quoted values are for when you want truly raw values
1. unquoted: can have interpolated variables, but only inline whitespace, and no escaped chars, nor byte code chars.
As these are the options bash recognizes. However, while bash does have
special meaning for each of these, in this library, they are all the same,
other than that you do not need to escape single quote chars inside
a double quoted value, nor double quotes inside single quotes.
As a special note: if a value is unquoted, it can still include a `#` char,
which might look like it is starting a comment, like:
```
KEY=value#notcomment #actualcomment
```
This is how bash works as well:
```
export TEST=value#notcomment #actualcomment
env | grep TEST
# TEST=value#notcomment
```
However, unlike bash, inline whitespace is allowed so you can do:
```
KEY=value#notcomment more words here # yes comment
"value#notcomment more words here" == System.Environment.GetEnvironmentVariable("KEY")
```
You can also declare unicode chars as byte codes in double quoted values:
UTF8 btes: "\xF0\x9F\x9A\x80" # rocket 🚀
UTF16 bytes: "\uae" # registered ®
UTF32 bytes: "\U1F680" # rocket 🚀
Capitalization on the hex chars is irrelevant, and leading zeroes are optional.
And standard escaped chars like `\t`, `\\``, `\n`, etc are also recognized
-- though quoted strings can also be multi line, e.g.:
```
KEY="value
and more"
OTHER='#not_comment
line2'
```
Loaded gives:
```
"value\nand more" == System.Environment.GetEnvironmentVariable("KEY")
"#not_comment\nline2" == System.Environment.GetEnvironmentVariable("OTHER")
```
You can also include whitespace before and after the equals sign in assignments,
between the name/identifier, and the value, quoted or unquoted.
Note that the pre/trailing and post/leading whitespace will be ignored.
If you want leading whitepace on your values, quote them with whitespace.
```
WHITE_BOTH = value
WHITE_QUOTED=" value "
```
Loaded gives:
```
"value" == System.Environment.GetEnvironmentVariable("WHITE_BOTH")
" value " == System.Environment.GetEnvironmentVariable("WHITE_QUOTED")
```
Note that bash env vars do not allow white space pre or post equals,
so this is a convenience feature that will break sourcing .env files.
But then, not all of this is 100% compatible anyway, and that's ok.
Note that other .env parsing libraries also might have slightly different rules
-- no consistent rules have arisen industry wide yet.
## A Note about Production and the Purpose of This Library
You should not be using a .env file in production. The purpose of this library is to enable easy local development.
Your dev team should have a .env with localdev testing credentials/etc stored in some secure storage -- 1pass/lastpass or s3 bucket or something like that.
Then every developer gets a copy of that file as part of onboarding that they save into their project dir that uses DotNetEnv to get env vars for configuration.
When the application is deployed into production, actual env vars should be used, not a static .env file!
This does mean that env vars, and thus this library, are only useful for load time configuration -- not anything that changes during the lifetime of an application's run.
(You should load env var values during startup or on first access and not look them up more than once during the application's lifetime.)
Admittedly, this is best practices advice, and if you want to use .env files in production, that's up to you. But at least I have told you so. :)
## Issue Reporting
If you have found a bug or if you have a feature request, please report them at this repository issues section.
## Contributing
Run `dotnet test` to run all tests.
Or some more specific test examples:
dotnet test --filter "FullyQualifiedName~DotNetEnv.Tests.EnvTests.BadSyntaxTest"
dotnet test --filter "FullyQualifiedName~DotNetEnv.Tests.ParserTests.ParseAssignment"
`src/DotNetEnvEnv/Env.cs` is the entry point for all behavior.
`src/DotNetEnvEnv/Parsers.cs` defines all the [Sprache](https://github.com/sprache/Sprache) parsers.
The `DotNetEnvTraverse.Tests` project tests loading `.env` files in parent (or higher) directories from the executable.
Open a PR on Github if you have some changes, or an issue if you want to discuss some proposed changes before creating a PR for them.
## License
This project is licensed under the MIT license. See the [LICENSE](LICENSE) file for more info.
| 33.123377 | 207 | 0.747108 | eng_Latn | 0.986674 |
f4d31e4e055fdc3f98516a550beedb061f3f8ad0 | 1,568 | md | Markdown | README.md | HanwenZhu/quizlet-cheater | 308777f307482792f38a5241cb6abd27b4f6f981 | [
"MIT"
] | null | null | null | README.md | HanwenZhu/quizlet-cheater | 308777f307482792f38a5241cb6abd27b4f6f981 | [
"MIT"
] | null | null | null | README.md | HanwenZhu/quizlet-cheater | 308777f307482792f38a5241cb6abd27b4f6f981 | [
"MIT"
] | null | null | null | # Quizlet Match Cheater
Use this to ~~beat your friends in Quizlet match games~~ lEaRn HoW tO dO pRoGrAmMiNg.
It can reach a speed of 0.5s for Quizlet matches (it could be 0.0s, but the fastest score the server accepts is 0.5s).
## Warning
This software is made and should **only** be used **for educational purposes**. Users should be responsible for using this software.
## Usage
1. Download the repository:
```sh
git clone https://github.com/HanwenZhu/quizlet-cheater.git
cd quizlet-cheater
```
2. Install dependencies:
```sh
pip install -U -r requirements.txt
```
And see [https://selenium-python.readthedocs.io/installation.html](https://selenium-python.readthedocs.io/installation.html) to install browser drivers, for your corresponding browser version.
3. Go to the desired Quizlet set and copy the _set number_. It is the first string of numbers in the URL of your set. It should be about (but not always) 9 (?) characters long.
4. Run the code:
```sh
python3 main.py
```
5. Paste the _set number_. Enter your Quizlet username and password.
6. Sit back.
## Remarks
- After many trials, I found that the fastest score the server accepts is 0.5 seconds.
- I initially wanted to keep the code not opensourced. But after 22 seconds of thought, I thought a bunch of other people will also want to use this.
- In the JavaScript source code of Quizlet matches, you can see that if Quizlet discovers that you're cheating, it will designate you as a `time_changing_scatter_cheater`.
- Feel free to use or change this code, as long as you comply with the license.
| 46.117647 | 192 | 0.762755 | eng_Latn | 0.997825 |
f4d3b62eaf9da0824aaa02f7ce35d16918dee7fb | 2,114 | md | Markdown | README.md | bartekbrzuchalski/Simple-Sound-Synthesis | a1ab7ab663a28c2cb5491f88663b183a8dc9e97d | [
"BSD-2-Clause"
] | 1 | 2021-05-25T20:00:31.000Z | 2021-05-25T20:00:31.000Z | README.md | bartekbrzuchalski/Simple-Sound-Synthesis | a1ab7ab663a28c2cb5491f88663b183a8dc9e97d | [
"BSD-2-Clause"
] | null | null | null | README.md | bartekbrzuchalski/Simple-Sound-Synthesis | a1ab7ab663a28c2cb5491f88663b183a8dc9e97d | [
"BSD-2-Clause"
] | null | null | null | # Simple Sound Synthesis
This library is intended to digitally produce simple sound waves, record them, play them back as well as analyze them.
The availible types of sounds that can be synthesised are sine waves, square waves and triangle waves. The provided
methods for analysis are to see the waveform of recorded sounds and their frequency spectrum.
It is required to have Python3 to use this library correctly. To be able to record with these functions, the user has
to make sure that the IDE or wherever you run Python, has access to the computer's audio input. There may appear
problems with certain IDEs. If you are using, like me, PyCharm on Mac, you have to allow the Terminal access
to the computer's microphone and then start PyCharm in the Terminal like this:
cd /Applications/PyCharm\ CE.app/Contents/MacOS/
./pycharm
There are a relatively large amount of modules necessary to use all of the functions. You should already have the
modules numpy, matplotlib, wave, threading, time and math in your Python library. However, the modules pyaudio and
scipy are external and have to be installed.
To install pyaudio, run this in the terminal: pip install PyAudio
To install scipy, run this in the terminal: pip install scipy
If the user would like to test the library, as in the built-in test program, further modules are necessary. These
include the built-in modules glob and os. Furthermore, the external module playsound is needed. To install this,
you have to run both "pip install playsound" and "pip3 install -U PyObjC".
It is recommended to have some software that can record internal sound from the computer. I have used the software
BlackHole (it is free), as can be seen in the testing program and the demo. This is not necessary and the built-in
microphone on your computer should also be fine. Recording with some inputs may cause problems so make sure that
they are set as the chosen audio device in the computer settings as well.
The demo is in Swedish but even if you do not understand, I hope that you can see how the library can be used through
my inputs and their results.
| 54.205128 | 118 | 0.79281 | eng_Latn | 0.999926 |
f4d46f0c584fa572ed1630f1f1d3eb558cf5221d | 18,946 | md | Markdown | docs/reporting-services/troubleshooting/troubleshoot-server-and-database-connection-problems-with-reporting-services.md | thiagoamc/sql-docs.pt-br | 32e5d2a16f76e552e93b54b343566cd3a326b929 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/reporting-services/troubleshooting/troubleshoot-server-and-database-connection-problems-with-reporting-services.md | thiagoamc/sql-docs.pt-br | 32e5d2a16f76e552e93b54b343566cd3a326b929 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/reporting-services/troubleshooting/troubleshoot-server-and-database-connection-problems-with-reporting-services.md | thiagoamc/sql-docs.pt-br | 32e5d2a16f76e552e93b54b343566cd3a326b929 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Solução de problemas de conexão de banco de dados e de servidor com o Reporting Services | Microsoft Docs"
ms.custom:
ms.date: 02/28/2016
ms.prod: reporting-services
ms.prod_service: reporting-services-sharepoint, reporting-services-native
ms.service:
ms.component: troubleshooting
ms.reviewer:
ms.suite: pro-bi
ms.technology:
ms.tgt_pltfrm:
ms.topic: article
ms.assetid: 8bbb88df-72fd-4c27-91b7-b255afedd345
caps.latest.revision: "6"
author: markingmyname
ms.author: maghan
manager: kfile
ms.workload: On Demand
ms.openlocfilehash: d6544043e8925c77dc88d7d1191e8ccd690b7a00
ms.sourcegitcommit: 7e117bca721d008ab106bbfede72f649d3634993
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 01/09/2018
---
# <a name="troubleshoot-server-and-database-connection-problems-with-reporting-services"></a>Solucionar problemas de conexão de banco de dados e servidor com o Reporting Services
Use este tópico para solucionar problemas de conexão com um servidor de relatório. Este tópico também fornece informações sobre mensagens de "erro inesperado". Para saber mais sobre configuração de fonte de dados e como configurar a conexão do servidor de relatório, confira [Especificar informações de credenciais e de conexão para fontes de dados de relatório](../../reporting-services/report-data/specify-credential-and-connection-information-for-report-data-sources.md) e [Configurar uma conexão de banco de dados do servidor de relatório (Gerenciador de configurações do SSRS)](../../reporting-services/install-windows/configure-a-report-server-database-connection-ssrs-configuration-manager.md).
## <a name="cannot-create-a-connection-to-data-source-datasourcename-rserroropeningconnection"></a>Não é possível criar uma conexão com uma fonte de dados 'datasourcename'. (rsErrorOpeningConnection)
Este é um erro genérico que ocorre quando o servidor de relatório não pode abrir uma conexão com uma fonte de dados externa que fornece dados a um relatório. Este erro aparece com uma segunda mensagem de erro que indica a causa subjacente. Os erros adicionais a seguir podem aparecer com **rsErrorOpeningConnection**.
### <a name="login-failed-for-user-username"></a>Falha no logon do usuário 'UserName'
O usuário não tem permissão para acessar a fonte de dados. Se você estiver usando um banco de dados do SQL Server, verifique se o usuário tem um logon de usuário de banco de dados válido. Para saber mais sobre como criar um usuário de banco de dados ou um logon do SQL Server, confira [Criar um usuário de banco de dados](../../relational-databases/security/authentication-access/create-a-database-user.md) e [Criar um logon do SQL Server](../../relational-databases/security/authentication-access/create-a-login.md).
### <a name="login-failed-for-user-nt-authorityanonymous-logon"></a>Falha no logon do usuário 'NT AUTHORITY\ANONYMOUS LOGON'
Este erro ocorre quando as credenciais são transmitidas em várias conexões de computador. Se você estiver usando a Autenticação do Windows e o protocolo Kerberos versão 5 não estiver habilitado, este erro ocorrerá quando as credenciais forem transmitidas em mais de uma conexão de computador. Para resolver este erro, use credenciais armazenadas ou credenciais solicitadas. Para saber mais sobre como contornar esse problema, confira [Especificar informações de credenciais e de conexão para fontes de dados de relatório](../../reporting-services/report-data/specify-credential-and-connection-information-for-report-data-sources.md).
### <a name="an-error-has-occurred-while-establishing-a-connection-to-the-server"></a>Ocorreu um erro ao estabelecer uma conexão com o servidor.
Ao conectar-se ao SQL Server, essa falha pode ser provocada porque, sob as configurações padrão, o SQL Server não permite conexões remotas. (provedor: Provedor de Pipes Nomeados, erro: 40 - não foi possível abrir uma conexão com o SQL Server). Esse erro é retornado pela instância do Mecanismo de Banco de Dados que hospeda o banco de dados do servidor de relatório. Na maioria das vezes, esse erro ocorre porque o serviço SQL Server é interrompido. Ou, se você estiver usando o SQL Server Express com Advanced Services ou uma instância nomeada, esse erro ocorrerá caso a URL do servidor de relatório ou a cadeia de conexão do banco de dados de tal servidor não esteja correta. Para resolver esses problemas, siga este procedimento:
* Verifique se o serviço SQL Server (**MSSQLSERVER**) foi iniciado. No computador que hospeda a instância do Mecanismo de Banco de Dados, clique em Iniciar, em Ferramentas Administrativas, em Serviços e role até o SQL Server (**MSSQLSERVER**). Se ele ainda não tiver sido iniciado, clique com o botão direito do mouse no serviço, selecione Propriedades, em Tipo de Inicialização, escolha Automático e clique consecutivamente em Aplicar, Iniciar e OK.
* Verifique se a URL do servidor de relatório e a cadeia de conexão do banco de dados de tal servidor estão corretas. Se o Reporting Services ou o Mecanismo de Banco de Dados tiver sido instalado como uma instância nomeada, a cadeia de conexão padrão criada durante a Instalação incluirá o nome da instância. Por exemplo, se você instalou uma instância padrão do SQL Server Express com Advanced Services em um servidor denominado DEVSRV01, a URL do Gerenciador de Relatórios será DEVSRV01\Reports$SQLEXPRESS. Além disso, o nome de servidor de banco de dados na cadeia de conexão será semelhante a DEVSRV01\SQLEXPRESS. Para saber mais sobre URLs e cadeias de conexão de fonte de dados para SQL Server Express, confira [Reporting Services no SQL Server Express com Advanced Services](http://technet.microsoft.com/library/ms365166(v=sql.105).aspx). Para verificar a cadeia de conexão do banco de dados do servidor de relatório, inicie a ferramenta Configuração do Reporting Services e exiba a página Configuração do Banco de Dados.
### <a name="a-connection-cannot-be-made-ensure-that-the-server-is-running"></a>Uma conexão não pode ser feita. Verifique se o servidor está em execução.
Este erro é retornado pelo provedor ADOMD.NET. Há várias razões para a ocorrência desse erro. Se você tiver especificado o servidor como “localhost”, tente especificar o nome do servidor. Esse erro também poderá ocorrer se não for possível alocar a memória na nova conexão. Para saber mais, confira [o artigo 912017 da Base de Dados de Conhecimento — Mensagem de erro quando você se conectar a uma instância do SQL Server 2005 Analysis Services:](http://support.microsoft.com/kb/912017).
Se o erro também incluir "Nenhum host desse tipo é conhecido", isso indica que o servidor do Analysis Services não está disponível ou está recusando a conexão. Se o servidor do Analysis Services estiver instalado como uma instância nomeada em um computador remoto, talvez seja necessário executar o serviço SQL Server Browser para obter o número da porta usada pela instância em questão.
### <a name="report-services-soap-proxy-source"></a>(Origem do Proxy SOAP do Report Services)
Se esse erro ocorrer durante a geração do modelo de relatório e a seção de informações adicionais incluir "O SQL Server não existe ou acesso foi negado", as seguintes condições podem existir:
* A cadeia de conexão da fonte de dados inclui "localhost".
* O TCP/IP está desabilitado para o serviço SQL Server.
Para resolver este erro, modifique a cadeia de conexão para usar o nome do servidor ou habilite o TCP/IP para o serviço. Siga estas etapas para habilitar o TCP/IP:
1. Inicie o SQL Server Configuration Manager
2. Expanda **Configuração de Rede do SQL Server**.
3. Selecione **Protocolos do MSSQLSERVER**.
4. Clique com o botão direito do mouse em **TCP/IP**e escolha **Habilitar**.
5. Escolha **Serviços do SQL Server**.
6. Clique com o botão direito do mouse em **SQL Server (MSSQLSERVER)**e escolha **Reiniciar**.
## <a name="wmi-error-when-connecting-to-a-report-server-in-management-studio"></a>Erro de WMI ao conectar-se a um servidor de relatório no Management Studio
Por padrão, o Management Studio usa o provedor de WMI (Instrumentação de Gerenciamento do Windows) do Reporting Services para estabelecer uma conexão com o servidor de relatório. Se o provedor WMI não estiver instalado corretamente, o seguinte erro ocorrerá quando você tentar se conectar ao servidor de relatório:
Não é possível se conectar ao \<your server name>. O provedor WMI do Reporting Services não está instalado ou está instalado incorretamente (Microsoft.SqlServer.Management.UI.RSClient).
Para resolver esse erro, reinstale o software. Em todos os outros casos, como solução temporária, você pode se conectar ao servidor de relatório pelo ponto de extremidade SOAP:
* Na caixa de diálogo **Conectar ao Servidor** no Management Studio, em **Nome do Servidor**, digite a URL do servidor de relatório. Por padrão, ela é `http://<your server name>/reportserver`. Ou se estiver usando o SQL Server 2008 Express com Advanced Services, ela será `http://<your server name>/reportserver$sqlexpress`.
Para resolver o erro e conseguir se conectar usando o provedor de WMI, execute o programa de instalação para reparar o Reporting Services ou reinstale o Reporting Services.
## <a name="connection-error-where-login-failed-due-to-unknown-user-name-or-bad-password"></a>Erro de conexão; o logon falhou devido a um nome de usuário desconhecido ou uma senha inválida
Um erro **rsReportServerDatabaseLogonFailed** poderá ocorrer se você estiver usando uma conta de domínio para a conexão do servidor de relatório com o banco de dados do servidor de relatório e se a senha da conta de domínio tiver sido alterada.
O texto completo do erro é: “O servidor de relatório não pode abrir uma conexão com seu banco de dados. Falha de logon (**rsReportServerDatabaseLogonFailed**). Falha de logon: nome de usuário desconhecido ou senha inválida”.
Se a senha for redefinida, atualize a conexão. Para saber mais, confira [Configurar uma conexão de banco de dados do servidor de relatório (Configuration Manager do SSRS)](../../reporting-services/install-windows/configure-a-report-server-database-connection-ssrs-configuration-manager.md).
## <a name="the-report-server-cannot-open-a-connection-to-the-report-server-database-rsreportserverdatabaseunavailable"></a>O servidor de relatório não pode abrir uma conexão com o banco de dados do servidor de relatório. (rsReportServerDatabaseUnavailable).
Mensagem completa: O servidor de relatório não pode abrir uma conexão com o banco de dados do servidor de relatório. Uma conexão com o banco de dados é necessária para todas as solicitações e processamentos. (rsReportServerDatabaseUnavailable)
Esse erro ocorre quando o servidor de relatório não consegue se conectar ao banco de dados relacional do SQL Server que fornece o armazenamento interno ao servidor. A conexão com o banco de dados do servidor de relatório é gerenciada pela ferramenta Configuração do Reporting Services. Você pode executar a ferramenta, ir à página Configuração do Banco de Dados e corrigir as informações de conexão. É recomendável usar a ferramenta para atualizar as informações de conexão; a ferramenta assegura que as configurações dependentes sejam atualizadas e que os serviços sejam reiniciados. Para saber mais, confira [Configurar uma conexão de banco de dados do servidor de relatório](../../reporting-services/install-windows/configure-a-report-server-database-connection-ssrs-configuration-manager.md) e [Configurar uma conta de serviço do servidor de relatório](../../reporting-services/install-windows/configure-the-report-server-service-account-ssrs-configuration-manager.md).
Esse erro também poderá ocorrer se a instância do Mecanismo de Banco de Dados que hospeda o banco de dados do servidor de relatório não estiver configurada para conexões remotas. A conexão remota é habilitada, por padrão, em algumas edições do SQL Server. Para verificar se ela está habilitada na instância do Mecanismo de Banco de Dados do SQL Server que você está usando, execute a ferramenta SQL Server Configuration Manager. Você deve habilitar TCP/IP e pipes nomeados. Um servidor de relatório usa os dois protocolos. Para obter instruções sobre como habilitar conexões remotas, confira a seção "Como configurar conexões remotas com o banco de dados do servidor de relatório" em [Configurar um servidor de relatório para administração remota](../../reporting-services/report-server/configure-a-report-server-for-remote-administration.md).
Se o erro incluir o texto adicional a seguir, a senha expirou na conta usada para executar a instância do Mecanismo de Banco de Dados: "Erro ao estabelecer uma conexão com o servidor. Ao conectar-se ao SQL Server, essa falha pode ser provocada porque, sob as configurações padrão, o SQL Server não permite conexões remotas. (**provedor: Interfaces de Rede do SQL Server, erro: 26 — erro ao localizar servidor/instância especificada)**". Para resolver esse erro, redefina a senha.
## <a name="rpc-server-is-not-listening"></a>“O servidor RPC não está escutando”
O serviço Servidor de Relatório usa o servidor RPC (Chamada de Procedimento Remoto) para algumas operações. Se o erro “O servidor RPC não está escutando” for exibido, verifique se o serviço Servidor de Relatório está em execução.
## <a name="unexpected-error-general-network-error"></a>Erro inesperado (erro de rede geral)
Esse erro indica um erro de conexão de fonte de dados. Verifique a cadeia de conexão e verifique se você tem permissão para acessar a fonte de dados. Se estiver usando a Autenticação do Windows para acessar uma fonte de dados, você deve ter permissão para acessar o computador que hospeda a fonte de dados.
## <a name="unable-to-grant-database-access-in-sharepoint-central-administration"></a>Não é possível conceder acesso a banco de dados na Administração Central do SharePoint
Ao configurar o Reporting Services para integração a um produto SharePoint, ou uma tecnologia no Windows Vista ou Windows Server 2008, você poderá receber a mensagem de erro a seguir ao tentar conceder acesso na página **Conceder Acesso ao Banco de Dados** na Administração Central do SharePoint: "Não é possível estabelecer uma conexão com o computador".
Isso acontece porque o UAC (Controle de Conta de Usuário) no Windows Vista e no Windows Server 2008 requer aceitação explícita de um administrador para elevar e usar o token de administrador na execução de tarefas que exigem permissões de administrador. No entanto, nesse caso, o serviço Administração do Windows SharePoint Services não pode ser elevado para conceder às contas de serviço do Reporting Services acesso aos bancos de dados de conteúdo e configuração do SharePoint.
No SQL Server 2008 Reporting Services, apenas a conta de serviço do Servidor de Relatório requer acesso ao banco de dados; já no SQL Server 2005 Reporting Services SP2, as contas de serviço do Servidor de Relatório, Windows e Web, exigem acesso ao banco de dados. Para saber mais sobre a conta de serviço do Servidor de Relatório no SQL Server 2008, confira Conta de Serviço (Configuração do Reporting Services).
Há duas soluções alternativas para esse problema.
1. Em uma delas, você pode desativar temporariamente o UAC e usar a Administração Central do SharePoint para conceder acesso.
> [!IMPORTANT]
> Tome cuidado ao desativar o UAC para usar a solução alternativa, e ative-o imediatamente depois de conceder acesso ao banco de dados na Administração Central do SharePoint. Se não desejar desativar o UAC, use a segunda solução alternativa apresentada nesta seção. Para obter mais informações sobre o UAC, consulte a documentação do produto Windows.
2. Na segunda solução alternativa, você pode conceder manualmente acesso ao banco de dados às contas de serviço do Reporting Services. Use o procedimento a seguir para conceder acesso adicionando as contas de serviço do Reporting Services às funções de banco de dados e ao grupo do Windows corretos. Esse procedimento se aplica à conta de serviço do Servidor de Relatório no SQL Server 2008 Reporting Services; se você estiver executando o SQL Server 2005 Reporting Services, execute o procedimento para ambas as contas de serviço do Servidor de Relatório, Windows e Web.
### <a name="to-manually-grant-database-access"></a>Para conceder manualmente acesso ao banco de dados
1. Adicione a conta de serviço do Servidor de Relatório ao grupo WSSP_WPG do Windows no computador do Reporting Services.
2. Conecte-se à instância do banco de dados que mantém a configuração e os bancos de dados de conteúdo do SharePoint, e crie um logon de banco de dados SQL para a conta de serviço do Servidor de Relatório.
3. Adicione o logon de banco de dados SQL às seguintes funções de banco de dados:
* db_owner role no banco de dados WSS Content
* WSS_Content_Application_Pools role no banco de dados SharePoint_Config
## <a name="unable-to-connect-to-the-reports-and-reportserver-directories-when-the-report-server-databases-are-created-on-a-virtual-sql-server-that-runs-in-a-microsoft-cluster-services-mscs-cluster"></a>Não é possível se conectar aos diretórios /reports e /reportserver quando os bancos de dados do servidor de relatório são criados em um SQL Server executando em um cluster MSCS (Serviços de Cluster da Microsoft)
Quando você cria os bancos de dados do servidor de relatório, **ReportServer** e **ReportServerTempDB**, em um SQL Server virtual executado em um cluster MSCS, o nome remoto no formato `<domain>\<computer_name>$` não pode ser registrado como logon no SQL Server. Se tiver configurado a conta de serviço do Servidor de Relatório de modo a exigir esse nome remoto para as conexões, os usuários não poderão se conectar aos diretórios /reports e /reportserver no Reporting Services. Por exemplo, a conta NetworkService interna do Windows requer tal nome remoto. Para evitar esse problema, use uma conta de domínio explícita ou um logon do SQL Server para se conectar aos bancos de dados do servidor de relatório.
## <a name="see-also"></a>Consulte Também
[Suporte ao navegador para Reporting Services e Power View](../../reporting-services/browser-support-for-reporting-services-and-power-view.md)
[Erros e eventos (Reporting Services)](../../reporting-services/troubleshooting/errors-and-events-reference-reporting-services.md)
[Solucionar problemas de recuperação de dados com relatórios do Reporting Services](../../reporting-services/troubleshooting/troubleshoot-data-retrieval-issues-with-reporting-services-reports.md)
[Solucionar problemas de assinaturas e entrega do Reporting Services](../../reporting-services/troubleshooting/troubleshoot-reporting-services-subscriptions-and-delivery.md)
[!INCLUDE[feedback_stackoverflow_msdn_connect](../../includes/feedback-stackoverflow-msdn-connect.md)]
| 144.625954 | 1,030 | 0.794046 | por_Latn | 0.999267 |
f4d472c5c38d20016f46503c748da87753c4b60c | 3,248 | md | Markdown | src/server/node_modules/socket.io/History.md | biojazzard/kirbout | 83b3c0885de67d796f4d8170e745aae32af0564c | [
"MIT"
] | 2 | 2018-07-31T02:40:16.000Z | 2019-01-17T17:12:47.000Z | src/server/node_modules/socket.io/History.md | biojazzard/kirbout | 83b3c0885de67d796f4d8170e745aae32af0564c | [
"MIT"
] | null | null | null | src/server/node_modules/socket.io/History.md | biojazzard/kirbout | 83b3c0885de67d796f4d8170e745aae32af0564c | [
"MIT"
] | null | null | null |
0.7.9 / 2011-08-12
==================
* Updated socket.io-client.
* Make sure we only do garbage collection when the server we receive is actually run.
0.7.8 / 2011-08-08
==================
* Changed; make sure sio#listen passes options to both HTTP server and socket.io manager.
* Added docs for sio#listen.
* Added options parameter support for Manager constructor.
* Added memory leaks tests and test-leaks Makefile task.
* Removed auto npm-linking from make test.
* Make sure that you can disable heartbeats. [3rd-Eden]
* Fixed rooms memory leak [3rd-Eden]
* Send response once we got all POST data, not immediately [Pita]
* Fixed onLeave behavior with missing clientsk [3rd-Eden]
* Prevent duplicate references in rooms.
* Added alias for `to` to `in` and `in` to `to`.
* Fixed roomClients definition.
* Removed dependency on redis for installation without npm [3rd-Eden]
* Expose path and querystring in handshakeData [3rd-Eden]
0.7.7 / 2011-07-12
==================
* Fixed double dispatch handling with emit to closed clients.
* Added test for emitting to closed clients to prevent regression.
* Fixed race condition in redis test.
* Changed Transport#end instrumentation.
* Leveraged $emit instead of emit internally.
* Made tests faster.
* Fixed double disconnect events.
* Fixed disconnect logic
* Simplified remote events handling in Socket.
* Increased testcase timeout.
* Fixed unknown room emitting (GH-291). [3rd-Eden]
* Fixed `address` in handshakeData. [3rd-Eden]
* Removed transports definition in chat example.
* Fixed room cleanup
* Fixed; make sure the client is cleaned up after booting.
* Make sure to mark the client as non-open if the connection is closed.
* Removed unneeded `buffer` declarations.
* Fixed; make sure to clear socket handlers and subscriptions upon transport close.
0.7.6 / 2011-06-30
==================
* Fixed general dispatching when a client has closed.
0.7.5 / 2011-06-30
==================
* Fixed dispatching to clients that are disconnected.
0.7.4 / 2011-06-30
==================
* Fixed; only clear handlers if they were set. [level09]
0.7.3 / 2011-06-30
==================
* Exposed handshake data to clients.
* Refactored dispatcher interface.
* Changed; Moved id generation method into the manager.
* Added sub-namespace authorization. [3rd-Eden]
* Changed; normalized SocketNamespace local eventing [dvv]
* Changed; Use packet.reason or default to 'packet' [3rd-Eden]
* Changed console.error to console.log.
* Fixed; bind both servers at the same time do that the test never times out.
* Added 304 support.
* Removed `Transport#name` for abstract interface.
* Changed; lazily require http and https module only when needed. [3rd-Eden]
0.7.2 / 2011-06-22
==================
* Make sure to write a packet (of type `noop`) when closing a poll.
This solves a problem with cross-domain requests being flagged as aborted and
reconnection being triggered.
* Added `noop` message type.
0.7.1 / 2011-06-21
==================
* Fixed cross-domain XHR.
* Added CORS test to xhr-polling suite.
0.7.0 / 2010-06-21
==================
* http://socket.io/announcement.html
| 33.833333 | 91 | 0.685961 | eng_Latn | 0.982291 |
f4d55cb9f6fa258b7bf841b8e288b0d2d9b835e7 | 21,379 | md | Markdown | src/content/translations/ar/developers/index.md | OnahProsperity/ethereum-org-website | 44c80dab94892261ff6ec93d9101af107cc4d16b | [
"MIT"
] | 4 | 2020-12-14T03:23:55.000Z | 2021-02-19T16:35:46.000Z | src/content/translations/ar/developers/index.md | OnahProsperity/ethereum-org-website | 44c80dab94892261ff6ec93d9101af107cc4d16b | [
"MIT"
] | 1 | 2020-11-25T13:43:00.000Z | 2020-11-25T13:43:00.000Z | src/content/translations/ar/developers/index.md | OnahProsperity/ethereum-org-website | 44c80dab94892261ff6ec93d9101af107cc4d16b | [
"MIT"
] | null | null | null | ---
title: إثيريوم للمطورين
description: أدلة، وموارد، وأدوات للمطورين العاملين على بناء وتطوير إيثريوم.
lang: ar
sidebar: true
sidebarDepth: 2
---
# موارد المطورين {#developer-resources}
<div class="featured">إرشادات، وموارد، وأدوات للمطورين العاملين على بناء وتطوير إيثريوم.</div>
## إبدأ هنا {#getting-started}
**اذا كنت حديث العهد في التطوير باستخدام إيثريوم، فأنت فى المكان الصحيح**. هذه المصادر المكتوبة من قبل مجتمع إيثريوم ستقدم إليك أساسيات حزمة إيثريوم ومفاهيم أساسية قد تكون مختلفة عن تطوير التطبيقات الأخرى التي تعرفها.
تريد البدء بالبرمجة الان؟ [إبدأ هنا](/ar/build/).
تربد مفاهيم أساسيه أولاً؟ راجع [مصادرنا التعليمية](/ar/learn/).
**مصادر مساعدة**
- [استعد للسرعة على إيثريوم](https://medium.com/@mattcondon/getting-up-to-speed-on-ethereum-63ed28821bbe) _7 أغسطس 2017 - Matt Condon_
- [إيثريوم بالتفصيل، الجزء الأول ](https://blog.zeppelin.solutions/ethereum-in-depth-part-1-968981e6f833) _11 مايو 2018 - Facu Spagnuolo_
- [إيثريوم بالتفصيل، الجزء الثاني ](https://blog.zeppelin.solutions/ethereum-in-depth-part-2-6339cf6bddb9) _24 يوليو 2018 - Facu Spagnuolo_
- [تطوير إيثريوم بالتطوير، الأجزاء 1-5](https://hackernoon.com/ethereum-development-walkthrough-part-1-smart-contracts-b3979e6e573e) _14 يناير 2018 - dev_zl_
- [إيثريوم 101، الأجزاء 1-7](https://kauri.io/collection/5bb65f0f4f34080001731dc2/ethereum-101) _13 فبراير 2019 - Wil Barnes_
- [درس التصويت العالمي على الترحيب بحزمة إيثريوم Dapp الكاملة](https://medium.com/@mvmurthy/full-stack-hello-world-voting-ethereum-dapp-tutorial-part-1-40d2d0d807c2) _فبراير 2019 - Mahesh Murthy_
- [إتقان إيثريوم - كتاب نصي شامل متوفر مجانًا على الإنترنت](https://github.com/ethereumbook/ethereumbook) _1 ديسمبر 2018 - Andreas Antonopoulos & Gavin Wood_
- [بوابة مطور إيثريوم - كل ما تحتاجه للبدء بالبناء على إيثريوم](https://ethereum.consensys.net/ethereum-dev-portal) _تُحدث دوريًا - ConsenSys_
- [تفكيك عقد بلغة Solidity](https://blog.zeppelin.solutions/deconstructing-a-solidity-contract-part-i-introduction-832efd2d7737) _13 أغسطس 2018 - Alejandro Santander & Leo Arias_
- [سلسلة دروس حزمة Dapp الكاملة ](https://kauri.io/collection/5b8e401ee727370001c942e3) _تُحدث دوريًا - Joshua Cassidy_
## العقود الذكية {#smart-contract-languages}
يشار إلى أي برنامج يعمل على الجهاز الافتراضي لإيثريوم (EVM)، عادةً باسم "عقد ذكي". أكثر اللغات شيوعًا لكتابة العقود الذكية على إيثريوم هي **Solidity** و**Vyper**، بالرغم من وجود [الآخرين قيد التطوير.](https://github.com/ConsenSys/ethereum-developer-tools-list#smart-contract-languages).
**Solidity -** **_اللغة الأكثر شيوعًا في إيثريوم، مستوحاة من C++, Python and JavaScript._**
- [التوثيق](https://solidity.readthedocs.io)
- [GitHub](https://github.com/ethereum/solidity/)
- [غرفة دردشة Solidity Gitter](https://gitter.im/ethereum/solidity/)
**Vyper -** **_لغة Vyper المرتكزة على الأمان لإيثريم، قائمة على Python._**
- [التوثيق](https://vyper.readthedocs.io)
- [Github](https://github.com/ethereum/vyper)
- [غرفة دردشة Vyper Gitter](https://gitter.im/ethereum/vyper)
**تبحث عن خيارات أخرى؟**
- [قائمة أدوات مطوّري الإيثريوم#SmartContractLanguages](https://github.com/ConsenSys/ethereum-developer-tools-list#smart-contract-languages)
## مصادر متخصصة {#language-specific-resources}
نحن نعمل على إنشاء مجموعة من الصفحات المتخصصة الخاصة بلغة معينة للمطورين للتعرف على إيثريوم بلغتهم البرمجية المفضلة.
- [إثيريوم لمطوري جافا](/ar/java/)
- [إثيروم لمطوري بايثون](/ar/python/)
- [إثيريوم لمطوري جافا سكربت](/ar/javascript/)
- [إثيريوم لمطوري قو](/ar/golang/)
- [إثيريوم لمطوري رست](/ar/rust/)
- [إثيريوم لمطوري دوت نت](/ar/dot-net/)
- المزيد قادم قريبا! ألا ترى لغتك هنا؟ [إفتح بلاغ](https://github.com/ethereum/ethereum-org-website/issues/new/choose)!
## أدوات المطورين {#developer-tools}
لدى إثيريوم عدد كبير ومتزايد من الأدوات لمساعدة المطورين على إنشاء تطبيقاتهم واختبارها ونشرها. ترد أدناه أشهر الأدوات لتساعدك على البدء. إذا كنت ترغب في التعمق أكثر، فتحقق من هذه [القائمة الشاملة](https://github.com/ConsenSys/ethereum-developer-tools-list).
### أطر عمل {#frameworks}
**Truffle -** **_بيئة لتطوير و اختبار وإنشاء العمليات الآلية وأدوات أخرى._**
- [trufflesuite.com](https://www.trufflesuite.com/)
- [GitHub](https://github.com/trufflesuite/truffle)
**Embark -** **_بيئة تطوير وإطار عمل للاختبار وأدوات أخرى متكاملة مع Ethereum، IPFS، وWhisper._**
- [التوثيق](https://embark.status.im/docs/)
- [GitHub](https://github.com/embark-framework/embark)
**Waffle -** **_إطار عمل لتطوير عقود ذكية متقدمة واختبارها (مرتكزة على ethers.js)_**
- [getwaffle.io](https://getwaffle.io/)
- [GitHub](https://github.com/EthWorks/Waffle)
**Etherlime -** **_هو إطار عمل قائم على Ethers.js لتطوير التطبيقات الموزعة ( Solidity & Vyper) ولنشر وتصحيح الأخطاء، الاختبار وأكثر من ذلك._**
- [المستندات](https://etherlime.readthedocs.io/en/latest/)
- [GitHub](https://github.com/LimeChain/etherlime)
### أدوات أخرى {#other-tools}
**Ethereum Grid - ** **_تطبيق سطح مكتب لتنزيل وتهيئة وتشغيل عملاء وأدوات إيثريوم_**
- [grid.ethereum.org](https://grid.ethereum.org)
- [GitHub](https://github.com/ethereum/grid)
**Hardhat -** **_منفذ المهام لمطوّري العقود الذكية على إيثريوم._**
- [hardhat.org](https://hardhat.org)
- [GitHub](https://github.com/nomiclabs/hardhat)
**OpenZeppelin SDK -** **_إطار عمل تطوير لبناء عقود ذكية قابلة للترقية، وإدارة تطبيقات العقود الذكية بأمان._**
- [OpenZeppelin SDK](https://openzeppelin.com/sdk/)
- [GitHub](https://github.com/OpenZeppelin/openzeppelin-sdk)
- [منتدى المجتمع](https://forum.openzeppelin.com/c/sdk)
**The Graph -** **_A بروتوكول لفهرسة بيانات إيثريوم و IPFS والاستعلام عنها باستخدام GraphQL._**
- [الرسم البياني](https://thegraph.com/)
- [مستكشف الرسم البياني](https://thegraph.com/explorer/)
- [التوثيق](https://thegraph.com/docs/)
- [GitHub](https://github.com/graphprotocol/)
- [Discord](https://thegraph.com/discord)
**Tenderly -** **_منصة لمراجعة العقود الذكية بسهولة من خلال تتبع الأخطاء والتنبيه و قياس الأداء وتحليلات مفصلة للعقود._**
- [tenderly.co](https://tenderly.co/)
- [GitHub](https://github.com/Tenderly)
- [Discord](https://discord.gg/eCWjuvt)
**Python Tooling -** **_مجموعة متنوعة من المكتبات للتفاعل مع إثيريوم عبر Python_**
- [py.ethereum.org](http://python.ethereum.org/)
- [web3.py GitHub](https://github.com/ethereum/web3.py)
- [دردشة web3.py](https://gitter.im/ethereum/web3.py)
**Brownie -** **_بيئة التطوير المستندة إلى Python وإطار الاختبار._**
- [التوثيق](https://eth-brownie.readthedocs.io/en/latest/)
- [GitHub](https://github.com/eth-brownie/brownie)
**web3j -** **_A Java/Android/Kotlin/Scala مكتبة التكامل مع إيثريوم._**
- [web3j.io](https://web3j.io)
- [GitHub](https://github.com/web3j/web3j)
- [المستندات](https://docs.web3j.io/)
- [Gitter](https://gitter.im/web3j/web3j)
**One Click Dapp -** **_قم بإنشاء واجهة مباشرة من ABI للتطوير والاختبار السريع._**
- [OneClickDapp.com](https://oneclickdapp.com)
- [مكون Truffle الإضافي](https://npmjs.org/package/oneclick)
- [مكون Remix الإضافي](https://github.com/pi0neerpat/remix-plugin-one-click-dapp)
- [GitHub](https://github.com/pi0neerpat/one-click-dapp)
**هل تبحث عن خيارات أخرى؟**
- [قائمة أدوات مطوري إثيريوم #Frameworks](https://github.com/ConsenSys/ethereum-developer-tools-list#frameworks)
## بيئات التطوير المتكاملة (IDEs) {#integrated-development-environments-ides}
**Ethereum Studio -** **_بيئة تطوير على الويب مثالية للمطورين الجدد الذين يرغبون فى تجربة العقود الذكية. Ethereum Studio مزود بقوالب متعددة ، تكامل مع MetaMask، ومسجل المعاملات، وماكينة ايثريوم افتراضية Ethereum Virtual Machine (EVM) مثبتة ف الويب لتساعدك على البدء ف البناء باقصى سرعه ممكنة._**
- [studio.ethereum.org](https://studio.ethereum.org)
- [superblocks.com/ethereum-studio](https://superblocks.com/ethereum-studio)
- [GitHub](https://github.com/SuperblocksHQ/ethereum-studio)
**Visual Studio Code -** **_بيئة التطوير المتكاملة اﻻحترافيه، يعمل على أى نظام تشغيل مع دعم إيثريوم بشكل رسمى._**
- [فيجوال ستوديو كود](https://code.visualstudio.com/)
- [أداة تطوير سلسلة كتلة Azure لإثيريوم](https://marketplace.visualstudio.com/items?itemName=AzBlockchain.azure-blockchain)
- [مكون طاولة عمل إضافي لسلسلة كتلة Azure](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/microsoft-azure-blockchain.azure-blockchain-workbench?tab=Overview)
- [نماذج أكواد](https://github.com/Azure-Samples/blockchain/blob/master/blockchain-workbench/application-and-smart-contract-samples/readme.md)
- [GitHub](https://github.com/microsoft/vscode)
**Remix -** **_بيئة تطوير متكاملة IDE قائمة على الويب ذات تحليل ثابت مدمج وجهاز سلاسل كُتل افتراضي للاختبار._**
- [remix.ethereum.org](https://remix.ethereum.org/)
**EthFiddle -** **_بيئة تطوير متكاملة IDE قائمة على الويب تتيح لك إمكانية كتابة العقد الذكي الخاص بك وتحويله ونشره. _**
- [ethfiddle.com](https://ethfiddle.com/)
- [Gitter](https://gitter.im/loomnetwork/ethfiddle)
**تبحث عن خيارات أخرى؟**
- [قائمة أدوات مطور إيثريوم #IDEs](https://github.com/ConsenSys/ethereum-developer-tools-list#ides)
## واجهات JavaScript APIs {#frontend-javascript-apis}
**Web3.js -** **_واجهات JavaScript على إثيريوم._**
- [التوثيق](https://web3js.readthedocs.io/en/1.0/)
- [GitHub](https://github.com/ethereum/web3.js/)
**Ethers.js -** **_تطبيق محفظة إيثريوم مكتملة مع الأدوات المساعدة باستخدام JavaScript و TypeScript._**
- [التوثيق](https://docs.ethers.io/ethers.js/html/)
- [GitHub](https://github.com/ethers-io/ethers.js/)
**light.js -** **_مكتبة JS تفاعلية عالية المستوى مُحسّنة ل light clients. _**
- [التوثيق](https://paritytech.github.io/js-libs/light.js/)
- [GitHub](https://github.com/paritytech/js-libs/tree/master/packages/light.js)
**Web3-wrapper -** **_بديل لWeb3.js مبرمج ب Typescript._**
- [التوثيق](https://0x.org/docs/web3-wrapper#introduction)
- [GitHub](https://github.com/0xProject/0x-monorepo/tree/development/packages/web3-wrapper)
**تبحث عن خيارات أخرى؟**
- [قائمة أدوات مطور إثيريوم #Frontend-Ethereum-APIs](https://github.com/ConsenSys/ethereum-developer-tools-list#frontend-ethereum-apis)
## Backend APIs {#backend-apis}
**Infura -** **_تقدم خدمة واجهة برمجة تطبيقات إيثريوم._**
- [infura.io](https://infura.io)
- [التوثيق](https://infura.io/docs)
- [GitHub](https://github.com/INFURA)
**Cloudflare Ethereum Gateway.**
- [cloudflare-eth.com](https://cloudflare-eth.com)
**Nodesmith -** **_وصول JSON-RPC API إلى الشبكة الرئيسية وشبكات الاختبار على إيثريوم._**
- [nodesmith.io](https://nodesmith.io/network/ethereum/)
- [التوثيق](https://nodesmith.io/docs/#/ethereum/apiRef)
**Chainstack -** **_نقطة اتصال إيثريوم متقاسمة ومخصصة كخدمة._**
- [chainstack.com](https://chainstack.com)
- [التوثيق](https://docs.chainstack.com)
## التخزين {#storage}
**IPFS -** **_نظام ملفات InterPlanetary هو نظام تخزين مرجعي وملفات لا مركزي لنظام إيثريوم._**
- [ipfs.io](https://ipfs.io/)
- [التوثيق](https://docs.ipfs.io/)
- [GitHub](https://github.com/ipfs/ipfs)
**Swarm -** **_منصة تخزين موزعة و توزيع المحتوى لكومة web3 إيثريوم._**
- [Swarm](https://ethersphere.github.io/swarm-home/)
- [GitHub](https://github.com/ethersphere/swarm)
**OrbitDB -** **_قاعدة بيانات النظير للنظير ﻻ مركزية مبنية على IPFS._**
- [التوثيق](https://github.com/orbitdb/field-manual)
- [GitHub](https://github.com/orbitdb/orbit-db)
## أدوات الأمان {#security-tools}
### تأمين العقود الذكية {#smart-contract-security}
**Slither -** **_اطار تحليل ثابت لسوليديتى Solidity مكتوب ب Python 3._**
- [GitHub](https://github.com/crytic/slither)
**MythX -** **_واجهة برمجة تطبيقات تحليل العقود الذكية فى إيثريوم._**
- [mythx.io](https://mythx.io/)
- [التوثيق](https://docs.mythx.io/en/latest/)
**Mythril -** **_أداة تحليل الأمن ل EVM bytecode._**
- [mythril](https://github.com/ConsenSys/mythril)
- [التوثيق](https://mythril-classic.readthedocs.io/en/master/about.html)
**SmartContract.Codes -** **_محرك بحث للتحقق من أكواد مصدر solidity._**
- [smartcontract.codes (alpha)](https://smartcontract.codes/)
- [التوثيق](https://github.com/ethereum-play/smartcontract.codes/blob/master/README.md)
**Manticore -** **_موجه أوامر باستخدام أداة تنفيذ رمزية على العقود الذكية والثنائيات._**
- [GitHub](https://github.com/trailofbits/manticore)
- [التوثيق](https://github.com/trailofbits/manticore/wiki)
**Securify -** **_فاحص أمني للعقود الذكية في إيثريوم._**
- [securify.chainsecurity.com](https://securify.chainsecurity.com/)
- [Discord](https://discordapp.com/invite/nN77ckb)
**ERC20 Verifier -** **_أداة تحقق تستخدم للتحقق مما إذا كان العقد يتوافق مع معيار ERC20._**
- [erc20-verifier.openzeppelin.com](https://erc20-verifier.openzeppelin.com)
- [المنتدى](https://forum.openzeppelin.com/t/online-erc20-contract-verifier/1575)
### التحقق الرسمي {#formal-verification}
**معلومات عن التحقق الرسمي**
- [كيفية التحقق الرسمي من عمل العقود الذكية](https://runtimeverification.com/blog/how-formal-verification-of-smart-contracts-works/) _20 يوليو 2018 - Brian Marick_
- [كيف يمكن للتحقق الرسمي أن يضمن صحة العقود الذكية](https://media.consensys.net/how-formal-verification-can-ensure-flawless-smart-contracts-cbda8ad99bd1) _29 يناير 2018 - Bernard Mueller_
**تبحث عن خيارات أخرى؟**
- [قائمة أدوات مطور إيثريوم #Security-Tools](https://github.com/ConsenSys/ethereum-developer-tools-list#security-tools)
## أدوات اختبار {#testing-tools}
**Solidity-Coverage -** **_أداة بديلة لتغطية أكواد solidity._**
- [GitHub](https://github.com/sc-forks/solidity-coverage)
**hevm -** **_تطبيق EVM المصنوع خصيصًا لاختبار الوحدات وتصحيح الأخطاء في العقود الذكية._**
- [GitHub](https://github.com/dapphub/dapptools/tree/master/src/hevm)
- [دردشة DappHub](https://dapphub.chat/)
**Whiteblock Genesis -** **_صندوق رمل للتطوير من النهاية إلى النهاية ومنصة اختبار لسلاسل الكتل._**
- [Whiteblock.io](https://whiteblock.io)
- [التوثيق](https://docs.whiteblock.io)
- [GitHub](https://github.com/whiteblock/genesis)
**تبحث عن خيارات أخرى؟**
- [قائمة أدوات مطور إيثريوم #Testing-Tools](https://github.com/ConsenSys/ethereum-developer-tools-list#testing-tools)
## مستكشفات الكتلة {#block-explorers}
مستكشفات الكتلة هي خدمات تتيح لك تصفح سلاسل الكتل الخاصة بإيثريوم (وشبكاتها التجريبية)، من خلال البحث عن معلومات حول معاملات محددة، وكتل، وعقود، وأنشطة أخرى على السلسلة.
- [Etherscan](https://etherscan.io/)
- [Blockscout](https://blockscout.com/)
- [Etherchain](https://www.etherchain.org/)
## شبكات اﻻختبار والصَنَابير {#testnets-and-faucets}
يوفر مجتمع إيثريوم شبكات اختبار متعددة. يتم استخدامها من قبل المطورين لاختبار تطبيقاتهم في ظل ظروف مختلفة قبل النشر على شبكة إيثريوم الرئيسية.
**Ropsten -** **_سلسة كتل قائمة على خوارزمية إثبات العمل، يمكن تعدين اختبار إيثر._**
- [صنبور اختبار إيثر](https://faucet.ropsten.be/)
**Rinkeby -** **_سلسة كتل قائمة على خوارزمية إثبات السلطة يديره فريق تطوير Geth._**
- [صنبور اختبار إيثر](https://faucet.rinkeby.io/)
- [صنبور عالمي](https://faucets.blockxlabs.com)
**Goerli -** **_سلسلة كتل قائمة على خوارزمية اثبات السلطه عبر العميل تم بناؤها وإدارتها بواسطة مجتمع Goerli_**
- [صنبور اختبار إيثر](https://faucet.goerli.mudit.blog/)
- [goerli.net](https://goerli.net/)
- [صنبور عالمي](https://faucets.blockxlabs.com)
## العملاء وتشغيل نقطة الالتقاء الخاصه بك {#clients--running-your-own-node}
تتكون شبكة إيثريوم من العديد من نقاط اﻻلتقاء "عقد" التي تدير برنامج عميل متوافق. أغلب نقاط الالتقاء تستخدم [Geth](https://geth.ethereum.org/) أو [Parity](https://www.parity.io/ethereum/) كل منها يمكن إعداده بطرق مختلفة وفقًا لاحتياجاتك.
### العملاء {#clients}
**Geth -** **_عملاء إثيريوم مبرمجين بلغة Go._**
- [GitHub](https://github.com/ethereum/go-ethereum)
- [دردشة Discord](https://discordapp.com/invite/nthXNEv)
**Parity -** **_عميل إيثريوم مبرمج بلغة Rust._**
- [parity.io](https://www.parity.io/)
- [GitHub](https://github.com/paritytech/parity-ethereum)
**Pantheon -** **_عميل إيثريوم مبرمج بلغة Java._**
- [pegasys.tech](http://pegasys.tech)
- [GitHub](https://github.com/PegaSysEng/pantheon/)
**Nethermind -** **_عميل إيثريوم مبرمج بلغة C# .NET Core._**
- [Nethermind.io](http://nethermind.io/)
- [GitHub](https://github.com/NethermindEth/nethermind)
- [Gitter](https://gitter.im/nethermindeth/nethermind)
### تشغيل نقطة اﻻتصال الخاصة بك {#running-your-own-node}
**Ethnode -** **_لتشغيل نقطة اتصال إيثريوم باستخدام (Geth أو Parity) للتطوير محليًا._**
- [GitHub](https://github.com/vrde/ethnode)
**مصادر لنقطة اتصال إيثريوم**
- [ورقة تزييف غعداد نقطة الاتصال](https://dev.to/5chdn/ethereum-node-configuration-modes-cheat-sheet-25l8) _5 يناير 2019 - Afri Schoeden_
**تبحث عن خيارات أخرى؟**
- [قائمة أدوات مطور إيثريوم #Ethereum-clients](https://github.com/ConsenSys/ethereum-developer-tools-list#ethereum-clients)
## أفضل الممارسات والأنماط والأنماط المضادة {#best-practices-patterns-and-anti-patterns}
### عقود ذكية {#smart-contracts}
**DappSys -** **_لبنات البناء الآمنة والبسيطة والمرنة للعقود الذكية._**
- [dapp.tools/dappsys](https://dapp.tools/dappsys/)
- [GitHub](https://github.com/dapphub/dappsys)
**OpenZeppelin Contracts -** **_مكتبة لتطوير عقد ذكى آمن._**
- [openzeppelin.com/contracts/](https://openzeppelin.com/contracts/)
- [GitHub](https://github.com/OpenZeppelin/openzeppelin-contracts)
- [منتدى المجتمع](https://forum.openzeppelin.com/c/contracts)
**aragonOS -** **_أنماط للتحديث والتحكم في الإذن._**
- [hack.aragon.org](https://hack.aragon.org/docs/aragonos-intro.html#aragonos-provides-the-following-functionality)
- [التوثيق](https://wiki.aragon.org/)
**سجل ضعف العقد الذكي**
- [سجل SWC](https://smartcontractsecurity.github.io/SWC-registry/)
- [GitHub](https://github.com/SmartContractSecurity/SWC-registry)
### الأمان {#security}
**دليل لأفضل ممارسات الأمان للعقود الذكية**
- [consensys.github.io/smart-contract-best-practices/](https://consensys.github.io/smart-contract-best-practices/)
- [GitHub](https://github.com/ConsenSys/smart-contract-best-practices/)
- [مجموعة مجمعة من توصيات الأمان وأفضل الممارسات](https://github.com/guylando/KnowledgeLists/blob/master/EthereumSmartContracts.md)
**معيار التحقق من أمان العقود الذكية (SCSVS)**
- [securing.github.io/SCSVS/](https://securing.github.io/SCSVS/)
**تبحث عن خيارات أخرى؟**
- [قائمة أدوات مطور إيثريوم #Patterns—best-practices](https://github.com/ConsenSys/ethereum-developer-tools-list#patterns--best-practices)
## دعم وتدريب المطور {#developer-support--training}
### التعلم العام {#general-learning}
**بورصة إيثريوم**
- [ethereum.stackexchange.com](https://ethereum.stackexchange.com/)
**ConsenSys Academy -** **_دورة تطوير مطوري إيثريوم من البداية إلى النهاية تعمل على مدار السنة._**
- [consensys.academy](https://consensys.net/academy/ondemand/)
**غرفة الدردشة الخاصه بـSolidity على Gitter**
- [gitter.im/ethereum/solidity](https://gitter.im/ethereum/solidity/)
**جميع غرف الدردشة الخاصه بإيثريوم على Gitter**
- [gitter.im/ethereum/home](https://gitter.im/ethereum/home)
**Chainshot -** **_دورات تعليم برمجة dapp على الويب._**
- [chainshot.com](https://www.chainshot.com/)
**Blockgeeks -** **_دورات عبر الإنترنت على تكنولوجيا سلاسل الكتل._**
- [courses.blockgeeks.com](https://courses.blockgeeks.com/)
**DappUniversity -** **_تعلم كيفية إنشاء التطبيقات اللامركزية على سلاسل كتلة خاصة بإيثريوم._**
- [DappUniversity.com](http://www.dappuniversity.com/)
**B9lab Academy -** **_موطن أقدم دورة تدريبية لمطوري Ethereum dapp ومزيد من التعلم للمدققين و مسؤلي الجودة. بما في ذلك المراقبة ومراجعة الكود. بما في ذلك المراقبة ومراجعة الكود._**
- [academy.b9lab.com](https://academy.b9lab.com)
### الألعاب التعليمية {#game-based-learning}
**Cryptozombies -** **_تعلم كيفية برمجة الألعاب على إيثريوم._**
- [Cryptozombies.io](https://cryptozombies.io/en/solidity)
**Ethernaut -** **_المناورات باستخدام Solidity حيث كل مستوى هو عقد ليتم اختراقها._**
- [ethernaut.openzeppelin.com](https://ethernaut.openzeppelin.com/)
**Capture the Ether -** **_لعبة أمان العقود الذكية فى إيثريوم.._**
- [capturetheether.com](https://capturetheether.com/)
## تصميم UI/UX {#uiux-design}
- [تحدي UX في إثيريوم](https://medium.com/ecf-review/challenge-of-ux-in-ethereum-122e1a33688d) _25 يونيو 2018 - Anna Rose_
- [تصميم سلسلة الكتل: ما الفر وما المعرض للخطر](https://media.consensys.net/designing-for-blockchain-whats-different-and-what-s-at-stake-b867eeade1c9) _22 مارس 2018 - Sarah Baker Mills_
**Rimble UI** **_- مكونات قابلة للتكيف ومعايير التصميم للتطبيقات اللامركزية._**
- [rimble.consensys.design](https://rimble.consensys.design)
- [GitHub](https://github.com/ConsenSys/rimble-ui)
## نماذج قياسية {#standards}
اعتمد مجتمع إيثريوم العديد من النماذج القياسية المفيدة للمطورين. عادةً ما يتم تقديمها كـ [ مقترحات تحسين لإيثريوم ](http://eips.ethereum.org/) (EIPs)، والتي يناقشها أعضاء المجتمع من خلال [عملية قياسية](http://eips.ethereum.org/EIPS/eip-1)
- [قائمة بال EIPs](http://eips.ethereum.org/)
- [EIP github repo](https://github.com/ethereum/EIPs)
- [مجلس مناقشة EIP](https://ethereum-magicians.org/c/eips)
- [نظرة عامة على حوكمة إثيريوم](https://blog.bmannconsulting.com/ethereum-governance/) _31 مارس 2019 - Boris Mann_
- [قائمة تشغيل جميع اجتماعاتEthereum Core Dev ](https://www.youtube.com/playlist?list=PLaM7G4Llrb7zfMXCZVEXEABT8OSnd4-7w)_(قائمة تشغيل على اليوتيوب)_
EIP معينة متعلقه بالمعايير على مستوى التطبيق (مثل تنسيق عقد ذكي قياسي)، والتي يتم تقديمها على أنها [طلبات إثيريوم للتعليق (ERC)](https://eips.ethereum.org/erc). العديد من ERCs هي معايير هامه تستخدم على نطاق واسع عبر النظام الإيكولوجي لإيثريوم.
- [قائمة بال ERCs](http://eips.ethereum.org/erc)
- [ERC20 - واجهة قياسية للعملات الرمزية](https://eips.ethereum.org/EIPS/eip-20)
- [ERC721 - واجهة قياسية للعملات الرمزية الغير قابلة للاستبدال](https://eips.ethereum.org/EIPS/eip-721)
| 42.587649 | 295 | 0.742037 | yue_Hant | 0.401049 |
f4d562f0c8f1f8d82ac2826a5f5669e434710e5b | 133 | md | Markdown | README.md | dhrubach/neural-network-manual | 9bed9a5fdde3eb56db25497169ec46a9dc0c547b | [
"MIT"
] | null | null | null | README.md | dhrubach/neural-network-manual | 9bed9a5fdde3eb56db25497169ec46a9dc0c547b | [
"MIT"
] | null | null | null | README.md | dhrubach/neural-network-manual | 9bed9a5fdde3eb56db25497169ec46a9dc0c547b | [
"MIT"
] | null | null | null | # neural-network-manual
multi-label classification of MNIST dataset using a vanilla neural network i.e without tensorflow or theanos
| 44.333333 | 108 | 0.834586 | eng_Latn | 0.974153 |
f4d57260323c58e57243c20a411275810769c6a3 | 1,376 | md | Markdown | _posts/2012-10-28-weak_ptr-comparison.md | nicoster/nicoster.github.io | 23e6baaea95e38c88dc3bb95eaedbb20a9fe2881 | [
"MIT"
] | null | null | null | _posts/2012-10-28-weak_ptr-comparison.md | nicoster/nicoster.github.io | 23e6baaea95e38c88dc3bb95eaedbb20a9fe2881 | [
"MIT"
] | null | null | null | _posts/2012-10-28-weak_ptr-comparison.md | nicoster/nicoster.github.io | 23e6baaea95e38c88dc3bb95eaedbb20a9fe2881 | [
"MIT"
] | null | null | null | ---
id: 666
title: weak_ptr comparison
date: 2012-10-28T20:36:12+00:00
author: nick
layout: post
guid: http://nick.luckygarden.org/?p=666
permalink: /weak_ptr-comparison/
tags:
- boost
- weak_ptr
- c++11
- shared_ptr
- owner_less
---
set<weak_ptr<int> > ints;
这行代码在 c++11 上编译出现错误. 而使用 boost, tr1 中的 `weak_ptr` 则编译通过. 原因在于 c++11 中的 `weak_ptr` 不支持 std::less. 而另外两个则支持. c++11 提供了 `std::owner_less` 解决这个问题. 所以
std<weak_ptr<int>, owner_less<weak_ptr<int>>> ints;
就可以在 c++11 正常工作了.
这里需要讨论一下 `weak_ptr` 的比较问题. 其实已经有一些文章讨论这个, 下面是其中之一.
<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1590.html>
smart ptr 的比较没有看起来的那么简单. 先看一下 `shared_ptr`/`weak_ptr` 的通常的内部实现:
图片来自 <a href="http://view.officeapps.live.com/op/view.aspx?src=http%3a%2f%2fecn.channel9.msdn.com%2fevents%2fGoingNative12%2fGN12STL11.pptx" title="这里">这里</a>
它有两个指针, `_Ptr` 指向真正的对象, `_Rep` 指向所谓的 control block, 其中记录着 `shared_count`, `weak_count`. 对于 `shared_ptr` 来说, 有两种方式来比较大小. value-based, owner-based. 也就是分别比较 `_Ptr` 或者 `_Rep` 的值. 而 `weak_ptr` 则不能简单的比较 `_Ptr`, 因为 `weak_ptr` 随时可能 expire, `_Ptr` 的值从而改变(清零). 所以就只能比较 `_Rep`, 也就是 control block 的地址. 一般的, 为了和 `weak_ptr` 的实现一致, `shared_ptr` 也采用 owner-based 的机制.
上面提到的 `owner_less` 会调用 `shared_ptr`/`weak_ptr` 的成员函数 `owner_before()`, 其实现就是比较 control block 的地址.
| 37.189189 | 350 | 0.730378 | yue_Hant | 0.75648 |
f4d596338e4bcd9f1b834177c0a532becdb380e1 | 3,612 | md | Markdown | articles/media-services/latest/migrate-v-2-v-3-differences-feature-gaps.md | pmsousa/azure-docs.pt-pt | bc487beff48df00493484663c200e44d4b24cb18 | [
"CC-BY-4.0",
"MIT"
] | 15 | 2017-08-28T07:46:17.000Z | 2022-02-03T12:49:15.000Z | articles/media-services/latest/migrate-v-2-v-3-differences-feature-gaps.md | pmsousa/azure-docs.pt-pt | bc487beff48df00493484663c200e44d4b24cb18 | [
"CC-BY-4.0",
"MIT"
] | 407 | 2018-06-14T16:12:48.000Z | 2021-06-02T16:08:13.000Z | articles/media-services/latest/migrate-v-2-v-3-differences-feature-gaps.md | pmsousa/azure-docs.pt-pt | bc487beff48df00493484663c200e44d4b24cb18 | [
"CC-BY-4.0",
"MIT"
] | 17 | 2017-10-04T22:53:31.000Z | 2022-03-10T16:41:59.000Z | ---
title: Lacunas de características entre a Azure Media Services V2 e v3
description: Este artigo descreve as lacunas de funcionalidade entre a Azure Media Services V2 a v3.
services: media-services
author: IngridAtMicrosoft
manager: femila
ms.service: media-services
ms.devlang: multiple
ms.topic: conceptual
ms.tgt_pltfrm: multiple
ms.workload: media
ms.date: 03/25/2021
ms.author: inhenkel
ms.openlocfilehash: 564f3127fc6901695890daa520152a7aa1a2337f
ms.sourcegitcommit: edc7dc50c4f5550d9776a4c42167a872032a4151
ms.translationtype: MT
ms.contentlocale: pt-PT
ms.lasthandoff: 03/30/2021
ms.locfileid: "105962973"
---
# <a name="feature-gaps-between-azure-media-services-v2-and-v3"></a>Lacunas de características entre a Azure Media Services V2 e v3
<hr color="#5ea0ef" size="10">
Esta parte da orientação de migração dá-lhe informações detalhadas sobre as diferenças entre as APIs V2 e V3.
## <a name="feature-gaps-between-v2-and-v3-apis"></a>Lacunas de características entre APIs V2 e V3
A API V3 tem as seguintes lacunas de características com a API V2. Algumas das funcionalidades avançadas da Norma Media Encoder em APIs V2 não estão atualmente disponíveis em V3:
- Inserir uma faixa de áudio silenciosa quando a entrada não tem áudio, uma vez que já não é necessário com o Azure Media Player.
- Inserir uma faixa de vídeo quando a entrada não tem vídeo.
- Eventos ao vivo com transcoding atualmente não suportam inserção de ardósia a meio do fluxo e inserção de marcador de anúncios através da chamada API.
- A Azure Media Premium Encoder deixará de ser suportado na V2. Se estiver a usá-lo para codificação HEVC de 8 bits, utilize o novo suporte HEVC no Standard Encoder.
- Adicionámos suporte para mapeamento de canais de áudio ao codificar Standard. Consulte [o Áudio nos Serviços de Comunicação Encoding Swagger documentação](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/mediaservices/resource-manager/Microsoft.Media/stable/2020-05-01/Encoding.json).
- Se estiver a utilizar funcionalidades avançadas ou formatos de saída do produto licenciado por terceiros, como mXF ou ProRes, utilize a solução Azure Partner da Telestream, que será transacional no momento da reforma do V2. Alternativamente, pode utilizar a Imagine Communications, ou [Bitmovin](http://bitmovin.com).
- A propriedade "conjunto de disponibilidade" no Streaming Endpoint em V2 já não é suportada. Consulte o projeto de amostra e orientação para a entrega [de VOD de Alta Disponibilidade](./architecture-high-availability-encoding-concept.md) na API V3.
- Nos Serviços de Comunicação Social V3, o FairPlay IV não pode ser especificado. Embora não tenha impacto nos clientes que utilizam os Media Services tanto para a embalagem como para a entrega de licenças, pode ser um problema quando se utiliza um sistema de DRM de terceiros para entregar as licenças FairPlay (modo híbrido).
- A encriptação de armazenamento do lado do cliente para proteção dos ativos em repouso foi removida na API V3 e substituída pela encriptação do serviço de armazenamento para dados em repouso. As APIs V3 continuam a trabalhar com os ativos encriptados de armazenamento existentes, mas não permitem a criação de novos.
## <a name="terminology-and-entity-changes"></a>Terminologia e alterações de entidades
Consulte terminologia e alterações [de entidades](migrate-v-2-v-3-differences-terminology.md) para alterações adicionais à API.
| 66.888889 | 327 | 0.801218 | por_Latn | 0.997181 |
f4d5c7e536add2a7b38c50ab8b806d777f9f5d1b | 2,841 | md | Markdown | _posts/2016-09-19-Shailk-Prom-2016-Style-3778-NAVY-2016.md | promsome/promsome.github.io | 69236f5c8f4d9591eec55dafa47ce21914b51851 | [
"MIT"
] | null | null | null | _posts/2016-09-19-Shailk-Prom-2016-Style-3778-NAVY-2016.md | promsome/promsome.github.io | 69236f5c8f4d9591eec55dafa47ce21914b51851 | [
"MIT"
] | null | null | null | _posts/2016-09-19-Shailk-Prom-2016-Style-3778-NAVY-2016.md | promsome/promsome.github.io | 69236f5c8f4d9591eec55dafa47ce21914b51851 | [
"MIT"
] | null | null | null | ---
layout: post
date: 2016-09-19
title: "Shailk Prom 2016 Style 3778 NAVY 2016"
category: Shailk
tags: [Shailk,2016]
---
### Shailk Prom 2016 Style 3778 NAVY
Just **$599.99**
### 2016
<table><tr><td>BRANDS</td><td>Shailk</td></tr><tr><td>Years</td><td>2016</td></tr></table>
<a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208037/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
<!-- break --><a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208038/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208039/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208040/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208041/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208042/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208043/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208044/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208045/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html"><img src="//img.readybrides.com/208036/shailk-prom-2016-style-3778-navy.jpg" alt="Shailk Prom 2016 Style 3778 NAVY" style="width:100%;" /></a>
Buy it: [https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html](https://www.readybrides.com/en/shailk/81923-shailk-prom-2016-style-3778-navy.html)
| 118.375 | 250 | 0.726153 | yue_Hant | 0.349306 |
f4d6ac0a41adf19f024c6ea5ea6f8e61c4765601 | 5,238 | md | Markdown | packages/nifty-news/README.md | alibama/datamodels | 6486bbbe1d1f41a10b73a7d92f8fc09674ebcc25 | [
"Apache-2.0",
"MIT"
] | null | null | null | packages/nifty-news/README.md | alibama/datamodels | 6486bbbe1d1f41a10b73a7d92f8fc09674ebcc25 | [
"Apache-2.0",
"MIT"
] | null | null | null | packages/nifty-news/README.md | alibama/datamodels | 6486bbbe1d1f41a10b73a7d92f8fc09674ebcc25 | [
"Apache-2.0",
"MIT"
] | null | null | null | # NiFTy News DataModel
DataModel implementation of the **NiFTy News** schema and definition specified here and inspired by https://schema.org/Event .
## Installation
```sh
npm install -D @datamodels/nifty-news
```
## Rationale
The **NiFTy News** contains a News or Blogs's basic information designed around sustainability, confidentiality, and simplicity of asserting accuracy through the ability to attach IPFS data for use in NFT creation. Leveraging the schema.org/Events space simplifies the process, however we use it aware of the limitations in its current design, as well as the opportunities to simplify this process using Ceramic's off-the-shelf features.
https://www.brightID.org is planned for integration in safely anonymizing the content with proving some anti-sybil security
https://www.foam.space/ is planned for integration in geospatially organizing this content
by building the product with BrightID compatibility we'll have a process for connecting content without risk of associating names or other biometric data that might compromise the safety of the news person
Ceramic also obviates some of the products in the schema.org profile. For instance the translator field - an integral asset tag for multi-language products - may be stored in the ceramic tile as the NiFTy News object is updated
**More provably first-hand accounts helps raise the bar in journalistic integrity.**: Obtaining accurate news from areas of conflict is difficult for many reasons. NiFTy News attempts to provide more equitable compensation, improved personal security, and more tamper-proof tools for people in many fields who may be familiar with these challenges.
## Schema
* description | description field
* image | a thumbnail image field
* location | wgs84 - pull from foam.space later, use peermaps.org for pinning?
* startDate | iso 8601
* endDate | iso 8601
* BrightID | weighted DID reference
* inLanguage | IETF BCP 47 standard (EN-US vs EN-GB parsible)
* media | IPFS
* additionalType | an optional linked data space
### [NiFTy News](./schemas/nifty-news.json)
The NiFTy News schema defines the format of a document that contains the properties listed below. Properties not defined in the schema _cannot_ be included in the Basic Profile, however the schema can always be updated via a new CIP.
| Property | Description | Value | Max Size | Required | Example |
| ------------------ | ------------------------------ | -------------------------------------------------------------------------------------- | -------- | -------- | ---------------------------- |
| `description` | what's going on | string | 420 char | optional | There's something strange, in the neighborhood |
| `image` | an image for the thumbnail | Image a tuhmbnail image | | optional | |
| `location` | WGS 84 ideally pulled from https://www.foam.space/ | unicode | 2 char | optional |
| `startDate` | a date and time of things starting | [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) | 19 char | optional | 2007-04-05T14:30 |
| `endDate` | a date and time of things ending | [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) | 19 char | optional | 2007-04-05T14:30 |string | 240 char | optional | http://ceramic.network |
| `inLanguage` | language being used - conform to IETF BCP 47 standard and reduce to two char hyphen two char format | string | 5 char | optional | en-en |
| `BrightID` | a reference to the BrightID identifier | string | 140 char | optional |
| `media` | associated media | ipfs file | 100MB? | optional | big file |
| `additionalType` | optional extension tool | CID Schema reference | ??? | optional | additional reference file to simplify upgrades
## [Discussion](https://github.com/ceramicstudio/datamodels/discussions/25)
## [Apologies]
The NiFTy News schema attempts to provide a reduced approach to the schema.org standard that, while inclusive and expansive, should probably be accorded a broader meta-data standard to then include mediawiki or other standard development products specific to the niche ecosystem. and the whole damn thing should be done with silly little widgets.
## License
Dual licensed under MIT and Apache 2
| 79.363636 | 437 | 0.582283 | eng_Latn | 0.991083 |
f4d7de585ed48a3618c76acb4d2a4fc8e4f02517 | 478 | md | Markdown | en/chapters/database/other-db.md | fraxken/ebook_nodejs | 823df28d1b9b81a9f43f9c379f98e9a9394592b7 | [
"MIT"
] | 4 | 2021-12-11T16:08:00.000Z | 2022-02-09T12:31:43.000Z | en/chapters/database/other-db.md | fraxken/ebook_nodejs | 823df28d1b9b81a9f43f9c379f98e9a9394592b7 | [
"MIT"
] | null | null | null | en/chapters/database/other-db.md | fraxken/ebook_nodejs | 823df28d1b9b81a9f43f9c379f98e9a9394592b7 | [
"MIT"
] | null | null | null | # 💾 Database
## Other databases
A list of other solutions you can explore:
- [LevelDB](https://github.com/Level/level) - fast key-value storage
- [Neo4j](https://neo4j.com/developer/javascript/)
- [RethinkDB](https://rethinkdb.com/)
- Firebase
Do not hesitate to consult the [following awesome list](https://github.com/agarcialeon/awesome-database) which contains many database solutions.
---
⬅️ [💾 Database: SQLite](./sqlite.md) |
➡️ [💾 Database: ORM or not ?](./orm.md)
| 26.555556 | 144 | 0.709205 | eng_Latn | 0.485238 |
f4d86860f74517f93a4ee9d58e2c171c90b54751 | 636 | md | Markdown | catalog/gamurakan/en-US_gamurakan.md | htron-dev/baka-db | cb6e907a5c53113275da271631698cd3b35c9589 | [
"MIT"
] | 3 | 2021-08-12T20:02:29.000Z | 2021-09-05T05:03:32.000Z | catalog/gamurakan/en-US_gamurakan.md | zzhenryquezz/baka-db | da8f54a87191a53a7fca54b0775b3c00f99d2531 | [
"MIT"
] | 8 | 2021-07-20T00:44:48.000Z | 2021-09-22T18:44:04.000Z | catalog/gamurakan/en-US_gamurakan.md | zzhenryquezz/baka-db | da8f54a87191a53a7fca54b0775b3c00f99d2531 | [
"MIT"
] | 2 | 2021-07-19T01:38:25.000Z | 2021-07-29T08:10:29.000Z | # Gamurakan
- **type**: manga
- **volumes**: 2
- **original-name**: 臥夢螺館
## Tags
- mystery
## Authors
- Fukuyama
- Youji (Story & Art)
## Sinopse
Lawyer Aoi Midorikawa is drawn from the torpor of his office by an old woman who wishes to got leave a tenant bad debtor. On the spot, it notes that lthe rented apartment is closed by a door padlocked from beginning to end and that the handle oozes a thick sticking liquid. Here begins an allucinating story full of mistery.
## Links
- [My Anime list](https://myanimelist.net/manga/13706/Gamurakan)
| 25.44 | 324 | 0.713836 | eng_Latn | 0.978152 |
f4d881aea9967f01a0b96e224e9a2324e1a69f56 | 762 | md | Markdown | docs/usual-workflow/Extension functions over usual class.md | Tetraquark/kotlin-swift-interopedia | fb6be70ae003285f270482b56e0b28bdd3fb2f5f | [
"MIT"
] | 85 | 2021-09-03T06:18:17.000Z | 2022-02-02T08:23:50.000Z | docs/usual-workflow/Extension functions over usual class.md | Tetraquark/kotlin-swift-interopedia | fb6be70ae003285f270482b56e0b28bdd3fb2f5f | [
"MIT"
] | null | null | null | docs/usual-workflow/Extension functions over usual class.md | Tetraquark/kotlin-swift-interopedia | fb6be70ae003285f270482b56e0b28bdd3fb2f5f | [
"MIT"
] | 2 | 2021-09-17T13:54:45.000Z | 2021-12-17T11:53:46.000Z | ## Extension function over usual class
| Статус | Ожидание | Реальность |
| ------------------ | -------------------------------------------- | ------------------------------------------- |
| :white_check_mark: | Функцию можно использовать на объекте класса | Реальность совпадает с ожиданием :thumbsup: |
### Пояснения
Объявим в Kotlin-коде extension-функцию над кастомным типом:
```kotlin
// UsualClassExt.kt
fun UsualClass.extensionFunction() {
// do something
}
```
На стороне Swift-а мы сможем использовать эту функцию аналогично Kotlin-у, на объекте нужного класса:
```swift
func example() {
UsualClass().extensionFunction()
}
```
---
[Оглавление](/README.md) | 26.275862 | 115 | 0.543307 | rus_Cyrl | 0.640756 |
f4d8e05e64304dd3d5b6c7602979cb1b0e9e9426 | 1,286 | md | Markdown | README.md | DevGearOrg/dg_starter_drupal | c998d1a6a8b1599d5b0ddad3113b0a8b041cb85d | [
"MIT"
] | null | null | null | README.md | DevGearOrg/dg_starter_drupal | c998d1a6a8b1599d5b0ddad3113b0a8b041cb85d | [
"MIT"
] | null | null | null | README.md | DevGearOrg/dg_starter_drupal | c998d1a6a8b1599d5b0ddad3113b0a8b041cb85d | [
"MIT"
] | null | null | null | # DevGear Drupal Starter
DevGear Starter Kit for Drupal projects with Docker.
Based on [wodby/docker4drupal](https://github.com/wodby/docker4drupal) project but simplified.
*Read this in other languages: [English](README.md), [Русский](README.ru.md).*
## Prerequirements:
We're using some popular tools to help acheave your goals:
1. Install Docker for your operational system: [Docker for Developers](https://www.docker.com/get-started)
2. Make sure you have working GNU Make or use makefile as "cheatsheet"
3. You should use Git to clone this StarterKit
## Quick start:
1. Create new project based on current file structure and content
2. Step into this folder in termial and execute `make run` command
3. Check result in your web browser following http://localhost
4. PhpMyAdmin runs on http://localhost:8080
## Makefile aliases reference:
- `make run` - wrapper around `docker-compose up`. Prepares and starts necessary containt
- `make stop` - suspends all working containers from this app
- `make restart` - stop and run alias
- `make prune` - stops and removes all containers and data images from this project
- `make clear` - like prune but deletes images
- `make drush` - runs Drush commands. Pass arguments right here
- `make logs` - connects to compose logs stram
| 40.1875 | 106 | 0.763608 | eng_Latn | 0.975299 |
f4d9159bd59227ab2999b3e9c2a11b02477a6d08 | 1,027 | md | Markdown | README.md | astridlujo/yolked | 45a0d9925b357842598721c81e5cf76bdd7c5859 | [
"Apache-2.0"
] | null | null | null | README.md | astridlujo/yolked | 45a0d9925b357842598721c81e5cf76bdd7c5859 | [
"Apache-2.0"
] | null | null | null | README.md | astridlujo/yolked | 45a0d9925b357842598721c81e5cf76bdd7c5859 | [
"Apache-2.0"
] | null | null | null | # Yolked App (REACT NATIVE)
This is the repository for the Yolked pantry app for Android and iOS, developed in React Native. Some of the key aspects of this app are:
- Able to Log In, Log Out and Sign Up to use the app.
- Users can search a recipe, see the instructions, ingredients and Nutritional value.
- Users can search for a food items and see their nutritional Value.
- There is a pantry where users can add food items and their quantity.
- A settings options where users can change their settings and search input.
# What was used to develop this project
- Created the UI design by using Adobe XD
- React Native as the main framework.
- Expo CLI to run the application.
- CSS, for styling
- React Paper as a helper UI.
- Firebase as a database.
- React Nativagtion to create the bottom menu and change the App screens.
- EDAMAM as the API for the project.
# See the App
You can see a video of the yolked app by following this link: https://drive.google.com/file/d/1P2q7nT_111zkHtV_Pms_AL6LTfuJjndB/view?usp=sharing | 44.652174 | 144 | 0.770204 | eng_Latn | 0.998111 |
f4d91eb368b769d8274529e9420644bb47cfe0e9 | 19,077 | md | Markdown | README.md | sei-nmvanhoudnos/Juneberry | a4824bc74180134a9ef5326addbc83110177102c | [
"MIT"
] | null | null | null | README.md | sei-nmvanhoudnos/Juneberry | a4824bc74180134a9ef5326addbc83110177102c | [
"MIT"
] | null | null | null | README.md | sei-nmvanhoudnos/Juneberry | a4824bc74180134a9ef5326addbc83110177102c | [
"MIT"
] | null | null | null | README
==========
# Introduction
Juneberry improves the experience of machine learning experimentation by providing a framework for automating the
training, evaluation and comparison of multiple models against multiple datasets, reducing errors and improving reproducibility.
This README describes how to use the Juneberry framework to execute machine learning tasks.
Juneberry follows a (mostly) declarative programming model composed of sets of config files
(dataset, model, and experiment configuration) and python plugins for things such
as model construction and transformation.
This README contains:
* Steps for running a simple test of your Juneberry installation
* A tutorial on running a simple experiment by hand
* Details about building your own models
# TL;DR
To see if the repo is installed and working properly
1) Clone the Juneberry repository
1) `cd juneberry` (or whatever directory you cloned the repository to)
1) `pipenv install -e . --dev`
1) `pipenv run jb_train -w . -d . tabular_multiclass_sample`
When the training is complete, you should see a training accuracy of 97.67% in the final epoch.
NOTE: When running the environment, all the Juneberry tools (scripts starting with jb_) are automatically placed
in your PATH.
## Other Environments
Juneberry is a fully-featured python package and can be installed into any environment such as venv. Once python has
been installed, simply install Juneberry using `pip install -e .` from within the juneberry directory. This will
set up the package, including its dependencies, and add the bin directory to your path.
# Experiment Overview
Juneberry uses a workspace directory structure to hold models and experiments. Most
of the configuration is done via files.
```
<workspace root>/
data_sets/ - JSON config files describing datasets are listed here.
<data-set-name>.json
models/ - Files related to models, including JSON config files describing models, are listed here.
<model-name>
config.json
... experiment specific artifacts (logs, visualizations, etc.) ARE PLACED here ...
experiments/ - experiments are sets of models with their tests
<experiment-name>
config.json
... output such as logs and trained models ARE PLACED here ...
<workspace package> - [OPTIONAL] Python code goes here and should be available for import
<subpackage>
<DATA_ROOT>/
datagroup_x/
version_x/
cache/
```
Juneberry scripts need to know the path to the workspace and data directories described above. These paths can
be provided on a per-script basis using the `-w` and `-d` switches respectively. Normally it is much more
convenient to specify these (and other settings) once via a `juneberry.ini` file, described below in
"Configuration via juneberry.ini". If you wish to use a `juneberry.ini` instead of providing the workspace and
data root directories via command line switches, you are expected to create your own `juneberry.ini` file in an
appropriate location. Refer to the "Search Order" section of "Configuration via juneberry.ini" for the relevant
details.
# WORKSPACE Directory
The workspace path can be set via the `-w` command line switch or more generally via `workspace_root` in your
`juneberry.ini`.
### Models (model directory)
A model directory (user specified name in models) should contain a config file that describes
an architecture to build, configuration changes to that architecture, and the datasets
used to train the model. It will also contain the trained model, log files, plots, and other
files specifically associated with this model.
One of the core concepts of Juneberry is the model. Our definition of model is the combination of an architecture
configured with hyperparameters, trained using a particular dataset (modified by transformers as needed),
a loss function, an optimizer, a training process (e.g. adversarial, validation splitting) which results
in a trained model, and resulting output files. Together, these components form what we refer to as the model.
The central part of the model is the "training config" (config.json) which describes the components of the model.
Constituent parts such as architecture code or dataset descriptions are stored elsewhere,
but the model config specifies which of these parts go in to the model.
### Datasets (data_set directory)
Dataset configs are JSON files that describe where data elements come from, and how that data should be labeled.
Data configs allow you to define subsets of source directories, how they are ordered, and how the data should be
split or transformed (such as image resizing). Together these options allow you to construct a unique and traceable
data input set. Each JSON file is a different dataset configuration. All data paths in the JSON file should be
relative to a single data root. This root is provided to Juneberry via the `juneberry.ini` file or the `-d`
command line switch.
### Experiments (experiments directory)
Experiments group multiple models together for the purpose of comparing their outputs, providing
the computational basis for scientific experiments. Each experiment should contain a JSON config file describing
the models in the experiment, the datasets to test against those models, and the reports to produce using those
trained models.
## DATA_ROOT Directory Path
The data root directory path can be set via the `-d` command line switch or via the `data_root` field in your
`juneberry.ini` file.
The DATA_ROOT directory is where input data files live. For more details on the exact DATA_ROOT structure,
refer to [data_file_structure.md](./juneberry/documentation/data_file_structure.md)
in the Juneberry documentation directory.
### datagroup_x (optional)
A group of data files grouped together under some common attributes.
### version_x (optional)
Datagroups can be versioned. If they are, you will see version directories within the datagroup directory.
## Configuration via juneberry.ini
### Content
The juneberry ini file can contain the following fields:
```
[DEFAULT]
workspace_root = /path/to/workspace
data_root = /path/to/data
tensorboard_root = /path/to/tensorboard/data
```
The Juneberry framework is designed to work with "workspaces" or "data roots"
that are external to the Juneberry code itself. This allows the workspace (which may be small and versioned)
to be independent.
The workspace (specified by workspace_root) is the data associated with the actual experiments. It
contains references to datasets, transforms for the input data, python files for constructing models,
hyperparameters to those models, references to loss functions or optimizers, and references to
visualizations or other reporting analytics.
The data root (specified by data_root) is the root level directory containing your input data. Paths in
the dataset config file will be treated as relative to this "data root" directory.
The tensorboard root (specified by tensorboard_root) controls where tensorboard summary data will be
written during training. If a tensorboard root is not provided, then the training data will not be
logged for tensorboard.
If an ini file is not specified, the path to the "workspace root" and "data root" can be passed to the
scripts via the -w and -d switches respectively.
### Search Order
Juneberry will inspect several locations for a workspace and data root location until a value is found. Only the
first value found will be used; others will be ignored on a per value basis. For example, one could specify
the data_root in a juneberry.ini in the current working directory, with a workspace root in the juneberry.ini in
the home directory. The command line switches -w and -d would override either of these values taken from the
ini files. The hierarchy:
1) Command line switches `-w` or `-d`.
1) ./juneberry.ini - The _current_ working directory.
1) ~/juneberry.ini - The home directory.
1) File path (not directory) specified in $JUNEBERRY_CONFIG environment variable
## Example
Juneberry provides a sample model used for a small system test. The model file is located in
[`models/imagenet_224x224_rgb_unit_test_pyt_resnet50`](./models/imagenet_224x224_rgb_unit_test_pyt_resnet50)
and uses the dataset
[`data_sets/imagenet_unit_train.json`](data_sets/imagenet_unit_train.json)
to 'train' the model and
[`data_sets/imagenet_224x224_rgb_unit_test.json`](./data_sets/imagenet_unit_test.json)
to test the model. The output is stored in
[`models/imagenet_224x224_rgb_unit_test_pyt_resnet50`](./models/imagenet_224x224_rgb_unit_test_pyt_resnet50).
The [`pytorchSystemTest`](./experiments/pytorchSystemTest) experiment will
use this model, along with the data sets, to generate two different ROC curves.
# Tutorial
## Step 1 - Create a dataset specification (data spec) file
Example file: [data_sets/imagenet_unit_train.json](data_sets/imagenet_unit_train.json)
Dataset specifications follow the format described in
[documentation/data_set_specification.md](./juneberry/documentation/data_set_specification.md)
in the repository. These files are used to describe a dataset
which is composed of image directories, labels, sampling criteria
and **desired** image properties. Remember that the paths are relative
to an externally specified 'data root.'
The script [jb_preview_filelist](./bin/jb_preview_filelist) can be used to preview the files that
will be selected by a specific dataset specification. Provide the dataset and config
to the script and it will output a csv ('file_list_preview.csv' by default) listing the files.
```jb_preview_filelist <data_root> data_sets/imagenet_224x224_rgb_unit_retrain.json```
## Step 2 - Create a training configuration file.
Example training config file:
[models/imagenet_224x224_rgb_unit_test_pyt_resnet50/config.json](./models/imagenet_224x224_rgb_unit_test_pyt_resnet50/config.json)
Training specifications follow the format described in
[documentation/training_configuration_specification.md](./juneberry/documentation/training_configuration_specification.md);
they must be named "config.json" and must be placed in model directory inside the "models" directory.
These config files specify details such as model architecture, hyperparameters, datasets,
transforms, etc. See the specification for details on each property of the
training config.
## Step 3 - Train
This step will demonstrate how to use the training script to train a model. The most commonly
used training script is [jb_train](./bin/jb_train), which requires a
model name (i.e. the name of a directory in the models directory containing a valid config.json
file) as input. The output of the training process is a trained model and training metrics in an
output JSON file.
**NOTE:** To train with TensorBoard activated, either set a system environment variable
```TENSORBOARD_DIR="path/to/dir"``` or configure the tensorboard root in a juneberry.ini.
The training script requires the configured workspace root and data root to be set
via the ini file or via command line. The following command demonstrates how to use
the training script to train a model, assuming the workspace and data roots are set via
a juneberry.ini file:
```jb_train. imagenet_224x224_rgb_unit_test_pyt_resnet50```
The script provides ongoing status to the console (which can be silenced)
as well as the model, log files and visual summaries. Some output files you may see:
* model.pt - The trained model.
* train_out.json - A JSON file containing all the output training data.
* train_out.png - Visualization of the accuracy and loss during training.
* log_train.txt - The log file from training.
Dry run mode offers an opportunity to observe what actions the training script would
perform without actually performing the training. You can initiate dry run mode by
adding the `--dryrun` argument to the training command. In dry run mode, Juneberry
will log messages about what actions it would have taken using a `<< DRY_RUN >>` prefix.
The training output will be saved to a logfile named `log_train_dryrun.txt`.
### Notes on Dataset Selection (Images)
During training, images are loaded based on the specified dataset configuration.
The dataset config describes the sources of data to pull from, their labels,
and how the data should be sampled. The training configuration specifies
how the validation process should occur. The order in which these data items are
processed is impacted by any seed values specified in the configs. These seed values
are used when setting up randomization.
The dataset construction process works as follows:
1) The directory specified in each `data` stanza is scanned for files.
1) Each `data` file list is individually sampled based on the sampling stanza in the dataset config.
If two or more stanzas have the same label, the sampling is per stanza file list not per the
aggregate label.
Thus, if the two stanzas are for label 0 with a shuffling of "randomQuantity" with size 10, then 20
images with label 0 in total will be selected.
If the sampling involves random operations then a seed may be specified for the sampling process.
1) The file list in each data section is then split into training and validation sets
based on the validation split stanza in the training configuration.
If the validation selection involves random operations then a seed may be specified
for the process.
1) The training and validation sets from each entry are then merged into one list for
training and one for validation, respectively.
1) The file lists are provided to other parts of the system for cache checks, shuffling,
loading, and transformation.
## Step 4 - Test
At this point we want to evaluate a test set against the model and see
how well the model predicts classes. To perform a test, we need a trained
model (like the one from step 3) and a dataset config describing the data to test
with. As with the other commands, the testing script requires workspace and data
roots to be set either via juneberry.ini or the -w/-d switches.
This example command shows how to conduct testing using the model from
the previous step and a holdout dataset. The workspace and dataroot were defined in a
juneberry.ini, so they will not be shown in this command:
```jb_make_predictions imagenet_224x224_rgb_unit_test_pyt_resnet50 imagenet_224x224_rgb_unit_test.json```
This script will output a file called `predictions_imagenet_unit_test.json` that
contains the labels for the test images along with the predictions the model made
for each test image.
## Step 5 - Format Report
The data from a predictions file can be used to construct ROC plots. The example command below demonstrates
how to plot the ROC data for particular labels in a predictions file.
```
jb_plot_roc
-f models/imagenet_224x224_rgb_unit_test_pyt_resnet50/predictions_imagenet_224x224_rgb_unit_test.json
-p "45,128,225,319,372,402,629,778,816,959"
myplot.png
```
The `-f` switch is used to indicate which predictions file the data should come from. The `-p` switch indicates
integer labels of which classes from the predictions file should be included on the plot. The `myplot.png`
indicates the filename to use when saving the plot. It is possible to plot data from multiple predictions files
on the same plot. To do so, you would simply add another `-f` switch and the desired file, along with another
`-p` switch with the desired class integers.
## Step 6 - Building experiments
Example data config file: [experiments/pytorchSystemTest/config.json](./experiments/pytorchSystemTest/config.json)
As described above, subdirectories in the "experiments" directory describe separate experiments to run.
Each experiment directory contains a config.json that describes the experiment. The config files follows
the format specified in
[documentation/experiment_configuration_specification.md](./juneberry/documentation/experiment_configuration_specification.md).
There are two primary sections. The first is the "models" section which lists each model to be built and the
set of datasets to be tested against each model. Each dataset that is tested is given a tag to be used to
refer to it in the reports section. The reports section lists a series of reports to be generated where each
report has a type (e.g. ROC curve) and a list of tags from the predictions above. Optionally, a set of
classes can be specified for the report for when large datasets (e.g. imagenet) are used in the experiment.
Once an experiment config is created, it can be executed with the [jb_run_experiment](./bin/jb_run_experiment)
command. As with other scripts the workspace root (-w) can be provided via juneberry.ini or via command line.
However, the data root **is ignored** because each model may use a different data root. The experiment runner will
switch to each model directory before training or testing the model, allowing for the train or test scripts
to find juneberry configs in those directories.
Because experiments can be extremely time-consuming to run, the default mode of the script is to run in dry run
mode, which describes what actions the experiment will perform. To see what the experiment would look like
for **pytorchSystemTest** run the following:
```jb_run_experiment pytorchSystemTest```
The output should describe the current state of the models, the predictions, and what reports it would generate.
From the logs one can look at the left most position of the log lines to see the mode of the experiment
runner. To actually perform the action, the `--commit` option should be specified.
```jb_run_experiment pytorchSystemTest --commit```
Before a full experiment run, sometimes it is useful to clean all the artifacts. To see what would be
removed, specify the `--clean` option.
```jb_run_experiment pytorchSystemTest --clean```
By default, the `--clean` option only describes what it would do. As with running the experiment, you must
specify the `--commit` option to perform the actual cleaning.
```jb_run_experiment pytorchSystemTest --clean --commit```
If you want to see what each model would do in detail before running them, you can run the `--dryrun`
command on each model by specifying `--dryrun` to the experiment runner. All the appropriate
dry run logs, summaries, and sample images will be in each model. This mode is incompatible with
`--commit` and `--clean`.
```jb_run_experiment pytorchSystemTest --dryrun```
# Special Configuration Variables
## JUNEBERRY_CUDA_MEMORY_SUMMARY_PERIOD
If this environment variable is set, then during training the `torch.cude.memory_summary()` shall be output after
model load and every number of epochs based on the above period starting at epoch one.
Thus, if JUNEBERRY_CUDA_MEMORY_SUMMARY_PERIOD is set to 10, then the memory summary will be emitted
after model load and again after epochs 1, 11, 21, 31, etc.
# Copyright
Copyright 2021 Carnegie Mellon University. See LICENSE.txt file for license terms.
| 51.559459 | 130 | 0.78959 | eng_Latn | 0.998439 |
f4d988f5a8137e14707203ee63a6704642386240 | 14,733 | md | Markdown | packages/wdio-devtools-service/README.md | pgliang001/webdriverio | 1aa1d04a24c8cf9f6be14e782215ba9b3ca86084 | [
"MIT"
] | null | null | null | packages/wdio-devtools-service/README.md | pgliang001/webdriverio | 1aa1d04a24c8cf9f6be14e782215ba9b3ca86084 | [
"MIT"
] | 17 | 2022-02-11T02:03:49.000Z | 2022-03-28T11:36:32.000Z | packages/wdio-devtools-service/README.md | pgliang001/webdriverio | 1aa1d04a24c8cf9f6be14e782215ba9b3ca86084 | [
"MIT"
] | 1 | 2022-03-22T00:37:32.000Z | 2022-03-22T00:37:32.000Z | WebdriverIO DevTools Service
============================
> A WebdriverIO service that allows you to run Chrome DevTools commands in your tests
With Chrome v63 and up the browser [started to support](https://developers.google.com/web/updates/2017/10/devtools-release-notes#multi-client) multi clients allowing arbitrary clients to access the [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). This provides interesting opportunities to automate Chrome beyond the [WebDriver protocol](https://www.w3.org/TR/webdriver/). With this service you can enhance the wdio browser object to leverage that access and call Chrome DevTools commands within your tests to e.g. intercept requests, throttle network capabilities or take CSS/JS coverage.
Since Firefox 86, [a subset of Chrome DevTools Protocol](https://firefox-source-docs.mozilla.org/remote/index.html) has been implemented by passing the capability `"moz:debuggerAddress": true`.
_**Note:** this service currently only supports Chrome v63 and up, Chromium, and Firefox 86 and up (Microsoft Edge is not yet supported)!_
## Installation
The easiest way is to keep `@wdio/devtools-service` as a devDependency in your `package.json`, via:
```sh
npm install @wdio/devtools-service --save-dev
```
Instructions on how to install `WebdriverIO` can be found [here.](https://webdriver.io/docs/gettingstarted)
## Configuration
In order to use the service you just need to add the service to your service list in your `wdio.conf.js`, like:
```js
// wdio.conf.js
export.config = {
// ...
services: ['devtools'],
// ...
};
```
## Usage
The `@wdio/devtools-service` offers you a variety of features that helps you to automate Chrome beyond the WebDriver protocol. It gives you access to the Chrome DevTools protocol as well as to a [Puppeteer](https://pptr.dev/) instance that you can use to automate Chrome with the Puppeteer automation interface.
### Performance Testing
The DevTools service allows you to capture performance data from every page load or page transition that was caused by a click. To enable it call `browser.enablePerformanceAudits(<options>)`. After you are done capturing all necessary performance data disable it to revert the throttling settings, e.g.:
```js
const assert = require('assert')
describe('JSON.org page', () => {
before(() => {
browser.enablePerformanceAudits()
})
it('should load within performance budget', () => {
/**
* this page load will take a bit longer as the DevTools service will
* capture all metrics in the background
*/
browser.url('http://json.org')
let metrics = browser.getMetrics()
assert.ok(metrics.speedIndex < 1500) // check that speedIndex is below 1.5ms
let score = browser.getPerformanceScore() // get Lighthouse Performance score
assert.ok(score >= .99) // Lighthouse Performance score is at 99% or higher
$('=Esperanto').click()
metrics = browser.getMetrics()
assert.ok(metrics.speedIndex < 1500)
score = browser.getPerformanceScore()
assert.ok(score >= .99)
})
after(() => {
browser.disablePerformanceAudits()
})
})
```
You can emulate a mobile device by using the `emulateDevice` command, throttling CPU and network as well as setting `mobile` as form factor:
```js
browser.emulateDevice('iPhone X')
browser.enablePerformanceAudits({
networkThrottling: 'Good 3G',
cpuThrottling: 4,
formFactor: 'mobile'
})
```
The following commands with their results are available:
#### getMetrics
Get most common used performance metrics.
```js
console.log(browser.getMetrics())
/**
* { timeToFirstByte: 566,
* serverResponseTime: 566,
* domContentLoaded: 3397,
* firstVisualChange: 2610,
* firstPaint: 2822,
* firstContentfulPaint: 2822,
* firstMeaningfulPaint: 2822,
* largestContentfulPaint: 2822,
* lastVisualChange: 15572,
* interactive: 6135,
* load: 8429,
* speedIndex: 3259,
* totalBlockingTime: 31,
* maxPotentialFID: 161,
* cumulativeLayoutShift: 2822 }
*/
```
#### getDiagnostics
Get some useful diagnostics about the page load.
```js
console.log(browser.getDiagnostics())
/**
* { numRequests: 8,
* numScripts: 0,
* numStylesheets: 0,
* numFonts: 0,
* numTasks: 237,
* numTasksOver10ms: 5,
* numTasksOver25ms: 2,
* numTasksOver50ms: 2,
* numTasksOver100ms: 0,
* numTasksOver500ms: 0,
* rtt: 147.20600000000002,
* throughput: 47729.68474448835,
* maxRtt: 176.085,
* maxServerLatency: 1016.813,
* totalByteWeight: 62929,
* totalTaskTime: 254.07899999999978,
* mainDocumentTransferSize: 8023 }
*/
```
#### getMainThreadWorkBreakdown
Returns a list with a breakdown of all main thread task and their total duration.
```js
console.log(browser.getMainThreadWorkBreakdown())
/**
* [ { group: 'styleLayout', duration: 130.59099999999998 },
* { group: 'other', duration: 44.819 },
* { group: 'paintCompositeRender', duration: 13.732000000000005 },
* { group: 'parseHTML', duration: 3.9080000000000004 },
* { group: 'scriptEvaluation', duration: 2.437999999999999 },
* { group: 'scriptParseCompile', duration: 0.20800000000000002 } ]
*/
```
#### getPerformanceScore
Returns the [Lighthouse Performance Score](https://developers.google.com/web/tools/lighthouse/scoring) which is a weighted mean of the following metrics: `firstContentfulPaint`, `speedIndex`, `largestContentfulPaint`, `cumulativeLayoutShift`, `totalBlockingTime`, `interactive`, `maxPotentialFID` or `cumulativeLayoutShift`.
```js
console.log(browser.getPerformanceScore())
/**
* 0.897826278457836
*/
```
#### enablePerformanceAudits
Enables auto performance audits for all page loads that are cause by calling the `url` command or clicking on a link or anything that causes a page load. You can pass in a config object to determine some throttling options. The default throttling profile is `Good 3G` network with a 4x CPU trottling.
```js
browser.enablePerformanceAudits({
networkThrottling: 'Good 3G',
cpuThrottling: 4,
cacheEnabled: true,
formFactor: 'mobile'
})
```
The following network throttling profiles are available: `offline`, `GPRS`, `Regular 2G`, `Good 2G`, `Regular 3G`, `Good 3G`, `Regular 4G`, `DSL`, `Wifi` and `online` (no throttling).
### Device Emulation
The service allows you to emulate a specific device type. If set, the browser viewport will be modified to fit the device capabilities as well as the user agent will set according to the device user agent. To set a predefined device profile you can run:
```js
browser.emulateDevice('iPhone X')
// or `browser.emulateDevice('iPhone X', true)` if you want to be in landscape mode
```
Available predefined device profiles are: `Blackberry PlayBook`, `BlackBerry Z30`, `Galaxy Note 3`, `Galaxy Note II`, `Galaxy S III`, `Galaxy S5`, `iPad`, `iPad Mini`, `iPad Pro`, `iPhone 4`, `iPhone 5`, `iPhone 6`, `iPhone 6 Plus`, `iPhone 7`, `iPhone 7 Plus`, `iPhone 8`, `iPhone 8 Plus`, `iPhone SE`, `iPhone X`, `JioPhone 2`,
`Kindle Fire HDX`, `LG Optimus L70`, `Microsoft Lumia 550`, `Microsoft Lumia 950`, `Nexus 10`, `Nexus 4`, `Nexus 5`, `Nexus 5X`, `Nexus 6`, `Nexus 6P`, `Nexus 7`, `Nokia Lumia 520`, `Nokia N9`, `Pixel 2`, `Pixel 2 XL`
You can also define your own device profile by providing an object as parameter like in the following example:
```js
browser.emulateDevice({
viewport: {
width: 550, // <number> page width in pixels.
height: 300, // <number> page height in pixels.
deviceScaleFactor: 1, // <number> Specify device scale factor (can be thought of as dpr). Defaults to 1
isMobile: true, // <boolean> Whether the meta viewport tag is taken into account. Defaults to false
hasTouch: true, // <boolean> Specifies if viewport supports touch events. Defaults to false
isLandscape: true // <boolean> Specifies if viewport is in landscape mode. Defaults to false
},
userAgent: 'my custom user agent'
})
```
#### Note
This only works if you don't use `mobileEmulation` within `capabilities['goog:chromeOptions']`.
If `mobileEmulation` is present the call to `browser.emulateDevice()` won't do anything.
### PWA Testing
With the `checkPWA` command you can validate if your webapp is compliant to latest web standards when it comes to progressive web apps. It checks:
- whether your app is installable
- provides a service worker
- has a splash screen
- provides apple touch and maskable icons
- can be served on mobile devices
If you are not interested in one of these checks you can pass in a list of checks you like to run. The `passed` property will return `true` if all checks pass. If they fail you can use the `details` property to enrich your failure message with details of the failure.
```js
// open page first
browser.url('https://webdriver.io')
// validate PWA
const result = browser.checkPWA()
expect(result.passed).toBe(true)
```
### Capture Code Coverage
The service offers you to capture the code coverage of your application under test. To do so you need to enable this feature as part of the service settings:
```js
// wdio.conf.js
services: [
['devtools', {
coverageReporter: {
enable: true,
type: 'html', // lcov, json, text
logDir: __dirname + '/coverage',
exclude: [/resources/]
}
}]
]
```
Then you have access to a command that calculates the ratio of covered code lines and branches for you to assert within your test:
```js
const coverage = browser.getCoverageReport()
expect(coverage.lines.total).toBeAbove(0.9)
expect(coverage.statements.total).toBeAbove(0.9)
expect(coverage.functions.total).toBeAbove(0.9)
expect(coverage.branches.total).toBeAbove(0.9)
```
### Chrome DevTools Access
For now the service allows two different ways to access the Chrome DevTools Protocol:
### `cdp` Command
The `cdp` command is a custom command added to the browser scope that allows you to call directly commands to the protocol.
```js
browser.cdp(<domain>, <command>, <arguments>)
```
For example if you want to get the JavaScript coverage of your page you can do the following:
```js
it('should take JS coverage', () => {
/**
* enable necessary domains
*/
browser.cdp('Profiler', 'enable')
browser.cdp('Debugger', 'enable')
/**
* start test coverage profiler
*/
browser.cdp('Profiler', 'startPreciseCoverage', {
callCount: true,
detailed: true
})
browser.url('http://google.com')
/**
* capture test coverage
*/
const { result } = browser.cdp('Profiler', 'takePreciseCoverage')
const coverage = result.filter((res) => res.url !== '')
console.log(coverage)
})
```
### `getNodeId(selector)` and `getNodeIds(selector)` Command
Helper method to get the nodeId of an element in the page. NodeIds are similar like WebDriver node ids an identifier for a node. It can be used as a parameter for other Chrome DevTools methods, e.g. `DOM.focus`.
```js
const nodeId = browser.getNodeId('body')
console.log(nodeId) // outputs: 4
const nodeId = browser.getNodeIds('img')
console.log(nodeId) // outputs: [ 40, 41, 42, 43, 44, 45 ]
```
### `startTracing(categories, samplingFrequency)` Command
Start tracing the browser. You can optionally pass in custom tracing categories (defaults to [this list](https://github.com/webdriverio/webdriverio/tree/main/packages/wdio-devtools-service/src/constants.js#L1-L9)) and the sampling frequency (defaults to `10000`).
```js
browser.startTracing()
```
### `endTracing` Command
Stop tracing the browser.
```js
browser.endTracing()
```
### `getTraceLogs` Command
Returns the tracelogs that was captured within the tracing period. You can use this command to store the trace logs on the file system to analyse the trace via Chrome DevTools interface.
```js
browser.startTracing()
browser.url('http://json.org')
browser.endTracing()
fs.writeFileSync('/path/to/tracelog.json', JSON.stringify(browser.getTraceLogs()))
```
### `getPageWeight` Command
Returns page weight information of the last page load.
```js
browser.startTracing()
browser.url('https://webdriver.io')
browser.endTracing()
console.log(browser.getPageWeight())
// outputs:
// { pageWeight: 2438485,
// transferred: 1139136,
// requestCount: 72,
// details: {
// Document: { size: 221705, encoded: 85386, count: 11 },
// Stylesheet: { size: 52712, encoded: 50130, count: 2 },
// Image: { size: 495023, encoded: 482433, count: 36 },
// Script: { size: 1073597, encoded: 322854, count: 15 },
// Font: { size: 84412, encoded: 84412, count: 5 },
// Other: { size: 1790, encoded: 1790, count: 2 },
// XHR: { size: 509246, encoded: 112131, count: 1 } }
// }
```
### Setting Download Paths for the Browser
The `cdp` command can be used to call the [`Page.setDownloadBehavior`](https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-setDownloadBehavior) command of Devtools Protocol to set the behavior when downloading a file. Make sure the `downloadPath` is an absolute path and the `browser.cdp()` call is made before the file is downloaded.
```js
browser.cdp('Page', 'setDownloadBehavior', {
behavior: 'allow',
downloadPath: '/home/root/webdriverio-project/',
});
```
### Access Puppeteer Instance
The service uses Puppeteer for its automation under the hood. You can get access to the used instance by calling the [`getPuppeteer`](https://webdriver.io/docs/api/browser/getPuppeteer) command. __Note:__ Puppeteer commands are async and either needs to be called within the `call` command or handled via `async/await`:
```js
describe('use Puppeteer', () => {
it('by wrapping commands with call', () => {
browser.url('http://json.org')
const puppeteer = browser.getPuppeteer()
const page = browser.call(() => puppeteer.pages())[0]
console.log(browser.call(() => page.title()))
})
it('by using async/await', async () => {
const puppeteer = browser.getPuppeteer()
const page = (await puppeteer.pages())[0]
console.log(await page.title())
})
})
```
### Event Listener
In order to capture events in the browser you can register an event listener to a Chrome DevTools event like:
```js
it('should listen on network events', () => {
browser.cdp('Network', 'enable')
browser.on('Network.responseReceived', (params) => {
console.log(`Loaded ${params.response.url}`)
})
browser.url('https://www.google.com')
})
```
----
For more information on WebdriverIO see the [homepage](https://webdriver.io).
| 34.995249 | 621 | 0.700808 | eng_Latn | 0.905724 |
f4d98e1ac1676274a8c910dc5bf8f31a7bbbc393 | 643 | md | Markdown | README.md | gwasserfall/matcha | ff9069375da0eb81d08a2205ee52e31d11676f01 | [
"MIT"
] | 3 | 2020-01-13T12:04:36.000Z | 2020-06-15T16:26:50.000Z | README.md | gwasserfall/matcha | ff9069375da0eb81d08a2205ee52e31d11676f01 | [
"MIT"
] | null | null | null | README.md | gwasserfall/matcha | ff9069375da0eb81d08a2205ee52e31d11676f01 | [
"MIT"
] | null | null | null | Ensure you have a ".env" file in the main project directory. They following env vars will need
to be in this file in order for the project to run.
```
ENV=dev
DB_HOST=127.0.0.1
DB_USERNAME=user
DB_PASSWORD=pass
DB_DATABASE=matcha
WEBHOOK_SECRET=somesecretthatisnotthisstringoftext
```
Install backend python libraries and start dev server.
```
pip3 -r requirements.txt
# Ensure MySQL is up and running.
python3 app.py
```
Import MySQL database.
```
Log into MySQL and run "create database matcha"
python3 database_setup.py
```
Install Frontend node libraries and start dev server
```
cd matcha-vue
npm install
npm run serve
``` | 14.953488 | 94 | 0.758942 | eng_Latn | 0.954964 |
f4d9a6556ff7c38b16038915634fa963bee9aa27 | 11,030 | md | Markdown | articles/app-service/app-service-web-tutorial-rest-api.md | LucianoLimaBR/azure-docs.pt-br | 8e05ae8584aa2620717d69ccb6a2fdfbb46446c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/app-service/app-service-web-tutorial-rest-api.md | LucianoLimaBR/azure-docs.pt-br | 8e05ae8584aa2620717d69ccb6a2fdfbb46446c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/app-service/app-service-web-tutorial-rest-api.md | LucianoLimaBR/azure-docs.pt-br | 8e05ae8584aa2620717d69ccb6a2fdfbb46446c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Tutorial: Hospedar API RESTful com CORS – Serviço de Aplicativo do Azure'
description: Saiba como o Serviço de Aplicativo do Azure ajuda a hospedar suas APIs RESTful com suporte a CORS.
services: app-service\api
documentationcenter: dotnet
author: cephalin
manager: cfowler
editor: ''
ms.assetid: a820e400-06af-4852-8627-12b3db4a8e70
ms.service: app-service
ms.workload: web
ms.tgt_pltfrm: na
ms.devlang: dotnet
ms.topic: tutorial
ms.date: 11/21/2018
ms.author: cephalin
ms.custom: seodec18
ms.openlocfilehash: f13b390047ea4d8280b106f3b02a8f18944a6f99
ms.sourcegitcommit: 1c2659ab26619658799442a6e7604f3c66307a89
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 10/10/2019
ms.locfileid: "72255123"
---
# <a name="tutorial-host-a-restful-api-with-cors-in-azure-app-service"></a>Tutorial: Hospedar uma API RESTful com CORS no Serviço de Aplicativo do Azure
O [Serviço de Aplicativo do Azure](overview.md) fornece um serviço de hospedagem na Web altamente escalonável e com aplicação automática de patches. Além disso, o Serviço de Aplicativo tem suporte interno a [CORS (Compartilhamento de Recursos entre Origens)](https://wikipedia.org/wiki/Cross-Origin_Resource_Sharing) para APIs RESTful. Este tutorial mostra como implantar um aplicativo de API do ASP.NET Core no Serviço de Aplicativo com suporte a CORS. Configure o aplicativo usando as ferramentas de linha de comando e implante o aplicativo usando o Git.
Neste tutorial, você aprenderá como:
> [!div class="checklist"]
> * Criar recursos do Serviço de Aplicativo usando a CLI do Azure
> * Implantar uma API RESTful no Azure usando o Git
> * Habilitar o suporte de CORS do Serviço de Aplicativo
Você pode seguir as etapas deste tutorial no macOS, no Linux e no Windows.
[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
## <a name="prerequisites"></a>Pré-requisitos
Para concluir este tutorial:
* [Instalar o Git](https://git-scm.com/).
* [Instalar o .NET Core 2.0](https://www.microsoft.com/net/core/).
## <a name="create-local-aspnet-core-app"></a>Criar um aplicativo ASP.NET Core local
Nesta etapa, você configura o projeto ASP.NET Core local. O Serviço de Aplicativo dá suporte ao mesmo fluxo de trabalho para APIs codificadas em outras linguagens.
### <a name="clone-the-sample-application"></a>Clonar o aplicativo de exemplo
Na janela do terminal, `cd` para um diretório de trabalho.
Execute o comando a seguir para clonar o repositório de exemplo.
```bash
git clone https://github.com/Azure-Samples/dotnet-core-api
```
Esse repositório contém um aplicativo que é criado com base no seguinte tutorial: [Páginas de ajuda da API Web do ASP.NET Core usando o Swagger](/aspnet/core/tutorials/web-api-help-pages-using-swagger?tabs=visual-studio). Ele usa um gerador de Swagger para servir a [interface do usuário do Swagger](https://swagger.io/swagger-ui/) e o ponto de extremidade JSON do Swagger.
### <a name="run-the-application"></a>Executar o aplicativo
Execute os comandos a seguir para instalar os pacotes necessários, executar as migrações de banco de dados e iniciar o aplicativo.
```bash
cd dotnet-core-api
dotnet restore
dotnet run
```
Navegue até `http://localhost:5000/swagger` em um navegador para trabalhar com a interface do usuário do Swagger.
Navegue até `http://localhost:5000/api/todo` e veja uma lista de itens JSON de tarefas pendentes.
Navegue até `http://localhost:5000` e experimente o aplicativo de navegador. Posteriormente, você vai apontar o aplicativo de navegador para uma API remota no Serviço de Aplicativo a fim de testar a funcionalidade CORS. O código do aplicativo de navegador é encontrado no diretório _wwwroot_ do repositório.
Para parar o ASP.NET Core a qualquer momento, pressione `Ctrl+C` no terminal.
[!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
## <a name="deploy-app-to-azure"></a>Implantar o aplicativo no Azure
Nesta etapa, você implantará seu aplicativo .NET Core conectado ao Banco de Dados SQL no Serviço de Aplicativo.
### <a name="configure-local-git-deployment"></a>Configurar a implantação do git local
[!INCLUDE [Configure a deployment user](../../includes/configure-deployment-user-no-h.md)]
### <a name="create-a-resource-group"></a>Criar um grupo de recursos
[!INCLUDE [Create resource group](../../includes/app-service-web-create-resource-group-no-h.md)]
### <a name="create-an-app-service-plan"></a>Criar um plano de Serviço de Aplicativo
[!INCLUDE [Create app service plan](../../includes/app-service-web-create-app-service-plan-no-h.md)]
### <a name="create-a-web-app"></a>Criar um aplicativo Web
[!INCLUDE [Create web app](../../includes/app-service-web-create-web-app-dotnetcore-win-no-h.md)]
### <a name="push-to-azure-from-git"></a>Enviar do Git para o Azure
[!INCLUDE [app-service-plan-no-h](../../includes/app-service-web-git-push-to-azure-no-h.md)]
```bash
Counting objects: 98, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (92/92), done.
Writing objects: 100% (98/98), 524.98 KiB | 5.58 MiB/s, done.
Total 98 (delta 8), reused 0 (delta 0)
remote: Updating branch 'master'.
remote: .
remote: Updating submodules.
remote: Preparing deployment for commit id '0c497633b8'.
remote: Generating deployment script.
remote: Project file path: ./DotNetCoreSqlDb.csproj
remote: Generated deployment script files
remote: Running deployment command...
remote: Handling ASP.NET Core Web Application deployment.
remote: .
remote: .
remote: .
remote: Finished successfully.
remote: Running post deployment command(s)...
remote: Deployment successful.
remote: App container will begin restart within 10 seconds.
To https://<app_name>.scm.azurewebsites.net/<app_name>.git
* [new branch] master -> master
```
### <a name="browse-to-the-azure-app"></a>Navegar até o aplicativo do Azure
Navegue até `http://<app_name>.azurewebsites.net/swagger` em um navegador e experimente a interface do usuário do Swagger.
Navegue até `http://<app_name>.azurewebsites.net/swagger/v1/swagger.json` para ver o _swagger.json_ da sua API implantada.
Navegue até `http://<app_name>.azurewebsites.net/api/todo` para ver sua API implantada funcionando.
## <a name="add-cors-functionality"></a>Adicionar funcionalidade CORS
Em seguida, habilite o suporte interno de CORS no Serviço de Aplicativo para a sua API.
### <a name="test-cors-in-sample-app"></a>Testar CORS no aplicativo de exemplo
No seu repositório local, abra _wwwroot/index.html_.
Na linha 51, defina a variável `apiEndpoint` como a URL da sua API implantada (`http://<app_name>.azurewebsites.net`). Substitua _\<appname>_ pelo nome do aplicativo no Serviço de Aplicativo.
Na janela do terminal local, execute novamente o aplicativo de exemplo.
```bash
dotnet run
```
Navegue até o aplicativo de navegador em `http://localhost:5000`. Abra a janela de ferramentas de desenvolvedor no navegador (`Ctrl` + `Shift` + `i` no Chrome para Windows) e inspecione a guia **Console**. Agora, você verá a mensagem de erro `No 'Access-Control-Allow-Origin' header is present on the requested resource`.
Devido à incompatibilidade de domínio entre o aplicativo de navegador (`http://localhost:5000`) e o recurso remoto (`http://<app_name>.azurewebsites.net`), e ao fato de sua API no Serviço de Aplicativo não estar enviando o cabeçalho `Access-Control-Allow-Origin`, seu navegador impediu que o conteúdo entre domínios fosse carregado no aplicativo de navegador.
Na produção, o aplicativo de navegador teria uma URL pública em vez da URL de localhost, mas a maneira de habilitar o CORS para uma URL de localhost é a mesma de uma URL pública.
### <a name="enable-cors"></a>Habilitar CORS
No Cloud Shell, habilite o CORS para URL do cliente usando o comando [ `az resource update` ](/cli/azure/resource#az-resource-update). Substitua o espaço reservado _<appname>_ .
```azurecli-interactive
az resource update --name web --resource-group myResourceGroup --namespace Microsoft.Web --resource-type config --parent sites/<app_name> --set properties.cors.allowedOrigins="['http://localhost:5000']" --api-version 2015-06-01
```
Você pode definir mais de uma URL de cliente `properties.cors.allowedOrigins` (`"['URL1','URL2',...]"`). Você também pode habilitar todas as URLs de cliente com `"['*']"`.
> [!NOTE]
> Se o seu aplicativo exigir credenciais, como o envio de cookies ou tokens de autenticação, o navegador poderá exigir o cabeçalho `ACCESS-CONTROL-ALLOW-CREDENTIALS` na resposta. Para habilitar isso no Serviço de Aplicativo, defina `properties.cors.supportCredentials` como `true` em sua configuração de CORS. Isso não pode ser habilitado quando `allowedOrigins` inclui `'*'`.
### <a name="test-cors-again"></a>Testar CORS novamente
Atualize o aplicativo de navegador em `http://localhost:5000`. A mensagem de erro na janela **Console** desapareceu e você pode ver os dados da API implantada e interagir com eles. Sua API remota agora dá suporte a CORS para o aplicativo de navegador em execução localmente.
Parabéns, você estiver executando uma API no Serviço de Aplicativo do Azure com suporte de CORS.
## <a name="app-service-cors-vs-your-cors"></a>CORS do Serviço de Aplicativo comparado com seu CORS
Você pode usar seus próprios utilitários CORS em vez do CORS do Serviço de Aplicativo para obter mais flexibilidade. Por exemplo, convém especificar diferentes origens permitidas para rotas ou métodos diferentes. Como o CORS do Serviço de Aplicativo permite especificar um conjunto de origens aceitas para todas as rotas e métodos de API, é melhor usar seu próprio código CORS. Veja como o ASP.NET Core faz isso em [Habilitando solicitações entre origens (CORS)](/aspnet/core/security/cors).
> [!NOTE]
> Não tente usar CORS do Serviço de Aplicativo e seu próprio CORS juntos. Quando usados juntos, o CORS do Serviço de Aplicativo terá precedência e seu próprio código CORS não terá nenhum efeito.
>
>
[!INCLUDE [cli-samples-clean-up](../../includes/cli-samples-clean-up.md)]
<a name="next"></a>
## <a name="next-steps"></a>Próximas etapas
O que você aprendeu:
> [!div class="checklist"]
> * Criar recursos do Serviço de Aplicativo usando a CLI do Azure
> * Implantar uma API RESTful no Azure usando o Git
> * Habilitar o suporte de CORS do Serviço de Aplicativo
Vá para o próximo tutorial e aprenda a autenticar e autorizar os usuários.
> [!div class="nextstepaction"]
> [Tutorial: autenticar e autorizar usuários de ponta a ponta](app-service-web-tutorial-auth-aad.md)
| 51.302326 | 557 | 0.764642 | por_Latn | 0.984666 |
f4d9aad8f1419fb12cb5f8db6e71ef159068072e | 2,075 | md | Markdown | README.md | DZOpenSource/dz-to-do-list | 8937280a21ac407fac3847b6c5dda077fe0f10e5 | [
"MIT"
] | 1 | 2020-06-13T08:28:13.000Z | 2020-06-13T08:28:13.000Z | README.md | DZOpenSource/dz-to-do-list | 8937280a21ac407fac3847b6c5dda077fe0f10e5 | [
"MIT"
] | 1 | 2020-06-09T21:59:55.000Z | 2020-06-09T21:59:55.000Z | README.md | DZOpenSource/dz-to-do-list | 8937280a21ac407fac3847b6c5dda077fe0f10e5 | [
"MIT"
] | null | null | null |
# DZ TODO LIST
### Dev tools
1. Install [NodeJS](https://nodejs.org/en/download/)
2. Run the following command in order to install the React generator:
`npm i create-react-app -g`
3. Install [MongoDB](https://docs.mongodb.com/manual/tutorial/install-mongodb-on-windows/)
4. To visualize your collections you can add this awesome tool "[robomongo](https://robomongo.org/)" :heart_eyes:
5. Your favorite IDE, but why not [Visual Studio Code](https://code.visualstudio.com/download)
### Install the application
1. Clone the repository
2. Install it using the command:
`npm install`
3. Run the MongoDB local en environment. It's the **mongo.exe** (normally for **Windows** under 'C:\Program Files\MongoDB\Server\4.2\bin' after doing installation explained before)
4. Connect your "**robomongo**" with the local database (still an option)
5. Create a database with the name "**todolist**" and a collection with the name "**items**"
### Launch application
Having the local MongoDB running several options are allowed:
1. Only the Backend using `npm run-script start-backend`
2. Only the Frontend (to have the auto refresh) `npm run-script font-end`
3. Start the two sides of the application using `npm run-script start-all`
The console will show you on which port the result could be displayed.
### Deploy to Heroku
1. Open a [Heroku](https://www.heroku.com/) free account
2. Download and install the [Heroku CLI](https://devcenter.heroku.com/articles/heroku-cli)
3. On the project folder run `heoku create` (this will create a dymo inside your personal space on Heroku)
4. Run `heroku addons:create mongolab` to create a database related to your Heroku's dyno (you can then access to your mLab space through your [dashboard](https://dashboard.heroku.com/apps) and create a collection with "**items**" as name)
5. Run `git push heroku master` to deploy your application
6. Use the `heroku open` command to open it :blush:
7. Demo [here](https://mighty-meadow-84139.herokuapp.com/)
Made with :heart: by the [DZOpenSource](https://github.com/DZOpenSource) community | 51.875 | 239 | 0.751325 | eng_Latn | 0.948527 |
f4d9f68f03524684c890aae1c129069766cb450e | 5,929 | md | Markdown | docs/CHANGELOG.md | romeomaryns/sprangular | 857fd07e900ea88f74e2f1b55c3243717aaa7bd7 | [
"MIT"
] | 133 | 2016-03-07T19:33:35.000Z | 2021-12-30T23:22:19.000Z | docs/CHANGELOG.md | romeomaryns/sprangular | 857fd07e900ea88f74e2f1b55c3243717aaa7bd7 | [
"MIT"
] | 4 | 2016-06-15T07:51:51.000Z | 2019-11-23T02:45:52.000Z | docs/CHANGELOG.md | romeomaryns/sprangular | 857fd07e900ea88f74e2f1b55c3243717aaa7bd7 | [
"MIT"
] | 40 | 2016-03-08T06:48:49.000Z | 2022-03-29T01:53:59.000Z | ## CHANGELOG:
### 2.2.0 (09.10.2016)
* Introduced Angular-Cli as angular build tool
* Updated Angular to 2.0.2
* Updated Angular Material to 2.0.0-alpha.9-3
* Updated Node to v6.7.0
* Updated Spring Platform to Athens-RELEASE
* Updated Spring Boot to 1.4.1.RELEASE
* Updated Spring Cloud to Camden.RELEASE
* Updated Spring Boot Admin to 1.4.2
* Updated Docker Maven Plugin to 0.4.13
* Added docker cleanup script for Windows
* Added tags for generated docker images
* Added separate routing modules to all lazy loaded Angular modules
* Extracted common modules and providers to one place
* Updated Angular-Cli to 1.0.0-beta.17
* Rewritten all Angular tests
### 2.1.0 (28.08.2016)
* Added Spring Cloud Config server for centralized configuration
* Added Spring REST Docs support for API microservices
* Remapped coverage reports to typescript
* Rewritten angular tests using Testbed
* Updated Spring Cloud to Brixton.SR5
* Updated angular2-material to 2.0.0-alpha.7-4
* Updated dependencies
* Removed typedoc (it doesn't support typescript2)
### 2.0.0 (16.08.2016)
* Updated Spring Platform to Athens-RC1 and Spring Boot to 1.4.0
* Updated Spring Cloud to Brixton.SR4
* Updated Node to v6.3.1 and npm to 3.10.3
* Updated dependencies
* Removed shardis-parent project
* Added docker support (thanks to Tarun Sukhu)
* Disabled Eureka client in unit tests
* Docker and standalone profiles
* Spring Boot admin support
* Added gateway service
* Updated Angular to rc.5
* Updated angular2-material to 2.0.0-alpha.7-2
* Added live demo
### 1.9.0 (29.07.2016)
* Updated dependencies
* Updated Angular to rc.4
* Switched back to awesome-ts-loader (faster)
* Updated Spring Cloud to Brixton.SR1
* Removed lombok from project
* Added UUID to all entities
* Moved styles from main.scss to separate module
* Updated Spring Cloud to Brixton.SR2
* Updated Spring Platform to 2.0.6 and Spring Boot to 1.3.6
* Renamed java test classes to match surefire convention
* Webpack 2 and Typescript 2
* Reduced bundle size
* Updated Spring Cloud to Brixton.SR3
* Enabled gzip compression
* Removed typings in favor of types
* Updated angular2-material to 2.0.0-alpha.6-2
* Updated Spring Platform to 2.0.7 and Spring Boot to 1.3.7
### 1.8.0 (30.06.2016)
* Better directory structure for angular components
* Dependency updates
* Updated Angular to rc.2
* Migrate awesome-ts-loader to ts-loader due to problems with karma
* Migrate to router 3
* Lazy routes with modified version of AngularClass webpack resolver
* Updated Angular to rc.3
* Added 404 page
* Much cleaner webpack configuration
* Role based visibility of menu items
* CRUD example for authenticated users
* Route access for selected roles (guards)
* Switched to new Angular Forms
* Updated angular2-material to 2.0.0-alpha.6
### 1.7.0 (08.06.2016)
* Added npm-check-updates as dev dependency
* Removed kitchensink page
* Updated dependencies
* Removed foundation and motion-ui
* Added angular2-material
* Basic angular2-material styling
* Added normalize.css
* Added fancy loading screen
* Removed development ribbon
* Updated angular2-material to 2.0.0-alpha.5-2
* Added angular2-material palette to main.scss
* Added sidenav navigation
* Added working login form
* Added ng2-webstorage library
* Inline base css from file and minify html
### 1.6.0 (26.05.2016)
* Updated node to 6.2.0
* Updated npm to 3.9.2
* Removed typings from git
* Updated typings
* Updated all node packages
* Fixed problem with nonexistent static directory
* Fixed webpack validator custom schema config
* Some fixes from AngularClass starter
### 1.5.0 (13.05.2016)
* Updated Spring Boot to 1.3.4
* Updated Spring Boot to 1.3.5
* Added Spring IO Platform dependency
* Various bugfixes
### 1.4.0 (05.05.2016)
* Updated Angular to beta 16
* Updated node dependencies
* Updated maven dependencies
* Fixed .gitignore
* Fully stateless authentication
* Storing oauth2 token in localstorage
* Removed form authentication
* Removed deprecated injectAsync
* Decoding user token and showing expiration date
* Updated Angular to beta 17
* Updated Angular to rc.1
* Replaced router-deprecated with router (temporary no async routes)
### 1.3.0 (21.07.2016)
* Refactoring to microservices
* Multi module pom project
* Shared common library
* Maven enforcer plugin
* Custom schema for webpack config validator
* Zull proxy
* Auth module
* Service discovery module (eureka)
* Oauth2 security
* Updated Angular to beta 14
* Included all rxjs
* Updated Angular to beta 15
* Updated some dependencies
* Path location strategy
* Implicit login flow
### 1.2.2 (01.04.2016)
* Updated Angular to beta 13
### 1.2.1 (24.03.2016)
* Updated Angular to beta 12
* Removed zone.js fixes for beta 11
* Replaced es6-promise loader with custom solution
### 1.2.0 (23.03.2016)
* Added motion-ui integration
* Added fancy animation for accordion
### 1.1.9 (21.03.2016)
* Refactoring
* First Angular component for Foundation : Accordion
### 1.1.8 (20.03.2016)
* Typescript files naming convention
* Foundation kitchensink wit samples
* Some changes from AngularClass
### 1.1.7 (19.03.2016)
* Switched to Angular2 beta 11
### 1.1.6 (17.03.2016)
* Added sourcemaps for css
* Added webpack text extract plugin for production
* Removed styles.ts entry point
### 1.1.5 (16.03.2016)
* Postcss and autoprefixer
### 1.1.4 (16.03.2016)
* Webpack config refactor and cleanup
* Sass loader path configuration
* Bootstrap 4 (alpha) replaced by Foundation 6
### 1.1.3 (15.03.2016)
* Some other fixes from original AngularClass starter
### 1.1.2 (14.03.2016)
* Some fixes from original AngularClass starter
### 1.1.1 (10.03.2016)
* Temporary removed ng2-bootstrap
### 1.1.0 (10.03.2016)
* Switched to Angular2 beta 9
* Added scss support
* Added font-awesome package
* Added Bootstrap 4
* Added ng-bootstrap (still buggy)
### 1.0.1 (09.03.2016)
* Replaced ts-loader with awesome-typescript-loader
### 1.0.0 (07.03.2016)
* Initial Version
| 29.351485 | 68 | 0.755102 | eng_Latn | 0.91115 |
f4da38c1d0f416212d164d6034d386bf457aa212 | 5,523 | md | Markdown | docs/4.10/subscriptions/client-implementations.md | haxibiao/lighthouse.cn | 928222fa3a267a7473c760b0580aa7a0c99d1036 | [
"MIT"
] | 1 | 2021-08-31T12:42:00.000Z | 2021-08-31T12:42:00.000Z | docs/4.10/subscriptions/client-implementations.md | haxibiao/lighthouse.cn | 928222fa3a267a7473c760b0580aa7a0c99d1036 | [
"MIT"
] | 5 | 2021-06-28T19:47:17.000Z | 2022-02-27T01:35:39.000Z | docs/4.10/subscriptions/client-implementations.md | haxibiao/lighthouse.cn | 928222fa3a267a7473c760b0580aa7a0c99d1036 | [
"MIT"
] | null | null | null | # 使用客户端（Client Implementations）
为使您快速入门并运行，以下各节说明如何将订阅（subcriptions）与常见的 GraphQL 客户端库一起使用。
## Apollo
要将 Lighthouse 订阅（subscriptions） 与 [Apollo](https://www.apollographql.com/docs/react/) 客户端库一起使用的话，您需要创建一个 `apollo-link`
```js
import { ApolloLink, Observable } from "apollo-link";
class PusherLink extends ApolloLink {
constructor(options) {
super();
// Retain a handle to the Pusher client
this.pusher = options.pusher;
}
request(operation, forward) {
return new Observable(observer => {
// Check the result of the operation
forward(operation).subscribe({
next: data => {
// If the operation has the subscription extension, it's a subscription
const subscriptionChannel = this._getChannel(
data,
operation
);
if (subscriptionChannel) {
this._createSubscription(subscriptionChannel, observer);
} else {
// No subscription found in the response, pipe data through
observer.next(data);
observer.complete();
}
}
});
});
}
_getChannel(data, operation) {
return !!data.extensions &&
!!data.extensions.lighthouse_subscriptions &&
!!data.extensions.lighthouse_subscriptions.channels
? data.extensions.lighthouse_subscriptions.channels[
operation.operationName
]
: null;
}
_createSubscription(subscriptionChannel, observer) {
const pusherChannel = this.pusher.subscribe(subscriptionChannel);
// Subscribe for more update
pusherChannel.bind("lighthouse-subscription", payload => {
if (!payload.more) {
// This is the end, the server says to unsubscribe
this.pusher.unsubscribe(subscriptionChannel);
observer.complete();
}
const result = payload.result;
if (result) {
// Send the new response to listeners
observer.next(result);
}
});
}
}
export default PusherLink;
```
然后初始化 pusher 客户端，并在链接堆栈（link stack）中使用它。
```js
const pusherLink = new PusherLink({
pusher: new Pusher(PUSHER_API_KEY, {
cluster: PUSHER_CLUSTER,
authEndpoint: `${API_LOCATION}/graphql/subscriptions/auth`,
auth: {
headers: {
authorization: BEARER_TOKEN
}
}
})
});
const link = ApolloLink.from([pusherLink, httpLink(`${API_LOCATION}/graphql`)]);
```
## Relay Modern
要将 Lighthouse 的订阅（subscriptions）与 Relay Modern 一起使用，您将需要创建一个自定义处理程序并将其注入 Relay 的环境中。
```js
import Pusher from "pusher-js";
import { Environment, Network, Observable, RecordSource, Store } from "relay-runtime";
const pusherClient = new Pusher(PUSHER_API_KEY, {
cluster: "us2",
authEndpoint: `${API_LOCATION}/graphql/subscriptions/auth`,
auth: {
headers: {
authorization: BEARER_TOKEN
}
}
});
const createHandler = options => {
let channelName;
const { pusher, fetchOperation } = options;
return (operation, variables, cacheConfig) => {
return Observable.create(sink => {
fetchOperation(operation, variables, cacheConfig)
.then(response => {
return response.json();
})
.then(json => {
channelName =
!!response.extensions &&
!!response.extensions.lighthouse_subscriptions &&
!!response.extensions.lighthouse_subscriptions.channels
? response.extensions.lighthouse_subscriptions.channels[
operation.name
]
: null;
if (!channelName) {
return
}
const channel = pusherClient.subscribe(channelName)
channel.bind(`lighthouse-subscription`, payload => {
const result = payload.result
if (result && result.errors) {
sink.error(result.errors)
} else if (result) {
sink.next({
data: result.data
})
}
if (!payload.more) {
sink.complete()
}
})
})
}).finally(() => {
pusherClient.unsubscribe(channelName)
})
};
};
const fetchOperation = (operation, variables, cacheConfig) => {
const bodyValues = {
variables,
query: operation.text,
operationName: operation.name
};
return fetch(`${API_LOCATION}/graphql`, {
method: "POST",
opts: {
credentials: "include"
},
headers: {
Accept: "application/json",
"Content-Type": "application/json",
Authorization: BEARER_TOKEN
},
body: JSON.stringify(bodyValues)
});
};
const fetchQuery = (operation, variables, cacheConfig) => {
return fetchOperation(operation, variables, cacheConfig).then(response => {
return response.json();
});
};
const subscriptionHandler = createHandler({
pusher: pusherClient,
fetchOperation: fetchOperation
});
const network = Network.create(fetchQuery, subscriptionHandler);
export const environment = new Environment({
network,
store: new Store(new RecordSource)
});
```
| 28.178571 | 118 | 0.567264 | eng_Latn | 0.422394 |
f4da7e19c849c5353de949e38ecf1448fca56832 | 3,545 | md | Markdown | translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md | IamthatIam777/docs | 68a4df9981e283115627a9608dfd82b7fe60d576 | [
"CC-BY-4.0",
"MIT"
] | 9 | 2021-04-02T15:46:42.000Z | 2022-03-06T17:21:45.000Z | translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md | IamthatIam777/docs | 68a4df9981e283115627a9608dfd82b7fe60d576 | [
"CC-BY-4.0",
"MIT"
] | 12 | 2021-04-07T08:33:01.000Z | 2021-08-03T07:51:13.000Z | translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md | erik-888/docs | 2e78dc37bc875b4df09986b152a56129ace3d62d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-02-28T00:59:02.000Z | 2021-02-28T00:59:02.000Z | ---
title: Configuring data encryption for your enterprise
shortTitle: Configuring data encryption
intro: 'For encryption at rest, you can provide your own encryption key to encrypt your data under your encryption policies.'
versions:
github-ae: '*'
---
{% note %}
**Note:** Configuring encryption at rest with a customer-managed key is currently in beta and subject to change.
{% endnote %}
### About data encryption
To provide a high level of security, {% data variables.product.product_name %} encrypts your data while at rest in the data centers and while your data is in transit between users' machines and the data centers.
For encryption in transit, {% data variables.product.product_name %} uses Transport Layer Security (TLS). For encryption at rest, {% data variables.product.product_name %} provides a default RSA key. After you've initialized your enterprise, you can choose to provide your own key instead. Your key should be a 2048 bit RSA private key in PEM format.
The key that you provide is stored in a hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages.
To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation.
### Adding or updating an encryption key
You can add a new encryption key as often as you need. When you add a new key, the old key is discarded. Your enterprise won't experience downtime when you update the key.
Your 2048 bit RSA private key should be in PEM format, for example in a file called _private-key.pem_.
```
-----BEGIN RSA PRIVATE KEY-----
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-----END RSA PRIVATE KEY-----
```
1. To add your key, use the `PATCH /enterprise/encryption` endpoint, replacing *~/private-key.pem* with the path to your private key.
```shell
curl -X PATCH http(s)://<em>hostname</em>/api/v3/enterprise/encryption \
-d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }"
```
2. Optionally, check the status of the update operation.
```shell
curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
```
### Disabling your encryption key
To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled.
1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently.
```shell
curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
```
2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest.
```shell
curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
```
To unfreeze your enterprise after you've disabled your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)."
### Weiterführende Informationen
- "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation
| 49.236111 | 411 | 0.746403 | eng_Latn | 0.972034 |
f4daa7302376234f71bdec63dd0772f05d270e53 | 1,098 | markdown | Markdown | src/changelog/_posts/2018-05-14-mandatory-content-type-header.markdown | christellethiebaut/developer.concur.com | f85300da47b0b477a52e5bc9d613e608c7ac3552 | [
"Apache-2.0"
] | null | null | null | src/changelog/_posts/2018-05-14-mandatory-content-type-header.markdown | christellethiebaut/developer.concur.com | f85300da47b0b477a52e5bc9d613e608c7ac3552 | [
"Apache-2.0"
] | null | null | null | src/changelog/_posts/2018-05-14-mandatory-content-type-header.markdown | christellethiebaut/developer.concur.com | f85300da47b0b477a52e5bc9d613e608c7ac3552 | [
"Apache-2.0"
] | null | null | null | ---
layout: post
title: Mandatory Content-Type Header required for Oauth2 /Token Calls
date: 2018-05-14
tags:
- Support
- Oauth2
- Authentication
---
In order to be compliant with the IETF Oauth2 Specification, specifically Appendix B (https://tools.ietf.org/html/draft-ietf-oauth-v2-31#appendix-B) the Authentication team will be releasing an update in the June Release (6/15/2018) that has a potential to break existing clients.
From the above date onwards, all calls to Oauth2's /token endpoint MUST have the content-type header.
`Content-Type: application/x-www-form-urlencoded`
We believe that most (if not all) clients have this header in place today, but please check just to be sure. We understand that disruptions like these are not desired but unfortunately are required from time to time to meet industry and security standards. We will minimize the frequency of these potential breaking changes and attempt to make changes like these in a more predictable manner. You can contact the Authentication team on our developer forums at : https://forum.developer.concur.com/
| 57.789474 | 497 | 0.785064 | eng_Latn | 0.995388 |
f4dae05aa9e5e166da44eacfb1d663bc1725bae6 | 7,873 | md | Markdown | _posts/2016-08-02-yum-笔记.md | mritd/mritd.github.io | 89712a3c2314aa66888cdd2bba0e08d414300571 | [
"Apache-2.0"
] | 32 | 2016-03-18T14:30:50.000Z | 2019-11-05T08:12:29.000Z | _posts/2016-08-02-yum-笔记.md | mritd/mritd.github.io | 89712a3c2314aa66888cdd2bba0e08d414300571 | [
"Apache-2.0"
] | 4 | 2017-03-09T01:48:36.000Z | 2018-09-10T08:04:48.000Z | _posts/2016-08-02-yum-笔记.md | mritd/mritd.github.io | 89712a3c2314aa66888cdd2bba0e08d414300571 | [
"Apache-2.0"
] | 69 | 2015-10-11T12:24:42.000Z | 2019-11-05T08:12:33.000Z | ---
layout: post
title: yum 笔记
categories: [Linux]
description: yum 笔记
keywords: Linux,yum
catalog: true
multilingual: false
tags: Linux
---
## 一、软件包管理概述
> 在漫长的 Linux 发展史中，由于 Linux 系统的特性，所有软件都为绿色的，编译成二进制解压后即可运行，所以软件安装和管理成了一个复杂的体力劳动，而软件包管理器应运而生。
### 1.1、相关术语概述
- POSIX : Portable Openratin System 跨平台调用
- API 兼容 : 开发库兼容，因此源代码可跨平台
- ABI 兼容 : 编译后的程序可以跨平台
- 库 : 可执行程序，本身不能作为程序执行入口，但可以被调用是编译好的二进制格式
- 程序的过程 : 预编译、编译、汇编、链接
- 静态链接 : 将库包含在程序中
- 动态链接 : dll，so(shared object)
- 编译 : 源代码翻译成cpu指令集的过程
**软件编译主要考虑以下两个因素 :**
- os 平台 : 编译好的应用程序必须为特定平台所支持的版本
- 硬件平台 : 应用程序为特定的cpu所支持
<!--more-->
### 1.2、软件包组成部分
- 二进制程序 : 通常为程序源码编译后产生的二进制文件，一般存放于 `bin`、`/sbin`、`/usr/bin`、`/usr/sbin`、`/usr/local/bin`、`/usr/local/sbin`
- 自身库文件 : 程序自身所用到的库文件，一般存放于 `/lib`、`/lib64`、`/usr/lib`、`/usr/lib64`、`/usr/local/lib`、`/usr/local/lib64`；程序开发时调用 API，运行时调用 ABI，**通过调整 `/etc/ld.so.conf.d/*.conf` 可改变内核装载的共享库文件**
- 配置文件 : 配置文件一般存放在 `/etc` 目录中，同时如果程序安装选择了指定目录，如 `/usr/local/nginx`，那么此时程序的可执行文件等将可能不会在标准目录中。
- 帮助文件 : 帮助文件一般包括 info文件、README、INSTALL、ChangeLog
### 1.3、应用管理器功能
应用管理器一般应该实现以下功能 :
- 数据库 : 应用程序管理器应该能够维护一个数据库，数据库中应该维护 **程序名称和版本、安装生成的各文件路径、程序文件校验码、程序间的依赖关系(解决循环依赖、版本依赖等)、提供功能性的说明**
- 程序组成格式 : 应用程序管理器应当能够提供应用程序的组成说明，如 **文件清单、安装卸载时运行的脚本等**
- 版本管理 : 应用程序管理器应当能管理应用程序的版本;应用程序源代码版本格式为 `name-major.minor.release.tar.gz`
### 1.4、常用的软件包管理器
常用发行版都有其自己的软件包管理器，如 :
- Debian : .deb 格式，使用 `dpkg` 管理
- RadHat : .rpm 格式，使用 `rmp` 管理
- SUSE : .rpm 格式,使用 `rpm` 管理，**注意，SUSE 的系统结构与 RadHat 不同，虽然都是用 rpm 管理，但其软件包内部文件组织不同，不能通用**
常用的软件包管理器都具备以下功能 : 打包、安装、查询、升级、卸载、校验、数据库管理
**包管理器虽然解决了软件包的管理混乱问题，但是其无法解决包分发等问题，因此出现了基于软件包管理器的前端管理器，如 Debian 系列的 `apt-get`、RadHat 系列的 `yum` 等**
## 二、rpm 使用
### 2.1、rpm 术语和概述
> rpm 全称 `RadHat Package Manager`，后经过 Linux 基金委员会吸纳为标准包管理工具，重新定义为 `RPM is Package Manager`.
- rpm 包名称 : name-version-release.arch.rpm
- release : 通常包含rpm的制作发行号，还包含使用的OS
- OS 平台 : OS 平台即为操作系统平台，如 el6(redhat enterprise linux6)、CentOS5、suse11 等
- 硬件平台 : 硬件平台用 arch 表示，常见的如 x86_64、i386、i586、i686、ppc 等，**如软件包无平台要求，则表示为 noarch**
- 分包 : 分包机制即将一个大的应用程序打包为多个 rpm 包，一般包含主包和支包，作用是满足不同用户需要，有些用户可能用不到太多的功能，可选择性安装支包
- 来源合法性校验 : 对于软件包来源一般要对源码进行 md5 或 sha1 校验码验证，对于 rpm 包则认为发行商提供的即为合法的，包完整性使用检验码校验，包的来源采用公钥加密机制校验
- **rpm 包获取途径** :
- 首先考虑发行商的光盘或站点服务器
- rpmfind : http://rpmfind.net
- rpmpbone : http://rpm.pbone.net
- Fedora EPEL : **对于发行商尚未提供或需要更高版本的 rpm 包可考虑 Fedora 维护的 EPEL 源，但对于 RadHat 企业版某些安全机制要求较高的地方可能会不被信任**
### 2.2、rpm 常用命令
#### 2.2.1、安装和卸载
- `rpm -i PACKAGE [...]` : -i 即 --install，安装软件包
- `-v` : 安装时显示安装信息，如进度
- `-vv` : 二级详细显示
- `-vvv` ; 三级详细显示
- `-h` : -h 即 hash，以 # 的形式显示安装进度，通常一个 # 代表 2%
- `rpm -ivh --test PACKAGE` : 仅测试，不进行安装
- `rpm -ivh --nodeps` ; 忽略依赖关系，当出现包依赖时，可使用此选项强制安装(装完可能不能用)
- `rpm -ivh --replacepkgs` : 重新安装软件包，**原来的配置文件不会被覆盖，新安装的配置文件将会重命名为以.rpmnew为后缀的文件**
- `rpm -e PACKAGE` : -e 即 --erase，卸载指定软件包，如果该软件包被其他程序依赖，**可使用 `--nodeps` 忽略依赖**
#### 2.2.2、查询
- `rpm -q PACKAGE` : 查询某软件包是否安装，`rpm -q` 用于查询，一般需要附带查询参数如 `a`
- `rpm -qa PACKAGE` : 查询安装的所有软件包，包名支持通配符，如 `rpm -qa php*` 查询 php 开头的所有包
- `rpm -qi PACKAGE` : 查询包的描述信息，如下
``` sh
Name : docker
Version : 1.10.3
Release : 44.el7.centos
Architecture: x86_64
Install Date: 2016年07月25日 星期一 10时28分19秒
Group : Unspecified
Size : 43643976
License : ASL 2.0
Signature : RSA/SHA256, 2016年06月24日 星期五 11时43分08秒, Key ID 24c6a8a7f4a80eb5
Source RPM : docker-1.10.3-44.el7.centos.src.rpm
Build Date : 2016年06月24日 星期五 08时10分54秒
Build Host : worker1.bsys.centos.org
Relocations : (not relocatable)
Packager : CentOS BuildSystem <http://bugs.centos.org>
Vendor : CentOS
URL : https://github.com/docker/docker
Summary : Automates deployment of containerized applications
Description :
Docker is an open-source engine that automates the deployment of any
application as a lightweight, portable, self-sufficient container that will
run virtually anywhere.
Docker containers can encapsulate any payload, and will run consistently on
and between virtually any server. The same container that a developer builds
and tests on a laptop will run at scale, in production*, on VMs, bare-metal
servers, OpenStack clusters, public instances, or combinations of the above.
```
- `rpm -ql PACKAGE` : **查询软件包安装后的文件列表**
- `rpm -qf FILE` : **反查询，查询某个文件由那个软件包生成/释放的**
- `rpm -qd PACKAGE` : 查询某个包安装完成后生成的文档文件
- `rpm -qc PACKAGE` : **查询某个软件安装后生成的配置文件**
- `rpm -q --scripts` : **查询软件爱你安装脚本，脚本一般包含4类，如下:**
- preinstall : 安装前脚本
- postinstall : 安装后脚本
- preuninstall : 卸载前脚本
- postuninstall : 卸载后脚本
- `rpm -qpl PACKAGE` : 查询某尚未安装软件包安装后生成的文件列表
- `rpm -qpi PACKAGE` : 查询某尚未安装软件包的描述信息
#### 2.2.3、升级
- `rpm -U PACKAGE` : 升级或安装软件包(可以与 v、h等一起使用)
- `rpm -F PACKAGE` : 升级软件包(可以与 v、h等一起使用)
- `rpm -U --force PACKAGE` : 强行升级或安装，当当前软件包被其他软件包所依赖、或升级后新版本跟其他软件包冲突时，可使用此选项进行强制升级或安装
#### 2.2.4、管理
- `rpm -V PACKAGE` : 检验指定软件包是否被修改，以下为修改后返回状态位含义
``` sh
S file Size differs 大小
M Mode differs (includes permissions and file type) 头文件
5 digest (formerly MD5 sum) differs MD5
D Device major/minor number mismatch
L readLink(2) path mismatch
U User ownership differs 属主
G Group ownership differs 属组
T mTime differs 修改时间
P caPabilities differ 能力改变了
```
- `rpm -K PACKAGE` : 校验 rmp 完整性和来源(-checksig)
- `--nosigeature` : 不检查来源合法性
- `--nodigest` : 不检查完整性
- `rpm --import KEY` : 导入 rpm 包制作商密钥
#### 2.2.5、rpm 数据库
**rpm 数据库位置: `/var/lib/rpm`**
- `rpm --initdb` : rpm 数据库初始化，**如果事先不存在则新建**
- `rpm --rebuilddb` : rpm 数据库重建，直接重建并覆盖原有数据
## 三、yum 使用
yum 全称 Yellowdog Update Modifier，是一个基于 rpm 软件包管理器的前端软件包管理器，其最主要的功能便是能自动管理软件包依赖关系。
### 3.1、yum 仓库简介
yum 仓库顾名思义是一个 rpm 软件仓库，域名安装软件时从仓库下载至本地并安装。yum 仓库实质是一个 rpm 软件包共享服务器，其中主要包含 **rpm 的各种软件包，以及各个软件包之间相互依赖关系的元数据信息**，服务器使用的协议可自行选择，比如 ftp、http、nfs、file 等。
yum 客户端在使用 yun 仓库时，主要完成以下操作 :
- 配置文件 : yum 客户端要能够自行配置使用的 yum 仓库，保证最优的下载速度和 rpm 包质量
- 缓存元数据 : yum 客户端要能够缓存 yum 仓库提供的软件包元数据，以便本地快速读取
- 分析元数据 : yum 客户端要能够分析理解 yum 仓库提供的元数据，包括软件依赖关系等
- 执行具体操作 : yum 客户端要能够根据仓库提供的元数据和用户指令完成各种操作，如 rpm 安装卸载等
### 3.2、yum 客户端配置
yum 客户端配置文件主要存放于 `/etc/yum.conf(主配置文件)`、`/etc/yum.repo.d/*.repo(自定义仓库配置)`
yum 配置文件一般分为 主配置段([main])、仓库配置段([repo])，类似于 Windows 的 ini 文件，**yum 仓库配置示例如下 :**
``` sh
[repo_ID]
name=String
baseurl=仓库的访问路径
enabled={1|0} 1:表示启用 0:表示不启用
gpgcheck={1|0} 1:验证gpg 0:表示不验证
gpgkey=公钥地址(可以是本地,也可以是服务器端路径)
cost=定义此仓库开销,默认为1000
```
### 3.4、yum 常用命令
- `yum repolist[all|enabled(默认)|disabled]` : 列出所有可用的 yum repo
- `yum clean [all|packeages(包)|metadata(元数据)|expire-cache(过期数据)|rpmdb(rpm数据)|plugins]` : 清理 yum 缓存
- `yum list [all|installed(已安装过的)|available(可用)]` : 列出 yum 软件包
- `yum info PACKAGE` : 显示软件包信息
- `yum grouplist` : 列出所有软件包组
- `yum groupinfo GROUP` : 列出软件包组信息，包括必要的安装软件包和可选的软件包，其中有三个跟开发相关的包组：
- Desktop Platform Development : 有图形程序时需安装此组
- Server Platform Development
- Development Tools
- 如果系统为Centos 5，开发包组为 `Development Tools` 和 `DeveLopment Libraries`
- 如何系统为centos 6，常用的开发包为 `Development tools` 和 `Server Platform Development`
- `yum install PACKAGE` : 安装软件包，**PACKAGE 可为本地 rpm 包路径，此时为安装本地 rpm 包，如包检查不通过可使用 --nogpgcheck 手动禁用包来源和完整性验证**
- `yum reinstall PACKAGE` : 重新安装软件包
- `yum check-update PACKAGE` : 检查软件包是否有升级
- `yum update PACKAGE` : 升级指定软件包
- `yum downgrade PACKAGE` : 降级软件包
- `yum erase|remove PACKAGE` : 删除/卸载软件包
- `yum whatprovides|provides FILE` : 查询某文件是有那个软件包提供的
- `yum groupinstll GROUP` : 安装软件包组
- `yum groupremove GROUP` : 删除软件包组
- `yum history` : 查看 yum 历史
### 3.5、yum 宏
yum 配置文件中有很多可用的宏变量，用于动态替换，以下列举常用的 :
- \$releasever : 程序的版本,对Yum而言指的是redhat-relrase版本.只替换为主版本号,如Redhat6.5 则替换为6
- \$arch : 系统架构
- \$basharch : 系统基本架构,如i686,i586等的基本架构为i386
- \$YUM0-9 : 在系统定义的环境变量,可以在yum中使用
### 3.6、搭建 yum 仓库
- 安装仓库创建工具 `yum install createrepo -y`
- 准备文件服务器，比如 httpd `yum install httpd -y`
- 在 http 的访问目录下创建仓库目录
- 复制仓库要存放的 rpm 到创建的目录
- 创建仓库元数据 `createrepo /var/www/html/openstack(仓库目录)`
- 配置客户端 yum 仓库文件指向自建的 yum 仓库
- 为避免仓库中 rpm 包不全最好同时配置 epel 源
- 测试使用
转载请注明出处，本文采用 [CC4.0](http://creativecommons.org/licenses/by-nc-nd/4.0/) 协议授权
| 31.874494 | 175 | 0.71904 | yue_Hant | 0.767842 |
f4dafea36cccbbc8a73179f881af4db99df6da1a | 12,942 | md | Markdown | README.md | adventurebrew/sci-sheets | 6cd77a13771452aee340bd1d6b6884fef4a8b171 | [
"MIT"
] | null | null | null | README.md | adventurebrew/sci-sheets | 6cd77a13771452aee340bd1d6b6884fef4a8b171 | [
"MIT"
] | null | null | null | README.md | adventurebrew/sci-sheets | 6cd77a13771452aee340bd1d6b6884fef4a8b171 | [
"MIT"
] | null | null | null | <p align="center">
<a href="" rel="noopener">
<img width="400" src="https://i.imgur.com/83Y7bWN.png" alt="React & Google Apps Script logos"></a>
</p>
<div align="center">
[]()
[](https://github.com/enuchi/React-Google-Apps-Script/issues)
[](https://github.com/enuchi/React-Google-Apps-Script/pulls)
[](/LICENSE)
</div>
<p align="center"> This is your boilerplate project for developing React apps inside Google Sheets, Docs, Forms and Slides projects. It's perfect for personal projects and for publishing complex add-ons in the G Suite Marketplace.
</p>
---
## 📝 Table of Contents
- [About](#about)
- [Install](#install)
- [Prerequisites](#prerequisites)
- [Getting started](#getting-started)
- [Deploy](#deploy)
- [[New!] Local Development](#local-development)
- [Usage](#usage)
- [The included sample app](#the-included-sample-app)
- [[New!] Typescript](#new-typescript)
- [Adding packages](#adding-packages)
- [Styles](#styles)
- [Modifying scopes](#modifying-scopes)
- [Calling server-side Google Apps Script functions](#calling-server-side-google-apps-script-functions)
- [Autocomplete](#Autocomplete)
- [Authors](#authors)
- [Acknowledgments](#acknowledgement)
<br/>
## 🔎 About <a name = "about"></a>
[Google Apps Script](https://developers.google.com/apps-script/overview) is Google's Javascript-based development platform for building applications and add-ons for Google Sheets, Docs, Forms and other Google Apps.
You can add custom [user interfaces inside dialog windows](https://developers.google.com/apps-script/guides/html), but the platform is designed for simple HTML pages built with [templates](https://developers.google.com/apps-script/guides/html/templates) and [jQuery](https://developers.google.com/apps-script/guides/html/best-practices#take_advantage_of_jquery).
However, using this repo, it's easy to run [React](https://reactjs.org/) apps inside these dialogs, and build everything from small projects to advanced add-ons that can be published on the G Suite Marketplace.
<p align="center">
<img width="75%" src="https://i.imgur.com/BZvQ5ua.png" alt="React & Google Apps Script">
</p>
This repo is a boilerplate project that uses React and the same development tools that you use for building traditional websites, all inside Google Apps Script projects.
See below how to get started!
<br/>
## 🚜 Install <a name = "install"></a>
These instructions will get you set up with a copy of the React project code on your local machine. It will also get you logged in to `clasp` so you can manage script projects from the command line.
See [deploy](#deploy) for notes on how to deploy the project and see it live in a Google Spreadsheet.
### Prerequisites <a name = "prerequisites"></a>
- Make sure you're running at least [Node.js](https://nodejs.org/en/download/) v10 and `npm` v6.
- You'll need to enable the Google Apps Script API. You can do that by visiting [script.google.com/home/usersettings](https://script.google.com/home/usersettings).
- [New!] To use live reload while developing, you'll need to serve your files locally using HTTPS. See [local development](#local-development) below for how to set up your local environment.
### 🏁 Getting started <a name = "getting-started"></a>
**1.** First, let's clone the repo and install the dependencies.
```bash
git clone https://github.com/enuchi/React-Google-Apps-Script.git
cd React-Google-Apps-Script
npm install
```
<img width="100%" src="https://i.imgur.com/EGSsCqO.gif">
**2.** Next, we'll need to log in to [clasp](https://github.com/google/clasp), which lets us manage our Google Apps Script projects locally.
```bash
npm run login
```
<img width="100%" src="https://i.imgur.com/zKCgkMl.gif">
**3.** Now let's run the setup script to create a New spreadsheet and script project from the command line.
```bash
npm run setup
```
<img width="100%" src="https://imgur.com/Zk2eHFV.gif">
Alternatively, you can use an existing Google Spreadsheet and Script file instead of creating a new one.
<details>
<summary>See instructions here for using an existing project.</summary>
1. Copy your existing script project's `scriptId`. You can find it by opening your spreadsheet, selecting **Tools > Script Editor** from the menubar, then **File > Project properties**.
2. Run the command below using your project's `scriptId`:
```bash
npm run setup:use-id your_script_id_here
```
This command will add the existing project's `scriptId` to your`.clasp.json` file. See [here](https://github.com/google/clasp#setting) for working with `clasp`.
<img width="100%" src="https://i.imgur.com/VYl3JHx.gif">
</details>
Next, let's deploy the app so we can see it live in Google Spreadsheets.
<br/>
## 🚀 Deploy <a name = "deploy"></a>
Run the deploy command. You may be prompted to update your manifest file. Type 'yes'.
```bash
npm run deploy
```
The deploy command will build all necessary files using production settings, including all server code (Google Apps Script code), client code (React bundle), and config files. All bundled files will be outputted to the `dist/` folder, then pushed to the Google Apps Script project.
Now open Google Sheets and navigate to your new spreadsheet (e.g. the file "My React Project"). Make sure to refresh the page if you already had it open. You will now see a new menu item appear containing your app!
<img width="100%" src="https://i.imgur.com/W7UkEpv.gif">
<br/>
## 🎈 [NEW!] Local Development <a name="local-development"></a>
We can develop our client-side React apps locally, and see our changes directly inside our Google Spreadsheet dialog window.
<img width="100%" src="https://i.imgur.com/EsnOEHP.gif">
There are two steps to getting started: installing a certificate (first time only), and running the start command.
1. Generating a certificate for local development <a name = "generatingcerts"></a>
Install the mkcert package:
```bash
# mac:
$ brew install mkcert
# windows:
$ choco install mkcert
```
[More install options here.](https://github.com/FiloSottile/mkcert#installation)
Then run the mkcert install script:
```bash
$ mkcert -install
```
Create the certs in your repo:
```
npm run setup:https
```
2. Now you're ready to start:
```bash
npm run start
```
The start command will create and deploy a development build, and serve your local files.
<img width="100%" src="https://imgur.com/uD4uZZK.gif">
After running the start command, navigate to your spreadsheet and open one of the menu items. It should now be serving your local files. When you make and save changes to your React app, your app will reload instantly within the Google Spreadsheet, and have access to any server-side functions!
<img width="100%" src="https://i.imgur.com/EsnOEHP.gif">
<br/>
## ⛏️ Usage <a name = "Usage"></a>
### The included sample app
The included sample app allows inserting/activating/deleting sheets through a simple HTML dialog, built with React. This simple app demonstrates how a React app can interact with the underlying Spreadsheet using Google Apps Script functions.
The included sample app has three menu items for loading pages in various dialogs and sidebars.
Two versions of the same app are provided with different styling: the first version uses vanilla React, and the second uses the popular bootstrap library (in this case, it uses [`react-bootstrap`](https://react-bootstrap.github.io/)). The bootstrap example also contains an example of a page built with typescript (see below)
A third app just demonstrates how to load a sidebar dialog.
Access the dialogs through the new menu item that appears. You may need to refresh the spreadsheet and approve the app's permissions the first time you use it.
### [New!] Typescript
This project now supports typescript!
To use, simply use a typescript extension in either the client code (.ts/.tsx) or the server code (.ts), and your typescript file will compile to the proper format.
For client-side code, see [FormInput.tsx in the Bootstrap demo](src/client/dialog-packer/components/FormInput.tsx) for an example file. Note that it is okay to have a mix of javascript and typescript, as seen in the Bootstrap demo.
To use typescript in server code, just change the file extension to .ts. The server-side code already utilizes type definitions for Google Apps Script APIs.
A basic typescript configuration is used here, because after code is transpiled from typescript to javascript it is once again transpiled to code that is compatible with Google Apps Script. However, if you want more control over your setup you can modify the included [tsconfig.json file](./tsconfig.json).
### Adding packages
You can add packages to your client-side React app.
For instance, install `react-transition-group` from npm:
```bash
npm install react-transition-group
```
Important: Since Google Apps Scripts projects don't let you easily reference external files, this project will bundle an entire app into one HTML file. This can result in large files if you are importing large packages. To help split up the files, you can grab a CDN url for your package and declare it in the [webpack file, here](./webpack.config.js#L129). If set up properly, this will add a script tag that will load packages from a CDN, reducing your bundle size.
### Styles
By default this project supports global CSS stylesheets. Make sure to import your stylesheet in your entrypoint file [index.js](./src/client/dialog-demo/index.js):
```javascript
import './styles.css';
```
Many external component libraries require a css stylesheet in order to work properly. You can import stylesheets in the HTML template, [as shown here with the Bootstrap stylesheet](src/client/dialog-packer/index.html).
The webpack.config.js file can also be modified to support scss and other style libraries.
### Modifying scopes
The included app only requires access to Google Spreadsheets and to loading dialog windows. If you make changes to the app's requirements, for instance, if you modify this project to work with Google Forms or Docs, make sure to edit the oauthScopes in the [appscript.json file](./appsscript.json).
See https://developers.google.com/apps-script/manifest for information on the `appsscript.json` structure.
### Calling server-side Google Apps Script functions
This project uses the [gas-client](https://github.com/enuchi/gas-client) package to more easily call server-side functions using promises.
```js
// Google's documentation wants you to do this. Boo.
google.script.run
.withSuccessHandler(response => doSomething(response))
.withFailureHandler(err => handleError(err))
.addSheet(sheetTitle);
// Poof! With a little magic we can now do this:
import Server from 'gas-client';
const { serverFunctions } = new Server();
// We now have access to all our server functions, which return promises!
serverFunctions
.addSheet(sheetTitle)
.then(response => doSomething(response))
.catch(err => handleError(err));
// Or we can equally use async/await style:
async () => {
try {
const response = await serverFunctions.addSheet(sheetTitle);
doSomething(response);
} catch (err) {
handleError(err);
}
};
```
In development, `gas-client` will interact with [the custom Webpack Dev Server package](https://github.com/enuchi/Google-Apps-Script-Webpack-Dev-Server) which allows us to run our app within the dialog window and still interact with Google Apps Script functions.
### Autocomplete
This project includes support for autocompletion and complete type definitions for Google Apps Script methods.
All available methods from the Google Apps Script API are shown with full definitions and links to the official documentation, plus information on argument, return type and sample code.
<br/>
## ✍️ Authors <a name = "authors"></a>
- [@enuchi](https://github.com/enuchi) - Creator and maintainer
See the list of [contributors](https://github.com/enuchi/React-Google-Apps-Script/contributors) who participated in this project.
<br/>
## 🎉 Acknowledgements <a name = "acknowledgement"></a>
Part of this project has been adapted from [apps-script-starter](https://github.com/labnol/apps-script-starter), a great starter project for server-side projects ([license here](https://github.com/labnol/apps-script-starter/blob/master/LICENSE)).
| 43.14 | 467 | 0.748571 | eng_Latn | 0.952142 |
f4db9f0e512d7e0455cd262e44af1e6e1afbdaa6 | 5,315 | md | Markdown | README.md | bish0polis/mariadb | d6ec0086e90bbe34f86f4008b61cb4849d667122 | [
"Apache-2.0"
] | 20 | 2017-10-16T10:12:22.000Z | 2021-12-14T07:27:00.000Z | README.md | bish0polis/mariadb | d6ec0086e90bbe34f86f4008b61cb4849d667122 | [
"Apache-2.0"
] | 187 | 2017-10-12T21:41:07.000Z | 2022-03-16T20:56:33.000Z | README.md | sous-chefs/mariadb | d6ec0086e90bbe34f86f4008b61cb4849d667122 | [
"Apache-2.0"
] | 56 | 2017-10-13T15:19:17.000Z | 2021-12-14T07:44:33.000Z | # MariaDB Cookbook
[](https://supermarket.chef.io/cookbooks/mariadb)
[](https://circleci.com/gh/sous-chefs/mariadb)
[](#backers)
[](#sponsors)
[](https://opensource.org/licenses/Apache-2.0)
## Description
This cookbook contains all the stuffs to install and configure and manage a mariadb server on a dpkg/apt compliant system (typically debian), or a rpm/yum compliant system (typically centos)
## Maintainers
This cookbook is maintained by the Sous Chefs. The Sous Chefs are a community of Chef cookbook maintainers working together to maintain important cookbooks. If you’d like to know more please visit [sous-chefs.org](https://sous-chefs.org/) or come chat with us on the Chef Community Slack in [#sous-chefs](https://chefcommunity.slack.com/messages/C2V7B88SF).
## Requirements
### repository
- `mariadb` - This cookbook need that you have a valid apt repository installed with the mariadb official packages
### packages
- `percona-xtrabackup` - if you want to use the xtrabckup SST Auth for galera cluster.
- `mariadb-backup` - if you want to use the mariabackup SST Auth for galera cluster.
- `socat` - if you want to use the xtrabckup or mariabackup SST Auth for galera cluster.
- `rsync` - if you want to use the rsync SST Auth for galera cluster.
- `debconf-utils` - if you use debian platform family.
### operating system
- `debian` - this cookbook is fully tested on debian
- `ubuntu` - this cookbook is fully tested on ubuntu
- `centos` - this cookbook is fully tested on centos
### Chef version
Chef Infra Client >= 15.3
## Upgrading
If you are wondering where all the recipes went in v2.0+, or how on earth I use this new cookbook please see [upgrading.md](https://github.com/sous-chefs/mariadb/blob/master/documentation/upgrading.md) for a full description.
## Resources
- [`repository`](https://github.com/sous-chefs/mariadb/blob/master/documentation/resource_mariadb_repository.md)
- [`client_install`](https://github.com/sous-chefs/mariadb/blob/master/documentation/resource_mariadb_client_install.md)
- [`server_install`](https://github.com/sous-chefs/mariadb/blob/master/documentation/resource_mariadb_server_install.md)
- [`configuration`](https://github.com/sous-chefs/mariadb/blob/master/documentation/resource_mariadb_configuration.md)
- [`server_configuration`](https://github.com/sous-chefs/mariadb/blob/master/documentation/resource_mariadb_server_configuration.md)
- [`galera_configuration`](https://github.com/sous-chefs/mariadb/blob/master/documentation/resource_mariadb_galera_configuration.md)
- [`replication`](https://github.com/sous-chefs/mariadb/blob/master/documentation/resource_mariadb_replication.md)
- [`user`](https://github.com/sous-chefs/mariadb/blob/master/documentation/resource_mariadb_user.md)
- [`database`](https://github.com/sous-chefs/mariadb/blob/master/documentation/resource_mariadb_database.md)
## Contributing
1. Fork the repository on Github
1. Create a named feature branch (like `add_component_x`)
1. Write your change
1. Write tests for your change (if applicable)
1. Run the tests, ensuring they all pass
1. Submit a Pull Request using Github
## Contributors
This project exists thanks to all the people who [contribute.](https://opencollective.com/sous-chefs/contributors.svg?width=890&button=false)
### Backers
Thank you to all our backers!
### Sponsors
Support this project by becoming a sponsor. Your logo will show up here with a link to your website.
| 59.055556 | 357 | 0.78476 | eng_Latn | 0.427066 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.