Skip to content
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

Quickfix Provider #16

Open
CrystalMethod opened this issue Sep 3, 2014 · 2 comments
Open

Quickfix Provider #16

CrystalMethod opened this issue Sep 3, 2014 · 2 comments

Comments

@CrystalMethod
Copy link

As a developer I want to use quick fixes so that I can remove validation errors more quickly. ("Class foo.bar not found" -> "Create Class foo.bar")

@angelozerr
Copy link
Owner

It's a good idea. I don't know how WTP manages quick fixes.

I will study that when I will have time.

@gamerson
Copy link
Contributor

gamerson commented Sep 3, 2014

This is a neat idea, however, the quick fix provider that plugs into WTP
XML Search will have to be able to ask the user 'where' they want the new
class, in the case of multiple source folders.

I'm thinking that a generalized 'quick-fix' would be good for other areas,
like missing key="*" attributes in JSPs, but the same thing goes, if you
wanted to "quick fix" add a language key, the framework would have to
resolve which properties file it should come from which would likely
require user intervention.

On Wed, Sep 3, 2014 at 4:22 PM, Angelo notifications@github.com wrote:

It's a good idea. I don't know how WTP manages quick fixes.

I will study that when I will have time.


Reply to this email directly or view it on GitHub
#16 (comment)
.

Greg Amerson
Liferay Developer Tools
Liferay, Inc. www.liferay.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants