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
After changing my PIMCORE_WRITE_TARGET_DATA_HUB from symfony-config to settings-store (see Docs) I looked for a possibility to rebuild the definitions, so the configuration will be initial saved in the database instead of config files.
I've found the metioned command but it has the namespace graphql and since I'm using the Data Importer, I thought this will be not an option.
After that, I looked into the command and found out, that no additional checks for the specific configuration type graphql are implemented. At the end the command does rebuild every configuration type, not only graphql.
So I would suggest to remove the graphql namespace from the command and adapt the description and documentation.
If you guys agree, I can make a PR.
The text was updated successfully, but these errors were encountered:
@jeykodev Thank you for reporting, we would glad to see a PR about the change.
I have also got a tip that this change may need a BC Layer/Alias to avoid any BC Break, hope this would help you as well when making the PR.
Improvement description
After changing my
PIMCORE_WRITE_TARGET_DATA_HUB
fromsymfony-config
tosettings-store
(see Docs) I looked for a possibility to rebuild the definitions, so the configuration will be initial saved in the database instead of config files.I've found the metioned command but it has the namespace
graphql
and since I'm using the Data Importer, I thought this will be not an option.After that, I looked into the command and found out, that no additional checks for the specific configuration type
graphql
are implemented. At the end the command does rebuild every configuration type, not onlygraphql
.So I would suggest to remove the
graphql
namespace from the command and adapt the description and documentation.If you guys agree, I can make a PR.
The text was updated successfully, but these errors were encountered: