Skip to content
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

[REF] Separate contact tokens from 'tokenCompatSubscriber' #21626

Merged
merged 1 commit into from
Sep 27, 2021

Conversation

eileenmcnaughton
Copy link
Contributor

@eileenmcnaughton eileenmcnaughton commented Sep 26, 2021

Overview

[REF] Separate contact tokens from 'tokenCompatSubscriber'

This just moves code around - loads of testing - but it separates
the contact entity stuff from the 'compat' - presumably 'compatibility'
subscriber.

Before

The contact token code has been separated from the 'compat' code within the class but is still in the same class

After

Token code gets it's own special class

Technical Details

We should consider renaming 'tokenCompatSubscriber' as a follow up - even 'tokenCompatibilitySubscriber' would be better as it is less English-speaking centric (dictionary words can be looked up if you don't know them). It's really a TokenSmartyHandler these days

Comments

@civibot civibot bot added the master label Sep 26, 2021
@civibot
Copy link

civibot bot commented Sep 26, 2021

(Standard links)

@eileenmcnaughton
Copy link
Contributor Author

@colemanw this is why I wanted to hustle on the other - because I wanted to move code around. The tests I ran locally passed but there are a lot of tests in the full suite so in another 1.75 hours we will know...

@colemanw
Copy link
Member

Ok

This just moves code around - loads of testing - but it separates
the contact entity stuff from the 'compat' - presumably 'compatibility'
subscriber.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants