-
Notifications
You must be signed in to change notification settings - Fork 476
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.
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
Harmonizing feed reader
type
#7490
Conversation
Parser name is `feed reader`, but we had some apps with type `Feed Reader` or even `Feed Reader App`, which was inconsistent compared to other client types
Can the checks be rerun? It does not look like they failed because of my change, after all. |
I committed through GitHub website. Cloned the repo in GitHub Desktop, triggered recheck there, and it shows as if the check were scheduled, but I do not see any updates on website. |
You can make a test commit and remove it in another commit then push both. It will trigger the checks. |
Done. Probably need to report a bug to GitHub, too. |
Doesn't this change make the |
Yup, no need to keep them. By default we are using |
Interesting, removing the type from YAML fails the tests, though 🤔 |
No longer required, since it's now fixed value
Test was failing on YAML structure check, not the parser check. Updated the test accordingly. |
Description:
Parser name for feed readers is
feed reader
, but we had apps with typeFeed Reader
or evenFeed Reader App
, which was inconsistent compared to other client types both in terms of case and name. This little change harmonizes things.Review