Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editor: Basic editing functionality #500

Closed
5 tasks done
goldpbear opened this issue Oct 27, 2016 · 0 comments
Closed
5 tasks done

Editor: Basic editing functionality #500

goldpbear opened this issue Oct 27, 2016 · 0 comments

Comments

@goldpbear
Copy link
Contributor

goldpbear commented Oct 27, 2016

  • Open place detail views in an admin-only editor mode
  • Update all form fields, title field, and all comment fields
  • Delete comments
  • Hide place
  • Handle unsaved changes when the user navigates away from a place detail view with editor mode toggled. What happens when the user switches to list view? Directly to another place? etc.
@goldpbear goldpbear added this to the Nov. 11 2016 sprint milestone Oct 27, 2016
@goldpbear goldpbear self-assigned this Oct 27, 2016
goldpbear added a commit that referenced this issue Oct 28, 2016
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Oct 28, 2016
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Oct 28, 2016
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Oct 28, 2016
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 8, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 8, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 11, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 11, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 16, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 16, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 22, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 22, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 22, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Feb 22, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 4, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 4, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 6, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 6, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 6, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 6, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 15, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 15, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 16, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 16, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 24, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 24, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 27, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Mar 27, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
goldpbear added a commit that referenced this issue Apr 6, 2017
Override route() method in routes.js with custom behavaior to check
if following a given route would navigate away from a detail view
with unsaved editor changes.

Addresses: #500
goldpbear added a commit that referenced this issue Apr 6, 2017
To guard against unsaved editor changes being lost, remember the detail
view that's on display in the side panel.

Addresses: #500
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant