Closed witrin closed 2 years ago
I also would like to suggest to exclude build results from version control.
I was trying to test your changes, and found that your PR was based on a a bit of an older commit. I applied your change directly in this commit. I also created a unit test based on your comments above. I published this change to NPM as v4.10.2
I also would like to suggest to exclude build results from version control.
What do you mean by this?
What do you mean by this?
Build results are e.g. the output of the TypeScript compiler (.js, .d.ts). Such files should be not part of a git repository, just build them in a pipeline, test them, push them into a sink (e.g. npm registry) and throw them away.
Ah... I keep the compiled .js files in the repo because WebStorm automatically compiles the .ts into .js, and I don't want to have a separate process to debug the code. I'd welcome a separate PR with the tsconfig.json
, .gitignore
changes needed to make that happen, along with some guidance on how to setup the IDE to make debugging easy :) I just don't have much time to figure that stuff out right now.
The test suite should be extended. I guess backbone elements with type references are not covered yet.
Given
Expected
Actual