Make Page fields private about verless HOT 4 CLOSED

Even though the fields still are accessible from a technical perspective, making the fields private and creating getters and setters for them indicates that they're not intended to be used like the other fields, so this serves as a kind of documentation. Also, we mark those fields as subjects to change and un-stable for usage in templates, so the implementation and the value of these fields are completely up to verless. They're not even documented in the template reference. One of the advantages is that the internal implementation and usage can change at any time, and breaking backwards compatibility won't require a new major release.

This is because verless stores the related pages parsed from the Markdown in RelatedFQNs for example, but those are only the URIs for the pages and don't provide any value for a template. verless creates Pages from these URIs and puts them in Related, which should be used in templates instead.

from verless.

which fields exactly?

from verless.

RelatedFQNs and Hide.

from verless.

But if I add public getters and setters, the fields can be accessed the same as before. I don't understand the purpose of making it private if we then provide the same public access using public getters and setters... Am I missing something?

from verless.