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
If you clone a solution with pac solution clone currently, any Power Pages components are listed by GUID in the powerpagecomponents directory. Has there been any consideration to add a switch similar to --processCanvasApps where the Power Pages sites can be expanded to the same structure as when using pac powerpages download?
This would simplify using source control for a solution with a Power Pages site, as currently if just the solution is in source control it's hard to get an overview of changes made in Power Pages, and having a separate repository for the Power Pages site can create worries about whether the two are in sync or not.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If you clone a solution with
pac solution clone
currently, any Power Pages components are listed by GUID in thepowerpagecomponents
directory. Has there been any consideration to add a switch similar to--processCanvasApps
where the Power Pages sites can be expanded to the same structure as when usingpac powerpages download
?This would simplify using source control for a solution with a Power Pages site, as currently if just the solution is in source control it's hard to get an overview of changes made in Power Pages, and having a separate repository for the Power Pages site can create worries about whether the two are in sync or not.
Beta Was this translation helpful? Give feedback.
All reactions