Look into merging trait definitions and macro code together.

[ruseinov]

For everything that is defined in near-sdk-macros/src/core_impl/code_generator. Perhaps a good approach could be to introduce a code_generator module for each trait in their respective modules.

Originally posted by @frol in #1118 (comment)

[frol]

On second thought, someone would need to look into the project structure and make a call on what would be the best way to resolve this structuring puzzle. I think it does not require deep NEAR understanding, so I mark this issue as good-first-issue for someone to potentially play around it, but it is not a high-priority issue by any means.

[ruseinov]

Sounds good! Let's see if someone wants to attack this.

[IjayAbby]

Hey @ruseinov can I give it a shot see what I can come up with?

[IjayAbby]

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

I have an understanding in both Rust and Python and would love to stretch out my rust skills a bit. Am not familiar with NEAR but I can work around it.

How I plan on tackling this issue

Work closely with the project maintainer to see how best I can resolve the issue with existing ideas in place. Would love to give it a shot.

[frol]

@IjayAbby Sure, give it a try