docs: add all possible PageResource attributes to spec
Regaez opened this issue · 1 comments
Regaez commented
At the moment, only the attributes which are included by default (api.yaml specifies limited fields) are shown in the API specification file. The specification should be updated to include all possible attributes.
This way, people will know which values are valid to add to the fields array within the /pages configuration object.
Regaez commented
We should also update the blueprints.yaml file to include all possible attributes for the endpoints./pages.get.fields field options.