Conversation
|
Okay so as I expected, we are actually relying on the behaviour of |
|
@jrudolph @raboof So I had a quick look at this and I don't know what to do here, it seems like making The whole reason why |
|
I know have come to the same conclusion at least once before. The whole attributes precedence story is quite complex and at the point back then I shied away from understanding enough of it to make sense of why we exactly depend on the previous behavior. To make progress in pekko I'd be fine moving the |
|
@jrudolph it would be fine to copy over the getFirst code to this one place where we seem to need it |
|
Question, why was |
So
getFirstfor getting an attribute is deprecated and you are instead meant to usegethowever this does have a different behaviour change (i.e.getFirstwill get the first found attribute where asgetwill get the most specific attribute).Since we are now in the 1.1.x branch these kinds of behaviour changes are allowed