You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. Has there been consideration into creating "blame maps" or blame maps metadata that could go into source maps? Consider a large organization with many teams and products. An individual in some part of the company stumbles upon some code in DevTools and wants to know who at the organization to contact about that line/chunk of code (maybe you're trying to implement the same thing and want pointers). If DevTools could have the author's alias (for instance), that could ease communication at the dev level.
Perhaps this is an idea in search of a problem, but wanted to ask this group.
The text was updated successfully, but these errors were encountered:
Hi. Has there been consideration into creating "blame maps" or blame maps metadata that could go into source maps? Consider a large organization with many teams and products. An individual in some part of the company stumbles upon some code in DevTools and wants to know who at the organization to contact about that line/chunk of code (maybe you're trying to implement the same thing and want pointers). If DevTools could have the author's alias (for instance), that could ease communication at the dev level.
Perhaps this is an idea in search of a problem, but wanted to ask this group.
The text was updated successfully, but these errors were encountered: