Fix README HTML element mistake.
This commit is contained in:
@@ -24,7 +24,7 @@ As soon as this file is read and exposed as a Class via 'json_decode', I use a f
|
|||||||
That contains a switch, which allows me to create a mapping for 'pretty' and 'ugly' names for categories.
|
That contains a switch, which allows me to create a mapping for 'pretty' and 'ugly' names for categories.
|
||||||
This fixes a limitation in how I wrote the data within the JSON file, in a very easy way. Once it
|
This fixes a limitation in how I wrote the data within the JSON file, in a very easy way. Once it
|
||||||
finishes generating the name mapping for the current Category, it writes each category's NiceName variable
|
finishes generating the name mapping for the current Category, it writes each category's NiceName variable
|
||||||
from the JSON file, with an accompanied line which resembles an <hr> tag in HTML. After this, it performs
|
from the JSON file, with an accompanied line which resembles an `<hr>` tag in HTML. After this, it performs
|
||||||
another foreach loop, this time upon each TileData entry as 'Entry'. I then nested a foreach loop,
|
another foreach loop, this time upon each TileData entry as 'Entry'. I then nested a foreach loop,
|
||||||
which checks if the current Entry's category matches the current UglyName for the current Category the site
|
which checks if the current Entry's category matches the current UglyName for the current Category the site
|
||||||
is parsing. If it does match, the site then writes out a new DIRECTORY (1) element, whose first section
|
is parsing. If it does match, the site then writes out a new DIRECTORY (1) element, whose first section
|
||||||
|
|||||||
Reference in New Issue
Block a user