<commit_before># EF-File-Core
A web application which integrates file handling with persisted storage via an ORM to a T-SQL db with data validation.

# Scenario

Build a system which allows for the storing of client information, the data will be imported per client either via a Json or CSV file. 

The client should specify the file path, file type per upload

Data validation should also be added on the imported data. Given the following scenario's the app should act accrodningly:

1) In valid data
  - Set IsValid = false and persist to storage agains the client
2) Valid data
  - Set IsValid = true and persistto storage against the client 

## Tech Stack

  - ASP.NET Core MVC 
  - Entity Framework Core
  - MS SQL

## Installation

TODO: Describe the installation process

## Usage

TODO: Write usage instructions

## Contributing

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## License

MIT<commit_msg>updated .md<commit_after># EF-File-Core
A web application which integrates file handling with persisted storage via an ORM to a T-SQL db with data validation.

## Scenario

Build a system which allows for the storing of client information, the data will be imported per client either via a Json or CSV file. 

The client should specify the file path, file type per upload

Data validation should also be added on the imported data. Given the following scenario's the app should act accrodningly:

1) In valid data
  - Set IsValid = false and persist to storage agains the client
2) Valid data
  - Set IsValid = true and persistto storage against the client 

## Tech Stack

  - ASP.NET Core MVC 
  - Entity Framework Core
  - MS SQL

## Installation

TODO: Describe the installation process

## Usage

TODO: Write usage instructions

## Architecture
This repo is by no means a guide nor complete implementation of the following:

- Domain Driven Design Pattern
- Repository Pattern
- Unit Of work patters

The focus is on implementing a solution to the above scenario 

## Contributing

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## License

MIT
{'fraction_non_alphanumeric': 0.05391953546246371, 'fraction_numerical': 0.005806719203649938, 'mean_word_length': 3.766798418972332, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6971717', 'n_tokens_mistral': 679, 'n_tokens_neox': 644, 'n_words': 366}