Viewing a response to: @codingdefined/re-programarivm-php-command-to-check-the-syntax-of-a-chess-pgn-file-20180820t113401462z
Hi @codingdefined, thanks for the review. Yep, it is better to divide the work across multiple commits. Let me just note that I am squash merging my new features as it is shown in this example: [Feature/pgnsyntax (#3)](https://github.com/programarivm/pgn-chess/commit/3e2390e1f315918f915d5b674f7606cb6aa3feae) Is that okay? :) I'd like to squash merge the branches to keep the history of the project a bit more concise. On the other hand, here is the reason behind so many additions. I just added a few sample PGN files for testing purposes, and those ones contain thousands of lines -- [games-02.pgn](https://github.com/programarivm/pgn-chess/blob/3e2390e1f315918f915d5b674f7606cb6aa3feae/tests/unit/PGN/File/data/games-02.pgn) is an example having 10004 lines.
author | programarivm |
---|---|
permlink | re-codingdefined-re-programarivm-php-command-to-check-the-syntax-of-a-chess-pgn-file-20180821t120646828z |
category | utopian-io |
json_metadata | {"tags":["utopian-io"],"users":["codingdefined"],"links":["https://github.com/programarivm/pgn-chess/commit/3e2390e1f315918f915d5b674f7606cb6aa3feae","https://github.com/programarivm/pgn-chess/blob/3e2390e1f315918f915d5b674f7606cb6aa3feae/tests/unit/PGN/File/data/games-02.pgn"],"app":"steemit/0.1"} |
created | 2018-08-21 12:06:51 |
last_update | 2018-08-21 12:08:21 |
depth | 2 |
children | 0 |
last_payout | 2018-08-28 12:06:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 768 |
author_reputation | 2,631,258,794,707 |
root_title | "PHP Command to Check the Syntax of a Chess PGN File" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 68,906,907 |
net_rshares | 0 |