Skip to content

Pattern config entities simplified ui#115

Merged
Berdir merged 76 commits into8.x-1.xfrom
pattern-config-entities-simplified-ui
Jan 1, 2016
Merged

Pattern config entities simplified ui#115
Berdir merged 76 commits into8.x-1.xfrom
pattern-config-entities-simplified-ui

Conversation

@Berdir
Copy link
Member

@Berdir Berdir commented Dec 31, 2015

No description provided.

EclipseGc and others added 30 commits October 19, 2015 18:09
…e PathautoWidgets to work with the method changes and special casing taxonomy_term entity token logic since it does not properly conform to the rest of core.
…tity interface and implemented them. Also provided preSave and postLoad overrides for the pathauto pattern entity in order to properly handle expanding and contracting relationship settings.
…n order to populate with appropriate tokens from available relationships.
juampynr and others added 17 commits December 19, 2015 19:21
Now that patterns are config entities, the UI tests were failing.
On top of that, the Add form has an Ajax interaction to select the
pattern type, which is covered too.
* Remove obsolete references.
* Adjust functions that changed.
Fix form redirection after bulk delete
The Drupal 7 version of Pathauto had logic to evaluate a bundle
being deleted and see if there were matching patterns that had
to be removed as well. This is something that we don't see a
real need for. Instead, we will let the site administrator
to clean up patterns manually after removing a bundle.
Don't expect Pathauto to delete patterns on bundle deletion
Plus:
* Small improvements suggested by Berdir.
* Make sure that the langcode is a valid machine-name. For example,
  Chinese traditional has a langcode zh-hant, which is not valid for a
  machine name.
[#10] Port patterns from config objects to config entities
@juampynr
Copy link

👹

How can I help peer reviewing this?

@Berdir
Copy link
Member Author

Berdir commented Jan 1, 2016

Currently going through and doing some cleanup. Will possibly merge this soon.

Note: I am using the new token entity mapper service. Make sure you are using the latest token 8.x-1.x.

@Berdir
Copy link
Member Author

Berdir commented Jan 1, 2016

Ok, going to merge this now!

A few follow-ups to work on:

  • Make pathauto_entity_base_field_info() configurable. Expose a list of checkboxes for each type. Ticking the checkbox should expose that base field for the selected entity types. In case a base field already exists and is not defined by us (e.g. node), it should be checked by default and be disabled. This in turn will then automatically expose a alias type plugin. At this point, we'll have achieved the goal of fully generic and automated integration with any entity type.
  • Decide about removing or keeping hook_pathauto_pattern_alter(), I'm considering to remove it, we can add it back if there is a use case.
  • Update and test forum related code
  • Introduce a method on pattern plugins to react to alias generation, so that we can move the condition code in updateEntityAlias() to a taxonomy term alias type plugin

Berdir added a commit that referenced this pull request Jan 1, 2016
@Berdir Berdir merged commit 749e06c into 8.x-1.x Jan 1, 2016
@juampynr
Copy link

juampynr commented Jan 1, 2016

👍 👍 👍 👍 👍 👍 👍 👍 👍

@balsama
Copy link

balsama commented Jan 1, 2016

Nice! HUGE step in the right direction. Thanks!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants