Closed karthickthangasamy closed 8 years ago
@karthickthangasamy I believe that the task doc.js presumes special formatting of the code you want to generate the docs for. As far as I know only aurelia core framework code is formatted that way and the autogenerated docs can be seen here
We never considered to use this in bridges as the type of docs we wanted to have is different from API docs - and Aurelia's autogenerate technology is not ready to be used outside the core team.
As I am not sure that all this is accurate, I will ask others to confirm or correct it.
This is because aurelia-framework
is used while aurelia-framework
is not a dependency of the plugin
You have two options, remove the aurelia-framework
imports or add the aurelia-framework
dependency.
Removing the aurelia-framework imports
here you import inlineView
from aurelia-framework
but you can also import this from aurelia-templating
. You can also get rid of this import and remove the : Aurelia
typing as the config function is not used directly by users of the bridge.
Adding the aurelia-framework dependency here. I'd actually recommend against adding a dependency on aurelia-framework, as that increases the chance of users having JSPM forks.
Also, make sure that you run gulp build
before gulp doc
as the d.ts
file of the syncfusion bridge is generated by gulp build
@JeroenVinke Thanks for the update. We can go with the first option.
Removing the aurelia-framework imports.
I made the required changes and committed in repository.
While generating typedoc for
aurelia-syncfusion-bridge
source, initially faced issue like below.The above issue resolved while installing
aurelia-framework
npm package.Currently facing exceptions in the below
aurelia-framework
source files.aurelia-history-browser
aurelia-loader
aurelia-router
I am also tried to run the
aurelia-kendo-bridge
source, facing the same error. Could you please guide me, how can I proceed further on this?