Closed danielfdsilva closed 8 years ago
Tried to test the iD part, but get stuck now on when saving an edit:
Can try to tackle this tomorrow morning. Any ideas @danielfdsilva ?
I am not able to replicate the problem. Can you give me all your steps? We can also try to work this out together.
Check out the branch. Run make & python simplehttpserver. I can start clean and do another attempt
@dereklieu Could you have a look at this PR? Have to focus on IFC proposal this morning.
@danielfdsilva I need to look at this more, but one enhancement I'd like to see is if we could hide the error box when there are no errors, instead of saying that they're all fixed? Or perhaps show it much smaller and grayed out. Something like:
[edit] although I think I'd prefer to see it hidden altogether. I also think the regular error display should be a bit more error-y, visually, to grab your attention more. As is, you wouldn't necessarily look to it at first when you selected a way.
@dereklieu Sure thing, that is not a problem. We should compile a list of all the enhancements, so then can be applied. I don't think hiding the errors is good UX, though. The user may be left wondering if they may be somewhere else.
@danielfdsilva sounds good. I'll put together a list this morning. And yeah I see your point about not hiding completely and think that's a good call.
Also trying to debug why I get a 500 error when trying to save to the currently deployed API on Heroku, which has the requisite route handler.
500 was this mispelling
@danielfdsilva ok, I fixed a few issues in other repos that were blocking this.
The last thing that remains to be done is to clean up the rendering code in waytask_list. To see the problem:
This is likely something to do with d3 enter/exit pattern.
Depends on: https://github.com/opengovt/openroads-api/pull/122