Not sure if that is accurate.
Because the first check !empty($this->item->id)is only true when the item already has an id set and other than 0/false (means we edit an existing item).
The second check !empty($this->item) && isset($this->item->id) will be true if the item is valid, but the ID may also be 0 (means it can also be a new item).

Well, but check !empty($this->item) is not needed and can be removed. If $this->item is empty at this point, all checks $this->item->id above this line will be wrong. Are you agree?
I can update the commit.

I do not understand, why commit 5ed1d17 is valid, but 6b585ae is not. I simple removed white spaces.

Imho, the isset should indeed be sufficient, because it will also return false if the item doesn't exist. So we gain nothing by explictiely checking the existence of the item prior to it.

I tried to restart the drone test. looks like an unrelated error to me.

@Bakual, why continuous-integration/jenkins/pr-merge reported an error? What I must do?

@nvyush you can ignore the jenkins failure for now, we are testing a new setup. It is important that the Required checks pass and the drone test (code styles) should also pass.

@rdeutz, thanks

I have tested this item ✅ successfully on 60788fd

For new items the ID is always NULL. Even by saying a_id=0 in the url. So why not joining the two if-conditions?

@FPerisa You're right. They can be combined and remove the second if statement.

Set to "closed" on behalf of @Quy by The JTracker Application at issues.joomla.org/joomla-cms/16412

See PR #20254