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

[core] Expose the full mapping from property type id to property extractor #758

Merged
merged 1 commit into from Nov 27, 2017

Conversation

oowekyala
Copy link
Member

While working on the designer, it occurred to me that we need a way to list the different (type id -> property extractor) mappings, if we want to make a GUI to define properties.

@adangel
Copy link
Member

adangel commented Nov 25, 2017

Interesting. Yes, we probably need this sooner or later. The eclipse plugin might have some support already for defining properties - at least for changing the values of properties. I've updated the eclipse plugin yesterday - the property changes were mostly related to the changed package (so organize import fixed most of the problems). Whatever has been implemented in the eclipse plugin works without this mapping...

@oowekyala
Copy link
Member Author

I don't remember how it's done in the plugin... maybe it's hardcoded somewhere?

Does the plugin support defining properties on XPath rules though? Not just overriding them? If not, I'm not sure it would need it.

@adangel adangel self-assigned this Nov 27, 2017
@adangel adangel added this to the 6.0.0 milestone Nov 27, 2017
@adangel adangel merged commit 4724ed4 into pmd:master Nov 27, 2017
adangel added a commit that referenced this pull request Nov 27, 2017
@oowekyala oowekyala deleted the expose-property-mapping branch November 27, 2017 21:38
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

Successfully merging this pull request may close these issues.

None yet

2 participants