yepengding / bibtex-js-parser Goto Github PK

Currently, type is sensitive, which is not convenient.

For example, the following example does not work:

@InProceedings{Foo,
  author    = {Tom and the gang},
  booktitle = {Something amazing},
  title     = {An awesome research},
  year      = {2022},
  month     = {jun},
}

But with type all lowercase, it works:

@inproceedings{Foo,
  author    = {Tom and the gang},
  booktitle = {Something amazing},
  title     = {An awesome research},
  year      = {2022},
  month     = {jun},
}

The BibTeX standard does not explicitly require the last entry to end with a comma. Moreover, example from Wikipedia and automatically generated BibTeX from Google Scholar do not include a comma at the end of the last entry.

While bibtex-js-parser currently handles entries without trailing commas correctly and produces the expected output, it also prints a warning in the console for such cases.

Take the example in the README, if we remove the comma at the end of the last entry, it would be:

@inproceedings{ding_dagbase_2020,
	title = {Dagbase: a decentralized database platform {Using} {DAG}-based consensus},
	copyright = {All rights reserved},
	isbn = {1-72817-303-5},
	booktitle = {2020 {IEEE} 44th {Annual} {Computers}, {Software}, and {Applications} {Conference} ({COMPSAC})},
	publisher = {IEEE},
	author = {Ding, Yepeng and Sato, Hiroyuki},
	year = {2020},
	pages = {798--807}
}

@article{ding_formalism-driven_2022,
	title = {Formalism-{Driven} {Development}: {Concepts}, {Taxonomy}, and {Practice}},
	volume = {12},
	copyright = {All rights reserved},
	issn = {2076-3417},
	url = {https://www.mdpi.com/2076-3417/12/7/3415},
	doi = {10.3390/app12073415},
	number = {7},
	journal = {Applied Sciences},
	author = {Ding, Yepeng and Sato, Hiroyuki},
	year = {2022}
}

This would cause two warnings:

line 10:0 missing ',' at '}'
line 23:0 missing ',' at '}'

I suggest changing the program's behavior to make it more tolerant of entries without trailing commas, eliminating the warning from the console output. This adjustment would align the program with common BibTeX practices and user expectations.

In addition, the warning printed to the console does not indicate that it is from bibtex-js-parser. It would be more helpful for users to debug if the warning message can indicate its source (for example, print bibtex-js-parser: line 10:0 missing ',' at '}'). I spent a lot of time looking for where the warning comes from.