Remove Lux dependency inside LuxletterLink middleware #233
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks good to me so far. Did you check if identification is still working with the changes if you open a link in a newsletter? |
|
@einpraegsam Yes, I just tested it again using the Luxletter development setup and the |
|
Just for a doublecheck to prevent failures: If an unknown user on the website opens a link in a newsletter (even if the link points to an external URL like google), LUX now recognize the User and the User is identified (with email)? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Once in2code-de/lux#67 is merged, this PR can be merged as well, removing the dependency on Lux inside the
LuxletterLinkmiddleware.Fixes #94