Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Improvement]: inconvenient namespace for datahub:graphql:rebuild-definitions command #489

Closed
jeykodev opened this issue Mar 7, 2022 · 3 comments

Comments

@jeykodev
Copy link

jeykodev commented Mar 7, 2022

Improvement description

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.

@kingjia90
Copy link
Contributor

@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.

@mcop1
Copy link
Contributor

mcop1 commented Oct 21, 2024

Deprecation is already there

*@deprecated Use Pimcore\Bundle\DataHubBundle\Command\Configuration\RebuildWorkspacesCommand instead.
+
>Note: The command ```datahub:graphql:rebuild-definitions ``` is marked as deprecated and will be removed in a future release.
, the command just needs to be removed with the next major version.

Therefore no need to change the old command, just use the new one.

@fashxp
Copy link
Member

fashxp commented Oct 21, 2024

see also #480

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants