You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies, it seems like for this and #94 I have something wrong with my .properties file. Let me know if it's easy for anyone to spot, I just used my files from 10+ years ago so I'm sure I missed something! I believe I have the name and prettyVersion fields so this error is a bit unclear to me!
Hi @shiffman , so sorry for the trouble. The current code is strict on the field names in the properties files for new contributions at the moment, though after some thought we decided to relax the rules, as per issue #45. I will renew work on getting this issue resolved.
But in the meantime, to pass the current strict rules, change authorList to authors and category to categories.
@shiffman just to clarify, the rules for existing libraries are relaxed, so it's backwards compatible, but the current validation for new additions expect authors instead of authorList, and categories instead of category as field names.
I've picked up the work on relaxing the validation, though, so I'll race ya to the solution for this issue. Till then, very sorry for the inconvenience.
@shiffman hello there, I just noticed, instead of minRevision and maxRevision your properties file has minVersion and maxVersion. Your examples are already added to the contributions database, but on your own time, would be great to revise this field as well, just so your properties files does what you expect it to - at the moment, we ignore these fields.
Thank you so much for helping me with this, I'm sorry I didn't get back to this sooner to fix the file. I appreciate your explanations and helping get the examples included! I'll open an issue linking back to here in my repo to remember to update the min and maxRevision properties next time I do a release!
Activity
github-actions commentedon Sep 1, 2025
There was an error in reading your properties file or parsing it.
Please ensure that the URL is correct and the file follows the required format.
Errors when parsing file. Please check all required fields, and file format.
[-]Nature of Code Processing Exa ples[/-][+]Nature of Code Processing Examples[/+]github-actions commentedon Sep 1, 2025
There was an error in reading your properties file or parsing it.
Please ensure that the URL is correct and the file follows the required format.
Errors when parsing file. Please check all required fields, and file format.
[-]Nature of Code Processing Examples[/-][+]Nature of Code Processing Example Pack[/+]github-actions commentedon Sep 2, 2025
There was an error in reading your properties file or parsing it.
Please ensure that the URL is correct and the file follows the required format.
Errors when parsing file. Please check all required fields, and file format.
shiffman commentedon Sep 2, 2025
Apologies, it seems like for this and #94 I have something wrong with my .properties file. Let me know if it's easy for anyone to spot, I just used my files from 10+ years ago so I'm sure I missed something! I believe I have the name and prettyVersion fields so this error is a bit unclear to me!
mingness commentedon Sep 2, 2025
Hi @shiffman , so sorry for the trouble. The current code is strict on the field names in the properties files for new contributions at the moment, though after some thought we decided to relax the rules, as per issue #45. I will renew work on getting this issue resolved.
But in the meantime, to pass the current strict rules, change
authorListtoauthorsandcategorytocategories.mingness commentedon Sep 3, 2025
@shiffman just to clarify, the rules for existing libraries are relaxed, so it's backwards compatible, but the current validation for new additions expect
authorsinstead ofauthorList, andcategoriesinstead ofcategoryas field names.I've picked up the work on relaxing the validation, though, so I'll race ya to the solution for this issue. Till then, very sorry for the inconvenience.
mingness commentedon Sep 3, 2025
Ah, and to explain the error message, it's saying that the field name on line 42,
authorsis missing.mingness commentedon Sep 4, 2025
Have relaxed the validation for new contributions. the properties file should pass once this issue is reprocessed.
[-]Nature of Code Processing Example Pack[/-][+]Nature of Code Processing Example Pack [/+]github-actions commentedon Sep 4, 2025
Your properties file was successfully parsed.
A pull request with your contribution has been successfully created.
mingness commentedon Sep 4, 2025
@shiffman hello there, I just noticed, instead of
minRevisionandmaxRevisionyour properties file hasminVersionandmaxVersion. Your examples are already added to the contributions database, but on your own time, would be great to revise this field as well, just so your properties files does what you expect it to - at the moment, we ignore these fields.shiffman commentedon Sep 4, 2025
Thank you so much for helping me with this, I'm sorry I didn't get back to this sooner to fix the file. I appreciate your explanations and helping get the examples included! I'll open an issue linking back to here in my repo to remember to update the min and maxRevision properties next time I do a release!