This message was deleted.
# community-support
s
This message was deleted.
p
No it won't. The interpreter in 8.0 is a first cut and only supports what's described in the release notes. We have plans to improve it progressively though.
e
the link from the release notes to the documentation says that ``«plugin id»`` is part of the constrained syntax
p
Note that using version catalog aliases for plugins or plugin specification type-safe accessors is not supported by the plugins {} block interpreter. This support will be added in a later version.
Maybe adding examples of what is not supported would make this clearer?
2
e
I guess it would be clearer to at least have a link from https://docs.gradle.org/8.0-rc-2/userguide/plugins.html#sec:constrained_syntax to somewhere describing other effects of using different syntax (such as this performance impact)
but it doesn't affect correctness, and is changing in the future… idk
p
Exactly
e
LGTM. (also I didn't know
Copy code
...`...`...
worked in markdown?)
p
I had to look it up 🙂
Please approve the PR if it LGTY
e
I don't think I'm authorized to do anything but I'll at least comment 🙂
p
anybody can do PR reviews
v
One more question I had was
id("java-library") apply false
It was not clear if that was supported or not
p
I answered on the PR
We decided not to warn for now because it causes no "regression" nor correctness issue
We might consider doing so once the interpreter supports all expected syntaxes, the warning would mean you're doing something funny
v
I agree warning by default is not something we want. However, it might be fun to have something like
org.gradle.earlyadopter.plugins_block.kotlin_interpreter=true
, so it warns earlier
p
We won't add this to 8.0, that ship has sailed. But thanks for the suggestion
👍 1
@Vladimir Sitnikov is your 👍 reaction on my comment to say that the current snippet is enough or that you would prefer it with all cases listed separately?
Thanks for clarifying!