Merge pull request #40 from icefoganalytics/issue-39/add-ability-for-current-user-viewing-a-place-to-see-their-current-proposed-edits-to-said-place

Issue 39: Add Ability For Current User Viewing a Place to See Their Current Proposed Edits To Said Place

Author: burkkyy

.eslintrc.yml

@@ -0,0 +1,11 @@
+env:
+  browser: true
+  es2021: true
+  node: true
+extends:
+  - prettier
+overrides: []
+parserOptions:
+  ecmaVersion: latest
+  sourceType: module
+rules: {}

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+# Context
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+Relates to:
+- TODO
+
+# Context
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/issue_template.md

@@ -1,43 +1,24 @@
-Please replace the following example with your own content.
+Fixes TODO
 
-Fixes [#25](https://github.com/icefoganalytics/yhsi/issues/25)
+Relates to:
 
-# User Story
+- TODO
 
-See https://github.com/icefoganalytics/yhsi/issues/3
-As an edit level user I can edit the /sites Themes & Function form and it will create a site change request for admin approval.
+# Context
 
-# Details
+TODO
 
-Now that I have a working example in the form of the Summary, Location, and Dates & Conditions sections, this task is simply a port of the existing patterns to include an additional sub-form.
+# Implementation
 
-# Implementation Details
-
-- Tweaked PlaceEdit saving and serialization to hopefully reduce developer errors.
-- Dockerize the test suite and update the README.
-- add a `dev ts-node` to get access to a local node repl that runs typescript.
+TODO
 
 # Screenshots
 
-![image](https://user-images.githubusercontent.com/23045206/163441939-d889fb77-1b78-40e6-b59d-c3a386cc3a5d.png)
+TODO
 
 # Testing Instructions
 
-1. Update your user roles to include `Site Admin` via the database console.
-2. Go to the /sites table and select a site.
-3. In the Themes & Function form, make an edit and press save.
-4. The site will refresh and your edits will be saved.
-5. Update your user roles so that they _do not include_ `Site Admin` or `Administrator` via the database console. Something like `Site Viewer` would probably be best.
-6. Go to the /sites table and select a site.
-7. In the summary form, make and edit (or two) and press save.
-8. The page will refresh and all Themes & Function fields will become readonly. The save button on the Themes & Function form will be disabled with an appropriate tooltip.
-9. Make yourself an `Site Admin` again and go to the /sites-change-requests table.
-10. The new change request will be at the top of the list. Click on it to review.
-11. Note the various features:
-
-- "accept/reject" toggle buttons
-- accept/reject all
-- save button is locked until all changes are approved/rejected
-
-12. Reject and accept some changes and press Save.
-13. Go back to the /sites table and check that you can now edit the site and that the changes have been applied or rejected correctly.
+1. Run the test suite via `dev test` (or `dev test_api`)
+2. Boot the app via `dev up`
+3. Log in to the app at http://localhost:8080
+4.

.github/pull_request_template.md

@@ -114,5 +114,4 @@ db/photo_data.sql
 db/place_data.sql
 
 # Other
-package-lock.json
 .DS_Store

.gitignore

@@ -1,5 +1,6 @@
 # .prettierrc or .prettierrc.yaml
-embeddedLanguageFormatting: "auto"
+$schema: 'https://json.schemastore.org/prettierrc'
+embeddedLanguageFormatting: 'auto'
 jsxSingleQuote: true
 pugAttributeSeparator: 'as-needed'
 pugSingleQuote: false
@@ -8,5 +9,11 @@ semi: true
 singleAttributePerLine: true
 singleQuote: true
 tabWidth: 2
-trailingComma: "es5"
+trailingComma: 'es5'
 useTabs: true
+printWidth: 100
+plugins:
+  - prettier-plugin-embed
+  - prettier-plugin-sql
+language: 'tsql'
+paramTypes: "{ named: [':'] }"

.prettierrc.yaml

@@ -10,17 +10,33 @@ Writing code and developing in this application requires running three services:
 
 ---
 
-Boot the three app services:
+1. Create a the `yhsi_sqlvolume` volume in docker to hold the app database.
 
-```bash
-docker-compose -f docker-compose.development.yml up
-```
+   ```bash
+   docker volume create yhsi_sqlvolume
+   ```
 
-Or if you have `ruby` installed
+2. Boot the three app services:
 
-```bash
-bin/dev up
-```
+   ```bash
+   dev build
+   dev up
+
+   # Or
+   docker compose -f docker-compose.development.yml build
+   docker compose -f docker-compose.development.yml up
+   ```
+
+3. Run the database migrations by going to http://localhost:3000/migrate/latest
+
+4. Create a new user account and log in to http://localhost:8080.
+
+5. Once you are logged in, open a database console with `dev sqlcmd` and run the following command to give your user admin permissions:
+
+   ```sql
+   UPDATE [Security].[User] SET [roles] = 'Administrator', [status] = 'Active' WHERE [email] = 'some-user@some-host.com';
+   GO
+   ```
 
 ### Legacy Development Setup
 
@@ -33,7 +49,10 @@ docker-compose -f docker-compose.dev.yml up -d
 This command will start SQL Server and bind it to your local machine's port 1433. When it starts the first time, the database will be empty. To load it with data, you must obtain a database backup and put it into `/db/backups/yhsi.bak` then run the follow commands:
 
 ```
-docker exec -it yhsi_sql_1 bash
+dev exec db bash
+
+# or
+docker compose -f docker-compose.development.yml exec db bash
 ```
 
 This connects you to the running SQL Server container. Once in, run the following commands to create and restore the database from the backup: