ember-source 7.2.0-alpha.4 → 7.2.0

package/types/stable/@ember/-internals/glimmer/lib/helpers/page-title.d.ts

@@ -1,20 +0,0 @@
-declare module '@ember/-internals/glimmer/lib/helpers/page-title' {
-    /**
-    @module ember
-    */
-    /**
-      `page-title` allows you to set the title of any page in your application and
-      append additional titles for each route. For complete documentation, see
-      https://github.com/ember-cli/ember-page-title.
-
-      ```handlebars
-      {{page-title "My Page Title" }}
-      ```
-
-      @method page-title
-      @for Ember.Templates.helpers
-      @param {String} param
-      @public
-    */
-    export {};
-}

package/types/stable/@ember/-internals/glimmer/lib/modifiers/on.d.ts

@@ -1,95 +0,0 @@
-declare module '@ember/-internals/glimmer/lib/modifiers/on' {
-    /**
-    @module ember
-    */
-    /**
-      The `{{on}}` modifier lets you easily add event listeners (it uses
-      [EventTarget.addEventListener](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)
-      internally).
-
-      For example, if you'd like to run a function on your component when a `<button>`
-      in the components template is clicked you might do something like:
-
-      ```app/components/like-post.hbs
-      <button {{on 'click' this.saveLike}}>Like this post!</button>
-      ```
-
-      ```app/components/like-post.js
-      import Component from '@glimmer/component';
-      import { action } from '@ember/object';
-
-      export default class LikePostComponent extends Component {
-        @action
-        saveLike() {
-          // someone likes your post!
-          // better send a request off to your server...
-        }
-      }
-      ```
-
-      ### Arguments
-
-      `{{on}}` accepts two positional arguments, and a few named arguments.
-
-      The positional arguments are:
-
-      - `event` -- the name to use when calling `addEventListener`
-      - `callback` -- the function to be passed to `addEventListener`
-
-      The named arguments are:
-
-      - capture -- a `true` value indicates that events of this type will be dispatched
-        to the registered listener before being dispatched to any EventTarget beneath it
-        in the DOM tree.
-      - once -- indicates that the listener should be invoked at most once after being
-        added. If true, the listener would be automatically removed when invoked.
-      - passive -- if `true`, indicates that the function specified by listener will never
-        call preventDefault(). If a passive listener does call preventDefault(), the user
-        agent will do nothing other than generate a console warning. See
-        [Improving scrolling performance with passive listeners](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners)
-        to learn more.
-
-      The callback function passed to `{{on}}` will receive any arguments that are passed
-      to the event handler. Most commonly this would be the `event` itself.
-
-      If you would like to pass additional arguments to the function you should use
-      the `{{fn}}` helper.
-
-      For example, in our example case above if you'd like to pass in the post that
-      was being liked when the button is clicked you could do something like:
-
-      ```app/components/like-post.hbs
-      <button {{on 'click' (fn this.saveLike @post)}}>Like this post!</button>
-      ```
-
-      In this case, the `saveLike` function will receive two arguments: the click event
-      and the value of `@post`.
-
-      ### Function Context
-
-      In the example above, we used `@action` to ensure that `likePost` is
-      properly bound to the `items-list`, but let's explore what happens if we
-      left out `@action`:
-
-      ```app/components/like-post.js
-      import Component from '@glimmer/component';
-
-      export default class LikePostComponent extends Component {
-        saveLike() {
-          // ...snip...
-        }
-      }
-      ```
-
-      In this example, when the button is clicked `saveLike` will be invoked,
-      it will **not** have access to the component instance. In other
-      words, it will have no `this` context, so please make sure your functions
-      are bound (via `@action` or other means) before passing into `on`!
-
-      @method on
-      @for Ember.Templates.helpers
-      @public
-      @since 3.11.0
-    */
-    export {};
-}

package/types/stable/@ember/-internals/glimmer/lib/syntax/in-element.d.ts

@@ -1,47 +0,0 @@
-declare module '@ember/-internals/glimmer/lib/syntax/in-element' {
-    /**
-     @module ember
-     */
-    /**
-     The `in-element` helper renders its block content outside of the regular flow,
-     into a DOM element given by its `destinationElement` positional argument.
-
-     Common use cases - often referred to as "portals" or "wormholes" - are rendering
-     dropdowns, modals or tooltips close to the root of the page to bypass CSS overflow
-     rules, or to render content to parts of the page that are outside of the control
-     of the Ember app itself (e.g. embedded into a static or server rendered HTML page).
-
-     ```handlebars
-     {{#in-element this.destinationElement}}
-       <div>Some content</div>
-     {{/in-element}}
-     ```
-
-     ### Arguments
-
-     `{{in-element}}` requires a single positional argument:
-
-     - `destinationElement` -- the DOM element to render into. It must exist at the time
-     of rendering.
-
-     It also supports an optional named argument:
-
-     - `insertBefore` -- by default the DOM element's content is replaced when used as
-     `destinationElement`. Passing `null` to `insertBefore` changes the behaviour to
-     append the block content to the end of any existing content. Any other value than
-     `null` is currently not supported.
-
-         For example:
-
-         ```handlebars
-         {{#in-element this.destinationElement insertBefore=null}}
-           <div>Some content</div>
-         {{/in-element}}
-         ```
-
-     @method in-element
-     @for Ember.Templates.helpers
-     @public
-     */
-    export {};
-}

package/types/stable/@ember/-internals/glimmer/lib/syntax/let.d.ts

@@ -1,55 +0,0 @@
-declare module '@ember/-internals/glimmer/lib/syntax/let' {
-    /**
-    @module ember
-    */
-    /**
-        The `let` helper receives one or more positional arguments and yields
-        them out as block params.
-
-        This allows the developer to introduce shorter names for certain computations
-        in the template.
-
-        This is especially useful if you are passing properties to a component
-        that receives a lot of options and you want to clean up the invocation.
-
-        For the following example, the template receives a `post` object with
-        `content` and `title` properties.
-
-        We are going to call the `my-post` component, passing a title which is
-        the title of the post suffixed with the name of the blog, the content
-        of the post, and a series of options defined in-place.
-
-        ```handlebars
-        {{#let
-            (concat post.title ' | The Ember.js Blog')
-            post.content
-            (hash
-              theme="high-contrast"
-              enableComments=true
-            )
-            as |title content options|
-        }}
-          <MyPost @title={{title}} @content={{content}} @options={{options}} />
-        {{/let}}
-      ```
-     or
-      ```handlebars
-        {{#let
-            (concat post.title ' | The Ember.js Blog')
-            post.content
-            (hash
-              theme="high-contrast"
-              enableComments=true
-            )
-            as |title content options|
-        }}
-          {{my-post title=title content=content options=options}}
-        {{/let}}
-      ```
-
-      @method let
-      @for Ember.Templates.helpers
-      @public
-    */
-    export {};
-}