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

How to allow custom metadata for fields? #454

Open
yellow1912 opened this issue May 24, 2015 · 2 comments
Open

How to allow custom metadata for fields? #454

yellow1912 opened this issue May 24, 2015 · 2 comments
Labels

Comments

@yellow1912
Copy link

Since we can have custom handler and custom exclusion rules, it makes sense to be able to allow the yml/xml/annotation driver to accepts and store additional/custom configuration key that will be later used.

Right now I see they are hardcoded in the driver files which means we probably have to override them to add our own configs. Is it the way to go now or there are other ways?

@kherge
Copy link

kherge commented Apr 28, 2016

I just bumped into this issue too.

It looks like there might be two issues that need to be sorted out for this work well:

  1. Consolidate the construction of property metadata.
  2. Store unrecognized property metadata into a $custom field on PropertyMetadata.

While #1 isn't really required, it would certainly save a lot of headaches in having to implement new features for each and every driver provided by this library.

@miguelrs
Copy link

👍 It'd be very useful to be able to add custom metadata to properties!
Looking at the code it seems that this is still impossible today, isn't it?

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

No branches or pull requests

4 participants