You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 8, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 8, 2021. It is now read-only.
First off I wanted to say thank you for the useful tools, I am using both ivy-tabs and ivy-codemirror in my project.
Just installed code-mirror today and followed the instructions, which did not work initially because version 1.4 is behind what is currently documented in your readme (in this case it had to do with the options hash being passed as a single attribute). I was able to figure it out by reading your commits and seeing where the discrepancy was, but I think less experienced devs may just give up and use another tool. My suggestion to you would be this: Keep all documentation current with your latest release (which should be what is registered with npm). For any new work create a release branch and only merge into master once ready and documented. This is really just a process change more than anything, but I think it would help avoid confusion to users of your packages.
For those who want the latest and greatest, you can have them point their npm packages at your repo instead of the current release:
"ivy-codemirror": "ivyapp/ivy-codemirror"
versus what ember install ivy-codemiror produces:
"ivy-codemirror": "1.4.0" # or whatever the latest version is
Activity