jcalero / kerbal-parser Goto Github PK

E.g.
NODE { .... }
NODE { .... }

At the moment modulemanager config nodes (e.g. @PART { ... } ) will be treated like normal nodes and added to the models (e.g. with name @PART, etc).

Need to detect if a node is a module manager node and ignore it or deal with it independently.

Hi.
I compiled your Kerbalparser to your techtree edit.
but it keep giving me this issue
Please help me.
Thanks!

E.g. ... } NODE { ... }

Annoying to deal with it in the current "line by line", sequential design. Should be easier in a "token by token" design.

E.g.

NODE {
  name
  property = value
  ...
}

name is ignored and the file parses fine. Should throw parse error in dirty files.

_Check how KSP handles this_

Important for library users to be able to catch parse errors.

E.g.

broken ¬! = node --- name
{
   property = value
   ....
}

Node name here becomes broken ¬! = node --- name and the file parses fine. Need to validate node name and catch parse errors like this.

• Single string
• No special characters

Apparently files can have loose properties outside a node or no top node at all. In which case the filename is considered a top node.

E.g. part.cfg that contains name = mk1pod and nothing else will be considered as a file with

PART {
  name = mk1pod
}

in it.

Verify how KSP deals with this.. But all in all, we need to be able to store multiple values with the same name. Essential for Tech Tree parser that stores parts lists.

One solution: Store values as lists.
Other solution: Store property/value pairs in a Lookup

With validation etc..

Throw parse error?
Update previous key value?
Store multiple values for each key? Unlikely

Write a test that parses the entire stock KSP GameData folder.

Extract operators, subtasks. Etc..

I.e.

NODE {
  property = value
  property = value }
  ....
}

The second value doesn't throw an exception (when it should), instead the value of property 2 is simply set to "value }"

Short example

E.g.

NODE {
  property = value
  SUBNODE {
    property = value
  }

This tree parses just fine. Need to make sure opening brackets always have a matching close bracket.

Set values to empty string.

Child nodes of STORY_DEF are CamelCase formatted instead of ALLCAPS.

I.e.

NODE { property = value
  property2 = value2
  ....
}

The first property = value should not be ignored.

Only first property with a certain name should be added, the rest are ignored and not throw errors.

Exceptions in NASAMission parts (atmosphericCurve, etc..) as well as STORY_DEF file.