Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Feature request: Add new depend.process.post extension point
See original GitHub issueThis is again a topic I thought I had created an issue for long time ago, but it does not seem so. I would like to have a depend.process.post (after everything) extension point.
Why
I extract metadata from the map using the depend.preprocess.post extension point, so after all keys have been resolved. This metadata is stored in properties, because I use OOPS xmltask. These properties are cleared, when the processing is done. So I need to store them in a property file and load this file after the processing. This feels really crappy. It would be much more elegant to do some moving, renaming, copying, uploading with all properties available. This could be done really simple by adding a new extension point to all transtypes.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ran a (completely unrelated) search today that brought up this one and #2289 – it looks like this one is a duplicate of the earlier issue. Does that sound right? (If they are different then I think I need some help figuring out the difference).
@robander, you’re right. I even upvoted Shane’s request, which was opened two years before mine. Also funny that years is a word that occurs quite often when speaking about periods and the toolkit. 😉