Jaipur, India
Account created on 22 December 2011, over 12 years ago
  • Staff Software Engineer in the Drupal Acceleration Team at Acquia 
#

Merge Requests

More

Recent comments

🇮🇳India narendraR Jaipur, India

😬 Forgot to change status while cloning

🇮🇳India narendraR Jaipur, India

Marked NR for initial review.

🇮🇳India narendraR Jaipur, India

I am not sure, what should be written on config save:

    $config_name = $event->getConfig()->getName();
    if ($config_name === 'core.menu.static_menu_link_overrides') {
      // What needs to be done here?
    }
🇮🇳India narendraR Jaipur, India

Changes look good to me. Moving to RTBC

🇮🇳India narendraR Jaipur, India

sdc_tags.settings in above list does not seems to be part of core.

🇮🇳India narendraR Jaipur, India

MR needs to be marked ready for review. Overall looks good to me.
Added one feedback to address.

🇮🇳India narendraR Jaipur, India

narendraR made their first commit to this issue’s fork.

🇮🇳India narendraR Jaipur, India

Not sure what next should be done in this issue, hence marking it for another review.

🇮🇳India narendraR Jaipur, India

Tests passing, changes looks good to me. Moving to RTBC.

🇮🇳India narendraR Jaipur, India

I tried to add a test in previous commit, which should fail, but it is not failing. 🤷‍♂️

🇮🇳India narendraR Jaipur, India

narendraR made their first commit to this issue’s fork.

🇮🇳India narendraR Jaipur, India

narendraR made their first commit to this issue’s fork.

🇮🇳India narendraR Jaipur, India

Sorry, but I don't get #17. As per #13, Only lowercase alphanumeric characters and underscores are allowed, and only lowercase letters and underscore are allowed as the first character.

🇮🇳India narendraR Jaipur, India

Adding _ in the end of field prefix failed core/modules/field_ui/tests/src/Functional/ManageFieldsFunctionalTest::testFieldPrefix. Either that test needs to be adjusted as per new validation rule or _ in the end of field prefix is not necessary. For now, I am removing the _ from field prefix end.

🇮🇳India narendraR Jaipur, India

narendraR changed the visibility of the branch 3437325-add-validation-constraints to hidden.

🇮🇳India narendraR Jaipur, India

I think that is already handled in core/modules/field/src/Entity/FieldStorageConfig::__construct

if (!preg_match('/^[_a-z]+[_a-z0-9]*$/', $values['field_name'])) {
throw new FieldException("Attempt to create a field storage {$values['field_name']} with invalid characters. Only lowercase alphanumeric characters and underscores are allowed, and only lowercase letters and underscore are allowed as the first character");
}

🇮🇳India narendraR Jaipur, India

narendraR made their first commit to this issue’s fork.

🇮🇳India narendraR Jaipur, India

Thanks for the follow-up. One test scenario which is missing here is "Imported node with owned by user that does not exist".
Rest LGTM.

🇮🇳India narendraR Jaipur, India

A follow-up documentation issue might be required to help understand how content can be created/imported using recipe system.

🇮🇳India narendraR Jaipur, India

A follow-up documentation issue is needed to include this change. Rest looks good to me.

🇮🇳India narendraR Jaipur, India

I think follow up needs to be created to update the recipe documentation to include this feature.

🇮🇳India narendraR Jaipur, India

Re #7, Test started failing after reverting the changes.

Production build 0.67.2 2024