after added a theme component from a repo (a branch),
sometimes, may need to update the branch to try new development.
it will be very nice if could change it …
thanks !
The discussion revolves around the need to easily change the repository URL and branch of a theme component in a development environment. fbpbdmin suggests that being able to update the branch directly would simplify debugging and testing different versions of a theme component. jericson responds by recommending installing a new version of the component instead, which places it in the “Unused components” section, allowing for easy replacement and updates. This approach avoids the need to delete and reinstall, but requires managing the component versions and ensuring the correct one is used in the theme. fbpbdmin agrees that installing a new version is possible but acknowledges that changing the branch directly would be more convenient for debugging purposes.
after added a theme component from a repo (a branch),
sometimes, may need to update the branch to try new development.
it will be very nice if could change it …
thanks !
I think it’s better to install a new version of the theme component. It’ll complain about the name:
But you can change it:
The new version will start off in the “Unused components” section, so it’s easy to find.
From there you’d need to update which themes have the new version of the component. Be sure to remove the main branch version! All this will be easier to do on a new copy of the theme. Ideally your theme is on a repo too, but you can export it and import from the local machine in a pinch.
when debug a theme component, could switch to try different branches, if it allows to change it, it is easier. it takes more step to delete and install a new one… ![]()