[SERVER-59115] Libdeps linter should include file and line information Created: 04/Aug/21 Updated: 27/Oct/23 Resolved: 27/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0 Desired |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Operating System: | ALL |
| Participants: |
| Description |
|
When LibdepLinter fails, it does not tell me which file and line number the error is located. This requires a developer to search the code base when it would save time if the error could simply include information about where the fault likes like compilers do. Example:
|
| Comments |
| Comment by Daniel Moody [ 05/Aug/21 ] |
|
maybe there is something nifty we can do with python exceptions to extract and present this info to the user. I'm not sure we can get the specific line number of the infraction, but we should be able to get the SConscript and line number of the builder call (e.g. env.Library or env.Program). |