As I was reviewing tests in #277, I realized that the fileReference name is a path (like ./test.png), not a basename (test.png). In particular, if you have two fileReferences in the same page, say one to test.png and the other to ./test.png, the name field is arbitrarily the one or the other.
We can normalize that name by removing a starting ./, but it still bugs me that the name is a path (especially since we also have a path field). Note that in build.ts we use this name as a path, when the file is not in the page directory.
As I was reviewing tests in #277, I realized that the fileReference name is a path (like
./test.png), not a basename (test.png). In particular, if you have two fileReferences in the same page, say one totest.pngand the other to./test.png, the name field is arbitrarily the one or the other.We can normalize that name by removing a starting
./, but it still bugs me that thenameis a path (especially since we also have a path field). Note that in build.ts we use this name as a path, when the file is not in the page directory.