mirror of
https://github.com/tiennm99/java-design-patterns.git
synced 2026-05-14 08:58:26 +00:00
fix: Fix minor typos (#2619)
Signed-off-by: Marcel Ribeiro-Dantas <mribeirodantas@seqera.io> Co-authored-by: Ilkka Seppälä <iluwatar@users.noreply.github.com>
This commit is contained in:
committed by
GitHub
parent
be0d5e5953
commit
f79782bea9
@@ -39,8 +39,8 @@ import lombok.extern.slf4j.Slf4j;
|
||||
* version of the feature toggle, where the enhanced version of the welcome message which is
|
||||
* personalised is turned either on or off at instance creation. This method is not as dynamic as
|
||||
* the {@link User} driven version where the feature of the personalised welcome message is
|
||||
* dependant on the {@link UserGroup} the {@link User} is in. So if the user is a memeber of the
|
||||
* {@link UserGroup#isPaid(User)} then they get an ehanced version of the welcome message.
|
||||
* dependent on the {@link UserGroup} the {@link User} is in. So if the user is a member of the
|
||||
* {@link UserGroup#isPaid(User)} then they get an enhanced version of the welcome message.
|
||||
*
|
||||
* <p>Note that this pattern can easily introduce code complexity, and if not kept in check can
|
||||
* result in redundant unmaintained code within the codebase.
|
||||
|
||||
+1
-1
@@ -30,7 +30,7 @@ import java.util.Properties;
|
||||
import lombok.Getter;
|
||||
|
||||
/**
|
||||
* This example of the Feature Toogle pattern is less dynamic version than {@link
|
||||
* This example of the Feature Toggle pattern is less dynamic version than {@link
|
||||
* com.iluwatar.featuretoggle.pattern.tieredversion.TieredFeatureToggleVersion} where the feature is
|
||||
* turned on or off at the time of creation of the service. This example uses simple Java {@link
|
||||
* Properties} however it could as easily be done with an external configuration file loaded by
|
||||
|
||||
+1
-1
@@ -29,7 +29,7 @@ import com.iluwatar.featuretoggle.user.User;
|
||||
import com.iluwatar.featuretoggle.user.UserGroup;
|
||||
|
||||
/**
|
||||
* This example of the Feature Toogle pattern shows how it could be implemented based on a {@link
|
||||
* This example of the Feature Toggle pattern shows how it could be implemented based on a {@link
|
||||
* User}. Therefore showing its use within a tiered application where the paying users get access to
|
||||
* different content or better versions of features. So in this instance a {@link User} is passed in
|
||||
* and if they are found to be on the {@link UserGroup#isPaid(User)} they are welcomed with a
|
||||
|
||||
Reference in New Issue
Block a user