{"push_id":1401075708,"size":2,"distinct_size":2,"ref":"refs/heads/maintenance-v1","head":"86fde7a2888b5d17947eee2361ed3ff40d0845ee","before":"65413b46834f15bb68032ef0a64a0b045fc3bd01","commits":[{"sha":"510e3a190e2680d40fb17c79e403d9d7e6872c78","author":{"name":"Henric Trotzig","email":"7e1ea0b4a315e72ef4f0b94e7cdb7e9b171ca163@brigade.com"},"message":"Properly resolve file paths for named exports\n\nWe've had a report in emacs-import-js [1] that `goto` wouldn't work for\nnamed exports.\n\nGiven the following structure\n\n  .importjs.js\n  app/\n    └── MyComponent.js\n    └── constants/\n      └── app_constants.js\n\nthe following config\n\n  module.exports = {\n    namedExports: {\n      'app/constants/app_constants': [\n        'Actions',\n      ],\n    },\n    lookupPaths: [\n      'app',\n    ],\n  }\n\nand app/MyComponent.js containing\n\n  import { Actions } from 'constants/app_constants';\n\nUsing `goto` on \"Actions\" opens `app/constants/app_constants` (which is\nnot a thing). It should be `app/constants/app_constants.js`.\n\nPR 11 [1] for emacs-import-js attempts to work around this problem\nlocally for emacs. But this is something that applies to all import-js\nplugins, so here's a fix in the core project instead.\n\n[1]: https://github.com/Galooshi/emacs-import-js/pull/11","distinct":true,"url":"https://api.github.com/repos/Galooshi/import-js/commits/510e3a190e2680d40fb17c79e403d9d7e6872c78"},{"sha":"86fde7a2888b5d17947eee2361ed3ff40d0845ee","author":{"name":"Henric Trotzig","email":"7e1ea0b4a315e72ef4f0b94e7cdb7e9b171ca163@brigade.com"},"message":"1.1.2","distinct":true,"url":"https://api.github.com/repos/Galooshi/import-js/commits/86fde7a2888b5d17947eee2361ed3ff40d0845ee"}]}
{"actor":{"display_login":"trotzig"}}