<commit_before># SLD-Editor

SLD-Editor is an Node.js based SLD backend.

## Getting started

1. Install [Node.js](http://nodejs.org/download/) locally
2. Follow the installation guides and if special permissions are needed, ask your Admin to add usage rights to the folders
3. npm install
4. node parse.js original.sld template.sld > fields.csv
5. Modify fields.csv
6. node build.js template.sld fields.csv > new.sld

If you want to store an SLD template in a PostgreSQL database after creating it:

1. Use sql/sld_styles_create_tables_script.sql to set up your database
2. Modify db.json
3. node store.js template.sld fields.csv

## Versioning

SLD-Editor uses Semantic Versioning and follows the guidelines as much as possible.

Releases will be numbered with the following format:

`<major>.<minor>.<patch>`

And constructed with the following guidelines:

* Breaking backward compatibility bumps the major (and resets the minor and patch)
* New additions without breaking backward compatibility bumps the minor (and resets the patch)
* Bug fixes and misc changes bumps the patch
<commit_msg>Add note how to avoid sending database credentials to Git repository.<commit_after># SLD-Editor

SLD-Editor is an Node.js based SLD backend.

## Getting started

1. Install [Node.js](http://nodejs.org/download/) locally
2. Follow the installation guides and if special permissions are needed, ask your Admin to add usage rights to the folders
3. npm install
4. node parse.js original.sld template.sld > fields.csv
5. Modify fields.csv
6. node build.js template.sld fields.csv > new.sld

If you want to store an SLD template in a PostgreSQL database after creating it:

1. Use sql/sld_styles_create_tables_script.sql to set up your database
2. To avoid accidentally publishing database credentials, use: git update-index --assume-unchanged db.json
3. Modify db.json
4. node store.js template.sld fields.csv

## Versioning

SLD-Editor uses Semantic Versioning and follows the guidelines as much as possible.

Releases will be numbered with the following format:

`<major>.<minor>.<patch>`

And constructed with the following guidelines:

* Breaking backward compatibility bumps the major (and resets the minor and patch)
* New additions without breaking backward compatibility bumps the minor (and resets the patch)
* Bug fixes and misc changes bumps the patch

{'fraction_non_alphanumeric': 0.06496815286624204, 'fraction_numerical': 0.008067940552016985, 'mean_word_length': 4.428571428571429, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 13, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2288990', 'n_tokens_mistral': 662, 'n_tokens_neox': 637, 'n_words': 314}