You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Project.id is a hash that depends only onProject.tree (the path to the directory that contains the project source: the content, templates, models, assets, and other directories).
The id is used to construct the default output path and (hashed with other bits) the package cache path.
A given project source tree can be built with different project files (.lektorproject files). In that case, a different default output path should be used for each (project file, project tree) combination. This is not currently done.
The Project.id should probably depend on at least Project.project_file as well as Project.tree.
It should possibly include Project.themes and/or Project.name as well, since it is possible — programmatically, at least — to construct projects which vary in those attributes.
The CLI appears to always set themes from the project file settings, and gets name either from the project file or by DWIMming it from the basename of the project file or the project tree. So perhaps basing the id only on tree and project_file is sufficient?
The text was updated successfully, but these errors were encountered:
Currently,
Project.id
is a hash that depends only onProject.tree
(the path to the directory that contains the project source: thecontent
,templates
,models
,assets
, and other directories).The
id
is used to construct the default output path and (hashed with other bits) the package cache path.A given project source tree can be built with different project files (
.lektorproject
files). In that case, a different default output path should be used for each (project file, project tree) combination. This is not currently done.The
Project.id
should probably depend on at leastProject.project_file
as well asProject.tree
.It should possibly include
Project.themes
and/orProject.name
as well, since it is possible — programmatically, at least — to construct projects which vary in those attributes.The CLI appears to always set
themes
from the project file settings, and getsname
either from the project file or by DWIMming it from the basename of the project file or the project tree. So perhaps basing theid
only ontree
andproject_file
is sufficient?The text was updated successfully, but these errors were encountered: