Status Update
Comments
gh...@google.com <gh...@google.com>
gh...@google.com <gh...@google.com> #2
Forgot to add the second screenshot. Here it is
gh...@google.com <gh...@google.com> #3
Hi! I don't seem to be able to reproduce this behavior. As far as the resolution goes, these are treated exactly the same under the hood so I'm not sure how there would be a discrepancy.
I did notice that in your example, you are missing a semicolon after "age" in the PersonView
, and when I left that out, I got the same issue with things not resolving, but once I put the semicolon then everything worked as expected. Just want to verify that that's not the cause.
an...@google.com <an...@google.com> #4
The missing semicolon is a typo from my part and shouldn't change the behaviour in the issue. In my own code, I also have a semicolon. Unfortunately I don't seem to be able to edit the issue description.
Maybe the issue only arises in certain situations? I gave a simplified version of the problem with simple objects, but in my project I have database view on joins. I made sure that the simplified version of the issue also arises syntax errors in my own project though. Maybe something else clashes with it?
At the moment of writing, there are 2 other persons who also seem to have the issue (looking at the "I am impacted" vote count), so it seems that I'm not the only one with the issue, but weird that you can't seem to reproduce with my example.
Let me try to reproduce the issue in a clean project. Give me day or two for that.
Description
Summary from a Slack conversation:
product-info.json
is created by IJ platform build scripts and added to the root of an IDE distribution.product-info.json
is used by various JetBrains tooling (e.g. IntelliJ Plugin Verifier, IntelliJ Platform Gradle Plugin) to understand the layout of the IDE, the list of bundled plugins, and more.The
product-info.json
file in Android Studio is inaccurate because it is missing metadata for all Bazel-built plugins, including the Android plugin. This breaks JetBrains tooling, forcing them to add workarounds.The most straightforward fix is to stamp
product-info.json
with additional metadata during our Bazel build. (However, note: AFAIKproduct-info.json
is undocumented and its format may change slightly between releases.)