Open antialias opened 4 years ago
Closed as duplicate of #357
Can we keep this open? It's a different ask. This issue describes adding custom importers and exporters to resume-cli whereas #357 requests adding support for Europass specifically.
Yes, just try to direct the conversation toward actionable changes. I'm trying my best to clean up a massive backlog of issues that were either not actionable or didn't result in any meaningful work.
Yes, just try to direct the conversation toward actionable changes.
This is pretty much done in my fork. I mostly opened this ticket to get feedback from the dev community (i.e. you as far as I can tell, lol) before opening a PR.
(btw, I have addressed all the open and still relevant issues for resume-cli in my own fork; kinda waiting for feedback on my first PR before opening the next one though)
Made a "Request For Comment" label to avoid stepping on toes.
Essentially we should just be adding all the importers and exporters to the homepage, I think there are quite a few already.
Instead of bringing importers/exporters directly into jsonresume code.
I suggest we have a naming convention much like themes. (as @antialias also suggested)
jsonresume-importer-europass
jsonresume-exporter-europass
Then given enough traction we support a command such as
resume import europass
(something else probably)
https://github.com/jsonresume/resume-cli/issues/357
to
and from
also sound nice
jsonresume-to-europass
and jsonresume-from-europass
(not sure it is the most obvious terminology to most folk)
The codebase is ready for this feature to be added. I will start work this weekend or Monday.
Similar to how themes are implemented as separate packages, it would be nice to have community-developed importers and exporters in order to implement interoperability with other resume formats, e.g. h-resume and europass.
Related ticket: https://github.com/jsonresume/resume-schema/issues/280