multiple relationships to one entity on one page with ERModern does not work about wonder HOT 5 CLOSED

I considered the same solution when I first encountered this. Unfortunately, that will still break if there are multiple ERDInspects of the same EO on a single page. Imagine entity A has two relationships to entity B. If the property level component for both A->B relationships is an ERDInspect, then this same problem happens with every field in the two inspects. Just adding the property key doesn't really fix the problem, it simply moves it one page deeper.

Also remember that sometimes the property key is actually a key path. That keypath could even terminate with an @key. That makes parsing the property key for a css ID a bit more difficult too.

from wonder.

What about using UUID's as part of the ID generation? Would that solve it, or am I misunderstanding the whole problem?

from wonder.

Well, it would have to be repeatable. UUID would work fine for uniqueness, but each div needs to have the same id for each page iteration. Otherwise, anything ajax outside of that container that uses the container id would break once the update container refreshed and the id changes.

The last time I did anything like ajax with d2w, I opted to generate the ids using ERXWOContext's safeId stuff in the component and pushed it onto the context after storing it on an ivar. I also remember firing a NSNotification to alert the interested parties.

It was a little complex, but it worked well with no potential for collisions. Doing that to all of ERModern would be a much more time consuming task. Have a look at the AjaxNotificationCenter and the AjaxObservingSwitch in the AjaxLook framework if you're interested.

Basically, using an assignment to do the job is straightforward and it works in most cases, but it is not flawless.

from wonder.

I thought this had been resolved but learned at WOWODC that it hadn't. I've added a pull request with a fix I've been using in production since late 2012: #561
It does not address Ramsey's concern regarding multiple editors for an entity on a single page, but I feel it's still a lot better than the current implementation.

from wonder.

This was fixed in [44c03bd].

from wonder.