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
I think this project is great, however: here, the schema sets endDate as iso8601. It's unclear to me how to represent ongoing employment. Omitting endDate, or defining it as null would imply employment has not ended, but seems incomplete, something undesirable in a resume. Also, anything other than a valid iso8601 formatted date throws a warning in the schema validator in an IDE, which is extremely annoying.
I humbly suggest adding a new boolean property called "ongoing", "current" or something similar so that one can omit endDate and set "ongoing" to True. I realize this might allow someone to confusingly set ongoing to True while also setting an endDate, which is not ideal.
The text was updated successfully, but these errors were encountered:
I think this project is great, however: here, the schema sets endDate as iso8601. It's unclear to me how to represent ongoing employment. Omitting endDate, or defining it as
null
would imply employment has not ended, but seems incomplete, something undesirable in a resume. Also, anything other than a valid iso8601 formatted date throws a warning in the schema validator in an IDE, which is extremely annoying.I humbly suggest adding a new boolean property called "ongoing", "current" or something similar so that one can omit endDate and set "ongoing" to True. I realize this might allow someone to confusingly set ongoing to True while also setting an endDate, which is not ideal.
The text was updated successfully, but these errors were encountered: