#68 Mark package dirty after definition change

Closed
opened 8 years ago by nero · 1 comments

Originally at 2015-06-16T15:55:39Z by Sean DeNigris

For example, right now if you add to the #imports: section, the package does not get marked dirty

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally at 2015-06-16T15:55:39Z by Sean DeNigris For example, right now if you add to the #imports: section, the package does not get marked dirty <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22245925-mark-package-dirty-after-definition-change?utm_campaign=plugin&utm_content=tracker%2F3968890&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F3968890&utm_medium=issues&utm_source=github). </bountysource-plugin>
Herby Vojčík commented 4 years ago
Owner

Actually responsibility of core Amber: amber/amber#1253.

Actually responsibility of core Amber: amber/amber#1253.
Sign in to join this conversation.
No Label
No Milestone
No assignee
2 Participants
Loading...
Cancel
Save
There is no content yet.