Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Export attributes should only be allowed on class

See original GitHub issue

I wanted to export some instances with attributes, so I was pleasantly surprised that ExportAttribute can be put on a property.

Some research later, I find nothing in Grace code that looks at export attributes on anything else than a class, so their attribute target should probably be changed.

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

ipjohnsoncommented, May 27, 2020

Yeah it is interesting how fluent registrations became so popular because registering hundreds (we have 500+) by hand sounds horrible. I usually just export a whole assembly by interface and apply lifestyles based on naming convention and patch any missing piece with fluent registration (there isn’t usually much).

I’ll make the change to the attribute usage to clear up any confusion. Sorry for the inconvenience.

0reactions

jods4commented, May 18, 2021

@ipjohnson sorry to necro that old issue, but I do have a related question:

I have cases where some of my assemblies has to export from a factory method. Is there a way to achieve this with attributes and automatic discovery?