Conversation
This confuses everyone.
|
Docs are definitely an improvement. Do we care that we call these Fake Natives internally; but Dynamic Natives to pawn? Anyone digging through code will know them by the former name. |
|
I belive the intention is that they become just "natives" in the future, and the term "fake" has confused people in the past, I figured "dynamic" was clear but happy to change/remove. I think dropping the qualifier would make the most sense if anything. |
|
Yeah; if Fake/Dynamic are ephemeral ("") qualifiers let's drop them entirely to userspace. |
|
You could even go as far as adding the name of the plugin, that has the native already registered in the second error. |
Headline
left a comment
There was a problem hiding this comment.
Good improvement, cool with taking as-is, but I also like Peace-Maker's suggestion at identifying the other plugin's name so debugging is easier so if you want to go the extra mile then go for it, otherwise no problem
This confuses everyone.