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
May be we should use the config('view.paths'); to get views paths instead of setting it to the laravelViewsPath, so It's possible to get user's configured paths at runtime.
Add a view path before setting theme like following
app('view.finder')->addLocation($sourcePath);
Then try to set current theme by
Themes::set('one_theme')
now the above path lost. instead of using the addLocation method, we can add new path to view.paths config ,
app('config')->push('view.paths', $sourcePath);
clearly say we want to keep the path like statically configured view paths after setting theme.
The text was updated successfully, but these errors were encountered:
videni
changed the title
Allow to keep the view paths set at runtime when set theme
Allow to keep the view paths set at runtime when setting theme
Nov 11, 2022
videni
changed the title
Allow to keep the view paths set at runtime when setting theme
Allowed to keep the view paths added at runtime when setting theme
Nov 11, 2022
videni
changed the title
Allowed to keep the view paths added at runtime when setting theme
Allowed to keep the view paths added at runtime after setting theme
Nov 11, 2022
laravel-theme/src/Themes.php
Line 76 in b1efebe
May be we should use the
config('view.paths');
to get views paths instead of setting it to thelaravelViewsPath
, so It's possible to get user's configured paths at runtime.Add a view path before setting theme like following
Then try to set current theme by
now the above path lost. instead of using the
addLocation
method, we can add new path toview.paths
config ,clearly say we want to keep the path like statically configured view paths after setting theme.
The text was updated successfully, but these errors were encountered: