-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Avoid hardcoding WP Links inside Gutenberg #9637
Labels
[Type] Code Quality
Issues or PRs that relate to code quality
[Type] Enhancement
A suggestion for improvement.
Comments
youknowriad
added
[Type] Enhancement
A suggestion for improvement.
npm Packages
Related to npm packages
labels
Sep 5, 2018
4 tasks
youknowriad
added
the
[Type] Code Quality
Issues or PRs that relate to code quality
label
Feb 8, 2019
Is this issue still relevant? |
yes :) |
Alrighty. Let's keep it open..:) |
Possibly related: Maybe the links could be generated in the WP backend and only display when they're accessible via editor settings in JS? |
I think for the block editor package and agnostic packages, there's no hard coded links anymore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
[Type] Code Quality
Issues or PRs that relate to code quality
[Type] Enhancement
A suggestion for improvement.
We use links to target WP Admin pages inside Gutenberg packages
These links only work in WP context and the packages are meant to be context agnostic.
We need to find a way to add these links in an "augmented" manner. Keeping the packages WP links free.
The text was updated successfully, but these errors were encountered: