Because resume publish performs an update into MongoDB, it actually merges what is published with the latest persistent state.
This can lead to difficulties in removing properties, sections, etc.
For example, publish a resume with a "volunteer" section, then publish it again without that section, and the "volunteer" section will still remain published -- as the version without it was just merged into the persistent one.
Because resume publish performs an update into MongoDB, it actually merges what is published with the latest persistent state. This can lead to difficulties in removing properties, sections, etc.
For example, publish a resume with a "volunteer" section, then publish it again without that section, and the "volunteer" section will still remain published -- as the version without it was just merged into the persistent one.