- šØšSwitzerland berdir Switzerland
We have \Drupal\Core\Entity\SynchronizableInterface since 2018 which is exactly this.
- šŗšøUnited States smustgrave
Thank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
- š³š±Netherlands bbrala Netherlands
I've split two issues for the missing tests.
- š³š±Netherlands bbrala Netherlands
Although there is some missing test:
- The constraint MatchesOtherConfigValue needs tests
- The constraint NoEntitiesExistYetWithHigherCardinality needs tests
Our tests are green :x
The Needs Review Queue Bot ā tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide ā to find step-by-step guides for working with issues.
- š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
So glad to see this moving forward again! š¤
Also, I had to do this yesterday:
protected static $configSchemaCheckerExclusions = [ // @todo Core bug: this is missing config schema: ``type: field.storage_settings.uri` does not exist! This is being fixed in https://www.drupal.org/project/drupal/issues/3324140. 'field.storage.entity_test.test_required__file_uri', 'field.storage.entity_test.test_optional__file_uri', // @todo Core bug: this is missing config schema: ``type: field.storage_settings.uuid` does not exist! This is being fixed in https://www.drupal.org/project/drupal/issues/3324140. 'field.storage.entity_test.test_required__uuid', 'field.storage.entity_test.test_optional__uuid', ];
That's for XB over at š Provide visibility into which (core) field type props can be mapped into Content Type Templates vs not Active , fixing this would allow me to remove those exclusions!
- šŗšøUnited States tim.plunkett Philadelphia
With the move to Attributes, I think this is safe to close
- šŗšøUnited States smustgrave
Thank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
- šŗšøUnited States smustgrave
Thank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
- š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
This is not actionable until decisions are made with solid answers WRT the concerns I surfaced.
- š¬š§United Kingdom joachim
This is absolutely still relevant. There is no proper documentation on plugin types the way that there is for hooks.
Nobody has worked on it because it's a big undertaking.
- šŗšøUnited States smustgrave
Thank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
- š§šŖBelgium borisson_ Mechelen, š§šŖ
I think most problems with this should be resolved when we get #2414951 working. I think that means we can close this issue.
- š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
Not too sure what's causing those unrelated test failures!
Hm ā¦ me neither, but this seems like yet another case of https://www.drupal.org/project/gitlab_templates ā being wrong and running contrib module's test suites differently for non-maintainer-pushed commits than for maintainer-pushed commits š¬ (I wish I was kidding!)
Also: you're right, I misjudged, this is not a trivial move. š Thanks for removing the tag.
But ā¦ this issue is novice-like in the sense that you were able to do this without deep XB knowledge! š What do you think would be a more appropriate tag? š
- š¦šŗAustralia tinarey
I could replicate the issue. The problem is dependencies:
Running `npm ls @typescript-eslint/eslint-plugin` shows these:
@drupal/experience_builder@0.0.0 /Users/tina/Sites/PNX/drupal-contrib/experience_builder/ui āāā @typescript-eslint/eslint-plugin@8.26.0 āāā¬ eslint-config-react-app@7.0.1 ā āāā @typescript-eslint/eslint-plugin@5.62.0 ā āāā¬ eslint-plugin-jest@25.7.0 ā āāā @typescript-eslint/eslint-plugin@8.26.0 deduped invalid: "^4.0.0 || ^5.0.0" from node_modules/eslint-plugin-jest āāā¬ typescript-eslint@7.18.0 āāā @typescript-eslint/eslint-plugin@7.18.0
typescript-eslint can be updated (done in MR), but eslint-config-react-app doesn't have an update (yet? might be abandonned). I've added an override which seems to work (peerDependencies didn't work), but that may need a follow up task to remove when we can.
Otherwise we may be able to use eslint-plugin-react instead.I now get linting errors as expected:
...experience_builder/ui/src/hooks/useCopyPasteComponents.ts 65:14 warning 'err' is defined but never used @typescript-eslint/no-unused-vars ...experience_builder/ui/src/services/componentAndLayout.ts 55:18 warning 'err' is defined but never used @typescript-eslint/no-unused-vars
- First commit to issue fork.
- š¦šŗAustralia acbramley
Not too sure what's causing those unrelated test failures!
- š¦šŗAustralia acbramley
I would say this isn't so Novice, the tests are quite complicated. I had to:
1. Swap to standard profile
2. Modify cache tags in existing tests to match
3. Enable some new modules
4. Port over helper functionsLocally these tests are throwing a bunch of warnings but I'm testing out the ddev XB setup so it might be related to that.
- @acbramley opened merge request.
- First commit to issue fork.
- šŗšøUnited States smustgrave
Thank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
- šŗšøUnited States smustgrave
Thank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!