`disableFeature` test helper not available in current release
See original GitHub issueThe README indicates a disableFeature
test helper is available[1]. However, the 6.0.0
release does not include this test helper which was added later via #97.
[1] https://github.com/kategengler/ember-feature-flags#enablefeature--disablefeature
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Issues · kategengler/ember-feature-flags - GitHub
Issues list ; disableFeature test helper not available in current release. #107 opened on Apr 29, 2021 ; Error message: Assertion Failed: You...
Read more >Is the 'Travel' time helper not available in feature specs?
In order to use these helpers you have to include them into your tests. You can do this by either including it into...
Read more >WebXR Features Manager | Babylon.js Documentation
Learn all about the powerful WebXR features manager in Babylon.js.
Read more >crosh/crosh - chromiumos/platform2 - Git at Google
This comes last so it can override any release modules. ... echo "help: command '${cmd}' is not available" ... 1 = Call is...
Read more >function_exists - Manual - PHP
echo "IMAP functions are not available. ... is_callable() - Verify that a value can be called as a function from the current scope....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
+1 for the release.
@kategengler is there anything we could do to help with releasing new version?
I’ve hit this bug today, when attempting to use
disableFeature
and getting back:If a release of this package reinstates this function, is it possible to get a 6.0.1 release to fix this issue?