You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I encountered problems with adjacent strings as input for annotation messages as described in #2393, I tried using a string constant as input instead, like so:
const pleaseRenderMe ='I am not rendered :(';
@Deprecated(pleaseRenderMe)
voidfoo() {
print('bar');
}
However, using this approach led to a different kind of problem, namely that not the constant value, but its name is being rendered in the annotation, which does not seem like the intended behavior, especially since you cannot click on the referenced constant to see its value directly from the annotation:
The text was updated successfully, but these errors were encountered:
srawlins
added
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
P3
A lower priority bug or feature request
labels
Dec 20, 2023
As I encountered problems with adjacent strings as input for annotation messages as described in #2393, I tried using a string constant as input instead, like so:
However, using this approach led to a different kind of problem, namely that not the constant value, but its name is being rendered in the annotation, which does not seem like the intended behavior, especially since you cannot click on the referenced constant to see its value directly from the annotation:
The text was updated successfully, but these errors were encountered: