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

visibility SPI does not enable to implement default rules #328

Open
rmannibucau opened this issue Apr 11, 2022 · 1 comment
Open

visibility SPI does not enable to implement default rules #328

rmannibucau opened this issue Apr 11, 2022 · 1 comment

Comments

@rmannibucau
Copy link

The default implicit visibility spi equivalent has rules like "if there is a field and some getter/setter ....", this can only be implemented if you have the field + the clazz being mapped (example ClassWithField and SubClassWithGetterForField). Current SPI does not enable to implement that.
Idea of this ticket is to give a context enabling to implement such a rule passing the class being mapped too and if it is for serialization or deserialization (I guess we want a context {field,class,type}).
Similarly for methods we would need a context too.
Current methods can be implemented with a default in a ContextAwarePropertyVisibility new SPI to not break backward compatibility maybe?

@rmannibucau rmannibucau changed the title visibility SPI does not enable to implement it visibility SPI does not enable to implement default rules Apr 11, 2022
@rmannibucau
Copy link
Author

partially related to #325 but also adds the (de)serialization info

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

1 participant