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
Given that source code files can be changed after maps are generated, this can lead to the pink "pins" being placed incorrectly within the file viewer.
Therefore we will add an extension setting that allows a user to disable the display of pins if they so choose. It will remain enabled by default when the extension is first installed.
Example pin in source code
Where the AppMap pin enabled setting should be located
Details
Add the setting to the configuration field in package.json.
@brikelly I'm not sure that this is the best approach. How are users going to know about this option? And then they have to disable the pins for the entire project - not just the files that are out of sync.
I suggest a different approach that I think is better. We know the timestamp of the AppMaps that include the source file. If the modified date of the source file is later than the timestamp of any of the AppMaps, don't show the Pin.
Issue
Given that source code files can be changed after maps are generated, this can lead to the pink "pins" being placed incorrectly within the file viewer.
Therefore we will add an extension setting that allows a user to disable the display of pins if they so choose. It will remain enabled by default when the extension is first installed.
Example pin in source code
Where the
AppMap pin enabled
setting should be locatedDetails
configuration
field inpackage.json
.unit
orintegration
, but please do not add asystem
test).The text was updated successfully, but these errors were encountered: