-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quick Fix for unknown properties broken #442
Comments
Was able to easily reproduce this easily. Thanks for reporting this. We weren't aware it was broken and also I have no idea when / how it got broken. It certainly wasn't an intentional change.
In future I hope you will report these kinds of things as soon as you notice them. I know, I know, we always think someone else will notice the bug too and report it, so we don't bother. I'm guilty of this myself on occasion as well. Anyhow...I'm really glad you finally reported it. |
Trying to verify the fix today in CI build but something is still not working. I'll have to take another look. |
Is there a quick fix for vscode? I'm getting the same error in vscode but with no quick fix available. |
Yes, it works I just tried in both application.properties and application.yml file. Works in both cases. Some little oddities I found that might be a little confusing:
|
For the past several versions of the STS (the Eclipse version) the "Quick Fix" for an unknown property isn't working as it used to work and is, in fact, not very useful.
Suppose that I have the following YAML:
In order versions of STS (I'm not sure when this quit working), the Quick Fix would offer an option for creating metadata for
myapp.orders.pageSize
. But in more recent versions it offers the option of creating metadata formyapp
. Not only is this inconsistent with how it used to work, it isn't useful at all. I would never need metadata formyapp
...but I would need it for the entiremyapp.orders.pageSize
.The text was updated successfully, but these errors were encountered: