Filter on content or sections

[akib1689]

Discussed in #163

_{Originally posted by akib1689 on August 29, 2024}

---

I don't know if I'm missing something or not. It would be great if we could hide/include some of the sections from the YAML file.

My Use Case:

I apply for 2-3 roles, and each time I need to manually comment/uncomment the relevant portion of the YAML file. It would be very useful if we had something like a tag in each item.

Note

Each section will have some tags. For example, one of my skill rows should be included for DevOps-related jobs but not for developer-related jobs. It would be really helpful to set a match tag from the command line, say "devops," and each node that has the tag "devops" would be included in that particular render of the CV. By default, it would include all the contents.

The implementation can be flexible. But here I'm providing one way to implement:

• Each element in our yaml file will have an optional field named tag
• This tag will be an array of strings.
• Every child element will have parents tag nested format unless they choose to ignore it. one liner currently has one line string then have 2 things say content, tag
• Then in cli will have some command line argument say match-tag or include-tag to include only those nodes that has the that tag attached to them.

[akib1689]

I think we should discuss how do implement this section. Here is my proposal:

• Each of the entry types in render cv should have an optional field named label.
• The sections are pre defined. or We can also make the whole section tag able like this. Then we can include whole section by that label. For my case It would be say publications. For job seeking I don't like to include publications section. I need it only for university application.
• Contrary to the second point, we might have a business logic that is if the entry of any of the section becomes 0, Then don't include the section. Either one is fine for me.

rendercv_settings:
  cli_options: # might be called render options also
    dont_generate_png: true
    # ... other cli options to implement
  versions:
    # array of different version
    - label1:
      include:
        labels: label1  # parses all the contents and its sub contents labled devops only.

[sinaatalay]

The cv field of the YAML input file should be used only for content-writing purposes. Whatever is in there should be the stuff that is meant to be printed in the PDF. What about something like this?

rendercv_settings:
  hidden_sections:
    - Publications

[akib1689]

Sorry, for not getting back to you, I would like this then:

rendercv_settings:
  versions:
    - devops:
      - experience.exp1
      - experience.exp2
    - research:
      - experience.exp2
      - experience.exp3

Finally rendercv render --version devops