Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
chore: limit `feature_flag` method to `ProjectSettingsService`
See original GitHub issueFollowing up on this discussion in #6485.
Currently the feature_flag decorator is a method defined on the SettingsService base class. However, since feature flags are top-level settings in a Meltano project and currently never defined in plugin settings, this has led to multiple cases of the method being used from a PluginSettingsService, where it will always show the given flag as not being set. To avoid this confusion, we should just move the method to ProjectSettingsService.
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@cjohnhanson the weight field is on the Engineering Assignments board which this wasn’t assigned to when you opened it. Leaving a comment is fine as it does help with prioritization prior to being pulled into that board.
@aaronsteers yeah I put this on the backburner since it’s definitely a chore that doesn’t have any immediate or short-term user impact. It should definitely have the
Urgency=Highflag removed.