Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looking for JS in wrong location? #7

Open
custa1200 opened this issue Jul 26, 2015 · 5 comments
Open

Looking for JS in wrong location? #7

custa1200 opened this issue Jul 26, 2015 · 5 comments

Comments

@custa1200
Copy link

Hi I have installed this plugin as described but it is failing to run properly. When I check the console I get the following problem:

screenshot 2015-07-26 10 02 14

This sone of my specs, I would have thought the idea of this plugin was to not have to copy the spec-status JS all over the specs which kind of pollutes the component. Maybe I have done something wrong, but I don't think so. Running latest versions of SourceJS, Spec-Status and CouchDB.

@robhrt7
Copy link
Member

robhrt7 commented Aug 6, 2015

Hi,

Sorry for the late reply, just returned from my vacation.

After installing the plugin and re running npm install or grunt update, build script generated custom requirejs-config which points the client-side part of the plugin to /node_modules/sourcejs-spec-status/assets/index.js.

Seems like in your case, this configuration is not available. Maybe you missed the grunt update part or have overridden requirejs-config.packages conf?

Of course you should not link the script manually per each spec.

@custa1200
Copy link
Author

So I followed the instructions a little closer and I am not getting any errors now, but I am also not getting any iconography. I am not sure if the fact I am using DSS to define my specs makes any difference or not.

@robhrt7
Copy link
Member

robhrt7 commented Aug 16, 2015

I will re-check the set-up with latest release.

@robhrt7
Copy link
Member

robhrt7 commented Aug 16, 2015

I noticed a bug and lack of description about installing plugins for sourcejs-npm version, will fix that. But plugin should work properly, I assume that you might missed this configuration:

assets: {
  pluginsOptions: {
    specStatus: {
      enabledCatalogs: ['specs']
    },
  }
}

This defines the catalog names in user root, where spec-status plugin should be loaded.

@robhrt7
Copy link
Member

robhrt7 commented Aug 16, 2015

Could you please check if entry js file is loaded?

image

And if markup was injected to source_info

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants