Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to choose fields to be exported? #45

Closed
Andre0991 opened this issue Dec 25, 2015 · 7 comments
Closed

How to choose fields to be exported? #45

Andre0991 opened this issue Dec 25, 2015 · 7 comments

Comments

@Andre0991
Copy link

I filled the address and languages parts on the json file, but they don't show up when exporting to any format.

Is it possible to change that?

I think it would be nice to put this on the readme (if it's possible).

Great tool, btw :)

@burntcookie90
Copy link

It seems like a lot of fields are just ignored, it's unfortuantely become a deal breaker for me.

Specifically:

resume.samples

and

resume.skills.list

@Andre0991
Copy link
Author

I suspect this depends on the theme and we would have to modify it to include another fields.

@hacksalot
Copy link
Owner

Hi gents, short answer here is that all built-in themes should support all JSON fields. If not, it's a bug, and most of this stuff should "just work" in v1.3. For now, this is a bug.

@burntcookie90 Apologies, and as a temporary workaround, you can use resume.skills.sets. The skills section is one of the more fluid (= messy) areas and one of the main reasons why fluent-themes releases are still tagged with a beta designator. Again, this is a bug, and will be fixed shortly. Thanks for the report.

@Andre0991 You're correct that it's up to theme, so for example, a business card-style theme doesn't have to present skill histories or employment timelines. For built-in themes, the requirement is that all documented JSON fields (and certainly major stuff like samples and skills) should flow to the resume.

Thanks guys.

@burntcookie90
Copy link

@hacksalot awesome, thanks for the update, I'll check back in with the project once it's out of beta then, looking forward to it!

@Andre0991
Copy link
Author

Cool @hacksalot, thanks.

@hacksalot
Copy link
Owner

Coverage has improved in 1.6.0/1.7.0. It's also now possible to explicitly ignore fields with the .ignore property (in both FRESH and JRS resumes). Closing this general issue but feel free to log specific bugs/features as you find them.

@Andre0991
Copy link
Author

Ok, thanks @hacksalot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants