Open Mcfloy opened 2 years ago
Hey Mcfloy, thanks for opening the issue.
I did include the type Timstamp
for timestamp dates. Regarding i16, u32 and other Rust types.. the main goal of ESDL is to not be specific to any language, and just provide basic types which can be mapped to language specific types.
Though, I'm sure there could be some improvements in customizing the generated code. But I don't feel it's too valuable to specify if a number is an 8 bit integer, or 64 bit integer. The main inspiration for this is GraphQL.
Though if people do have this requirement for their projects, I may look into it further.
I'll leave this issue open for now in case anyone has anything to add.
Coming back to this, I do thing uint may be useful. I wonder what would be a good way of making it more dynamic.
The options I can thing of now are:
i32
to Int
. But the downside of this is that the type would be overwritten completely.Double
, Float
, Int32
, Int64
, Uint32
, Uint64
, Bool
, String
, Bytes
But I'm open to other ideas about this.
I like the protobuf types idea as people that would use ESDL would also be familiar with Protobuf.
Hello, thanks for the thalo initiative, really good project!
Currently the language is strongly opinionated, as a
Int
is ai64
however we are missing other types such asi16
,i32
,u16
,u32
,u64
(for timestamp)I would like to have the ability to explicit a type from Rust in a ESDL file. As there are multiple languages involved, it would be probably easier to cheat a bit and explicit the primitive types as custom types.
Do you have any idea about this ?