IssueTracker

I noticed today that Dackka seems to append () when generating anchors for Java fields.

Example: https://developer.android.com/reference/androidx/media/AudioAttributesCompat#CONTENT_TYPE_MOVIE()

This is generated from the following Java (source):

public static final int CONTENT_TYPE_MOVIE = AudioAttributes.CONTENT_TYPE_MOVIE;

Aside from the AndroidX style guide, nothing stops the AudioAttributesCompat class also have a zero-args method called CONTENT_TYPE_MOVIE, something like:

public String CONTENT_TYPE_MOVIE() {
  return "foo";
}

How would Dackka disambiguate between these elements in this case?

A more realistic/risky example is androidx.media3.common.Format#id because it's lowercase, so it's much more plausible that an identically-named method could also exist.

I would expect Dackka to generate the following links instead (i.e. only suffix parentheses for methods):

• public static final int CONTENT_TYPE_MOVIE
  • https://developer.android.com/reference/androidx/media/AudioAttributesCompat#CONTENT_TYPE_MOVIE
• public String CONTENT_TYPE_MOVIE()`
  • https://developer.android.com/reference/androidx/media/AudioAttributesCompat#CONTENT_TYPE_MOVIE()