However, the same approach does not work when using sol! for a path to a Solidity file.
It would be great if such a pattern would also work here to add derives (probably serde being the most relevant one) to all applicable generated types.
Of course, the content of the Solidity file could be copied into the macro to make the derives work, but this would lead to code duplication and consistency errors.
Component
sol! macro
Describe the feature you would like
When using the
sol!
macro for ABI JSON files it is possible to specify additional (derive
) attributes and everything works as expected:However, the same approach does not work when using
sol!
for a path to a Solidity file. It would be great if such a pattern would also work here to add derives (probablyserde
being the most relevant one) to all applicable generated types. Of course, the content of the Solidity file could be copied into the macro to make the derives work, but this would lead to code duplication and consistency errors.Additional context
No response