Bug or feature: TableView.EditEvent - same type for value and row?

Question

Just noticed (normally I don't care overly much about generics, they are my natural enemies : -) that the return type for both cell and row data is the same:
class EditEvent<T> {
    T getNewValue()
    T getOldValue()
    T getRowValue()
}old/new value is fine, but typically the row has another type, which most probably is completely unrelated, as f.i. in
TableView<Person> tableView = new TableView<Person>(persons);
TableColumn<String> firstName = new TableColumn<String>("First Name");
firstName.setProperty("firstName");
EventHandler<EditEvent<String>> nameEditHandler = new EventHandler<TableView.EditEvent<String>>() {
            @Override
            public void handle(TableView.EditEvent<String> e) {
// compile error
                Person p = (Person)e.getRowValue();
                String newValue = (String)e.getNewValue();
                p.setFirstName(newValue);
firstNameCol.setOnEditCommit(nameEditHandler);The compile error is due to the event requiring the same type for row and cell. Obviously, can remove all type parameters - but how to solve cleanly without getting unchecked/rawtype warnings?
Thanks
Jeanette

Answer 1

Good morning, Jonathan (my day time : -)
If you mean that big issue where you threaten (and locally actually already did) to remove all the niceties of auto-magic column binding via setting property names - yeah, I've read it, partly unhappily. But that's another story.
to create two separate EditEvents - one for row edits and one for cell edits.
hmm .. have been expecting something along the lines of
EditEvent<R, C> {
     R getRowValue();
     C getOldValue();
     C getNewValue();
// used in
TableView<R>
TableColumn<C>
// for row edits
R == C
getRowValue() == getOldValue()Musing a bit longer, the event could be streamlined a bit - remove all the convenience sugar: the receiver has to know the exact details of grabbing the data anyway in order to be able to change it (in the current workflow, it's not necessarily the way to go) so old/row is redundant
EditEvent<S> {
   <S> getEditValue();
}Cheers
Jeanette