Closed gth828r closed 1 year ago
Hi @gth828r
Perhaps you are looking at accessing the constants with symbolic names rather than the values (when generating the message) -
here is an example of that. Is this what you are looking at? Like the constant ID_NG_SETUP
. These constants are generated by the code already and can be included through the code generated using build.rs
mechanism.
You can check whether the constant you need is indeed generated or not. It's possible some keys were missed in code generation and that support will be required to be added then.
@gabhijit yes, that was exactly what I was looking for. Thanks for setting me straight!
Thank you for your excellent work on this project!
I was wondering if it is possible to access the value of the key meta value for the asn attribute which gets defined in the generated code?
For example, in ngap code that I generated, I see this:
When defining an NGAP_PDU, I need to explicitly set the procedure_code for an
InitiatingMessage
. Right now, I am just manually filling in the literal value like64
, but I am wondering if there is some way to just reference a key value forId_AMFCPRelocationIndication
from the generated code?