diff --git a/snippets/actions/actions/classic.hbs b/snippets/actions/actions/classic.hbs
deleted file mode 100644
index 4f23af8..0000000
--- a/snippets/actions/actions/classic.hbs
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
\ No newline at end of file
diff --git a/snippets/actions/actions/classic.js b/snippets/actions/actions/classic.js
deleted file mode 100644
index ed61696..0000000
--- a/snippets/actions/actions/classic.js
+++ /dev/null
@@ -1,13 +0,0 @@
-import Component from '@ember/component';
-
-export default Component.extend({
- actions: {
- sayHello() {
- console.log('Hello, world!');
- },
-
- saySomethingElse(message) {
- console.log(message)
- }
- }
-});
\ No newline at end of file
diff --git a/snippets/actions/actions/octane.hbs b/snippets/actions/actions/octane.hbs
deleted file mode 100644
index 4fefed6..0000000
--- a/snippets/actions/actions/octane.hbs
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
\ No newline at end of file
diff --git a/snippets/actions/actions/octane.js b/snippets/actions/actions/octane.js
deleted file mode 100644
index 632c8aa..0000000
--- a/snippets/actions/actions/octane.js
+++ /dev/null
@@ -1,12 +0,0 @@
-import Component from '@glimmer/component';
-import { action } from '@ember/object';
-
-export default class MyComponent extends Component {
- @action sayHello() {
- console.log('Hello, world!');
- }
-
- @action saySomethingElse(message) {
- console.log(message);
- }
-}
\ No newline at end of file
diff --git a/snippets/actions/mixins/classic.js b/snippets/actions/mixins/classic.js
deleted file mode 100644
index 6ff8cea..0000000
--- a/snippets/actions/mixins/classic.js
+++ /dev/null
@@ -1,6 +0,0 @@
-import Component from '@ember/component';
-import SomeMixin from 'some-addon';
-
-export default Component.extend(SomeMixin, {
- // ...
-});
\ No newline at end of file
diff --git a/snippets/actions/template-arguments-default/classic.hbs b/snippets/actions/template-arguments-default/classic.hbs
deleted file mode 100644
index 2258649..0000000
--- a/snippets/actions/template-arguments-default/classic.hbs
+++ /dev/null
@@ -1,2 +0,0 @@
-{{!-- parent-component.hbs --}}
-{{child-component answer=answer}}
\ No newline at end of file
diff --git a/snippets/actions/template-arguments-default/classic.js b/snippets/actions/template-arguments-default/classic.js
deleted file mode 100644
index c7a567d..0000000
--- a/snippets/actions/template-arguments-default/classic.js
+++ /dev/null
@@ -1,6 +0,0 @@
-// child-component.js
-import Component from '@ember/component';
-
-export default Component.extend({
- answer: 42
-});
\ No newline at end of file
diff --git a/snippets/actions/template-arguments-default/octane.hbs b/snippets/actions/template-arguments-default/octane.hbs
deleted file mode 100644
index 52cb98d..0000000
--- a/snippets/actions/template-arguments-default/octane.hbs
+++ /dev/null
@@ -1,2 +0,0 @@
-{{!-- parent-component.hbs --}}
-
'@action'
' Decorator die Funktion einer JavaScript-Klasse, die vom Template aufgerufen werden sollte.
- Verwenden Sie den '{{on}}
' Modifizierer, um über das Wann zu entscheiden.
- Wenn Sie der Funktion ein Argument übergeben wollen, fügen Sie auch den '{{fn}}
' Helfer hinzu.
- (''Besuchen Sie die Ember Guides, um mehr zu erfahren''.)
\ No newline at end of file
diff --git a/translations/actions/actions/en-us.yaml b/translations/actions/actions/en-us.yaml
deleted file mode 100644
index 5988754..0000000
--- a/translations/actions/actions/en-us.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Use @action, '{{on}}', and '{{fn}}' instead of '{{action}}'
-description: >
- In the JavaScript class, use the ''@action'
' decorator to mark the function that you want to call from the template.
- In the template, use the '{{on}}
' modifier to decide when to call the function.
- If you need to pass an argument to the function, use '{{fn}}
' helper too.
- (''Visit the Ember Guides to learn more''.)
\ No newline at end of file
diff --git a/translations/actions/actions/es.yaml b/translations/actions/actions/es.yaml
deleted file mode 100644
index 698a6d8..0000000
--- a/translations/actions/actions/es.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Use @action, '{{on}}', y '{{fn}}' en lugar de '{{action}}'
-description: >
- En la clase de JavaScript, use el decorador ''@action'
' para marcar la función que desea llamar desde el template.
- En el template, use el modificador '{{on}}
' para decidir cuándo llamar a la función.
- Si necesita pasar un argumento a la función, use el '{{fn}}
' helper.
- (''Visite las guías de Ember para obtener más información''.)
diff --git a/translations/actions/actions/ja.yaml b/translations/actions/actions/ja.yaml
deleted file mode 100644
index efd8c7a..0000000
--- a/translations/actions/actions/ja.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: "'{{action}}'の代わりに、@action、'{{on}}'、そして'{{fn}}'を使う"
-description: >
- JavaScriptのクラスで、テンプレートから呼び出したい関数には''@action'
'デコレーターで関数をマークする必要があります。
- テンプレートでは、'{{on}}
'修飾子を使うことでいつ関数を呼ぶかを決めることが出来ます。
- 関数に引数を渡す必要がある場合、'{{fn}}
'ヘルパーも使用してください。
- (''詳細については、Emberガイドを参照してください''。)
diff --git a/translations/actions/actions/pt-br.yaml b/translations/actions/actions/pt-br.yaml
deleted file mode 100644
index 7e29700..0000000
--- a/translations/actions/actions/pt-br.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Use @action, '{{on}}', e '{{fn}}' no lugar de '{{action}}'
-description: >
- Na classe JavaScript, use o decorator ''@action'
' para sinalizar a função que você gostaria de chamar no template.
- No template, use o modifier '{{on}}
' para marcar quando chamar uma função.
- Se precisa passar um argumento para a função, use o helper '{{fn}}
' também.
- (''Veja o Ember Guides para saber mais''.)
diff --git a/translations/actions/de-de.yaml b/translations/actions/de-de.yaml
deleted file mode 100644
index d3e7605..0000000
--- a/translations/actions/de-de.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Aktionen
\ No newline at end of file
diff --git a/translations/actions/en-us.yaml b/translations/actions/en-us.yaml
deleted file mode 100644
index f568e16..0000000
--- a/translations/actions/en-us.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Actions
\ No newline at end of file
diff --git a/translations/actions/es.yaml b/translations/actions/es.yaml
deleted file mode 100644
index 80216f2..0000000
--- a/translations/actions/es.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Acciones
diff --git a/translations/actions/ja.yaml b/translations/actions/ja.yaml
deleted file mode 100644
index 7fc39e8..0000000
--- a/translations/actions/ja.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: アクション
diff --git a/translations/actions/mixins/de-de.yaml b/translations/actions/mixins/de-de.yaml
deleted file mode 100644
index ff5920f..0000000
--- a/translations/actions/mixins/de-de.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Mixins
-description: >
- Mixins sind mit den die native JavaScript-Syntax nutzenden Dingen inkompatibel (z. B. mit den aus dem ''@glimmer/component'
' importierten Komponenten).
- Die Art und Weise, mit der Sie den Code umstellen, weicht von Fall zu Fall ab.
- Falls Ihre App von einem Mixin-nutzenden Addon abhängt, wäre es vielleicht am besten, die klassische Komponenten in Ruhe zu lassen, bis das Addon für Octane bereit ist.
-octaneDescription: >
- Schauen Sie in ''Do you need Ember Object?'', um die Alternativen zu Mixins zu finden, z. B. Dienstfunktionen, Services, Delegates und Klasse Decorators.
\ No newline at end of file
diff --git a/translations/actions/mixins/en-us.yaml b/translations/actions/mixins/en-us.yaml
deleted file mode 100644
index 2601bea..0000000
--- a/translations/actions/mixins/en-us.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Mixins
-description: >
- You cannot use mixins on anything that uses native class syntax (e.g. components that import from ''@glimmer/component'
').
- The migration strategy depends on your use case.
- If your app depends on an addon that uses mixins, it may be best to continue using classic components until the addon is Octane-ready.
-octaneDescription: >
- See ''Do you need Ember Object?'' for alternatives to mixins, which include utility functions, services, delegates, and class decorators.
\ No newline at end of file
diff --git a/translations/actions/mixins/es.yaml b/translations/actions/mixins/es.yaml
deleted file mode 100644
index 6efc009..0000000
--- a/translations/actions/mixins/es.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Mixins
-description: >
- No puede usar mixins en nada que use sintaxis de clase nativa (por ejemplo, componentes que se importen desde ''@glimmer/component'
').
- La estrategia de migración depende de su caso de uso.
- Si su aplicación depende de un addon que usa mixins, puede ser mejor continuar usando componentes clásicos hasta que el addon esté listo para Octane.
-octaneDescription: >
- Vea ''Do you need Ember Object?'' para alternativas a mixins, que incluyen funciones de utilidad, servicios, delegates y decoradores de clases.
diff --git a/translations/actions/mixins/ja.yaml b/translations/actions/mixins/ja.yaml
deleted file mode 100644
index 9d0efa7..0000000
--- a/translations/actions/mixins/ja.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: ミックスイン
-description: >
- ネイティブのクラス構文(たとえば''@glimmer/component'
'をimportするコンポーネント)を使用するものについて、ミックスインを使用することは出来ません。
- ユースケースによって、どうマイグレーションするかは変わります。
- もし依存しているアドオンがミックインを使っている場合、そのアドオンがOctaneに対応するまでClassicコンポーネントを継続して使用することが最善の場合があります。
-octaneDescription: >
- ミックスインの代替案について知りたい場合、''Do you need Ember Object?''を参照してください。代替案には、ユーティリティ関数、サービス、デリゲート、そしてクラスデコレーターが含まれています。
diff --git a/translations/actions/mixins/pt-br.yaml b/translations/actions/mixins/pt-br.yaml
deleted file mode 100644
index 65961ab..0000000
--- a/translations/actions/mixins/pt-br.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Mixins
-description: >
- Não é possível usar mixins em nada que use a sintaxe de classe nativa (e.g. componentes que importam do ''@glimmer/component'
').
- A estratégia para migração depende do seu caso de uso.
- Se seu app depende de um addon que usa mixins, talvez o ideal seja continuar usando componentes clássicos até que o addon seja atualizado pra Octane.
-octaneDescription: >
- Veja ''Do you need Ember Object?'' para alternativas aos mixins, que inclui utility functions, services, delegates, e decorators de classes.
diff --git a/translations/actions/pt-br.yaml b/translations/actions/pt-br.yaml
deleted file mode 100644
index f568e16..0000000
--- a/translations/actions/pt-br.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Actions
\ No newline at end of file
diff --git a/translations/actions/template-arguments-default/de-de.yaml b/translations/actions/template-arguments-default/de-de.yaml
deleted file mode 100644
index bdc666d..0000000
--- a/translations/actions/template-arguments-default/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Den Standardwert eines Arguments festlegen
-description: >
- Ein Argument ist nur lesen, somit ist ihren Standardwert von der konsumierenden Klasse nicht zu setzen.
- Sie können stattdessen einen Getter erstellen, der das Argument umgibt und ''den Standardwert festlegt''.
\ No newline at end of file
diff --git a/translations/actions/template-arguments-default/en-us.yaml b/translations/actions/template-arguments-default/en-us.yaml
deleted file mode 100644
index a59f4d6..0000000
--- a/translations/actions/template-arguments-default/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Setting the default value of an argument
-description: >
- Because an argument is read-only, you cannot set its default value in the consuming class.
- Instead, you can create a getter to wrap the argument and ''provide the default value''.
\ No newline at end of file
diff --git a/translations/actions/template-arguments-default/es.yaml b/translations/actions/template-arguments-default/es.yaml
deleted file mode 100644
index de94edc..0000000
--- a/translations/actions/template-arguments-default/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Establecer el valor predeterminado de un argumento
-description: >
- Como un argumento es de solo lectura, no puede establecer su valor predeterminado en la clase que lo consume.
- En su lugar, puede crear un getter para envolver el argumento y ''proporcionar el valor predeterminado''.
diff --git a/translations/actions/template-arguments-default/ja.yaml b/translations/actions/template-arguments-default/ja.yaml
deleted file mode 100644
index 73d5ca7..0000000
--- a/translations/actions/template-arguments-default/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: 引数にデフォルト値を設定する
-description: >
- 引数は読み出し専用なので、デフォルト値を引数を渡される側のクラスで設定することは出来ません。
- 代わりに、引数をラップして''デフォルト値を提供するゲッターを作成することが出来ます''。
-
diff --git a/translations/actions/template-arguments-default/pt-br.yaml b/translations/actions/template-arguments-default/pt-br.yaml
deleted file mode 100644
index 62b97ea..0000000
--- a/translations/actions/template-arguments-default/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Definindo o valor padrão de um argumento
-description: >
- Pelo fato de um argumento ser apenas leitura ("read-only"), não é possível definir o seu valor padrão na classe consumidora.
- Ao invés disso, você pode criar um getter para encapsular o argumento e ''fornecer o valor padrão''.
\ No newline at end of file
diff --git a/translations/component-lifecycle/constructors/de-de.yaml b/translations/component-lifecycle/constructors/de-de.yaml
deleted file mode 100644
index ff8e327..0000000
--- a/translations/component-lifecycle/constructors/de-de.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: constructor statt init
-description: >
- Die ''constructor'
' Methode gehört zur nativen JavaScript-Syntax.
- Sie können sie verwenden, um die Klasse einer Komponente zu initialisieren, wie Sie es wohl in ''init'
' getan haben.
- (Auf der Ember Guides erfahren Sie mehr über ''die constructor Methode'' und ''das super''.)
\ No newline at end of file
diff --git a/translations/component-lifecycle/constructors/en-us.yaml b/translations/component-lifecycle/constructors/en-us.yaml
deleted file mode 100644
index 016fb28..0000000
--- a/translations/component-lifecycle/constructors/en-us.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Use constructor instead of init
-description: >
- ''constructor'
' comes from native JavaScript class.
- You can use this hook to set up the component class, similarly to what you might have done in ''init'
'.
- (Visit the Ember Guides to learn more about ''constructor'' and ''super''.)
\ No newline at end of file
diff --git a/translations/component-lifecycle/constructors/es.yaml b/translations/component-lifecycle/constructors/es.yaml
deleted file mode 100644
index f07c157..0000000
--- a/translations/component-lifecycle/constructors/es.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Utilice constructor en lugar de init
-description: >
- ''constructor'
' proviene de la clase JavaScript nativa.
- Puede utilizar este hook para configurar la clase de componente, de manera similar a lo que podría haber hecho en ''init'
'.
- (Visite las guías de Ember para obtener más información sobre ''constructor'' y ''super''.)
diff --git a/translations/component-lifecycle/constructors/ja.yaml b/translations/component-lifecycle/constructors/ja.yaml
deleted file mode 100644
index 7d00a76..0000000
--- a/translations/component-lifecycle/constructors/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: initの代わりにconstructorを使う
-description: >
- ネイティブのJavaScriptクラスには''constructor'
'があります。
- ''init'
'でやっていたのと同様に、このフックを使うことでコンポーネントクラスを設定できます。
- (さらに詳細について学びたい場合は、Emberガイドの''constructor''や''super''を参照してください。)
diff --git a/translations/component-lifecycle/constructors/pt-br.yaml b/translations/component-lifecycle/constructors/pt-br.yaml
deleted file mode 100644
index f77193e..0000000
--- a/translations/component-lifecycle/constructors/pt-br.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Use o construtor ao invés do método init
-description: >
- ''constructor'
' vem da classe nativa do JavaScript.
- Você pode usá-lo para configurar a classe do componente, de forma similar ao que você já deve ter feito no método ''init'
'.
- (Veja o Ember Guides para saber mais sobre ''construtor'' e ''super''.)
\ No newline at end of file
diff --git a/translations/component-lifecycle/de-de.yaml b/translations/component-lifecycle/de-de.yaml
deleted file mode 100644
index ae559d3..0000000
--- a/translations/component-lifecycle/de-de.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Lifecycle einer Komponente
\ No newline at end of file
diff --git a/translations/component-lifecycle/did-insert/de-de.yaml b/translations/component-lifecycle/did-insert/de-de.yaml
deleted file mode 100644
index 1aeb3c6..0000000
--- a/translations/component-lifecycle/did-insert/de-de.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: "'{{did-insert}}' statt didInsertElement"
-description: >
- Überlegen Sie sich, eine Aktion anstatt des Hooks ''didInsertElement'
' zu haben.
- Mit dem Modifizierer '{{did-insert}}
' können Sie die Aktion aufrufen.
- Wenden Sie den Decorator ''@action'
' an, um den richtigen Kontext aufs ''this'
' zu setzen.
- (Auf der Ember Guides erfahren Sie mehr über ''die Lifecycle Hooks einer Glimmer-Komponente''.)
\ No newline at end of file
diff --git a/translations/component-lifecycle/did-insert/en-us.yaml b/translations/component-lifecycle/did-insert/en-us.yaml
deleted file mode 100644
index 381fb8c..0000000
--- a/translations/component-lifecycle/did-insert/en-us.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Use '{{did-insert}}' instead of didInsertElement
-description: >
- If you used the ''didInsertElement'
' hook, consider making an action.
- You can call the action with the '{{did-insert}}
' modifier.
- Use the ''@action'
' decorator to bind the correct context (''this'
').
- (Visit the Ember Guides to learn more about ''lifecycle of Glimmer components''.)
\ No newline at end of file
diff --git a/translations/component-lifecycle/did-insert/es.yaml b/translations/component-lifecycle/did-insert/es.yaml
deleted file mode 100644
index 82000d8..0000000
--- a/translations/component-lifecycle/did-insert/es.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Utilice '{{did-insert}}' en lugar de didInsertElement
-description: >
- Si usa el hook ''didInsertElement'
', considere usar una acción.
- Puede llamar la acción con el modificador '{{did-insert}}
'.
- Utilice el decorador ''@action'
' para unir el contexto correcto (''this'
').
- (Visite las guías de Ember para obtener más información sobre ''ciclo de vida de los componentes de Glimmer''.)
diff --git a/translations/component-lifecycle/did-insert/ja.yaml b/translations/component-lifecycle/did-insert/ja.yaml
deleted file mode 100644
index 1c6a3bb..0000000
--- a/translations/component-lifecycle/did-insert/ja.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: didInsertElementの代わりに'{{did-insert}}'を使う
-description: >
- もし''didInsertElement'
'を使っていたら、アクションを作ることを考えてみてください。
- '{{did-insert}}
'修飾子と一緒にアクションを呼び出すことが出来ます。
- ''@action'
'デコレーターを使うことで、正しいコンテキスト(要は''this'
')に束縛します。
- (さらに学ぶためには、Emberガイドの''lifecycle of Glimmer components''を参照してください。)
diff --git a/translations/component-lifecycle/did-insert/pt-br.yaml b/translations/component-lifecycle/did-insert/pt-br.yaml
deleted file mode 100644
index 8d1e8c0..0000000
--- a/translations/component-lifecycle/did-insert/pt-br.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Use '{{did-insert}}' ao invés de didInsertElement
-description: >
- Se você já usou o hook ''didInsertElement'
', considere criar uma action.
- Você pode chamar a action com o modifier '{{did-insert}}
'.
- Use o decorator ''@action'
' para fazer o "bind" do contexto correto (''this'
').
- (Veja o Ember Guides para saber mais sobre ''lifecycle de componentes Glimmer''.)
\ No newline at end of file
diff --git a/translations/component-lifecycle/en-us.yaml b/translations/component-lifecycle/en-us.yaml
deleted file mode 100644
index 067b747..0000000
--- a/translations/component-lifecycle/en-us.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Component Lifecycle
\ No newline at end of file
diff --git a/translations/component-lifecycle/es.yaml b/translations/component-lifecycle/es.yaml
deleted file mode 100644
index 68d6654..0000000
--- a/translations/component-lifecycle/es.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Ciclo de vida de los componentes
diff --git a/translations/component-lifecycle/ja.yaml b/translations/component-lifecycle/ja.yaml
deleted file mode 100644
index 57b016a..0000000
--- a/translations/component-lifecycle/ja.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: コンポーネント ライフサイクル
diff --git a/translations/component-lifecycle/pt-br.yaml b/translations/component-lifecycle/pt-br.yaml
deleted file mode 100644
index 9bbf11c..0000000
--- a/translations/component-lifecycle/pt-br.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Ciclo ("Lifecycle") de um Componente
\ No newline at end of file
diff --git a/translations/component-lifecycle/render-modifiers/de-de.yaml b/translations/component-lifecycle/render-modifiers/de-de.yaml
deleted file mode 100644
index 6c61ee0..0000000
--- a/translations/component-lifecycle/render-modifiers/de-de.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Element-Modifizierer
-description: >
- Nach der Installation des Pakets ''@ember/render-modifiers'', erhalten Sie die Modifizierer '{{did-insert}}
' and '{{did-update}}
'.
- Dadurch können Sie die Lifecycle Hooks einer klassischen Komponente ersetzen, nämlich 'didInsertElement
', 'didRender
' und 'didUpdate
'.
-classicDescription: >
- Haben Sie Apps auf Ember 2.18+?
- Diese Modifizierer können Sie gleich jetzt benutzen, um klassische Komponenten in eine Glimmer überzuführen.
\ No newline at end of file
diff --git a/translations/component-lifecycle/render-modifiers/en-us.yaml b/translations/component-lifecycle/render-modifiers/en-us.yaml
deleted file mode 100644
index cf57704..0000000
--- a/translations/component-lifecycle/render-modifiers/en-us.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Element Modifiers
-description: >
- If you install ''@ember/render-modifiers'', you get '{{did-insert}}
' and '{{did-update}}
' modifiers.
- You may use them to replace a classic component's lifecycle hooks 'didInsertElement
', 'didRender
', and 'didUpdate
'.
-classicDescription: >
- Have Ember apps at version 2.18 or higher?
- You can use these modifiers to start converting classic components to Glimmer ones.
\ No newline at end of file
diff --git a/translations/component-lifecycle/render-modifiers/es.yaml b/translations/component-lifecycle/render-modifiers/es.yaml
deleted file mode 100644
index 35b9f62..0000000
--- a/translations/component-lifecycle/render-modifiers/es.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Modificadores de elementos
-description: >
- Si instala ''@ember/render-modifiers'', usted obtiene los modificadores '{{did-insert}}
' y '{{did-update}}
'.
- Puede usarlos para reemplazar los hooks del ciclo de vida de un componente clásico 'didInsertElement
', 'didRender
', y 'didUpdate
'.
-classicDescription: >
- ¿Tiene aplicaciones Ember en la versión 2.18 o superior?
- Puede usar estos modificadores para comenzar a convertir componentes clásicos en componentes Glimmer.
diff --git a/translations/component-lifecycle/render-modifiers/ja.yaml b/translations/component-lifecycle/render-modifiers/ja.yaml
deleted file mode 100644
index ff8971d..0000000
--- a/translations/component-lifecycle/render-modifiers/ja.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Element修飾子
-description: >
- ''@ember/render-modifiers''をインストールすれば、'{{did-insert}}
'や'{{did-update}}
'修飾子を使えるようになります。
- Classicコンポーネントのライフサイクルフックである、'didInsertElement
'、'didRender
'、そして'didUpdate
'を置き換えることが出来ます。
-classicDescription: >
- バージョン2.18以上のEmberアプリですか?
- これらの修飾子を使うことで、ClassicコンポーネントからGlimmerコンポーネントへの書き換えをやり始めることが出来ます。
diff --git a/translations/component-lifecycle/render-modifiers/pt-br.yaml b/translations/component-lifecycle/render-modifiers/pt-br.yaml
deleted file mode 100644
index acd88b6..0000000
--- a/translations/component-lifecycle/render-modifiers/pt-br.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Modifiers de elementos
-description: >
- Se você instalar ''@ember/render-modifiers'', você poderá usar os modifiers '{{did-insert}}
' e '{{did-update}}
'.
- Você pode usá-los para substituir os "lifecycle hooks" 'didInsertElement
', 'didRender
', e 'didUpdate
' dos componentes clássicos.
-classicDescription: >
- Possui apps Ember na versão 2.18 ou superior?
- Você pode usar esses modifiers para já iniciar a conversão de componentes clássicos em componentes Glimmer.
\ No newline at end of file
diff --git a/translations/component-lifecycle/will-destroy/de-de.yaml b/translations/component-lifecycle/will-destroy/de-de.yaml
deleted file mode 100644
index 67b9b05..0000000
--- a/translations/component-lifecycle/will-destroy/de-de.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: willDestroy statt willDestroyElement
-description: >
- ''willDestroy'
' ist der einzige andere Lifecycle Hook (neben ''constructor'
'), der für eine Glimmer-Komponenten verfügbar ist.
- Sie können ihn verwenden, um die Klasse einer Komponente zu beenden, wie Sie es wohl in ''willDestroyElement'
' getan haben.
- (Auf der Ember Guides erfahren Sie mehr über ''die Lifecycle Hooks einer Glimmer-Komponente''.)
\ No newline at end of file
diff --git a/translations/component-lifecycle/will-destroy/en-us.yaml b/translations/component-lifecycle/will-destroy/en-us.yaml
deleted file mode 100644
index 281a351..0000000
--- a/translations/component-lifecycle/will-destroy/en-us.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Use willDestroy instead of willDestroyElement
-description: >
- ''willDestroy'
' is the only other lifecycle hook (besides ''constructor'
') that Glimmer components have.
- You can use this hook to tear down the component class, similarly to what you might have done in ''willDestroyElement'
'.
- (Visit the Ember Guides to learn more about ''lifecycle of Glimmer components''.)
\ No newline at end of file
diff --git a/translations/component-lifecycle/will-destroy/es.yaml b/translations/component-lifecycle/will-destroy/es.yaml
deleted file mode 100644
index 797321a..0000000
--- a/translations/component-lifecycle/will-destroy/es.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Utilice willDestroy en lugar de willDestroyElement
-description: >
- ''willDestroy'
' es el único hook del ciclo de vida (además de ''constructor'
') que tienen los componentes Glimmer.
- Puede usar este hook para derribar / destruir la clase del componente, de manera similar a lo que podría haber hecho en ''willDestroyElement'
'.
- (Visite las guías de Ember para obtener más información sobre ''ciclo de vida de los componentes de Glimmer''.)
diff --git a/translations/component-lifecycle/will-destroy/ja.yaml b/translations/component-lifecycle/will-destroy/ja.yaml
deleted file mode 100644
index 3b14883..0000000
--- a/translations/component-lifecycle/will-destroy/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: willDestroyElementの代わりにwillDestroyを使う
-description: >
- ''willDestroy'
'はGlimmerコンポーネントが持っている唯一のライフサイクルフックです(''constructor'
'を除く。)
- ''willDestroyElement'
'で行っていたのと同様に、このフックを使ってコンポーネントを破棄することが出来ます。
- (さらに学ぶためには、Emberガイドの''lifecycle of Glimmer components''を参照してください。)
diff --git a/translations/component-lifecycle/will-destroy/pt-br.yaml b/translations/component-lifecycle/will-destroy/pt-br.yaml
deleted file mode 100644
index 1f97879..0000000
--- a/translations/component-lifecycle/will-destroy/pt-br.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Use willDestroy ao invés de willDestroyElement
-description: >
- ''willDestroy'
' é o único "lifecycle hook" (além do ''constructor'
') que componentes Glimmer possuem.
- Você pode usar esse hook para desfazer ("tear down") a classe do componente, de forma similar ao que você já deve ter feito no ''willDestroyElement'
'.
- (Veja o Ember Guides para saber mais sobre ''lifecycle de componentes Glimmer''.)
\ No newline at end of file
diff --git a/translations/component-properties/args/de-de.yaml b/translations/component-properties/args/de-de.yaml
deleted file mode 100644
index e0b5b34..0000000
--- a/translations/component-properties/args/de-de.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Argumente einer Komponente
-description: >
- Mit Octane sind die Argumente mit der Eigenschaft ''args'
' (d. h. ''this.args'
') verknüpft.
- Sie sind ''nicht'' mit der Klassinstanz ''this'
' verbunden.
- Infolgedessen können Sie zwischen den inneren Werten einer Klasse und den äußeren Argumenten unterscheiden.
- (Besuchen Sie die Ember Guides, um mehr über ''Argumente'' zu erfahren.)
\ No newline at end of file
diff --git a/translations/component-properties/args/en-us.yaml b/translations/component-properties/args/en-us.yaml
deleted file mode 100644
index f5febe4..0000000
--- a/translations/component-properties/args/en-us.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Component Arguments
-description: >
- In Octane, arguments are set on the ''args'
' property, ''this.args'
'.
- They are ''not'' set on the class instance, ''this'
'.
- As a result, you can distinguish internal class values from external arguments.
- (Visit the Ember Guides to learn more about ''arguments''.)
diff --git a/translations/component-properties/args/es.yaml b/translations/component-properties/args/es.yaml
deleted file mode 100644
index efdda04..0000000
--- a/translations/component-properties/args/es.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Argumentos de componentes
-description: >
- En Octane, los argumentos se establecen en la propiedad ''args'
', ''this.args'
'.
- Estos ''no'' están establecidos en la instancia de clase, ''this'
'.
- Como resultado, puede distinguir los valores de clase internos de los argumentos externos.
- (Visite las guías de Ember para obtener más información sobre ''argumentos''.)
diff --git a/translations/component-properties/args/ja.yaml b/translations/component-properties/args/ja.yaml
deleted file mode 100644
index bd21fdf..0000000
--- a/translations/component-properties/args/ja.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: コンポーネントの引数
-description: >
- Octaneにおいて、引数は''args'
'プロパティに設定され、''this.args'
'で参照することが出来ます。
- 引数はクラスのインスタンス(つまり''this'
')に設定されることは''ありません。''
- 結果として、クラス内部の値と外部からの引数を区別することが出来ます。
- (さらに学ぶために、Emberガイドの''arguments''を参照してください。)
diff --git a/translations/component-properties/args/pt-br.yaml b/translations/component-properties/args/pt-br.yaml
deleted file mode 100644
index d7b8731..0000000
--- a/translations/component-properties/args/pt-br.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Argumento dos Componentes
-description: >
- Na Octane, argumentos são definidos na property ''args'
': ''this.args'
'.
- Eles ''não'' são definidos na instância da classe, ''this'
'.
- Por causa disso, é possível distinguir valores internos da classe de argumentos externos.
- (Veja o Ember Guides para saber mais sobre ''argumentos''.)
diff --git a/translations/component-properties/computed-decorator/de-de.yaml b/translations/component-properties/computed-decorator/de-de.yaml
deleted file mode 100644
index 403fd03..0000000
--- a/translations/component-properties/computed-decorator/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: 'Der Decorator @computed'
-description: >
- Mit Octane wird es empfohlen, eine computed-Eigenschaft in eine tracked- zu ändern.
- Falls Sie sie nicht neu schreiben können (vielleicht brauchen Sie den Cache), ist der Decorator ''@computed'
' verfügbar.
\ No newline at end of file
diff --git a/translations/component-properties/computed-decorator/en-us.yaml b/translations/component-properties/computed-decorator/en-us.yaml
deleted file mode 100644
index 3e9c95c..0000000
--- a/translations/component-properties/computed-decorator/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: '@computed decorator'
-description: >
- In Octane, it is recommended to rewrite a computed property as tracked property.
- In case that isn't possible (maybe you need caching), the ''@computed'
' decorator is available.
\ No newline at end of file
diff --git a/translations/component-properties/computed-decorator/es.yaml b/translations/component-properties/computed-decorator/es.yaml
deleted file mode 100644
index c64b1d5..0000000
--- a/translations/component-properties/computed-decorator/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: '@computed decorator'
-description: >
- En Octane, se recomienda reescribir una propiedad computada como propiedad rastreada.
- En caso de que eso no sea posible (tal vez necesite de caché), el decorador ''@computed'
' está disponible.
diff --git a/translations/component-properties/computed-decorator/ja.yaml b/translations/component-properties/computed-decorator/ja.yaml
deleted file mode 100644
index e49ac0a..0000000
--- a/translations/component-properties/computed-decorator/ja.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: '@computedデコレーター'
-description: >
- Octaneにおいて、computedプロパティはtrackedプロパティとして書き直すのがオススメです。
- それが難しい場合(キャッシュしたい場合とか)、''@computed'
'デコレーターがが使用可能です。
diff --git a/translations/component-properties/computed-decorator/pt-br.yaml b/translations/component-properties/computed-decorator/pt-br.yaml
deleted file mode 100644
index 5e1a86a..0000000
--- a/translations/component-properties/computed-decorator/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: '@computed decorator'
-description: >
- Na Octane, é recomendável reescrever uma computed property como uma tracked property.
- No caso de não ser possível (talvez você precise do caching), o decorator ''@computed'
' está disponível.
\ No newline at end of file
diff --git a/translations/component-properties/ddau/de-de.yaml b/translations/component-properties/ddau/de-de.yaml
deleted file mode 100644
index 788c8b3..0000000
--- a/translations/component-properties/ddau/de-de.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Data Down, Actions Up
-description: >
- Octane-Komponenten setzen „Data Down, Actions Up“ durch.
- Daten fließen nur in eine Richtung, weswegen der Ruf eines übergebenen Callbacks (sog. Aktion) die einzige Methode ist, die Daten zu verändern.
- Mit anderen Worten, für die Argumente einer Komponente sollte das Two-Way-Binding unmöglich bleiben.
\ No newline at end of file
diff --git a/translations/component-properties/ddau/en-us.yaml b/translations/component-properties/ddau/en-us.yaml
deleted file mode 100644
index 08a2d0d..0000000
--- a/translations/component-properties/ddau/en-us.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Data Down, Actions Up
-description: >
- Octane components enforce "Data Down, Actions Up."
- When data is passed down to a component, the only way to change that data is to call an action that was passed in too.
- In another words, there is no two-way binding for component arguments.
\ No newline at end of file
diff --git a/translations/component-properties/ddau/es.yaml b/translations/component-properties/ddau/es.yaml
deleted file mode 100644
index f6712e9..0000000
--- a/translations/component-properties/ddau/es.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Data Down, Actions Up
-description: >
- Los componentes Octane refuerzan el concepto de "Data Down, Actions Up."
- Cuando los datos se pasan a un componente, la única forma de cambiar esos datos es llamar a una acción que también se pasó.
- En otras palabras, no existe un enlace bidireccional para los argumentos de los componentes.
diff --git a/translations/component-properties/ddau/ja.yaml b/translations/component-properties/ddau/ja.yaml
deleted file mode 100644
index bc6d9d9..0000000
--- a/translations/component-properties/ddau/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: データは下に、アクションは上に
-description: >
- Octaneコンポーネントは、「データは下に、アクションは上に」を強制します。
- データがコンポーネントに渡されるとき、データを変更する唯一の方法は、渡されたアクションを呼び出すことです。
- 言い換えると、コンポーネントの引数に対して双方向バインディングを設定することは出来ません。
diff --git a/translations/component-properties/ddau/pt-br.yaml b/translations/component-properties/ddau/pt-br.yaml
deleted file mode 100644
index 4dab62b..0000000
--- a/translations/component-properties/ddau/pt-br.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Data Down, Actions Up
-description: >
- Componentes Octane enfatizam "Data Down, Actions Up."
- Quando dados são passados para um componente, a única forma de modificar esses dados é chamando uma action que foi passada junto.
- Em outras palavras, não existe "two-way binding" para os argumentos dos componentes.
\ No newline at end of file
diff --git a/translations/component-properties/de-de.yaml b/translations/component-properties/de-de.yaml
deleted file mode 100644
index 8da2b44..0000000
--- a/translations/component-properties/de-de.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Eigenschaften der Komponenten
\ No newline at end of file
diff --git a/translations/component-properties/en-us.yaml b/translations/component-properties/en-us.yaml
deleted file mode 100644
index dc6b161..0000000
--- a/translations/component-properties/en-us.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Component Properties
\ No newline at end of file
diff --git a/translations/component-properties/es.yaml b/translations/component-properties/es.yaml
deleted file mode 100644
index 6159b46..0000000
--- a/translations/component-properties/es.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Propiedades de los componentes
diff --git a/translations/component-properties/get-and-set/de-de.yaml b/translations/component-properties/get-and-set/de-de.yaml
deleted file mode 100644
index 7c922d0..0000000
--- a/translations/component-properties/get-and-set/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Kein get und set erforderlich
-description: >
- Octane-Komponenten brauchen kein ''this.get'
' und ''this.set'
'.
- Lesen und Setzen Sie die Eigenschaften, genauso wie es bei nativen JavaScript-Klassen durchgeführt wird.
\ No newline at end of file
diff --git a/translations/component-properties/get-and-set/en-us.yaml b/translations/component-properties/get-and-set/en-us.yaml
deleted file mode 100644
index 09f14f7..0000000
--- a/translations/component-properties/get-and-set/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: No more get and set on components
-description: >
- Octane components do not use ''this.get'
' or ''this.set'
'.
- Access and modify properties directly, the same as you would in a regular JavaScript class.
\ No newline at end of file
diff --git a/translations/component-properties/get-and-set/es.yaml b/translations/component-properties/get-and-set/es.yaml
deleted file mode 100644
index 8e29ce8..0000000
--- a/translations/component-properties/get-and-set/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Ya no es necesario get y set en componentes
-description: >
- Los componentes Octane no utilizan ''this.get'
' ni ''this.set'
'.
- Acceda y modifique las propiedades directamente, al igual que lo haría en una clase de JavaScript normal.
diff --git a/translations/component-properties/get-and-set/ja.yaml b/translations/component-properties/get-and-set/ja.yaml
deleted file mode 100644
index e81c00b..0000000
--- a/translations/component-properties/get-and-set/ja.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: コンポーネントでgetとsetを使う必要はない
-description: >
- Octaneコンポーネントでは、''this.get'
'や''this.set'
'を使いません。
- プロパティは、通常のJavaScriptクラスのように直接アクセスし編集します。
diff --git a/translations/component-properties/get-and-set/pt-br.yaml b/translations/component-properties/get-and-set/pt-br.yaml
deleted file mode 100644
index d12759d..0000000
--- a/translations/component-properties/get-and-set/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Sem mais get e set nos componentes
-description: >
- Componentes Octane não usam ''this.get'
' ou ''this.set'
'.
- Acesse e modifique as properties diretamente, da mesma forma que você faria com qualquer classe JavaScript.
\ No newline at end of file
diff --git a/translations/component-properties/ja.yaml b/translations/component-properties/ja.yaml
deleted file mode 100644
index c34af30..0000000
--- a/translations/component-properties/ja.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: コンポーネント プロパティ
diff --git a/translations/component-properties/js-boilerplate/de-de.yaml b/translations/component-properties/js-boilerplate/de-de.yaml
deleted file mode 100644
index 65eb55b..0000000
--- a/translations/component-properties/js-boilerplate/de-de.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: JavaScript-Syntax der Komponenten
-description: >
- Auf den Namensraum ''@glimmer'
' bezieht sich eine Octane-Komponente beim Import von ihrer Klasse.
- Des Weiteren ermöglicht sie die native JavaScript-Syntax.
- Glimmer-Komponenten haben andere API-Methoden als die klassische.
- Wenn Sie mit den nativen Klassen nicht vertraut sind, können Sie sich sie durch ''die Dokumentation von MDN'' aneignen.
- Danach informieren Sie sich über die Glimmer-Komponenten mithilfe der ''Ember.js Guides'' und der ''API Dokumentation''.
\ No newline at end of file
diff --git a/translations/component-properties/js-boilerplate/en-us.yaml b/translations/component-properties/js-boilerplate/en-us.yaml
deleted file mode 100644
index 1bca45c..0000000
--- a/translations/component-properties/js-boilerplate/en-us.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Component JavaScript Syntax
-description: >
- An Octane component imports from the ''@glimmer'
' package namespace.
- It also uses native class syntax.
- Glimmer components have different API methods than classic components.
- If you aren't familiar with native classes, first check out the ''documentation on MDN''.
- Then, learn more about Glimmer components from the ''Ember.js Guides'' and the ''API Reference''.
\ No newline at end of file
diff --git a/translations/component-properties/js-boilerplate/es.yaml b/translations/component-properties/js-boilerplate/es.yaml
deleted file mode 100644
index 4d270cc..0000000
--- a/translations/component-properties/js-boilerplate/es.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Sintaxis de JavaScript de componentes
-description: >
- Un componente Octane es importado desde el espacio de nombre del paquete ''@glimmer'
'.
- Este también usa sintaxis de clase nativa.
- Los componentes de Glimmer tienen diferentes métodos de API que los componentes clásicos.
- Si no está familiarizado con las clases nativas, consulte ''la documentación en MDN''.
- Luego, obtenga más información sobre los componentes de Glimmer en las ''guías de Ember.js'' y en la ''Referencia de API''.
diff --git a/translations/component-properties/js-boilerplate/ja.yaml b/translations/component-properties/js-boilerplate/ja.yaml
deleted file mode 100644
index ada7030..0000000
--- a/translations/component-properties/js-boilerplate/ja.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: コンポーネントのJavaScript構文
-description: >
- Octaneコンポーネントは、''@glimmer'
'パッケージからimportします。
- また、ネイティブのクラス構文を使用します。
- GlimmerコンポーネントはClassicコンポーネントとは違うAPIを持っています。
- もしネイティブのクラスについて詳しくないのであれば、''MDNドキュメント''をまず見ましょう。
- そして、Glimmerコンポーネントについてさらに知りたい場合は、''Ember.js Guides''や''API Reference''を参照してください。
diff --git a/translations/component-properties/js-boilerplate/pt-br.yaml b/translations/component-properties/js-boilerplate/pt-br.yaml
deleted file mode 100644
index 28f4375..0000000
--- a/translations/component-properties/js-boilerplate/pt-br.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-title: Sintaxe do JavaScript do Componente
-description: >
- Um componente na Octane importa do namespace do pacote ''@glimmer'
'.
- Também usa sintaxe nativa de classes.
- Componentes Glimmer possuem diferentes métodos API com relação aos componentes clássicos.
- Se você ainda não está familiarizado com as classes nativas, dê uma olhada na ''documentação no MDN''.
- A partir daí, saiba mais sobre os componentes Glimmer no ''Ember.js Guides'' e na ''API Reference''.
diff --git a/translations/component-properties/js-properties/de-de.yaml b/translations/component-properties/js-properties/de-de.yaml
deleted file mode 100644
index 220851d..0000000
--- a/translations/component-properties/js-properties/de-de.yaml
+++ /dev/null
@@ -1,3 +0,0 @@
-title: Eigenschaften definieren
-description: >
- Mit der nativen JavaScript-Syntax können Sie die Eigenschaften definieren. Keine Kommas nötig!
\ No newline at end of file
diff --git a/translations/component-properties/js-properties/en-us.yaml b/translations/component-properties/js-properties/en-us.yaml
deleted file mode 100644
index 383cc63..0000000
--- a/translations/component-properties/js-properties/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Declaring a property
-description: >
- Properties follow native JavaScript class syntax.
- No commas!
\ No newline at end of file
diff --git a/translations/component-properties/js-properties/es.yaml b/translations/component-properties/js-properties/es.yaml
deleted file mode 100644
index 1c4f902..0000000
--- a/translations/component-properties/js-properties/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Declarar una propiedad
-description: >
- Las propiedades siguen la sintaxis de las clases nativas de JavaScript.
- ¡Sin comas!
diff --git a/translations/component-properties/js-properties/ja.yaml b/translations/component-properties/js-properties/ja.yaml
deleted file mode 100644
index d94990e..0000000
--- a/translations/component-properties/js-properties/ja.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: プロパティの宣言
-description: >
- ネイティブのJavaScriptのクラス構文に従いプロパティを書くことができます。
- カンマは必要ありません!
diff --git a/translations/component-properties/js-properties/pt-br.yaml b/translations/component-properties/js-properties/pt-br.yaml
deleted file mode 100644
index 37d11f0..0000000
--- a/translations/component-properties/js-properties/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Declarando uma property
-description: >
- Properties seguem a sintaxe nativa das classes JavaScript.
- Sem vírgulas!
\ No newline at end of file
diff --git a/translations/component-properties/pt-br.yaml b/translations/component-properties/pt-br.yaml
deleted file mode 100644
index faa4175..0000000
--- a/translations/component-properties/pt-br.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Properties do Componente
\ No newline at end of file
diff --git a/translations/component-properties/tracked-vs-cp/de-de.yaml b/translations/component-properties/tracked-vs-cp/de-de.yaml
deleted file mode 100644
index 4c39d85..0000000
--- a/translations/component-properties/tracked-vs-cp/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: '@tracked und Getters statt computed-Eigenschaften'
-description: >
- Markieren Sie mit ''@tracked'
' die Eigenschaften, die nachverfolgt müssen werden.
- Die Werte der Getters werden dann automatisch aktualisiert.
\ No newline at end of file
diff --git a/translations/component-properties/tracked-vs-cp/en-us.yaml b/translations/component-properties/tracked-vs-cp/en-us.yaml
deleted file mode 100644
index a97344f..0000000
--- a/translations/component-properties/tracked-vs-cp/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Use @tracked and getters instead of computed properties
-description: >
- Label the properties that should be tracked.
- Getters will be updated automatically.
\ No newline at end of file
diff --git a/translations/component-properties/tracked-vs-cp/es.yaml b/translations/component-properties/tracked-vs-cp/es.yaml
deleted file mode 100644
index b37a714..0000000
--- a/translations/component-properties/tracked-vs-cp/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Utilice @tracked y Getters en lugar de propiedades computadas
-description: >
- Etiquete las propiedades que se deben rastrear.
- Los Getters se actualizarán automáticamente.
diff --git a/translations/component-properties/tracked-vs-cp/ja.yaml b/translations/component-properties/tracked-vs-cp/ja.yaml
deleted file mode 100644
index ec1883d..0000000
--- a/translations/component-properties/tracked-vs-cp/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: '@trackedとゲッターをcomputedプロパティの代わりに使用する'
-description: >
- 追跡すべきプロパティにラベルを付けます。
- ゲッターは自動的に更新されます。
-
diff --git a/translations/component-properties/tracked-vs-cp/pt-br.yaml b/translations/component-properties/tracked-vs-cp/pt-br.yaml
deleted file mode 100644
index 4b718b0..0000000
--- a/translations/component-properties/tracked-vs-cp/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Use @tracked e getters ao invés de computed properties
-description: >
- Marque as properties que devem ser "trackeadas".
- Getters serão atualizados automaticamente.
\ No newline at end of file
diff --git a/translations/component-templates/angle-brackets-nested/de-de.yaml b/translations/component-templates/angle-brackets-nested/de-de.yaml
deleted file mode 100644
index 3d7af61..0000000
--- a/translations/component-templates/angle-brackets-nested/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Komponenten in einem Unterordner speichern
-description: >
- In einem Unterordner können Sie Komponenten speichern, dann können Sie sie mit der Winkelklammern aufrufen.
- Funktionell gibt es keine Unterschiede.
\ No newline at end of file
diff --git a/translations/component-templates/angle-brackets-nested/en-us.yaml b/translations/component-templates/angle-brackets-nested/en-us.yaml
deleted file mode 100644
index b20b2b5..0000000
--- a/translations/component-templates/angle-brackets-nested/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Nesting components in your file structure
-description: >
- You can nest components in your file structure, and use them in a template with angle brackets invocation.
- There's no change in behavior.
\ No newline at end of file
diff --git a/translations/component-templates/angle-brackets-nested/es.yaml b/translations/component-templates/angle-brackets-nested/es.yaml
deleted file mode 100644
index c35408f..0000000
--- a/translations/component-templates/angle-brackets-nested/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Anidar componentes en su estructura de archivos
-description: >
- Puede anidar componentes en su estructura de archivos y usarlos en un template con invocación de Angle Brackets.
- No hay cambios de comportamiento.
diff --git a/translations/component-templates/angle-brackets-nested/fr-fr.yaml b/translations/component-templates/angle-brackets-nested/fr-fr.yaml
deleted file mode 100644
index 47936f9..0000000
--- a/translations/component-templates/angle-brackets-nested/fr-fr.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: «Nester» les composants dans le système de fichiers
-description: >
- Vous pouvez «nester» les composants dans votre codebase et les utiliser dans un template via l'invocation «angle brackets».
- Les fonctionnalités seront identiques.
\ No newline at end of file
diff --git a/translations/component-templates/angle-brackets-nested/ja.yaml b/translations/component-templates/angle-brackets-nested/ja.yaml
deleted file mode 100644
index 263f37f..0000000
--- a/translations/component-templates/angle-brackets-nested/ja.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: ファイル構成でネストしているコンポーネント
-description: >
- ネストしたコンポーネントをファイル構成に含めることが出来ます。そして、山括弧('<>')呼び出しでネストしたコンポーネントを使うことができます。
- 動作に変更はありません。
diff --git a/translations/component-templates/angle-brackets-nested/pt-br.yaml b/translations/component-templates/angle-brackets-nested/pt-br.yaml
deleted file mode 100644
index a8330c5..0000000
--- a/translations/component-templates/angle-brackets-nested/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Componentes aninhados na estrutura de arquivos
-description: >
- Você pode aninhar componentes na sua estrutura de arquivos, e usá-los em um template com a chamada do tipo angle brackets.
- Não há mudança no comportamento.
\ No newline at end of file
diff --git a/translations/component-templates/angle-brackets/de-de.yaml b/translations/component-templates/angle-brackets/de-de.yaml
deleted file mode 100644
index 3eeff4d..0000000
--- a/translations/component-templates/angle-brackets/de-de.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Syntax der Winkelklammern
-description: >
- Mit der Winkelklammern (anstelle des geschweiften Klammern) können Sie Komponenten in einem Template rendern.
- Funktionell gibt es keine Unterschiede.
- Erfahren Sie ''die Hauptkonzepte zur Komponenten'' und ''die Anwendung der Codemods'', um Ihre bestehenden Komponenten aktualisieren zu können.
\ No newline at end of file
diff --git a/translations/component-templates/angle-brackets/en-us.yaml b/translations/component-templates/angle-brackets/en-us.yaml
deleted file mode 100644
index c495edc..0000000
--- a/translations/component-templates/angle-brackets/en-us.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Angle brackets component invocation
-description: >
- Angle brackets are a way to invoke components in a template file.
- There's no change in behavior.
- Learn more about ''features'' and ''using codemods'' to update your existing components.
\ No newline at end of file
diff --git a/translations/component-templates/angle-brackets/es.yaml b/translations/component-templates/angle-brackets/es.yaml
deleted file mode 100644
index 9bb951e..0000000
--- a/translations/component-templates/angle-brackets/es.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Invocación de componentes Angle brackets
-description: >
- Angle brackets son una forma de invocar componentes en un archivo de plantilla.
- No hay cambios de comportamiento.
- Aprender más acerca de ''caracteristicas'' y ''uso de codemods'' para actualizar sus componentes existentes.
diff --git a/translations/component-templates/angle-brackets/fr-fr.yaml b/translations/component-templates/angle-brackets/fr-fr.yaml
deleted file mode 100644
index 993a6a9..0000000
--- a/translations/component-templates/angle-brackets/fr-fr.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Invocation «Angle brackets» des composants
-description: >
- «Angle brackets» est une manière d'invoquer un/des composants dans un fichier de templates.
- Fonctionnellement, cela n'a aucun impact.
- Pour en savoir plus: ''features'' et ''les codemods'' pour migrer vos composants.
\ No newline at end of file
diff --git a/translations/component-templates/angle-brackets/ja.yaml b/translations/component-templates/angle-brackets/ja.yaml
deleted file mode 100644
index d273362..0000000
--- a/translations/component-templates/angle-brackets/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: 山括弧('<>')はコンポーネントを呼び出す
-description: >
- 山括弧('<>')を使えばテンプレートでコンポーネントを呼び出すことができます。
- 動作に変更はありません。
- 既存のコンポーネントを更新するために、''features''や''using codemods''を参照してください。
diff --git a/translations/component-templates/angle-brackets/pt-br.yaml b/translations/component-templates/angle-brackets/pt-br.yaml
deleted file mode 100644
index 05d6a04..0000000
--- a/translations/component-templates/angle-brackets/pt-br.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Chamada de componente com angle brackets
-description: >
- Angle brackets é uma forma de chamar os componentes dentro de um template.
- Não houve alteração no comportamento.
- Saiba mais sobre ''funcionalidades'' e o ''uso de codemods'' para atualizar os seus componentes atuais.
\ No newline at end of file
diff --git a/translations/component-templates/de-de.yaml b/translations/component-templates/de-de.yaml
deleted file mode 100644
index 81557f4..0000000
--- a/translations/component-templates/de-de.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Templates der Komponenten
\ No newline at end of file
diff --git a/translations/component-templates/element-id/de-de.yaml b/translations/component-templates/element-id/de-de.yaml
deleted file mode 100644
index 7cd2d4f..0000000
--- a/translations/component-templates/element-id/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: elementId
-description: >
- Da alle Komponenten „tagless“ sind, gibt es keine ''elementId'
' mehr.
- Sie können jedoch selbst eine ID generieren, um bspw. barrierefreie Formulare zu erstellen.
\ No newline at end of file
diff --git a/translations/component-templates/element-id/en-us.yaml b/translations/component-templates/element-id/en-us.yaml
deleted file mode 100644
index eb0e0bb..0000000
--- a/translations/component-templates/element-id/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Make your own elementId
-description: >
- Since components are tagless, there's no ''elementId'
', but you can generate your own.
- This is especially helpful for creating accessible forms.
\ No newline at end of file
diff --git a/translations/component-templates/element-id/es.yaml b/translations/component-templates/element-id/es.yaml
deleted file mode 100644
index 08772da..0000000
--- a/translations/component-templates/element-id/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Haga su propio elementId
-description: >
- Dado que los componentes no tienen etiquetas, no hay ''elementId'
', pero puede generar la suyo.
- Esto es especialmente útil para crear formularios accesibles.
diff --git a/translations/component-templates/element-id/ja.yaml b/translations/component-templates/element-id/ja.yaml
deleted file mode 100644
index 82655dc..0000000
--- a/translations/component-templates/element-id/ja.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: 自前のelementIdを作成する
-description: >
- コンポーネントはタグレスになったため、''elementId'
'はありません。しかし自前で生成することは出来ます。
- アクセシブルなフォームを作成する際に役立ちます。
diff --git a/translations/component-templates/element-id/pt-br.yaml b/translations/component-templates/element-id/pt-br.yaml
deleted file mode 100644
index ecca0e2..0000000
--- a/translations/component-templates/element-id/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Crie seu próprio elementId
-description: >
- Já que os componentes não possuem tags automáticas, não existe ''elementId'
', mas você pode criar o seu próprio.
- Isso é útil na criação de formulários acessíveis.
diff --git a/translations/component-templates/en-us.yaml b/translations/component-templates/en-us.yaml
deleted file mode 100644
index 4d6ea89..0000000
--- a/translations/component-templates/en-us.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Component Templates
\ No newline at end of file
diff --git a/translations/component-templates/es.yaml b/translations/component-templates/es.yaml
deleted file mode 100644
index ed39f04..0000000
--- a/translations/component-templates/es.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Templates de componentes
diff --git a/translations/component-templates/fr-fr.yaml b/translations/component-templates/fr-fr.yaml
deleted file mode 100644
index e2fc987..0000000
--- a/translations/component-templates/fr-fr.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Templates des composants
\ No newline at end of file
diff --git a/translations/component-templates/inline-vs-block/de-de.yaml b/translations/component-templates/inline-vs-block/de-de.yaml
deleted file mode 100644
index 58175ba..0000000
--- a/translations/component-templates/inline-vs-block/de-de.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Inline- und Block-Komponenten
-description: >
- Mit der Winkelklammern können Sie sowohl Inline- als auch Block-Komponenten rendern.
- Funktionell gibt es keine Unterschiede.
- Die Syntax '{{yield}}
' sieht gleich aus und funktionert auch so.
- Erfahren Sie ''die Hauptkonzepte zur Komponenten'' und ''die Anwendung der Codemods'', um Ihre bestehenden Komponenten aktualisieren zu können.
\ No newline at end of file
diff --git a/translations/component-templates/inline-vs-block/en-us.yaml b/translations/component-templates/inline-vs-block/en-us.yaml
deleted file mode 100644
index b8137d5..0000000
--- a/translations/component-templates/inline-vs-block/en-us.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Inline vs block components
-description: >
- Angle brackets components can be used as either inline or block components.
- There's no change in behavior.
- '{{yield}}
' looks and works the same.
- Learn more about ''features'' and ''using codemods'' to update your existing components.
\ No newline at end of file
diff --git a/translations/component-templates/inline-vs-block/es.yaml b/translations/component-templates/inline-vs-block/es.yaml
deleted file mode 100644
index 257f648..0000000
--- a/translations/component-templates/inline-vs-block/es.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Componentes en línea vs en bloque
-description: >
- Los componentes Angle brackets se puede utilizar como componentes en línea o en bloque.
- No hay cambios de comportamiento.
- '{{yield}}
' se ve y funciona igual.
- Aprender más acerca de ''caracteristicas'' y ''uso de codemods'' para actualizar sus componentes existentes.
diff --git a/translations/component-templates/inline-vs-block/fr-fr.yaml b/translations/component-templates/inline-vs-block/fr-fr.yaml
deleted file mode 100644
index c7d83af..0000000
--- a/translations/component-templates/inline-vs-block/fr-fr.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Composants inline vs composants block
-description: >
- Vous pouvez invoquer un composant «Angle brackets» inline ou bien sous forme de block.
- Le fonctionnement ne sera pas affecté.
- '{{yield}}
' se comporte de la même manière.
- Pour en savoir plus: ''features'' et ''les codemods'' pour migrer vos composants.
\ No newline at end of file
diff --git a/translations/component-templates/inline-vs-block/ja.yaml b/translations/component-templates/inline-vs-block/ja.yaml
deleted file mode 100644
index fbd423b..0000000
--- a/translations/component-templates/inline-vs-block/ja.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: インラインコンポーネント vs ブロックコンポーネント
-description: >
- 山括弧('<>')コンポーネントはインラインコンポーネントとしても、ブロックコンポーネントとしても使うことが出来ます。
- 動作に変更はありません。
- '{{yield}}
'の見た目も動作も同じです。
- 既存のコンポーネントを更新するために、''features''や''using codemods''を参照してください。
diff --git a/translations/component-templates/inline-vs-block/pt-br.yaml b/translations/component-templates/inline-vs-block/pt-br.yaml
deleted file mode 100644
index 8400ecb..0000000
--- a/translations/component-templates/inline-vs-block/pt-br.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-title: Componentes inline vs block
-description: >
- Componentes do tipo angle brackets podem ser usados tanto inline quanto no formato de block.
- Não há mudança no comportamento.
- Usa-se '{{yield}}
' da mesma forma, e o comportamento é o mesmo.
- Saiba mais sobre ''funcionalidades'' e o ''uso de codemods'' para atualizar os seus componentes atuais.
\ No newline at end of file
diff --git a/translations/component-templates/ja.yaml b/translations/component-templates/ja.yaml
deleted file mode 100644
index 916c03e..0000000
--- a/translations/component-templates/ja.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: コンポーネント テンプレート
diff --git a/translations/component-templates/pt-br.yaml b/translations/component-templates/pt-br.yaml
deleted file mode 100644
index 9cecce2..0000000
--- a/translations/component-templates/pt-br.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Templates dos Componentes
\ No newline at end of file
diff --git a/translations/component-templates/tag-name/de-de.yaml b/translations/component-templates/tag-name/de-de.yaml
deleted file mode 100644
index bfd0d14..0000000
--- a/translations/component-templates/tag-name/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Alle Komponenten sind „tagless“
-description: >
- Mit Octane haben die Komponenten keinen Behälter mehr, folglich brauchen Sie keinen ''tagName'
'.
- Schreiben Sie je nach Bedarf das Tag im Template.
\ No newline at end of file
diff --git a/translations/component-templates/tag-name/en-us.yaml b/translations/component-templates/tag-name/en-us.yaml
deleted file mode 100644
index 3dcc33f..0000000
--- a/translations/component-templates/tag-name/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: All components are tagless
-description: >
- In Octane, components don't have a default wrapper anymore, so you don't need ''tagName'
'!
- Just put the tag right in the template.
\ No newline at end of file
diff --git a/translations/component-templates/tag-name/es.yaml b/translations/component-templates/tag-name/es.yaml
deleted file mode 100644
index 2395214..0000000
--- a/translations/component-templates/tag-name/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Todos los componentes no tienen etiquetas
-description: >
- En Octane, los componentes ya no tienen un contenedor predeterminado, ¡por lo que no es necesario ''tagName'
'!
- Simplemente coloque la etiqueta en la plantilla.
diff --git a/translations/component-templates/tag-name/ja.yaml b/translations/component-templates/tag-name/ja.yaml
deleted file mode 100644
index b8264af..0000000
--- a/translations/component-templates/tag-name/ja.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: すべてのコンポーネントはタグレスである
-description: >
- Octaneでは、コンポーネントはもはやデフォルトのラッパーを持っていません。そのため、''tagName'
'は必要ありません!
- タグをテンプレートに正しく配置するだけです。
diff --git a/translations/component-templates/tag-name/pt-br.yaml b/translations/component-templates/tag-name/pt-br.yaml
deleted file mode 100644
index c342a66..0000000
--- a/translations/component-templates/tag-name/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Todos os componentes são "tagless"
-description: >
- Na Octane, componentes não são automaticamente envolvidos em uma tag HTML, então ''tagName'
' não é necessário!
- Apenas use a tag no próprio template.
\ No newline at end of file
diff --git a/translations/component-templates/template-arguments-named/de-de.yaml b/translations/component-templates/template-arguments-named/de-de.yaml
deleted file mode 100644
index 7b7df3d..0000000
--- a/translations/component-templates/template-arguments-named/de-de.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Argumente übergeben
-description: >
- Wenn Sie einer Komponente ein Argument weitergeben möchten, fügen Sie vorm Argumentnamen ''@'
' hinzu.
- Funktionell gibt es keine Unterschiede.
- Erfahren Sie ''die Hauptkonzepte zur Komponenten'' und ''die Anwendung der Codemods'', um Ihre bestehenden Komponenten aktualisieren zu können.
\ No newline at end of file
diff --git a/translations/component-templates/template-arguments-named/en-us.yaml b/translations/component-templates/template-arguments-named/en-us.yaml
deleted file mode 100644
index c938ce5..0000000
--- a/translations/component-templates/template-arguments-named/en-us.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Passing named arguments
-description: >
- When you pass an argument to a component, use an ''@'
' symbol on the left hand side.
- There's no change in behavior.
- Learn more about ''features'' and ''using codemods'' to update your existing components.
\ No newline at end of file
diff --git a/translations/component-templates/template-arguments-named/es.yaml b/translations/component-templates/template-arguments-named/es.yaml
deleted file mode 100644
index 25790fd..0000000
--- a/translations/component-templates/template-arguments-named/es.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Pasar argumentos con nombre
-description: >
- Cuando pase un argumento a un componente, utilice un símbolo ''@'
' en el lado izquierdo.
- No hay cambios de comportamiento.
- Aprender más acerca de ''caracteristicas'' y ''uso de codemods'' para actualizar sus componentes existentes.
diff --git a/translations/component-templates/template-arguments-named/fr-fr.yaml b/translations/component-templates/template-arguments-named/fr-fr.yaml
deleted file mode 100644
index 8dac125..0000000
--- a/translations/component-templates/template-arguments-named/fr-fr.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Les arguments nommés lors de l'invocation
-description: >
- Lorsque vous fournissez un argument à un composant lors de l'invocation, préfixez le nom de cet argument par un ''@'
'.
- Fonctionnellement, cela n'a aucun impact.
- Pour en savoir plus ''features'' et ''les codemods'' pour migrer vos composants.
\ No newline at end of file
diff --git a/translations/component-templates/template-arguments-named/ja.yaml b/translations/component-templates/template-arguments-named/ja.yaml
deleted file mode 100644
index efe1e96..0000000
--- a/translations/component-templates/template-arguments-named/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: 名前付き引数を渡す
-description: >
- ''@'
'を左辺の接頭詞としてつけることで、コンポーネントに引数を渡すことが出来ます。
- 動作に変更はありません。
- 既存のコンポーネントを更新するために、''features''や''using codemods''を参照してください。
diff --git a/translations/component-templates/template-arguments-named/pt-br.yaml b/translations/component-templates/template-arguments-named/pt-br.yaml
deleted file mode 100644
index 40f4f13..0000000
--- a/translations/component-templates/template-arguments-named/pt-br.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Passando argumentos nomeados
-description: >
- Quando você passa um argumento para um componente, use uma ''@'
' no início do argumento.
- Não há mudança no comportamento.
- Saiba mais sobre ''funcionalidades'' e o ''uso de codemods'' para atualizar os seus componentes atuais.
\ No newline at end of file
diff --git a/translations/component-templates/template-arguments-this/de-de.yaml b/translations/component-templates/template-arguments-this/de-de.yaml
deleted file mode 100644
index 36f232d..0000000
--- a/translations/component-templates/template-arguments-this/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Eigenschaften übergeben
-description: >
- Wenn Sie einer Komponente eine Eigenschaft übergeben möchten, fügen Sie vor ihrem Namen ''this'
' hinzu.
- Erfahren Sie ''die Hauptkonzepte zur Komponenten'' und ''die Anwendung der Codemods'', um Ihre bestehenden Komponenten aktualisieren zu können.
\ No newline at end of file
diff --git a/translations/component-templates/template-arguments-this/en-us.yaml b/translations/component-templates/template-arguments-this/en-us.yaml
deleted file mode 100644
index ebb4092..0000000
--- a/translations/component-templates/template-arguments-this/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Passing arguments defined on "this" component
-description: >
- If a property is coming from a template's own JavaScript file, remember to put a ''this'
' before it and wrap it in curly braces.
- Learn more about ''features'' and ''using codemods'' to update your existing components.
\ No newline at end of file
diff --git a/translations/component-templates/template-arguments-this/es.yaml b/translations/component-templates/template-arguments-this/es.yaml
deleted file mode 100644
index c39bf9a..0000000
--- a/translations/component-templates/template-arguments-this/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Pasar argumentos definidos en "este" componente
-description: >
- Si una propiedad proviene del mismo archivo JavaScript del template, recuerde poner un ''this'
' delante de él y envuélvalo en llaves.
- Aprender más acerca de ''caracteristicas'' y ''uso de codemods'' para actualizar sus componentes existentes.
diff --git a/translations/component-templates/template-arguments-this/ja.yaml b/translations/component-templates/template-arguments-this/ja.yaml
deleted file mode 100644
index fcb198c..0000000
--- a/translations/component-templates/template-arguments-this/ja.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: 自身のコンポーネントに定義された引数を渡す
-description: >
- テンプレート自身のJavaScriptファイルにあるプロパティの場合、''this'
'をプロパティに接頭詞として付与し、中括弧('{}')で囲います。
- 既存のコンポーネントを更新するために、''features''や''using codemods''を参照してください。
diff --git a/translations/component-templates/template-arguments-this/pt-br.yaml b/translations/component-templates/template-arguments-this/pt-br.yaml
deleted file mode 100644
index 69e9ed7..0000000
--- a/translations/component-templates/template-arguments-this/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Passando argumentos definidos no próprio componente
-description: >
- Se uma property vem do JavaScript do próprio componente, lembre de colocar ''this'
' antes da variável e entre chaves.
- Saiba mais sobre ''funcionalidades'' e o ''uso de codemods'' para atualizar seus componentes atuais.
\ No newline at end of file
diff --git a/translations/component-templates/template-named/de-de.yaml b/translations/component-templates/template-named/de-de.yaml
deleted file mode 100644
index 80b27f7..0000000
--- a/translations/component-templates/template-named/de-de.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Argumente
-description: >
- Nimmt die Komponente von ihrer Eltern ein Argument entgegen, fügen Sie vorm Argumentnamen ''@'
' hinzu.
- Funktionell gibt es keine Unterschiede.
- (''Besuchen Sie die Ember Guides, um mehr zu erfahren''.)
\ No newline at end of file
diff --git a/translations/component-templates/template-named/en-us.yaml b/translations/component-templates/template-named/en-us.yaml
deleted file mode 100644
index 610c380..0000000
--- a/translations/component-templates/template-named/en-us.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Using named argument
-description: >
- If a property was received from a parent component, refer to it with an ''@'
'.
- There's no change in behavior.
- (''Visit the Ember Guides to learn more''.)
\ No newline at end of file
diff --git a/translations/component-templates/template-named/es.yaml b/translations/component-templates/template-named/es.yaml
deleted file mode 100644
index d532fae..0000000
--- a/translations/component-templates/template-named/es.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Usando un argumento con nombre
-description: >
- Si una propiedad se recibe desde un componente de padre, refierace a ella con una ''@'
'.
- No hay cambios de comportamiento.
- (''Visite las guías de Ember para obtener más información''.)
diff --git a/translations/component-templates/template-named/fr-fr.yaml b/translations/component-templates/template-named/fr-fr.yaml
deleted file mode 100644
index 0f55847..0000000
--- a/translations/component-templates/template-named/fr-fr.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Utiliser les arguments nommés
-description: >
- Quand vous faites référence à une propriété précisée lors de l'invocation, elle doit être préfixée d'un ''@'
'.
- Fonctionnellement, cela n'a aucun impact.
- (''Consultez les «Ember Guides» pour en savoir plus''.)
\ No newline at end of file
diff --git a/translations/component-templates/template-named/ja.yaml b/translations/component-templates/template-named/ja.yaml
deleted file mode 100644
index 2f6a686..0000000
--- a/translations/component-templates/template-named/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: 名前付き引数を使う
-description: >
- 親コンポーネントからプロパティを受け取った場合、''@'
'を接頭詞として付けることで参照出来ます。
- 動作に変更はありません。
- (''Emberガイドにより多くの情報があります。'')
diff --git a/translations/component-templates/template-named/pt-br.yaml b/translations/component-templates/template-named/pt-br.yaml
deleted file mode 100644
index 46532fe..0000000
--- a/translations/component-templates/template-named/pt-br.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Usando argumentos nomeados
-description: >
- Se uma property foi recebida de um componente pai, faça a referência usando ''@'
'.
- Não há mudança no comportamento.
- (''Veja o Ember Guides para saber mais''.)
\ No newline at end of file
diff --git a/translations/component-templates/template-this/de-de.yaml b/translations/component-templates/template-this/de-de.yaml
deleted file mode 100644
index 903fce5..0000000
--- a/translations/component-templates/template-this/de-de.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Eigenschaften
-description: >
- Ist eine Eigenschaft in der JavaScript-Klasse der Komponente definiert, fügen Sie vor ihrem Namen ''this'
' hinzu.
- Funktionell gibt es keine Unterschiede.
- Erfahren Sie ''die Hauptkonzepte zur Komponenten'' und ''die Anwendung der Codemods'', um Ihre bestehenden Komponenten aktualisieren zu können.
\ No newline at end of file
diff --git a/translations/component-templates/template-this/en-us.yaml b/translations/component-templates/template-this/en-us.yaml
deleted file mode 100644
index d871d18..0000000
--- a/translations/component-templates/template-this/en-us.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Using own properties
-description: >
- If a property is defined in the JavaScript file for this component's template, use ''this'
' when you refer to it.
- There's no change in behavior.
- Learn more about ''features'' and ''using codemods'' to update your existing components.
\ No newline at end of file
diff --git a/translations/component-templates/template-this/es.yaml b/translations/component-templates/template-this/es.yaml
deleted file mode 100644
index 309820e..0000000
--- a/translations/component-templates/template-this/es.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Usando propiedades propias
-description: >
- Si una propiedad está definida en el archivo JavaScript para el template de este componente, utilice ''this'
' cuando se refiera a esta.
- No hay cambios de comportamiento.
- Aprender más acerca de ''caracteristicas'' y ''uso codemods'' para actualizar sus componentes existentes.
diff --git a/translations/component-templates/template-this/fr-fr.yaml b/translations/component-templates/template-this/fr-fr.yaml
deleted file mode 100644
index 0f1e236..0000000
--- a/translations/component-templates/template-this/fr-fr.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Utiliser les propriétés d'un composant
-description: >
- Lorsqu'une propriété est définie dans le fichier JavaScript d'un composant, elle doit être préfixée par ''this'
' lorsque vous y faites référence dans le template du composant.
- Fonctionnellement, cela n'a aucun impact.
- Pour en savoir plus ''features'' et ''les codemods'' pour migrer vos composants.
\ No newline at end of file
diff --git a/translations/component-templates/template-this/ja.yaml b/translations/component-templates/template-this/ja.yaml
deleted file mode 100644
index e50dbca..0000000
--- a/translations/component-templates/template-this/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: 自分のプロパティを使う
-description: >
- テンプレートのJavaScriptファイルでプロパティが定義されている場合、''this'
'を接頭詞として付けることで参照することができます。
- 動作に変更はありません。
- 既存のコンポーネントを更新するために、''features''や''using codemods''を参照してください。
diff --git a/translations/component-templates/template-this/pt-br.yaml b/translations/component-templates/template-this/pt-br.yaml
deleted file mode 100644
index 34b5bf1..0000000
--- a/translations/component-templates/template-this/pt-br.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Usando properties próprias
-description: >
- Se uma property é definida no arquivo JavaScript desse componente, use ''this'
' quando estiver fazendo uma referência.
- Não há mudança no comportamento.
- Saiba mais sobre ''funcionalidades'' e o ''uso de codemods'' para atualizar os seus componentes atuais.
diff --git a/translations/de-de.yaml b/translations/de-de.yaml
index 43605b2..c5aa7e3 100644
--- a/translations/de-de.yaml
+++ b/translations/de-de.yaml
@@ -1,20 +1,20 @@
layout:
application:
- logo-alt-text: 'Ember Octane: die neueste Edition von Ember.js'
- title: EmberData Request Service Cheat Sheet
+ logo-alt-text: 'EmberData Request Service Spickzettel'
+ title: EmberData Request Service Spickzettel
description-1: >
- Dieses Guide ist ein ''Ember Octane''-Spickzettel.
- Sie finden nicht alles darin, aber es sollte Ihren Einstieg in Ember.js erleichtern.
- Pull Requests können auf ''GitHub'' eingereicht werden.
+ Dieser Leitfaden ist ein Spickzettel für die Verwendung des 'EmberData-Anforderungsdienstes'.
+ Es deckt nicht alles ab, aber es sollte Ihnen den Einstieg erleichtern!
+ PRs sind willkommen im ''GitHub-Repository''.
description-2: >
- Sehen Sie in ''The Octane Upgrading Guide'' nach, um sich über das Upgrade auf Octane zu informieren.
+ Für detaillierte Informationen zu den Upgrade-Pfaden und Unterschieden im Vergleich zu älteren EmberData-Mustern, siehe 'den RFC für den EmberData-Anforderungsdienst'.
component:
guide-section:
section: §
subsection:
classic: Classic
- octane: Octane
+ octane: Request Service
edit-translation-text: Übersetzung ändern
locale-menu:
locale-select:
diff --git a/translations/es.yaml b/translations/es.yaml
index 0a23abe..5bea54f 100644
--- a/translations/es.yaml
+++ b/translations/es.yaml
@@ -1,20 +1,20 @@
layout:
application:
- logo-alt-text: 'Ember Octane: la última edición de Ember.js'
- title: EmberData Request Service Cheat Sheet
+ logo-alt-text: 'EmberData Request Service Cheat Sheet'
+ title: Hoja de trucos del servicio de solicitud de EmberData
description-1: >
- Esta guía es una hoja de referencia para usar ''Ember.js Octane''.
- No cubre todo, ¡pero debería ayudarlo a comenzar!
- PRs bienvenidos en ''el repositorio de GitHub''.
+ Esta guía es una hoja de trucos para usar el 'Servicio de solicitud de EmberData'.
+ No cubre todo, ¡pero te ayudará a empezar!
+ Se aceptan PRs en ''el repositorio de GitHub''.
description-2: >
- Para obtener información detallada sobre la ruta de actualización y las diferencias introducidas en Octane, vea ''The Octane Upgrading Guide''.
+ Para obtener información detallada sobre las rutas de actualización y las diferencias en comparación con los patrones antiguos de EmberData, consulta 'el RFC para el Servicio de solicitud de EmberData'.
component:
guide-section:
section: §
subsection:
- classic: Classic
- octane: Octane
+ classic: Older patterns
+ octane: Request Service
edit-translation-text: Editar traducción
locale-menu:
locale-select:
diff --git a/translations/fetching-data/de-de.yaml b/translations/fetching-data/de-de.yaml
new file mode 100644
index 0000000..4cf05d4
--- /dev/null
+++ b/translations/fetching-data/de-de.yaml
@@ -0,0 +1 @@
+title: Daten Abrufen
diff --git a/translations/fetching-data/es.yaml b/translations/fetching-data/es.yaml
new file mode 100644
index 0000000..8d9ce69
--- /dev/null
+++ b/translations/fetching-data/es.yaml
@@ -0,0 +1 @@
+title: Recuperacion de datos
diff --git a/translations/fetching-data/fr-fr.yaml b/translations/fetching-data/fr-fr.yaml
new file mode 100644
index 0000000..3973c8a
--- /dev/null
+++ b/translations/fetching-data/fr-fr.yaml
@@ -0,0 +1 @@
+title: Récupération des données
diff --git a/translations/fetching-data/ja.yaml b/translations/fetching-data/ja.yaml
new file mode 100644
index 0000000..7eafd19
--- /dev/null
+++ b/translations/fetching-data/ja.yaml
@@ -0,0 +1 @@
+title: データの取得
diff --git a/translations/fetching-data/pt-br.yaml b/translations/fetching-data/pt-br.yaml
new file mode 100644
index 0000000..b5973fb
--- /dev/null
+++ b/translations/fetching-data/pt-br.yaml
@@ -0,0 +1 @@
+title: Buscando Dados
diff --git a/translations/fr-fr.yaml b/translations/fr-fr.yaml
index a7a8b6d..931a210 100644
--- a/translations/fr-fr.yaml
+++ b/translations/fr-fr.yaml
@@ -1,20 +1,20 @@
layout:
application:
- logo-alt-text: 'Ember Octane: the latest edition from Ember.js'
- title: EmberData Request Service Cheat Sheet
+ logo-alt-text: 'Feuille de triche du service de demande EmberData'
+ title: Feuille de triche du service de demande EmberData
description-1: >
- Ce guide est un aide-mémoire (eng: cheat sheet) afin d'utiliser ''Ember.js Octane''.
- Tout n'y est pas abordé, mais il devrait permettre de bien démarrer avec Octane!
- Toutes les PRs sont les bienvenues sur ''le repository GitHub''.
+ Ce guide est une feuille de triche pour utiliser le 'service de demande EmberData'.
+ Il ne couvre pas tout, mais cela devrait vous aider à démarrer!
+ Les PR sont les bienvenus sur ''le dépôt GitHub''.
description-2: >
- Pour plus d'information sur la manière de migrer vers Octane et les nouveautés qui y sont introduites, consultez ''Le guide de migration vers Octane''.
+ Pour des informations approfondies sur les chemins de mise à niveau et les différences par rapport aux anciens modèles EmberData, consultez 'la RFC pour le service de demande EmberData'.
component:
guide-section:
section: §
subsection:
- classic: Classic
- octane: Octane
+ classic: Older patterns
+ octane: Request Service
edit-translation-text: Edit Translation
locale-menu:
locale-select:
diff --git a/translations/generating-files/de-de.yaml b/translations/generating-files/de-de.yaml
deleted file mode 100644
index d1e0ab7..0000000
--- a/translations/generating-files/de-de.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Dateien erstellen
\ No newline at end of file
diff --git a/translations/generating-files/en-us.yaml b/translations/generating-files/en-us.yaml
deleted file mode 100644
index f318e42..0000000
--- a/translations/generating-files/en-us.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Generating Files
\ No newline at end of file
diff --git a/translations/generating-files/es.yaml b/translations/generating-files/es.yaml
deleted file mode 100644
index a30208e..0000000
--- a/translations/generating-files/es.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Generar archivos
diff --git a/translations/generating-files/file-structure/de-de.yaml b/translations/generating-files/file-structure/de-de.yaml
deleted file mode 100644
index d860910..0000000
--- a/translations/generating-files/file-structure/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Das Template und die JavaScript-Klasse einer Komponente existieren nebeneinander
-description: >
- Mit Octane ist die Speicherstelle des Templates anders.
- Dies bezeichnet man als „template co-location“.
\ No newline at end of file
diff --git a/translations/generating-files/file-structure/en-us.yaml b/translations/generating-files/file-structure/en-us.yaml
deleted file mode 100644
index b38d17e..0000000
--- a/translations/generating-files/file-structure/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Component templates and JavaScript are in the same directory
-description: >
- The location of component templates has changed in Octane.
- This is known as "template co-location."
\ No newline at end of file
diff --git a/translations/generating-files/file-structure/es.yaml b/translations/generating-files/file-structure/es.yaml
deleted file mode 100644
index 89ab986..0000000
--- a/translations/generating-files/file-structure/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Los templates de componentes y el archivo JavaScript están en el mismo directorio
-description: >
- La ubicación de los templates de componentes ha cambiado en Octane.
- Esto se conoce como "template co-location."
diff --git a/translations/generating-files/file-structure/fr-fr.yaml b/translations/generating-files/file-structure/fr-fr.yaml
deleted file mode 100644
index 5c67bbc..0000000
--- a/translations/generating-files/file-structure/fr-fr.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Les fichiers .hbs et .js d'un composant sont placés dans le même dossier
-description: >
- Avec Octane, l'emplacement du template d'un composant a changé.
- Nous parlons maintenant de "template co-location."
\ No newline at end of file
diff --git a/translations/generating-files/file-structure/ja.yaml b/translations/generating-files/file-structure/ja.yaml
deleted file mode 100644
index 2bf6f0d..0000000
--- a/translations/generating-files/file-structure/ja.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: コンポーネントのテンプレートとJavaScriptは同じディレクトリに生成される
-description: >
- Octaneでは、コンポーネントのテンプレートの場所が変更されました。
- これは"template co-location"と呼ばれています。
diff --git a/translations/generating-files/file-structure/pt-br.yaml b/translations/generating-files/file-structure/pt-br.yaml
deleted file mode 100644
index ee028cc..0000000
--- a/translations/generating-files/file-structure/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Templates e arquivos JavaScript dos componentes ficam no mesmo diretório
-description: >
- A localização dos templates dos componentes mudou no Octane.
- Chamamos esse formato de "template co-location."
\ No newline at end of file
diff --git a/translations/generating-files/fr-fr.yaml b/translations/generating-files/fr-fr.yaml
deleted file mode 100644
index 49a1d91..0000000
--- a/translations/generating-files/fr-fr.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Génération de fichiers
\ No newline at end of file
diff --git a/translations/generating-files/generating-component/de-de.yaml b/translations/generating-files/generating-component/de-de.yaml
deleted file mode 100644
index 0adce63..0000000
--- a/translations/generating-files/generating-component/de-de.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Geben Sie ein Flag ein, um die JavaScript-Klasse einer Komponente zu erstellen
-description: >
- Mit Ember Classic hat der Befehl ''ember generate component'
' 3 Dateien angelegt: ein Template, eine JavaScript-Klasse und einen Test.
- Verglichen damit erstellt Octane automatisch keine JavaScript-Klasse.
- Verwenden Sie das Flag ''-gc'
', um sie zu erstellen.
\ No newline at end of file
diff --git a/translations/generating-files/generating-component/en-us.yaml b/translations/generating-files/generating-component/en-us.yaml
deleted file mode 100644
index dcde8d0..0000000
--- a/translations/generating-files/generating-component/en-us.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Use an option to generate a component's JavaScript
-description: >
- In classic Ember, ''ember generate component'
' created three files: the template, a JavaScript file, and a test.
- In Octane, ''ember generate component'
' skips creating the JavaScript file.
- If you want the backing JavaScript class as well, include the ''-gc'
' option.
\ No newline at end of file
diff --git a/translations/generating-files/generating-component/es.yaml b/translations/generating-files/generating-component/es.yaml
deleted file mode 100644
index 3645338..0000000
--- a/translations/generating-files/generating-component/es.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Utilice una opción para generar el JavaScript de un componente
-description: >
- En Ember clásico, ''ember generate component'
' creaba tres archivos: el template, el archivo JavaScript, y el archivo de test.
- En Octane, ''ember generate component'
' omite la creación del archivo JavaScript.
- Si desea la clase (archivo) JavaScript para el componente, incluya la opción ''-gc'
'.
diff --git a/translations/generating-files/generating-component/fr-fr.yaml b/translations/generating-files/generating-component/fr-fr.yaml
deleted file mode 100644
index 780b5e5..0000000
--- a/translations/generating-files/generating-component/fr-fr.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Utiliser une option pour générer le fichier JavaScript d'un composant
-description: >
- Avec Ember classic, ''ember generate component'
' générait trois fichiers: le template, un fichier JavaScript et un test.
- Sous Octane, ''ember generate component'
' crée uniquement un template.
- Si vous souhaitez également générer le fichier JavaScript définissant la class, vous devez préciser une option.
\ No newline at end of file
diff --git a/translations/generating-files/generating-component/ja.yaml b/translations/generating-files/generating-component/ja.yaml
deleted file mode 100644
index 8a81b02..0000000
--- a/translations/generating-files/generating-component/ja.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: オプションを使用してコンポーネントのJavaScriptを生成する
-description: >
- Classic Emberでは、''ember generate component'
'を実行することで3つのファイルが生成されました。テンプレート、JavaScript、そしてテストです。
- Octaneは、''ember generate component'
'を実行してもJavaScriptファイルは生成されません。
- もしテンプレートを補佐するJavaScriptファイルが欲しいのであれば、''-gc'
'オプションもコマンド実行時に含める必要があります。
diff --git a/translations/generating-files/generating-component/pt-br.yaml b/translations/generating-files/generating-component/pt-br.yaml
deleted file mode 100644
index b12612e..0000000
--- a/translations/generating-files/generating-component/pt-br.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-title: Use uma opção para gerar o arquivo JavaScript de um componente
-description: >
- No Ember clássico, ''ember generate component'
' criava três arquivos: o template, um arquivo JavaScript e um teste.
- No Octane, ''ember generate component'
' não cria o arquivo JavaScript.
- Caso queira o arquivo JavaScript com a classe do componente, inclua a opção ''-gc'
'.
diff --git a/translations/generating-files/ja.yaml b/translations/generating-files/ja.yaml
deleted file mode 100644
index b55a1c0..0000000
--- a/translations/generating-files/ja.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: ファイルの生成
diff --git a/translations/generating-files/pt-br.yaml b/translations/generating-files/pt-br.yaml
deleted file mode 100644
index 6716244..0000000
--- a/translations/generating-files/pt-br.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Geração de arquivos
\ No newline at end of file
diff --git a/translations/ja.yaml b/translations/ja.yaml
index 5061888..7170c79 100644
--- a/translations/ja.yaml
+++ b/translations/ja.yaml
@@ -1,20 +1,20 @@
layout:
application:
- logo-alt-text: 'Ember Octane: Ember.jsの最新版'
- title: Ember.js OctaneとClassicの比較用チートシート
+ logo-alt-text: 'EmberData リクエストサービス チートシート'
+ title: EmberData リクエストサービス チートシート
description-1: >
- このガイドは、''Ember.js Octane''を使うためのチートシートです。
- すべてを網羅しているわけではありませんが、始めるには十分です!
- プルリクエストを''GitHubリポジトリ''でお待ちしてます。
+ このガイドは、'EmberDataのリクエストサービス'の使用に関するチートシートです。
+ すべてを網羅しているわけではありませんが、スタートするのに役立つでしょう!
+ 'GitHubリポジトリ'でのPRは歓迎です。
description-2: >
- より詳細なアップグレードパスや、Octaneで導入された違いについての情報は、''The Octane Upgrading Guide''を参照してください。
+ アップグレードパスや古いEmberDataパターンとの違いについての詳細な情報については、'EmberDataリクエストサービスのRFC'を参照してください。
component:
guide-section:
section: §
subsection:
- classic: Classic
- octane: Octane
+ classic: Older patterns
+ octane: Request Service
edit-translation-text: 翻訳を修正する
locale-menu:
locale-select:
diff --git a/translations/pt-br.yaml b/translations/pt-br.yaml
index c2806e7..43d1b15 100644
--- a/translations/pt-br.yaml
+++ b/translations/pt-br.yaml
@@ -1,20 +1,20 @@
layout:
application:
- logo-alt-text: 'Ember Octane: a mais recente edição do Ember.js'
+ logo-alt-text: 'EmberData Request Service Cheat Sheet'
title: EmberData Request Service Cheat Sheet
description-1: >
- Esse guia é uma cola para usar o ''Ember.js Octane''.
- Ele não cobre tudo, mas é o suficiente para você começar!
- Pull requests são bem-vindos no ''repositório do GitHub''.
+ Este guia é um resumo para usar o 'Serviço de Requisição do EmberData'.
+ Não cobre tudo, mas deve te ajudar a começar!
+ Contribuições são bem-vindas no ''repositório do GitHub''.
description-2: >
- Para uma visão mais aprofundada sobre as formas de atualizar e as diferenças introduzidas na Octane, veja ''The Octane Upgrading Guide''.
+ Para informações detalhadas sobre os caminhos de atualização e diferenças em relação aos padrões antigos do EmberData, veja 'o RFC para o Serviço de Requisição do EmberData'.
component:
guide-section:
section: §
subsection:
- classic: Classic
- octane: Octane
+ classic: Older patterns
+ octane: Request Service
edit-translation-text: Editar tradução
locale-menu:
locale-select:
diff --git a/translations/routes/de-de.yaml b/translations/routes/de-de.yaml
deleted file mode 100644
index a514836..0000000
--- a/translations/routes/de-de.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Routen
\ No newline at end of file
diff --git a/translations/routes/en-us.yaml b/translations/routes/en-us.yaml
deleted file mode 100644
index 15ea26b..0000000
--- a/translations/routes/en-us.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Routes
\ No newline at end of file
diff --git a/translations/routes/es.yaml b/translations/routes/es.yaml
deleted file mode 100644
index db82371..0000000
--- a/translations/routes/es.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Rutas
diff --git a/translations/routes/ja.yaml b/translations/routes/ja.yaml
deleted file mode 100644
index cb9fc69..0000000
--- a/translations/routes/ja.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: ルート
diff --git a/translations/routes/model-access/de-de.yaml b/translations/routes/model-access/de-de.yaml
deleted file mode 100644
index c425d52..0000000
--- a/translations/routes/model-access/de-de.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Das Modell einer Route lesen
-description: >
- Was das Template einer Route anbelangt, kommt das ''model'
' von einem äußeren Kontext her.
- Daher verwenden Sie ''@model'
', um den Rückgabewert vom ''model'
'-Hook der Route zu lesen.
\ No newline at end of file
diff --git a/translations/routes/model-access/en-us.yaml b/translations/routes/model-access/en-us.yaml
deleted file mode 100644
index a9025a8..0000000
--- a/translations/routes/model-access/en-us.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Accessing a route's model
-description: >
- In a route template, the ''model'
' comes from an outside context.
- Use ''@model'
' to access the result from the route's ''model'
' hook.
\ No newline at end of file
diff --git a/translations/routes/model-access/es.yaml b/translations/routes/model-access/es.yaml
deleted file mode 100644
index edc53bd..0000000
--- a/translations/routes/model-access/es.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Acceder al modelo de una ruta
-description: >
- En un template de ruta, el ''model'
' proviene de un contexto externo.
- Utilice ''@model'
' para acceder al resultado del ''model'
' hook de la ruta.
diff --git a/translations/routes/model-access/ja.yaml b/translations/routes/model-access/ja.yaml
deleted file mode 100644
index 465eeba..0000000
--- a/translations/routes/model-access/ja.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: ルートモデルへのアクセス
-description: >
- ルートテンプレートにおいて、''model'
'は外部コンテキストからやってきます。
- ルートの''model'
'フックの結果にアクセスするために、''@model'
'を使います。
diff --git a/translations/routes/model-access/pt-br.yaml b/translations/routes/model-access/pt-br.yaml
deleted file mode 100644
index 94c448a..0000000
--- a/translations/routes/model-access/pt-br.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-title: Acessando o model de uma rota
-description: >
- No template de uma rota, o ''model'
' vem de um contexto externo.
- Use ''@model'
' para acessar o resultado do hook ''model'
' da rota.
diff --git a/translations/routes/pt-br.yaml b/translations/routes/pt-br.yaml
deleted file mode 100644
index 1c7557e..0000000
--- a/translations/routes/pt-br.yaml
+++ /dev/null
@@ -1 +0,0 @@
-title: Rotas
\ No newline at end of file