Add getCacheFilePath to HasteMap

[rubennorte]

Summary

This makes it easier for tools to interact with the file without making assumptions about how it's generated.

Test plan

It's just a getter for a class field, so just Flow type checking.

[cpojer]

@rubennorte Can you give some more context about this change? The cache file path is intentionally hidden inside of jest-haste-map and should not be accessible from the outside. Exposing it like this will allow other tools to access the contents and messing with it, potentially saving corrupt state.

If this is for facebook/metro#267, I would recommend changing Metro not to print that message but rather allow Metro to clear the cache, and exposing a HasteMap.clearCache method.

[cpojer]

In addition, could you remove this method from Jest again? I really don't think it belongs here.

[rubennorte]

@cpojer it wasn't created for that Metro issue, but to be able to restore the cache generated by Jest in a different host with a different root directory (for remote caching).

[cpojer]

Yeah, this is exactly the sort of thing we shouldn't really be doing, because it allows swapping out the file from under jest-haste-map. Can you change it so you can specify the haste-map to read from, like HasteMap.createMapFrom(file, config)?

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.