amtrack / force-dev-tool

[DEPRECATED] Command line tool supporting the Force.com development lifecycle
MIT License
108 stars 37 forks source link

ERROR git diff with force-dev-tool changeset create #101

Closed rodolfonoviski closed 6 years ago

rodolfonoviski commented 6 years ago

When I try to generate a changeset with the difference between two branchs it returns the following error:

TypeError: Cannot read property 'type' of null at module.exports.Manifest.add (C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\manifest.js:56:19) at C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\metadata-container.js:174:42 at Array.forEach (<anonymous>) at module.exports.MetadataContainer.diff (C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\metadata-container.js:161:15) at Socket.<anonymous> (C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\cli\changeset.js:74:38) at emitOne (events.js:115:13) at Socket.emit (events.js:210:7) at Pipe._handle.close [as _onclose] (net.js:545:12)

amtrack commented 6 years ago

@rodolfonoviski Can you please provide the following information:

rodolfonoviski commented 6 years ago

$ force-dev-tool --version 1.0.0

Yes I did commit and push to git server

amtrack commented 6 years ago

Could you send me the list of changed files (git diff --name-status) in a secret Gist (https://gist.github.com) and email me the link to mr.amtrack@gmail.com?

rodolfonoviski commented 6 years ago

I just sent you

rodolfonoviski commented 6 years ago

@amtrack Now it is returning this error:


TypeError: field.childNamed is not a function
    at C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\metadata-file-container.js:110:29
    at Array.forEach (<anonymous>)
    at C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\metadata-file-container.js:109:44
    at Array.forEach (<anonymous>)
    at module.exports.MetadataFileContainer.parse (C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\metadata-file-container.js:106:22)
    at module.exports.MetadataFileContainer.diff (C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\metadata-file-container.js:45:8)
    at C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\metadata-container.js:169:26
    at Array.forEach (<anonymous>)
    at module.exports.MetadataContainer.diff (C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\metadata-container.js:161:15)
    at Socket.<anonymous> (C:\Users\rnoviski\AppData\Roaming\npm\node_modules\force-dev-tool\lib\cli\changeset.js:74:38)
Manifest:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <version>40.0</version>
</Package>

exported metadata container to config\deployments\deploy0712

`
amtrack commented 6 years ago

The latest error should be fixed on the master branch.

Can you try using the latest version

$ npm install -g git+https://github.com/amtrack/force-dev-tool.git#master
rodolfonoviski commented 6 years ago

Thank you very much for your attention. It worked now !

amtrack commented 6 years ago

OK, great! I guess I need to publish a new release soon.

rodolfonoviski commented 6 years ago

@amtrack I am waiting for updates because its solution is incredible. Help me a lot in the DevOps process.