To make it less confusing, but first, lets make it more confusing.

Brings you back to the initial app page, all project data is gone. Start over Please.

Steps to re-create:

1. Login, Input a Project, Select a Zone
2. Click Edit button on one of the records of the selected zone.
3. Hit be browser back button.
4. Game Over.

A user has edited records in a zone, and goes to select another zone, or a new project.

Inform the user that there are un-saved changes to the Zone and they will be lost if they navigate away from them.

Add Welcome Content to Make more user friendly.

Add assets/images for future asset use, and teach gulp to make copies.

Validate user input for all of the fields with the following requirements:

"Create" button is disabled until requirements are met.

Zone Name:

• not empty

Domain Name:

• not empty
• valid domain format
• ends in period (make sure what ever is submited has a period on the end, regardless of what the user types)

Description:

• not required.

Create a form for adding a Resource Record to a Change Set

After you create a new zone show records.

On the initial page after login, add messaging to notify the user they must input a "Project" name to begin editing Zones.

After the Project is entered, then display the "No Zone Selected" message, indicating they must select a zone to begin viewing or editing.

Add a cancel button for the Save Changes dialog in Zone Record Edit mode.

Validate user input for all of the fields with the following requirements:

"Save" button is disabled until requirements are met.

Type:

• Not Empty
• Needs to be a valid record type of A, AAAA, CNAME, MX, NS, PTR, SOA, SPF, SRV, or TXT
• Capitalized

TTL:

• not empty
• integer with a with a minimum value of 0, and a maximum value of 2147483647 (RFC 2181 - TTL)

Name:

• not empty
• ends in period (make sure what ever is submited has a period on the end, regardless of what the user types)

Value (or RRData Values in the Form):

• not empty
• value has to match record type (i.e. A record is a valid IP, MX Records need a weight + hostname ending with a period (10 mail.example.com.) etc.)

Highlight the selected Zone in the Zone list to reflect what you are working on.

Inform user why it failed. (i.e. ContainerNotEmpty = Can Not Delete Zone with Records)

Mock the Google API for dev.

Buttons, etc...

Ability to Delete a Managed Zone and Prompt the user for verification of data delete.

Give the user an option to review changes they are about to make to a zone.

Modal with change summary????

Currently if you add a new record with the same type and name as another record.
Saving will fail.
Deleting the new record will remove both the existing and the duplicate. Bad.

Let the people know when their session has timed out.

After filling out the form to create a new A record (or pick record type for that matter), filing out the input for the first RRData value and clicking "Save" results in an empty "value" field.

You shouldn't have to add a new field to submit the contents of the first field.

To recreate this defect:

1. Login, Input a Project, Select a Zone
2. Click Add or Edit button on one of the records of the selected zone.
3. Fill out the form.
4. If you selected "edit" the record, remove the previous RRData Values to get to the first field only.
5. Input data into the RRData Value field, and click "Save"

Input Field:

Result:

Make the forms full with.

Ask the user if they are sure they would like to delete the record. Modal or otherwise.

The top panel will serve as a Zone Selector.

You input the project name, click load button.
This populates a ManagedZone dropdown selector.
Selecting a ManagedZone from the dropdown will populate a list of resource record sets and display Zone information: dnsName, name and nameservers.

While in record editing mode, disable the "edit" and "delete" buttons in the Zone Header:

Disable the Zone "edit" and "delete" buttons in the Zone Header while record add view.

Steps to recreate:

1. Login, Input a Project, Select a Zone
2. Click Add button on one of the records of the selected zone.

We need to create a change request view.
With Google Cloud DNS, you don't add/edit/remove individual zone records.
You submit Change requests:

{ additions: [...], deletions: [...] }
by default clicking make changes button should add the SOA record to both additions & deletions because you want to increment the serial number.

The readme is outdated and needs to be updated.

Disable the Zone "edit" and "delete" buttons in the Zone Header while record add view.

Steps to recreate:

1. Login, Input a Project, Select a Zone
2. Click Add button on one of the records of the selected zone.

express deprecated res.send(status): Use res.status(status).end() instead srv/lib/config/routes.js:21:13

body-parser deprecated bodyParser: use individual json/urlencoded middlewares srv/lib/config/express.js:14:11
body-parser deprecated undefined extended: provide extended option node_modules/body-parser/index.js:75:29
express-session deprecated undefined resave option; provide resave option srv/lib/config/express.js:17:11
express-session deprecated undefined saveUninitialized option; provide saveUninitialized option srv/lib/config/express.js:17:11

Ask the user if they are sure they would like to delete a zone with a modal, or some other method.

Confirm changes before submitting. It will show the zone name and additions/deletions