Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
documentation clarification #2778
As I'm working through the "create a new addon" documentation I think I'm missing something/and or the docs aren't something you can read top to bottom.
The first step goes like this (using the name my-x-button)
Next you show the index.js w/ the name "my-addon" (diff from step 1)
Then later when you say to create a component ...you show this import for the file
Does all this match up correctly or was this several parts/different starts ?
I've gone through this tutorial a few times over the past week but no matter what I do I can't seem to get beyond the error
Handlebars error: Could not find property 'x-button'
...when used like so in my ember-cli app after a simple npm install
I'd like to ensure others (new to ember) don't hit the site and have the same issues I did so I'd PR in a change if/when I get this working (not the state I'm in today sadly).
Any clarification around this (the addon component example in particular) would be helpful! thank you!
here is the full addon (single commit to show what I've changed since the init commit)
At this time I get an error as-is - that's in part why I opened this issue. I still can't get a working component that I can install
Here are the steps I took to install this/use it with ember-cli
then add the below to the app.hbs
@toranb You need to
I was able to follow those same steps with the
Also, you can use the dummy app in your addon to serve it up too. You can run
BOOM that was exactly it :)
thank you, thank you, thank you
About the original issue where I asked about "one voice/ flow" through the addon documentation for ember-cli ... am I correct to voice the inconsistency or is this something I misunderstood ? I honestly felt like the docs where a mix of several addons (names mismatch/ etc).
Agreed, seems less of a guide and more of a patch work of examples.
Just want to chime in that that potentially causes the reverse of this. If you remove from package.json and don't prune, then you have addons included that aren't in the package.json.
Maybe we should have dependency checker check for this instead? An addon being in node_modules but not package.json?