Skip to content

Update README.md #129

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.

Sign up for GitHub

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

Open
jacobkagon wants to merge 1 commit into
base: trunk
Choose a base branch
from
Open

Update README.md #129

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ my_registry[:greeter] {"Dolly"} # => "Hello Dolly"
my_registry.register_feature(my_species)
```

Namespaced Features respect their anscesters with regard to code access. For instance ```Feature#enabled?``` will check not only the referenced Feature, but traverse all ancestors in its namespace. If any of the referenced Feature's anscestors is disabled, then the referenced Feature is considered disabled -- regardless of whether ```is_enabled``` is set to ```true``` or ```false```.
Namespaced Features respect their ancestors with regard to code access. For instance ```Feature#enabled?``` will check not only the referenced Feature, but traverse all ancestors in its namespace. If any of the referenced Feature's ancestors is disabled, then the referenced Feature is considered disabled -- regardless of whether ```is_enabled``` is set to ```true``` or ```false```.

For instance, extending the ```species``` Feature example above:

Expand Down