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

Any method to detect the METADATA conflicts? #345

Open
ray-linn opened this issue Sep 5, 2022 · 0 comments
Open

Any method to detect the METADATA conflicts? #345

ray-linn opened this issue Sep 5, 2022 · 0 comments

Comments

@ray-linn
Copy link

ray-linn commented Sep 5, 2022

I add two metadata with a conflict key under the same property

		registration::property("value", &g_value)(
			metadata(ASN1_ATTRIBUTE_TAG, ASN1IntegerAttr {.name = "Data" }),
			metadata(ASN1_ATTRIBUTE_TAG, ASN1BooleanAttr {.name = "Flag"})

			);

When running unit test, it looks only 1st metadata is reserved, however, I hope this conflict can be reported at runtime? is there any method to force it throws exceptions instead of ignore the conflict?

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