Explore TOML support

Open
#114 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
tooling

Research direction

No file or test is named in the issue. Start by reviewing how Blueprints currently use JSON, then define the TOML support scope and acceptance criteria before implementation; done means an agreed path for supporting TOML alongside JSON.

Written by the indexing model from the issue text.

Description

enhancement

JSON is a great data format, but lack of multiline strings can make writing Blueprints in it annoying. TOML seems like a reasonable alternative that supports multiline strings, has a less verbose syntax, and none of the YAML downsides (ambiguity, refs). Perhaps we could easily support both in the medium term?

cc @dmsnell @brandonpayton @juanmagarrido

Dominant language
PHP
Stars
61
Forks
21
Avg merge
19h 34m
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WordPress/php-toolkit

All issues in WordPress/php-toolkit

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.