[SERVER-70052] Investigate static analysis mechanism for enforcing architectural rules Created: 28/Sep/22 Updated: 27/Oct/23 Resolved: 27/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | 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 | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
|
| Comments |
| Comment by Alex Neben [ 01/Dec/22 ] |
|
I moved the work of actually doing this as part of clang-tidy into |
| Comment by Jordi Serra Torrens [ 01/Dec/22 ] |
|
alexander.neben@mongodb.com CollectionShardingRuntime is something we only want to be used within the sharding mongod code (mongo/db/s/). |
| Comment by Alex Neben [ 01/Dec/22 ] |
|
jordi.serra-torrens@mongodb.com I am not super familiar with CollectionSharingRuntime. Is this something that we are trying to deprecate and we want to guard against future uses? Or is this something that we only want to use in a specific areas of the code? Here is another way to think about this. |