You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I reviewed the discussions about code generation, and I also looked at Smithy's specific implementation of code generation. A question arose for me: why does code generation directly consume IDL and follow the path IDL -> code, rather than IDL -> YAML -> code? The second approach could fully leverage existing code generators, and I don't see any advantages to the first approach. Is it just to win what Nordic referred to as the "definition war" over API specifications?I would appreciate it if you could clarify my doubts.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, I reviewed the discussions about code generation, and I also looked at Smithy's specific implementation of code generation. A question arose for me: why does code generation directly consume IDL and follow the path IDL -> code, rather than IDL -> YAML -> code? The second approach could fully leverage existing code generators, and I don't see any advantages to the first approach. Is it just to win what Nordic referred to as the "definition war" over API specifications?I would appreciate it if you could clarify my doubts.
Beta Was this translation helpful? Give feedback.
All reactions