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
When using the demo on your website for parsing LinkedIn .zip files, there are a lot of fields parsed incorrectly.
startDate contains , summary contains and endDate contains StartDate.
The LinkedIn Job Description is completely left out.
I have seen a Pull Request, but I am unable to verify if this solves this issue because of the other issue that is preventing me from running the linkedin-to-json-resume code on my webserver.
Regardless of the issues/bugs, I compliment you (JMPerez) for this software initiative! I hope I will be able to use it soon.
Snippet from resulting JSON with sime data replaced by <...>:
{
"company": "",
"position": "",
"website": "",
"startDate": "undefined--01",
"summary": "",
"highlights": [],
"endDate": "undefined--01"
},
{
The text was updated successfully, but these errors were encountered:
When using the demo on your website for parsing LinkedIn .zip files, there are a lot of fields parsed incorrectly.
startDate contains , summary contains and endDate contains StartDate.
The LinkedIn
Job Description
is completely left out.I have seen a Pull Request, but I am unable to verify if this solves this issue because of the other issue that is preventing me from running the linkedin-to-json-resume code on my webserver.
Regardless of the issues/bugs, I compliment you (JMPerez) for this software initiative! I hope I will be able to use it soon.
Snippet from resulting JSON with sime data replaced by <...>:
{
"company": "",
"position": "",
"website": "",
"startDate": "undefined--01",
"summary": "",
"highlights": [],
"endDate": "undefined--01"
},
{
The text was updated successfully, but these errors were encountered: