Add relative_source_path attribute to content

[bryanbrattlof]

I wanted to see what the consensus is for adding a relative_source_path attribute to the Content object.

@egberts, and I in #2484 where talking about using an unpublished way to add a relative path as a comment into the generated html for page and article for better debugging using continuous integration pipelines like gitlab-ci.

I also saw the PR (#2416) wanted the ability to generate urls to edit his content in github, but it seems like it died there.

Hope everyone's weekend it going well.

[avaris]

This doesn't need to be a property.

[bryanbrattlof]

Thanks @avaris,

I switched to setting relative_source_path after source_path is set during the creation of the Content object.

I also fixed a typo in the page's attribute table in the documentation that I missed.

Although, I'm having trouble figuring out if this is something others will want vs something that I want. If I'm the only one I can use the content_init signal to attach this for my own use. So feel free to tell me to push off and I'll close this. :)

Thanks again

[avaris]

For debugging purposes, I see very little benefit in this over source_path but one can use this to have a link to the source. So, I'm not opposed to it.

[bryanbrattlof]

Sorry for the updates, I just now noticed how bad I am at spelling

[egberts]

Awesome!

[pedrohdz]

As much as I would love to see this change in sooner rather than later, there should be a unit test added. tests/test_contents.py seems like the correct place.

[bryanbrattlof]

Thanks @pedrohdz for the suggestion. I've added the tests. :)

[justinmayer]

Many thanks to @bryanbrattlof for the enhancement and to @avaris, @egberts, and @pedrohdz for reviewing. 🎉