s/elastic-client-generator/elasticsearch-specification (elastic#464)

* s/elastic-client-generator/elasticsearch-specification

* Updated README.md

Author: delvedor

.github/ISSUE_TEMPLATE/feature.md

@@ -8,7 +8,7 @@ labels: enhancement
 and post an issue here that does not follow the instructions, your issue might be closed,
 locked, and assigned the `invalid` label.**
 
-It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should [search](https://github.com/elastic/elastic-client-generator/labels/enhancement) at first before submitting a new one.
+It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should [search](https://github.com/elastic/elasticsearch-specification/labels/enhancement) at first before submitting a new one.
 
 ## 🚀 Feature Proposal
 

.github/ISSUE_TEMPLATE/missing-type.md

@@ -8,10 +8,10 @@ labels: missing type
 and post an issue here that does not follow the instructions, your issue might be closed,
 locked, and assigned the `invalid` label.**
 
-It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should [search](https://github.com/elastic/elastic-client-generator/labels/missing%20type) at first before submitting a new one.
+It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should [search](https://github.com/elastic/elasticsearch-specification/labels/missing%20type) at first before submitting a new one.
 
 If you want to try adding the type yourself, you are most welcome!
-Take a look at [our documentation](https://github.com/elastic/elastic-client-generator#how-to-validate-the-specification) to see how to do it.
+Take a look at [our documentation](https://github.com/elastic/elasticsearch-specification#how-to-validate-the-specification) to see how to do it.
 
 ## 🐛 Missing type
 
@@ -20,4 +20,4 @@ The name of the API that is currently missing (for version 7.x), it can be a req
 ## Definition
 
 If possible provide a basic definition that we can use as base.
-You can see [here](https://github.com/elastic/elastic-client-generator/blob/master/docs/add-new-api.md) how to create a basic definition for any API.
+You can see [here](https://github.com/elastic/elasticsearch-specification/blob/master/docs/add-new-api.md) how to create a basic definition for any API.

.github/ISSUE_TEMPLATE/question.md

@@ -6,4 +6,4 @@ labels: question
 
 ## 💬 Questions and Help
 
-It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should [search](https://github.com/elastic/elastic-client-generator/labels/question) at first before submitting a new one.
+It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should [search](https://github.com/elastic/elasticsearch-specification/labels/question) at first before submitting a new one.

.github/ISSUE_TEMPLATE/wrong-type.md

@@ -8,10 +8,10 @@ labels: wrong type
 and post an issue here that does not follow the instructions, your issue might be closed,
 locked, and assigned the `invalid` label.**
 
-It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should [search](https://github.com/elastic/elastic-client-generator/labels/wrong%20type) at first before submitting a new one.
+It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should [search](https://github.com/elastic/elasticsearch-specification/labels/wrong%20type) at first before submitting a new one.
 
 If you want to try fixing the type yourself, you are most welcome!
-Take a look at [our documentation](https://github.com/elastic/elastic-client-generator#how-to-validate-the-specification) to see how to do it.
+Take a look at [our documentation](https://github.com/elastic/elasticsearch-specification#how-to-validate-the-specification) to see how to do it.
 
 ## 🐛 Wrong type
 

README.md

@@ -1,4 +1,4 @@
-# elastic client generator
+# Elasticsearch Specification
 
 This repository contains the Elasticsearch request/response definitions in TypeScript,
 you can find them inside [`/specification`](./specification).
@@ -29,7 +29,7 @@ nvm install 14
 
 ```
 # clone the project
-$ git clone https://github.com/elastic/elastic-client-generator.git
+$ git clone https://github.com/elastic/elasticsearch-specification.git
 
 # install the dependencies
 $ npm install --prefix specification
@@ -187,10 +187,10 @@ how to generate a token.
 Once you have configured the environment, run the following commands:
 
 ```sh
-git clone https://github.com/elastic/elastic-client-generator.git
+git clone https://github.com/elastic/elasticsearch-specification.git
 git clone https://github.com/elastic/clients-flight-recorder.git
 
-cd elastic-client-generator
+cd elasticsearch-specification
 ./run-validations.sh
 ```
 

compiler/steps/add-info.ts

@@ -25,11 +25,11 @@ import { JsonSpec } from '../model/json-spec'
  */
 export default async function addInfo (model: model.Model, jsonSpec: Map<string, JsonSpec>): Promise<model.Model> {
   model._info = {
-    version: '7.11.0',
+    version: '7.13.0',
     title: 'Elasticsearch Request & Response Specification',
     license: {
       name: 'Apache 2.0',
-      url: 'https://github.com/elastic/elastic-client-generator/blob/master/LICENSE'
+      url: 'https://github.com/elastic/elasticsearch-specification/blob/master/LICENSE'
     }
   }
   return model

docs/modeling-guide.md

@@ -125,7 +125,7 @@ type Indices = string | string[]
 ...
 ```
 
-You can find the full list [here](https://github.com/elastic/elastic-client-generator/blob/update-docs/specification/specs/common.ts),
+You can find the full list [here](https://github.com/elastic/elasticsearch-specification/blob/update-docs/specification/specs/common.ts),
 feel free to add more if it feels appropriate!
 
 ### Dates

docs/validation-example.md

@@ -46,7 +46,7 @@ expectAssignable<T.IndexRequest<any>>({
 ```
 
 You can play with the response to better understand where is the problem, once you have done it
-you should search inside `elastic-client-generator/specification` the type definition,
+you should search inside `elasticsearch-specification/specification` the type definition,
 open it with your favourite editor and perform the fix
 
 ```diff

output/schema/schema.json

@@ -2,10 +2,10 @@
   "_info": {
     "license": {
       "name": "Apache 2.0",
-      "url": "https://github.com/elastic/elastic-client-generator/blob/master/LICENSE"
+      "url": "https://github.com/elastic/elasticsearch-specification/blob/master/LICENSE"
     },
     "title": "Elasticsearch Request & Response Specification",
-    "version": "7.11.0"
+    "version": "7.13.0"
   },
   "endpoints": [
     {

specification/indices/simulate_index_template/IndicesSimulateIndexTemplateResponse.ts

@@ -20,5 +20,5 @@
 
 import { AcknowledgedResponseBase } from '@_types/Base'
 
-// https://github.com/elastic/elastic-client-generator/pull/373 is merged.
+// https://github.com/elastic/elasticsearch-specification/pull/373 is merged.
 export class Response extends AcknowledgedResponseBase {}