Skip to content
This repository has been archived by the owner on Jul 8, 2019. It is now read-only.

Remove hardCode value for node #131

Merged
merged 2 commits into from
Jun 18, 2017

Conversation

j0nathan33
Copy link
Contributor

I need that because node isn't in environment path

@coveralls
Copy link

Coverage Status

Coverage increased (+0.05%) to 92.018% when pulling eb12374 on j0nathan33:Fix-HardCode-node into cdf2bd5 on Pablissimo:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.05%) to 92.018% when pulling eb12374 on j0nathan33:Fix-HardCode-node into cdf2bd5 on Pablissimo:master.

@Pablissimo Pablissimo added this to the v1.2 milestone Mar 28, 2017
@Pablissimo
Copy link
Owner

Thanks - seems sensible, will seek to merge once I promote the 1.1 RC to an official release and target 1.2 for the change to go live

@Pablissimo Pablissimo merged commit 840bcff into Pablissimo:master Jun 18, 2017
@j0nathan33 j0nathan33 deleted the Fix-HardCode-node branch June 19, 2017 17:41
@glandais
Copy link

Sorry but this merge doesn't work for me, PathResolverImpl is not happy at all with "node" value as it can't get its absolute path. So the value for pathToNode in TsLintExecutorConfig is set to null. Then it fails in TsLintExecutorImpl.getBaseCommand as config.getPathToNode() is null.

I had to set sonar.ts.tslint.nodePath property to my local node.

I think that PathResolver.getPath should have "resolveAbsolutePath" parameter, calling getAbsolutePath or not.

Regards

@Pablissimo
Copy link
Owner

Cool, shall investigate.

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

Successfully merging this pull request may close these issues.

None yet

4 participants