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
{{ message }}
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
Today the SDK contains a lot of boilerplate code to send an event. This can be seen when writing the unit test (see https://github.com/cdfoundation/sig-events/pull/92/files for an example). We could probably reduce the amount of code one needs to write to generate an event.
Some ideas on doing this could be:
Generate the code from a specification
Write the code smarter
The text was updated successfully, but these errors were encountered:
When developing the new SDK I tried to avoid where possible code duplication.
It is the nature of go to be explicit though, it is harder in go than in python to reduce the amount of code as there is no such thing as polymorphism in go.
I've used a simple shell script to generate the base file for most events, but the limitation is that the generated files need then to be manually updated, so it is not possible to regenerate existing files. It is rather straight forward to add new events to the SDK though, and I plan to document the process eventually.
I would close this one and open an issue in the SDK about documenting how to add new events and new fields to existing events.
Today the SDK contains a lot of boilerplate code to send an event. This can be seen when writing the unit test (see https://github.com/cdfoundation/sig-events/pull/92/files for an example). We could probably reduce the amount of code one needs to write to generate an event.
Some ideas on doing this could be:
The text was updated successfully, but these errors were encountered: