Merge pull request #18 from yukal/dev

Use native nodejs test and assert modules

Author: Alexander

.github/workflows/node.js.yml

@@ -16,7 +16,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [12.x, 14.x, 16.x]
+        node-version: [18, 20]
 
     steps:
     - uses: actions/checkout@v2

CHANGELOG.md

@@ -0,0 +1,55 @@
+## [v1.2.1](https://github.com/yukal/slim-validator/compare/f7485d8fa2a84bc3ab4a2156ef62add21f8ae615...a6ca46f363d6f343b1941d5b25eaa31a0529542d) – 2024-01-16
+
+### Refactors
+
+*  update tests ([da00c2ad](https://github.com/yukal/gulp-json-loader/commit/da00c2ad5e2d1e292c8150e8818a4b4173f0fbaa))
+
+### Chores
+
+* **readme:**  update and fix typos and grammar ([19e0dbb7](https://github.com/yukal/gulp-json-loader/commit/19e0dbb7d40ee335ce156f1cc0b8541dfd3f47d0))
+* **package:**  update package within dependencies ([2a825757](https://github.com/yukal/gulp-json-loader/commit/2a825757948e66895ad8ddd67a9adb99e8795b8f))
+
+### Continuous Integration
+
+- **action:**  use latest stable nodejs ([bf570a7a](https://github.com/yukal/gulp-json-loader/commit/bf570a7a3cb03f555916c05ec4faf83817627ba6))
+- **action:**  update node matrix ([a6ca46f3](https://github.com/yukal/gulp-json-loader/commit/a6ca46f363d6f343b1941d5b25eaa31a0529542d))
+
+## [v1.2.1](https://github.com/yukal/slim-validator/compare/v1.2.1...f7485d8fa2a84bc3ab4a2156ef62add21f8ae615)
+
+### Build System / Dependencies
+
+- **deps-dev:**  bump chai from 4.3.8 to 4.3.10 ([a0f02551](https://github.com/yukal/gulp-json-loader/commit/a0f02551bddefad86d2864cf1e42527d6ebbed0f))
+- **deps-dev:**  bump chai from 4.3.7 to 4.3.8 ([e5d80951](https://github.com/yukal/gulp-json-loader/commit/e5d80951f8f1245879924bd71db2b621e5409d91))
+- **deps-dev:**  bump mocha from 10.1.0 to 10.2.0 ([367897bb](https://github.com/yukal/gulp-json-loader/commit/367897bb4ed1b9812edc867a8c1fc18ffa92d974))
+- **deps:**  bump decode-uri-component from 0.2.0 to 0.2.2 ([4252fa92](https://github.com/yukal/gulp-json-loader/commit/4252fa92d0e6f31d0d31d22a4e23c4b6fc4b3fdf))
+
+### Other Changes
+
+*  codestyle ([515d18d4](https://github.com/yukal/gulp-json-loader/commit/515d18d40e607e7157a646eb27b5c10e83720b5f))
+
+## v1.1.0
+- Updated core
+  - Imposed restrictions on accessing external directories.
+  - There is no need to pass the config data to GulpJsonLoader, now it's optional
+    and defined from defaults. But if you want to change them, you might tune it in
+    both ways: using an old-style passing an object with options to GulpJsonLoader
+    factory or just pass the settings into a package.json. See package.json.
+
+- Updated dependencies
+  - gulp-load-plugins: ^2.0.7
+  - gulp-pug: ^5.0.0
+
+- Improvement of variables names
+  - To distinguish variables from stylistic PAG syntax it is preferable to name
+    variables in a different way as opposed to decoration text. That's why I name 
+    variables with a capital letter and a dollar sign at the beginning.
+    See PUG files to find out more about it.
+
+  - The entry name of the Data loaded from the JSON file is defined in a global
+    space as a "data" entry, now you can change this name as you like.
+    See package.json and PUG files to find out more about it.
+
+- Implemented data caching
+  - The data that has already been loaded will be getting from the cache
+
+- Added tests

README.md

@@ -1,12 +1,8 @@
 # gulp-json-loader
-A little tool for the [gulp-data](https://www.npmjs.com/package/gulp-data) plugin. 
-It useful for automatically data loading in the development including the PUG files.
+A little tool for the [gulp-data](https://www.npmjs.com/package/gulp-data) plugin. It useful for automatically data loading in the development including the PUG files.
 
 ### What for
-I tried to find any simple solution to assign my variables to a current PUG file in a building 
-process, but some of the solutions are the same with solutions between the 2014th and 2019th 
-years and, actually do not satisfy my needs as I want. And the most popular solution I have 
-found looks like:
+I've tried to find a simple solution for assigning my variables into PUG files in a building process. Some of them have similar examples between the 2014th and 2019th years and don't satisfy my technical needs. The most popular solution I have found looks like this:
 
 ```javascript
 // Somewhere in gulp task
@@ -16,34 +12,14 @@ found looks like:
 .pipe(data(() => require('data.json') ))
 ```
 
-After a while, in search of the solution I have found one more way in solving this decision 
-in a [detailed article](https://tusharghate.com/rendering-pug-templates-with-multiple-data-files),
-but still not satisfied.
-
-So, what's wrong with these solutions?
-First of all, any time, when the queue reaches to Html part, it starts the merging process of all 
-the JSON files. Each any Html file, Carl! It means that sometimes the process is performing 
-unnecessary actions. What if you don't need to include the data in some of the Html file, it still 
-will run enforced actions, any time, again and again, merge... merge... merge. Yes, you can solve 
-it by running a once merge, and then always include it as a combined object from the JSON file, as 
-the solution in an article above. But it still not a good solution to including the JSON file there 
-where you should not include.
-
-And I decided to fix this problem in my vision.
+What's wrong with these examples?
+First of all, each time when the queue reaches the HTML part, it starts the merging process of all the JSON files. It means that sometimes the process is performing unnecessary actions. What if we don't need to include the data for some of the HTML files? Well, it still runs enforced actions at any time. We can solve it by once running merge and then always including it as a combined object from the JSON file. But it is still not a good idea to include the JSON file there where we shouldn't.
 
 ### How does it work
-When the build process's queue reaches Html, it automatically searches the JSON file with the same 
-name as in the directory with Html files, or PUG files (it depends on how you set up your project).
+When the build process queue reaches HTML, it automatically searches the JSON file with the same name as in the directory with kinds of PUG files (it depends on how you set up your project).
 
 ### Structure
-To automatically asigning data to the pages, you must be following the canonical paths. The 
-structure of directory with the JSON files should contains with two required folders inside: 
-**pages** and **imports**. The **pages** directory structure must be exactly the same structure as 
-the directory with PUG files. Here in example the PUG files located in **html** directory. The 
-**imports** directory is provided for the JSON files which you can include as a partial data.
-If you missed any of the JSON files in the data/pages directory, the loading of the JSON files will 
-not happen and the error will not rise except one thing - It would not happen if you will not try 
-to get the data variable from current context while the building process is running.
+To assign some data inside your pages, you have to follow canonical paths. The directory structure with JSON files must contain two necessary folders inside pages and imports. The "pages" directory structure must have the same structure as the directory with the pug files. In the example below, pug files are placed inside the "html" directory. The "imports" directory is provided for the JSON files, which you can include as partial data. If you've missed any JSON file inside the data/pages directory, the loading of the JSON files will not happen, and the error will not rise except, It will not rise if you do not try to get the data variable from the current context while the building process is running.
 
 ```bash
 src                 src