Omit startup warnings if they're not relevant
Open
Nobody has claimed this yet.
good-first-issue
- Dominant language
- Ruby
- Stars
- 1.9k
- Forks
- 739
- Avg merge
- 21h 2m
- Merged PRs (30d)
- 1
Description
As stated in the comment, we're currently displaying these warnings every time. Perhaps we can look at the configs / versions to avoid over-logging them if they've been addressed.
is there a way to silence these log messages? i'm installing shopify_app in a brand new app, and these messages don't seem terribly useful.
Originally posted by @joevandyk in https://github.com/Shopify/shopify_app/issues/1884#issuecomment-2272596416
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by locating the startup warning code and the related configuration or version checks. Done means irrelevant warnings are omitted while relevant warnings still appear, with tests covering that distinction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- backend, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100