Closed vvuk closed 1 year ago
I think this is a good idea. I'm always open to pull requests if you want to contribute this. Between work and baby, I don't have tons of time to invest in FlatSharp right now; however, I'm very happy to look at PRs!
I don't think the fix will be terribly profound. Usually with attributes like this, I try to make them apply on both the table/struct level, as well as the field level. So this layout would result in this result:
table fooTable (fs_preserveCase)
{
x : int (fs_perserveCase:"false");
y : int;
}
public class fooTable
{
public int X { get; set }
public int y { get; set; }
}
The NonVirtual documentation should apply for this as well I'd think.
This has been merged. I'll get it published in 6.3.4.
[Apologies for large number of issues -- I am happy to tackle all/most of these, just want to get a sense of whether they would be accepted or other thoughts!]
given
with
--normalize-field-names
, this would end up with a field namedX
. This is sometimes not what you want, especially with single-letter fields. Would be nice to be able to sayx: float (fs_preserveCase);
and have the field be generated exactly as declared in the fbs file.