Urban Risk Map reporting cards web-app.
Run npm run start
(for default deployment jp) or dep=cc npm run pre-build-tasks && ng serve
(for deployment with code cc) for a dev server. Navigate to http://localhost:4200/
. The app will automatically reload if you change any of the source files.
- Run
export dep='xx'
&npm run add-deployment
to create the scaffolding for a new deployment. - The following files will be added in the specified folders:
src/environments/xx
- environment.json
- environment.prod.json
deployments/xx/
- index.html
/assets
/icons
/images
/locales
- en.json
/logos
/resources
angular.json
will be modified to add deployment configurations.package.json
will be modified to add build scripts.- The default deck that will be served is
flood
. - To test the deployment locally, change the deployment variable in
package.json
>scripts.start
, runnpm start
, and openhttp://localhost:4200/test123/flood
in the browser.
- Run
export deck=sample
&npm run add-deck
to create a route to a new cards deck. - This will add a new folder,
sample
insrc/app/routes/decks
, including the following:
- sample-routing.module.ts
- sample.component.html
- sample.component.scss
- sample.component.spec.ts
- sample.component.ts
- sample.module.ts
- Add a new object to the list of "decks" in
src/environments/$dep/environment.json
for the respective deployments, with the following structure:
{
"decks": [
"name": "sample",
"cards": [
"location"
]
]
}
- To test the deck locally, change the deployment variable in
package.json
>scripts.start
to $dep for which the environment file was modified in Step 3, runnpm start
, and openhttp://localhost:4200/test123/sample
.
- Run
export card=card_name
&npm run add-card
to create a route to a new card. - Add
card_name
to the list of 'cards' insrc/environments/$dep/environment.json
for the desired deck object, eg.
{
"decks": [
"name": "flood",
"cards": [
"card_name"
]
]
}
- To test the card locally, change the deployment variable in
package.json
>scripts.start
to $dep for which the environment file was modified in Step 2, runnpm start
, and openhttp://localhost:4200/test123/flood/card_name
.
Run ng build
to build the project. The build artifacts will be stored in the dist/
directory. Use the -prod
flag for a production build.
Run ng test
to execute the unit tests via Karma.
Run ng e2e
to execute the end-to-end tests via Protractor.
To get more help on the Angular CLI use ng help
or go check out the Angular CLI README.
- Location - bug: pin location not showing immediately
2. Location - Search bar height set to 48
3. Flood depth - decrease opacity of water to 70% - 80% of what it is now.
-
Flood depth - main image is currently blurry
-
Flood depth - main image - new height to be sent by Hafsa
6. Flood depth - bug: shows in cm before changing to ft in
7. Flood depth - dots to be added below gender icons
8. Photo - make it optional. Enable next button from the beginning.
9. Photo - fix font size of button. ‘Upload image’
-
Photo - bug. When a second photo is replaced by new photo it still shows the previous one in edit
-
Photo - being compressed in view. Focus on center point in the viewing square and let the rest not show. So the scale is not off.
-
Photo - Allow uploading of the entire image not just square. This is done right alright. Don’t change. Remove the cropping out feature, change to focusing in.
-
Photo - Edit option needs to be reworked to match figma
14. Description - ‘enter description here’ a. Fix font color b. Fix font size c. Fix font itself
15. Description - remove ‘(optional)’ from copy next to ‘Add description’
16. Description - remove ‘a’ from between ‘Add’ and ‘description’
17. Description - bug: the character count is a countdown. Make it count up.
-
Desktop Location - Instruction Copy. We want to keep it different. Should read “Click and drag to your pin location” instead of “Move…”
-
Overall - Buttons. Both next and back button backgrounds should remain white in full opacity. Just the words should be lesser in opacity
-
Overall - Buttons - Next and Back button are not turning green on phone. Works fine on desktop
-
Checklist - work to start after Hafsa notifies that screen is ready
-
Summary - work on this screen once Hafsa has made changes and they have been discussed.