In #706 ember-cli-addon-docs was updated and the branding color defaulted to ember's orangey-red, and the hero image also changed (Addepar/ember-table#706 (review)).

Fix these up before deploying the docs.

Can we please get toggle button groups, similar to what's described here: https://material.io/components/buttons/#toggle-button

They're also called button groups in bootstrap: https://getbootstrap.com/docs/4.4/components/button-group/

In angular material they're button toggles: https://material.angular.io/components/button-toggle/overview

Environment

• Mac OS: 10.14.6
• node: 8.16.2
• npm: 6.4.1

1. Test for Ember 2.18

npm install -g ember-cli@2.18
ember new test-ember-2-18
cd test-ember-2-18
ember i ember-bootstrap@3.1.0 ember-angle-bracket-invocation-polyfill@2.0.2

# copied from https://www.ember-bootstrap.com/api/classes/Components.Navbar.html
cat <<EOF > app/templates/application.hbs
<BsNavbar a

Environment

• Ember Version: n/a
• Ember CLI Version: n/a
• Ember CP Validations Version: n/a

Steps to Reproduce

On the documenation site, try searching for 'checkbox' or 'input'. Nothing happens.

I've just now realized it's because there were no results for 'checkbox' or 'input'. I'm going to leave this issue open because it does feel like the UX around searching the docs is

How about replacing the magic file at app/utils/intl/missing-message.js with a hook on the service?

Something like this:

// ember-intl service
// …
missingTranslation(locale, key, options = {}) {
  return `Missing translation for ${key} in ${locale}`;
}

// …

That hook could be used both to modify the returned message, e.g. by hooking up a fallback message in a specifi

Update docs to recommend the usage of ember-cli-dependency-lint to prevent errors like #445.

I don't have ANY Google Tag Manager experience (as of yesterday ;), and so - maybe it isn't addon specific - but I roughhoused with trying to find how to access the GTM dataLayer and wrote all sorts of messes trying to get to it.

If I hadn't just accidentally logged it, I would have kept going down this hole (which was all wrong)

    const metricsAdapters = this.get('metrics.options.

If occlusion rendering is enabled, but the table does not contain enough rows to display a scrollbar, fixed headers do not align with the rows below -- the lt-head-wrap is given padding on the right to account for the scrollbar regardless of the scrollbar's presence.

Possibly related to these? #484 #487

Documentation on how to alias models and fields would be really helpful. I think there's a way with ember-graphql-adapter but it's unclear.

For example, say my graph has a type foo, but I want to use bar instead, what do I do?

https://github.com/ember-lifeline/ember-lifeline/blob/803117c4b6899f181186d694e8749ec414956b8b/addon/dom-event-listeners.ts#L99

This assertion seems to assert that the second argument must be a DOM element and not a string, etc. However, this is not in line with the current docs:

addEventListener will provide the run

I was unable to find anything in the docs, tutorials, or example projects about how to exactly use watch queries in data-loading components. From the docs, I know that I can use the ComponentQueryManager which will track active watch queries and unsubscribe when the component is destroyed. I also know that watchQuery will return an Ember.Object and can be used in computed properties. What I

There doesn't seem to be any documentation for the feature outlined in the issue #18, I mentioned it in the issue it self but I feel like tracking that as an issue may be easier if I create a seperate issue.

I've read the documentation a couple of times, but I can't seem to locate any mention of this feature, but I get the feeling there was documentation for this at some point, so if there's a

The docs use unhelpful terminology like like "easily", and has contribution information that could be better placed in a CONTRIBUTING.md file to better integrate with GitHub UI.

I will hopefully improve on the docs a bit, PR forthcoming.

Version of x-select:

^3.1.1

Ember Version / Ember CLI Version:

Ember Version: ~3.8.0
Ember CLI Version: ~3.8.1

Expected Behavior

If one passes in an optional argument to the action on x-select, the order of the arguments received in the action handler will be: 1.value, 2.event, and 3.optional, as per the description in the docs under **Actions and Ac

• I'm submitting a ...

  • bug report
  • [ *] feature request
  • [ ] support request Ask in the official Ember Discord server.

• What is the current behavior?
  Current examples demo comes with UI only.

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

• **[Bu

ember-cli-addon-docs has become a very nice tool for generating documentation for an addon. Benefits include: testability, versioned docs, and an easy-peasy deployment process with CI.

It'll also make it easier to add pages with demos and snippets for various use-cases, as well as breakout the large chunks of docs in the README that are dif

should be

ember build --environment production && ember github-pages:commit --message \"Deploy gh-pages from commit $(git rev-parse HEAD)\" && git push origin gh-pages:gh-pages

instead