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

"TypeNotFoundException: Namespace is not defined for type org.example.biznet.User" on npm test #3

Open
nyetwurk opened this issue Aug 31, 2018 · 1 comment

Comments

@nyetwurk
Copy link
Contributor

nyetwurk commented Aug 31, 2018

Pre-commit hook fails on npm test

> composer-file-storage-ways@0.0.1 test /home/nyet/src/hyperledger_composer_file_storage
> mocha --recursive

  #org.example.biznet
    ChangeAssetValue()
      1) should change the value property of SampleAsset to newValue

  0 passing (1s)
  1 failing

  1) #org.example.biznet ChangeAssetValue() should change the value property of SampleAsset to newValue:
     TypeNotFoundException: Namespace is not defined for type org.example.biznet.User
      at ModelManager.getType (node_modules/composer-common/lib/modelmanager.js:378:19)
      at Factory.newResource (node_modules/composer-common/lib/factory.js:103:45)
      at Context.it (test/logic.js:91:34)
@nyetwurk
Copy link
Contributor Author

in modules/v0/users/users-crud.js USER_NS is defined as org.preetam.composer not org.example.biznet.User

If I fix the name space there, it fails with

TypeNotFoundException: Type SampleAsset is not defined in namespace org.preetam.composer

because org.preetam.composer.SampleAsset isn't defined anywhere.

Are these unit tests actually supposed to work?

nyetwurk added a commit to Blockdaemon/hyperledger_composer_file_storage that referenced this issue Aug 31, 2018
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

1 participant