Skip to content

fix: add warnings for unsupported feature flags - #19345

Merged
mcollovati merged 1 commit into
mainfrom
warning-for-unsupported-flags
May 10, 2024
Merged

mcollovati merged 1 commit into
mainfrom
warning-for-unsupported-flags

Conversation

@mshabarov

Copy link
Copy Markdown
Contributor

A copy of #19049 patch, but with proper formatting.

Thanks @schastlivcev for contribution!

There was no indication if you were using non-existent or unsupported feature flags at startup. This change brings log warnings about existence of such feature flags.

Fixes #18672

There was no indication if you were using non-existent or unsupported feature flags at startup. This change brings log warnings about existence of such feature flags

Fixes #18672
@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@github-actions

Copy link
Copy Markdown
Contributor

Test Results

1 103 files  ± 0  1 103 suites  ±0   1h 24m 1s ⏱️ +14s
7 009 tests + 3  6 960 ✅ + 3  49 💤 ±0  0 ❌ ±0 
7 353 runs   - 23  7 294 ✅  - 23  59 💤 ±0  0 ❌ ±0 

Results for commit eddcb71. ± Comparison against base commit fa1ebd0.

@vaadin-bot

Copy link
Copy Markdown
Collaborator

This ticket/PR has been released with Vaadin 24.5.0.alpha1 and is also targeting the upcoming stable 24.5.0 version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Log or throw for non-existent feature flags

3 participants