nestia 2.1.1 → 2.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CONTRIBUTING.md +1 -1
- package/README.md +566 -469
- package/lib/IConfiguration.d.ts +28 -7
- package/lib/IConfiguration.d.ts.map +1 -1
- package/lib/analyses/ControllerAnalyzer.d.ts.map +1 -1
- package/lib/analyses/ControllerAnalyzer.js +30 -41
- package/lib/executable/nestia.js +0 -0
- package/lib/factories/MetadataFactory.d.ts.map +1 -1
- package/lib/factories/MetadataFactory.js +2 -6
- package/lib/factories/SchemaFactory.js +1 -1
- package/lib/factories/TypeFactry.js +1 -1
- package/package.json +1 -1
package/CONTRIBUTING.md
CHANGED
|
@@ -42,7 +42,7 @@ If you succeeded to compile, but failed to pass the test-automation, then *debug
|
|
|
42
42
|
### Adding a Test
|
|
43
43
|
As this `nestia` is not a typical library who being used by the `import` statement but a executable program generating the SDK (Software Development Kit), adding a test means that adding a demonstration project.
|
|
44
44
|
|
|
45
|
-
I know that adding a demonstration project is much difficult than adding a test function, but there's no way if newly contributed code requires a new type of testing tool. Looking at the [src/test/demonstratios](
|
|
45
|
+
I know that adding a demonstration project is much difficult than adding a test function, but there's no way if newly contributed code requires a new type of testing tool. Looking at the [src/test/demonstratios](demo) directory and traveling the demonstration projects, create a new demonstration project following their structures and styles.
|
|
46
46
|
|
|
47
47
|
Of course, if your contribution code does not require a test new project, don't mind this.
|
|
48
48
|
|