A memory efficient parser for the Valve Data Format (*.vdf) written in PHP.
Fully supports the VDF specification, except for the #include
macro.
PHP 7 or later. No production dependencies.
You can install the package via composer:
composer require exayer/vdf-converter
Let's say we are parsing the following VDF:
$vdf = '{
"mercury" {
"distance" "58"
}
"venus" {
"distance" "108"
}
"earth" {
"distance" "149"
}
}';
It can be parsed in one of these ways (based on input source):
<?php
use EXayer\VdfConverter\VdfConverter;
// $vdf declaration
$planets = VdfConverter::fromString($vdf);
$planets = VdfConverter::fromFile('data://text/plain,' . $vdf); // usually filename here
$tempFile = tmpfile();
fwrite($tempFile, $vdf);
fseek($tempFile, 0);
$planets = VdfConverter::fromStream($tempFile);
$planets = VdfConverter::fromIterable([substr($vdf, 0, -60), substr($vdf, -60)]);
To get the data you need to iterate over generator using foreach
foreach ($planets as $name => $data) {
// #1 iteration: $name === "mercury" $data === ["distance" => "58"]
// #2 iteration: $name === "venus" $data === ["distance" => "108"]
// #3 iteration: $name === "earth" $data === ["distance" => "149"]
}
Or simply convert it to array
$result = iterator_to_array($planets);
//
// $result = [
// "mercury" => [
// "distance" => "58"
// ]
// "venus" => [
// "distance" => "108"
// ]
// "earth" => [
// "distance" => "149"
// ]
// ]
Some VDFs are known to contain duplicate keys.
To keep the result structure the same as the VDF and since the parser is generator based (not keeping in memory pairs)
the duplicated key will be modified - the counter will be concatenated to the end (e.g. key__[2]
).
$vdf = '{
"mercury" {
"distance" "58"
"velocity" "35"
"distance" "92"
}
"mercury" {
"distance" "108"
}
"earth" {
"distance" "149"
}
}';
$result = iterator_to_array(VdfConverter::fromString($vdf));
//
// $result = [
// "mercury" => [
// "distance" => "58"
// "velocity" => "35"
// "distance__[2]" => "92"
// ]
// "mercury__[2]" => [
// "distance" => "108"
// ]
// "earth" => [
// "distance" => "149"
// ]
// ]
If you want to customize the formatting key process, you can create your own custom formatter. A formatter is any class that implements EXayer\VdfConverter\UniqueKey\Formatter
.
This is what that interface looks like.
namespace EXayer\VdfConverter\UniqueKey;
interface Formatter
{
public function buildKeyName(string $key, int $index): string;
}
After creating your formatter, you can specify its class name in the uniqueKeyFormatter
method of the EXayer\VdfConverter\VdfConverterConfig
object. The config can be passed as second argument to any from
builder method. Your formatter will then be used by default for all duplicate key handling calls.
$config = VdfConverterConfig::create()
->uniqueKeyFormatter(YourCustomFormatter::class);
$iterator = VdfConverter::fromString($vdf, $config);
Warning: Do not create formatters that create a key like __2
, as some VDFs may have keys in this format.
composer test
- Key Pointer - Parse only the specific part of the VDF based on the path built from the keys (e.g. 'key1.key2.key3').
The code is inspired by @halaxa package json-machine. Thank you!
The MIT License (MIT). Please see License File for more information.