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
Idea to have each packet (and its fields) contain a property pointing to intermediary mappings? I would then go on an include different json files for different mappings and have a branch-based system to choose for the right protocol version. The mapping files will probably have to be auto-generated and edited as I don't want to include every mapping but only the ones that are important (field names, class names)
The text was updated successfully, but these errors were encountered:
Idea to have each packet (and its fields) contain a property pointing to intermediary mappings? I would then go on an include different json files for different mappings and have a branch-based system to choose for the right protocol version. The mapping files will probably have to be auto-generated and edited as I don't want to include every mapping but only the ones that are important (field names, class names)
The text was updated successfully, but these errors were encountered: