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
TypeExtractor.isSimpleLiteral() used to determine whether a FieldDef.initializer should be serialized as a literal value "initializer" or an "initializerExpression"
Changed
FieldExtractor now parses field default value assignments and returns FieldDef instead of FieldSig (FieldDef contains initializer field)
FieldExtractor constructor requires a new 3rd parameter, an OperatorUtil<>
ClassAst remove T_ENUM type parameter, enum members in a parsed enum will be represented by T_FIELD
FieldDef.initializerToJson() signature changed significantly to support new multiple token initializer expressions
AccessModifierParser and AccessModifierEnum removed parseFromSrc(), cleaned up code, added documentation
AccessModifierParsertryParseFromSrc(String) and defaultAccessModifier(String, ...) modified to takes List<String> for correctness and to simplify call sites
AstExtractor.createFieldParser() and implementations (CsBlock and JavaBlock) now return AstParser<List<FieldDef>> instead of ...FieldSig
BlockUtilparseKeyword() and tryParseKeyword() replaced with tryToBlock()
CsBlockParser._extractBlocksFromTree() renamed extractBlocksFromTree() (which was already public)
AstParser added blockComplete() with empty default implementation, will be called by BlockExtractor
Removed
Merged FieldSig and FieldSigResolved into FieldDef and FieldDefResolved
Fixed
C# annotation parsing fixed to handle multiple annotations in the same block, i.e. '[Annotation(One), Annotation(Two), ...]'
An issue with nested classes/interfaces getting assigned the incorrect access modifiers