<commit_before>Whats the goal?

1st goal is to create an portal to view exceptions.  Project details to come later.
2nd goal is to create an full-stack application framework for asp.net core 
	(this should be seperated from the exception portal as a reusable tempalte, this tempalte will be saved to a branch named tempalte)
	sub goals
		1. adhere to specific database standards.
			a. All tables must have IsSuppressed, CreatedDt, CreatedByUserId, UpdatedDt, UpdatedByUserId, LastUpdatedGuid, EntityGuid columns.
			b. more to be listed here...
		2. adhere to open such as DI, SOLID, etc.
			a. consider using simple injector over microsofts home grown di 
		3. provide a generic repository pattern that works with any type of entities.
			a. this should include a SqlRepository and SqlUnitOfWork 
		4. provide a default scaffolding of controllers and views that renders an elegant ui for all crud operations
			a. crud operations are create, read, update, delete. 
			b. bootstrapped ui
			c. confirmation/modal dialogs for delete
			d. create modal for any general entity
			f. out of the box drop down menus for code tables
			e. out of the box validations 
		5. easy to implement caching mechanism, should be attribute based.
			a. consider using a redis provider for caching
		6. provide a layer for application logic
		7. avoid using microsoft tables  for authentication
			a. instead of AspNetUsers => User
			b. Instead of User.Id => User.UserId
			etc..
		8. do not use session, user id should be saved in a bearer/jwt token
		9. an architecture that allows lazy loading<commit_msg>format readme<commit_after># Whats the goal?

## 1st goal is to create an portal to view exceptions.  Project details to come later.
## 2nd goal is to create an full-stack application framework for asp.net core 
	this should be seperated from the exception portal as a reusable tempalte, this tempalte will be saved to a branch named tempalte
	
		* adhere to specific database standards.
		```
			a. All tables must have IsSuppressed, CreatedDt, CreatedByUserId, UpdatedDt, UpdatedByUserId, LastUpdatedGuid, EntityGuid columns.
			b. more to be listed here...
		```
		* adhere to open such as DI, SOLID, etc.
		```
			a. consider using simple injector over microsofts home grown di 
		```
		* provide a generic repository pattern that works with any type of entities.
		```
			a. this should include a SqlRepository and SqlUnitOfWork 
		```
		* provide a default scaffolding of controllers and views that renders an elegant ui for all crud operations
		```
			a. crud operations are create, read, update, delete. 
			b. bootstrapped ui
			c. confirmation/modal dialogs for delete
			d. create modal for any general entity
			f. out of the box drop down menus for code tables
			e. out of the box validations 
		```
		* easy to implement caching mechanism, should be attribute based.
		```
			a. consider using a redis provider for caching
		```
		* provide a layer for application logic
		* avoid using microsoft tables  for authentication
		```
			a. instead of AspNetUsers => User
			b. Instead of User.Id => User.UserId
			etc..
		```
		* do not use session, user id should be saved in a bearer/jwt token
		* an architecture that allows lazy loading
{'fraction_non_alphanumeric': 0.05209617755856967, 'fraction_numerical': 0.004007398273736128, 'mean_word_length': 3.4029850746268657, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 7, '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': '2902934', 'n_tokens_mistral': 987, 'n_tokens_neox': 860, 'n_words': 472}