Problem/Motivation

Migrate multilingual data from D6 and D7.

Proposed resolution

D6 migration and much of D7 is working so use those migrations, and their plugins as models for these migrations. It is preferred to improve the existing destination plugins instead of creating new ones.

Remaining tasks

Because D6 is nearing end of life, the D6 multilingual migrations are the highest priority as shown in the list below.

Top Priority

High priority - remaining content migrations

• #2754493: D6 synchronized field settings aren't migrated properly

Multilingual taxonomies / content migrations

• #2746541: Migrate D6 and D7 node revision translations to D8
• #2979964: Migrate translations for D7 i18n taxonomy 'localized' terms
• #2859297: Migrate taxonomy term references for D6 Node translations
• #2979966: Migrate D7 i18n taxonomy term language

Comments

• #2981393: Migrate D6 comment type language settings
• #3024460: Migrate D7 comment type language settings

Medium Priority

• #2979970: Migrate D7 vocabulary language settings
• #2980551: Errors When Migrating Books From Multilingual Drupal 7

Low Priority

• #3008028: Migrate D7 i18n menu links
• #3008029: Migrate D7 i18n CCK field option translations
• #3008030: Migrate D7 i18n fields label and description

Nice to haves

• #2746517: Automatically derive auxiliary migrations

Problem/Motivation

Using DatabaseStorageExpirable:setWithExpireIfNotExists on expired keys is not setting a new element.

Proposed resolution

When calling DatabaseStorageExpirable:setWithExpireIfNotExists on an expired key the new value should be set.

Remaining tasks

User interface changes

none

API changes

none

Data model changes

none

Release notes snippet

Problem/Motivation

This D7 migration has been move out of #2981393: Migrate D6 comment type language settings because the D7 fixture is broken and needs to be fixed before work continues.

Postponed on #3024459: Fix D7 test fixture

In #2981392: Comment migration corrupts data with multilingual sites we found out that the comment type language settings are not migrated sensibly when the source content type has multilingual support enabled.

Migrations generate one comment type for each Drupal 7 content type (except Forum which uses the hard coded comment_forum). The D8 comment type has a default language for new comments, see the screenshot below.

Currently we leave the default language (for new comments created in D8) to site default language. We also do not show the language selector for comments so that users could change the comment language when they are creating / editing the comments.

Proposed resolution

1. If the Drupal 7 content type has multilingual support 'disabled'.
Drupal 7 fixture: book.

• 'Default language' setting of the comment type: 'Site default'.
• 'Show language selector' setting of the comment type: disabled.
• 'Enable translation' setting of the comment type: disabled.

2. If the Drupal 7 content type has multilingual support 'enabled'.
Drupal 7 fixture: Page.

This means that the nodes can have a language code but the different nodes cannot be linked as translations of each other.

• 'Default language': 'Interface text language selected for page' instead of 'Site default'.
• 'Show language selector': enabled. This way the D8 user can see what the language of the new comments will be.
• 'Enable translation': disabled. This is because the comments in D7 are independent i.e. the comments are not translations of each other.

3. If the Drupal 7 content type has multilingual support 'Enabled, with translation'.
Drupal 7 fixture: article and blog.

This means that the nodes can have a language code and the nodes with different language codes can be linked as translations of each other. The different node language versions will have their independent comments i.e. the comments are not translations of each other.

• 'Default language': 'Interface text language selected for page' instead of 'Site default'.
• 'Show language selector': enabled. This way the D8 user can see what the language of the new comments will be.
• 'Enable translation': disabled. This is because the comments in D7 are independent i.e. the comments are not translations of each other.

4. If the Drupal 7 content type has multilingual support as 'Enabled, with field translation'.
Drupal 7 fixture: test_content_type.

• 'Default language': 'Interface text language selected for page' instead of 'Site default'.
• 'Show language selector': enabled. This way the D8 user can see what the language of the new comments will be.
• 'Enable translation': Depends on the Entity Translation settings in Drupal 7 (admin/config/regional/entity_translation). If the 'Translatable Entity Types' include Comments, then it means that actual comments entities can be translated and D8 'Enable translation' should be enabled. Note: D7-D8 Entity Translation settings were handled in #2073467: Migrate Drupal 7 Entity Translation settings to Drupal 8 and this works correctly at the moment.

Remaining tasks

1. Patch
2. Review and test
3. Commit

User interface changes

Enables the comment language selector + changes the default comment language for multilingual sites.

API changes

None.

Data model changes

None.

Hi,

In my project, I have a view with an exposed form style : value required.
When I load the view page, there are not result, it's ok.
But, if I submit it with empty values, there are results.

I will upload a path soon.

Thanks for your responses.

Problem/Motivation

Set AccessResult::forbidden if the user hasn't the permission to edit his username.

Proposed resolution

See Patch.

Remaining tasks

Review patch.

User interface changes

None

API changes

None

Data model changes

None

An instruction on /admin/modules reads:

Download additional contributed modules to extend your site's functionality.

It might better read:

Download additional contributed modules to extend your site's functionality. Or upload a custom module from your computer network.

Problem/Motivation

This code does not work:

    $query = db_select('table_a', 'a');
    $join_condition = db_and();
    foreach ($fields as $field) {
      $field = db_escape_field($field);
      $join_condition->where("a.$field = b.$field");
    }
    $query->innerJoin('table_b', 'b', $join_condition);

The reason is that the condition is not compiled, and thus converting the query to string breaks.

Proposed resolution

Fix it

Remaining tasks

Reviews

User interface changes

None

API changes

None

Data model changes

None

I have a simple question:
Why does the update.php script not perform entity updates? You need admin access for update.php or to run drush entity-updates, so what is the reason?

Problem/Motivation

#2796173: Add experimental Field Layout module to allow entity view/form modes to switch between layouts adds an experimental module that extends and alters the EntityDisplay entity classes and forms.

It provides no additional paradigms or functionality other than enhancing the existing UI.

Proposed resolution

Once the module is approaching a stable release, merge it directly into those core classes instead of having an optional module, even one in the Standard profile.

Remaining tasks

N/A

User interface changes

N/A

API changes

Added EntityDisplayInterface::getDefaultRegion()
Added EntityViewDisplayInterface::getFieldFromBuild()
Added EntityViewDisplayInterface::setFieldOnBuild()

Data model changes

entity_view_display and enitty_form_display both get a layout_id (string) and layout_settings (array)

Problem/Motivation

In terms of interaction, file fields could be a lot more accessible. The style guide proposes both a new appearance and a new interaction design.

Proposed resolution

1. Files can be added from the local filesystem using drag-and-drop, or using the traditional click-browse-attach workflow (which hands the action off to the OS and back)
2. Files upload automatically once added by dropping or browsing.
3. Uploaded files provide a preview where possible (images) or a file-type-specific icon where not.
4. File fields with multiple attachments use progressive disclosure to reveal each additional slot in turn. They should support dropping multiple files onto a single dropzone to upload multiple files at once.
5. The “Browse Library” functionality is speculative at this time, but designed to accommodate contrib.

An important reason to encapsulate much of this functionality, is that it tends to scale much better amongst many items and especially if placed between forms it can serve as a clear visual landmark.

Aspects of proposed design postponed to follow-ups

• #2863846: File Field design update progress bar
• #2863808: File Field design update mobile specific table issue

Test Pages

• A file field will have to be created and add to an existing content type

Related Issues

View all styleguide issues

Screenshots (patch #158)

Single file/image fields

Single file/image fields (RTL)

Single file/image fields (No JS)

Multi file/image fields

Multi file/image fields (RTL)

Multi file/image fields (No JS)

Default image

Default image (No JS)

Problem/Motivation

Tabledrag library has a button to swap between draggable handles, and numeric weight fields, which is important for assistive tech users (screen readers, speech control) and keyboard-only users. The button has a clear label, so that's good.

However it also has a title attribute, which provides a slightly more verbose explanation of what the button is for. The trouble is, this title attribute is basically useless. It can only be perceived by sighted mouse users (i.e. hover-capable pointers). More importantly, the title attribute can't be perceived by the intended audience - people who need to use the row weights feature. The title attribute is not available to sighted keyboard users, speech control users, or (most) screen reader users. When the button element has text content (like this one does) the title attribute is not supposed to be used when calculating the button's accessible name for assistive technology. Screen magnifier users with a mouse can trigger it, but it's a long title which may not fit in their magnifier viewport.

Background reading: Using the HTML title attribute.

Drupal has a lot of unnecessary title attributes, and it's something we have been called out for in the wider accessibility community (see Tenon Research first glimpse: The best & worst of content management systems).

Note also:

• We have another variant of this in MediaLibraryWidget (which says "media items" instead of rows).
• The behaviour of this button is documented in System module's hook_help. This can stay, and we'll probably also document it with the help_topics, once #2920309: Add experimental module for Help Topics lands.

Proposed resolution

Remove the title attribute from the "show/hide row weights" button.
Also remove the similar title attribute from MediaLibraryWidget.

Remaining tasks

Patch to remove the title attribute from these buttons:

• Update tabledrag.es6.js, and re-compile the JS in tabledrag.js.
• Update MediaLibraryWidget.php

Does this affect any tests? The title string appears in core/modules/migrate_drupal/tests/fixtures/drupal7.php - is this relevant?

User interface changes

Remove some title attributes which are of very little use, and cannot be perceived by the intended audience.
Removes a couple of translatable strings, which are no longer used.

I'm using config_installer to install. Almost at the end of the installation, I get the following fatal error. I previously applied patch 1356276-302, but I don't think this is related. It started happening after upgrading core to 8.3.0. The install does not finish correctly (the site has no admin user set). Any help or workaround is appreciated.

~/p/n/n/d/bin (master ⚡☡=) ./drush site-install config_installer config_installer_sync_configure_form.sync_directory=/var/www/drupal/config/sync --verbose --db-url=mysql://root:xxx@db/drupal --account-name=admin --account-pass=xxx -y
Executing: mysql --defaults-extra-file=/tmp/drush_IucryR --database=drupal --host=db --silent  < /tmp/drush_4Sag50 > /dev/null
You are about to DROP all tables in your 'drupal' database. Do you want to continue? (y/n): y
Sites directory /var/www/drupal/web/sites/default already exists -      [notice]
proceeding.
Executing: mysql --defaults-extra-file=/tmp/drush_mYQQIy --database=drupal --host=db --silent  < /tmp/drush_nu5C8H > /dev/null
Executing: mysql --defaults-extra-file=/tmp/drush_hGpyVf --database=drupal --host=db --silent  < /tmp/drush_vyJbkp
Executing: mysql --defaults-extra-file=/tmp/drush_YotAaX --database=drupal --host=db --silent  < /tmp/drush_S0z3x6
Starting Drupal installation. This takes a while. Consider using the        [ok]
--notify global option.
Error: Call to a member function getThirdPartySetting() on null in /var/www/drupal/web/core/modules/content_translation/src/ContentTranslationManager.php on line 98 #0 /var/www/drupal/web/core/modules/content_translation/content_translation.module(166): Drupal\content_translation\ContentTranslationManager->isEnabled('media', '')
#1 /var/www/drupal/web/core/lib/Drupal/Core/Extension/ModuleHandler.php(501): content_translation_entity_bundle_info_alter(Array, NULL, NULL)
#2 /var/www/drupal/web/core/lib/Drupal/Core/Entity/EntityTypeBundleInfo.php(110): Drupal\Core\Extension\ModuleHandler->alter('entity_bundle_i...', Array)
#3 /var/www/drupal/web/core/lib/Drupal/Core/Entity/EntityTypeBundleInfo.php(80): Drupal\Core\Entity\EntityTypeBundleInfo->getAllBundleInfo()
#4 /var/www/drupal/web/core/lib/Drupal/Core/Entity/Plugin/DataType/Deriver/EntityDeriver.php(95): Drupal\Core\Entity\EntityTypeBundleInfo->getBundleInfo('block')
#5 /var/www/drupal/web/core/lib/Drupal/Component/Plugin/Discovery/DerivativeDiscoveryDecorator.php(101): Drupal\Core\Entity\Plugin\DataType\Deriver\EntityDeriver->getDerivativeDefinitions(Array)
#6 /var/www/drupal/web/core/lib/Drupal/Component/Plugin/Discovery/DerivativeDiscoveryDecorator.php(87): Drupal\Component\Plugin\Discovery\DerivativeDiscoveryDecorator->getDerivatives(Array)
#7 /var/www/drupal/web/core/lib/Drupal/Core/Plugin/DefaultPluginManager.php(283): Drupal\Component\Plugin\Discovery\DerivativeDiscoveryDecorator->getDefinitions()
#8 /var/www/drupal/web/core/lib/Drupal/Core/Plugin/DefaultPluginManager.php(174): Drupal\Core\Plugin\DefaultPluginManager->findDefinitions()
#9 /var/www/drupal/web/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryCachedTrait.php(22): Drupal\Core\Plugin\DefaultPluginManager->getDefinitions()
#10 /var/www/drupal/web/core/lib/Drupal/Core/TypedData/DataDefinition.php(193): Drupal\Core\Plugin\DefaultPluginManager->getDefinition('field_item:stri...')
#11 /var/www/drupal/web/core/lib/Drupal/Core/Field/BaseFieldDefinition.php(566): Drupal\Core\TypedData\DataDefinition->getClass()
#12 /var/www/drupal/web/core/lib/Drupal/Core/Field/BaseFieldDefinition.php(555): Drupal\Core\Field\BaseFieldDefinition->getFieldItemClass()
#13 /var/www/drupal/web/core/lib/Drupal/Core/Field/BaseFieldDefinition.php(485): Drupal\Core\Field\BaseFieldDefinition->getMainPropertyName()
#14 /var/www/drupal/web/modules/contrib/media_entity/src/Entity/Media.php(309): Drupal\Core\Field\BaseFieldDefinition->setDefaultValue('')
#15 /var/www/drupal/web/core/lib/Drupal/Core/Entity/EntityFieldManager.php(204): Drupal\media_entity\Entity\Media::baseFieldDefinitions(Object(Drupal\Core\Entity\ContentEntityType))
#16 /var/www/drupal/web/core/lib/Drupal/Core/Entity/EntityFieldManager.php(171): Drupal\Core\Entity\EntityFieldManager->buildBaseFieldDefinitions('media')
#17 /var/www/drupal/web/core/lib/Drupal/Core/Entity/EntityFieldManager.php(394): Drupal\Core\Entity\EntityFieldManager->getBaseFieldDefinitions('media')
#18 /var/www/drupal/web/core/lib/Drupal/Core/Entity/EntityManager.php(154): Drupal\Core\Entity\EntityFieldManager->getFieldStorageDefinitions('media')
#19 /var/www/drupal/web/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php(282): Drupal\Core\Entity\EntityManager->getFieldStorageDefinitions('media')
#20 /var/www/drupal/web/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php(1411): Drupal\Core\Entity\Sql\SqlContentEntityStorage->getTableMapping()
#21 /var/www/drupal/web/core/lib/Drupal/Core/Field/FieldStorageDefinitionListener.php(74): Drupal\Core\Entity\Sql\SqlContentEntityStorage->onFieldStorageDefinitionCreate(Object(Drupal\Core\Field\BaseFieldDefinition))
#22 /var/www/drupal/web/core/lib/Drupal/Core/Entity/EntityManager.php(411): Drupal\Core\Field\FieldStorageDefinitionListener->onFieldStorageDefinitionCreate(Object(Drupal\Core\Field\BaseFieldDefinition))
#23 /var/www/drupal/web/core/lib/Drupal/Core/Entity/EntityDefinitionUpdateManager.php(169): Drupal\Core\Entity\EntityManager->onFieldStorageDefinitionCreate(Object(Drupal\Core\Field\BaseFieldDefinition))
#24 /var/www/drupal/web/core/modules/content_translation/src/ContentTranslationUpdatesManager.php(63): Drupal\Core\Entity\EntityDefinitionUpdateManager->installFieldStorageDefinition('content_transla...', 'media', 'content_transla...', Object(Drupal\Core\Field\BaseFieldDefinition))
#25 /var/www/drupal/web/core/modules/content_translation/src/ContentTranslationUpdatesManager.php(77): Drupal\content_translation\ContentTranslationUpdatesManager->updateDefinitions(Array)
#26 /var/www/drupal/web/core/lib/Drupal/Component/EventDispatcher/ContainerAwareEventDispatcher.php(111): Drupal\content_translation\ContentTranslationUpdatesManager->onConfigImporterImport(Object(Drupal\Core\Config\ConfigImporterEvent), 'config.importer...', Object(Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher))
#27 /var/www/drupal/web/core/lib/Drupal/Core/Config/ConfigImporter.php(644): Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch('config.importer...', Object(Drupal\Core\Config\ConfigImporterEvent))
#28 /var/www/drupal/web/core/lib/Drupal/Core/Config/ConfigImporter.php(488): Drupal\Core\Config\ConfigImporter->finish(Array)
#29 /var/www/drupal/web/profiles/contrib/config_installer/config_installer.profile(139): Drupal\Core\Config\ConfigImporter->doSyncStep('finish', Array)
#30 /var/www/drupal/web/core/includes/batch.inc(252): config_install_batch_process(Object(Drupal\Core\Config\ConfigImporter), 'finish', Array)
#31 /var/www/drupal/web/core/includes/form.inc(874): _batch_process()
#32 /var/www/drupal/web/core/includes/install.core.inc(625): batch_process(Object(Drupal\Core\Url), Object(Drupal\Core\Url))
#33 /var/www/drupal/web/core/includes/install.core.inc(546): install_run_task(Array, Array)
#34 /var/www/drupal/web/core/includes/install.core.inc(117): install_run_tasks(Array)
#35 /var/www/drupal/vendor/drush/drush/includes/drush.inc(726): install_drupal(Object(Composer\Autoload\ClassLoader), Array)
#36 /var/www/drupal/vendor/drush/drush/includes/drush.inc(711): drush_call_user_func_array('install_drupal', Array)
#37 /var/www/drupal/vendor/drush/drush/commands/core/drupal/site_install.inc(84): drush_op('install_drupal', Object(Composer\Autoload\ClassLoader), Array)
#38 /var/www/drupal/vendor/drush/drush/commands/core/site_install.drush.inc(254): drush_core_site_install_version('config_installe...', Array)
#39 /var/www/drupal/vendor/drush/drush/includes/command.inc(422): drush_core_site_install('config_installe...', 'config_installe...')
#40 /var/www/drupal/vendor/drush/drush/includes/command.inc(231): _drush_invoke_hooks(Array, Array)
#41 /var/www/drupal/vendor/drush/drush/includes/command.inc(199): drush_command('config_installe...', 'config_installe...')
#42 /var/www/drupal/vendor/drush/drush/lib/Drush/Boot/BaseBoot.php(67): drush_dispatch(Array)
#43 /var/www/drupal/vendor/drush/drush/includes/preflight.inc(66): Drush\Boot\BaseBoot->bootstrap_and_dispatch()
#44 /var/www/drupal/vendor/drush/drush/drush.php(12): drush_main()
#45 {main}
Drush command terminated abnormally due to an unrecoverable error.       [error]
Error: Call to a member function getThirdPartySetting() on null in Drupal\content_translation\ContentTranslationManager->isEnabled() (line 98 of /var/www/drupal/web/core/modules/content_translation/src/ContentTranslationManager.php).

Problem/Motivation

There is ENTITY_TYPE_list cache tag and it is being invalidated very often. For example, if we have 20 different content types and created views page to display the list of content for each type, then whenever editor adds/edits/deletes one of the content - all 20 views pages will be invalidated BUT only related should be invalidated, others still have no changes. So, it means that on current sites if somebody changes something then Drupal will clear cache for almost the entire website.

Proposed resolution

Add bundle specific list cache tags - ENTITY_TYPE_list:BUNDLE
For example:

• If the node listing is empty then add node_list tag.
• If the node listing is only showing single bundle(page) then add node_list:page tag.
• If the node listing is showing more than one bundle then add node_list tag.

Also:

• Rename getListCacheTags to getListCacheTagsToInvalidate.
• Add getListCacheTags in the follow up where we determine bundle specific cache tag based on query object.

so that listing pages can add bundle specific list cache tags or generic list cache tags

Remaining tasks

1. Write tests as per #93.5
2. Create follow-ups.
3. Create change record.

Original report by [effulgentsia]

Follow up from #1712456: How to leverage cache tags in Views.

Two problems:

1. That issue changed EntityViewBuilder::resetCache() from just clearing the TYPE:ID tag to also clearing the TYPE_view_BUNDLE tag. However, what is the meaning of this tag? What does it mean to "view" a bundle? #1712456-50: How to leverage cache tags in Views says "Say you save settings for one node type, it would invalidate caches for every node on the system?!", so ok, if the intent of this tag is to clear caches upon a change to the settings of a bundle, then why is it being cleared upon the saving of a single entity, which is when EntityViewBuilder::resetCache() is called? OTOH, the same comment also says We need a way like this to invalidate 'lists' containing this entity type. This and 'view' could be similar though I guess.. Hm, if the 'view' here refers to lists (where Views module is the most common list generator) rather than to the 'view' in the sense of EntityViewBuilder, then let's rename this tag to 'list' instead. If we then also want a per-bundle 'view' tag for clearing when bundle settings change in a way that would affect their display, then that's what we should use 'view_BUNDLE' for, but then clear it only where bundle settings are managed (e.g., EntityDisplay) rather than in EntityViewBuilder::resetCache().
2. If we do rename this to TYPE_list_BUNDLE, then how should we handle Views that are cross-bundle? For example, currently in HEAD, if I enable tag-based caching on the front page View, then visit the front page at a time when only Article nodes are promoted to the front page, then I add a Page node and promote it, it doesn't show up on my front page until I manually clear caches. Perhaps we need a non-bundle-specific TYPE_list tag as well, and add that to all cross-bundle Views, but not to Views and EFQ listings that we know are bundle-specific?

The documentation for hook_link_alter is in core/lib/Drupal/Core/Menu/menu.api.php.
This give the impression that this is only for menu links. When actually the hook is invoked in \Drupal\Core\Utility\LinkGenerator::generate

Problem/Motivation

Our CSS coding standards say https://www.drupal.org/docs/develop/standards/css/css-formatting-guideli... so let's enforce it using styleint.

This came up in #2992635: Pass all Umami CSS files through CSScomb to Ensure they Follow our CSS Coding Standards

Proposed resolution

Use https://stylelint.io/user-guide/rules/string-quotes/

Remaining tasks

User interface changes

None

API changes

None

Data model changes

None

Release notes snippet

None

API page: https://api.drupal.org/api/drupal/core%21core.api.php/group/testing/8.6.x

At the bottom of the page, in Class list, below the "KernelTestBase Deprecated core/modules/simpletest/src/KernelTestBase.php Base class for functional integration tests. " should be added "KernelTestBase core/tests/Drupal/KernelTests/KernelTestBase.php Base class for functional integration tests."

So, the Class list should look like:
.....
Classes
.....
BrowserTestBase Deprecated core/modules/simpletest/src/BrowserTestBase.php Provides a test case for functional Drupal tests.
BrowserTestBase core/tests/Drupal/Tests/BrowserTestBase.php Provides a test case for functional Drupal tests.
KernelTestBase Deprecated core/modules/simpletest/src/KernelTestBase.php Base class for functional integration tests.
KernelTestBase core/tests/Drupal/KernelTests/KernelTestBase.php Base class for functional integration tests.
UnitTestCase core/tests/Drupal/Tests/UnitTestCase.php Provides a base class and helpers for Drupal unit tests.
WebTestBase core/modules/simpletest/src/WebTestBase.php Test case for typical Drupal tests.
.....

When I go to taxonomy pages as an anonymous user that used to be accessible pre 8.6 release is now showing 'Page not found'.

I have had to install the Taxonomy Access Fix module just so I can show these pages to anonymous users.

I have not seen anything in permissions or elsewhere to fix this issue and it seems nothing is coming up on google either.

This has happened to all my sites at 8.6 update.

Problem/Motivation

In #2842431: [policy] Remove PHP 5.5, 5.6 support in Drupal 8.7 and #2927344: Specifically warn about end dates for PHP support for old versions, we decided to end PHP 5.5 and 5.6 support after determining that most hosting providers had PHP 7.0+ available. However, to better support the community for this upgrade, we also want to track which hosts do not yet support PHP 7.0+. Tracking the availability of PHP 7.1+ will also help us make informed decisions about how long that version is supported.

Proposed resolution

Track which hosting providers do and don't support PHP 7.0+.

PHP 7 already supported

Unclear or unknown

(None ATM)

Problem/Motivation

Run yarn upgrade stylelint

Proposed resolution

We should be on our latest version of this - it fixes a rule.

Remaining tasks

User interface changes

None

API changes

None

Data model changes

None

Release notes snippet

None

Views not updating the following pending updates.
views module
•Add placeholder settings to string or numeric filters.
•Rebuild caches to ensure schema changes are read in.
•Fix table names for revision metadata fields. @see https:www.drupal.orgnode2831499
•Fix cache max age for table displays.
• Include views data table provider in views dependencies.

The error afterwards is this:

views module
Update filter_placeholder_text
Failed: InvalidArgumentException: The configuration property display.default.display_options.filters.order_id.value.min doesn't exist. in Drupal\Core\Config\Schema\ArrayElement->get() (line 76 of /home/domain/public_html/core/lib/Drupal/Core/Config/Schema/ArrayElement.php).

Everything seems to work fine but I'm unable to get rid of these pending updates.
Any help on this issue? Thanks