V8: Add the AngularJS directive template url pathname into the template itself for easier finding

[PeteDuncanson]

I had this as an issue on the old tracker. Currently if you are hacking around in the UI and need to find where a template lives so you can edit it its very difficult to work out where to go find it. I'd like it if in the HTML itself we could write out the filename/path to the template file in the source. That way you can very quickly find where the template lives and you can shorten the development time and focus on the actual problem.

We could inject it as a data-path attribute on the top most element in the template or a HTML comment but I'm not sure if that will be rendered out or not in dev tools. Something to check.

Two ways to do it. Manually go through and add them all, quickish but likely to break over time. Better would be to have gulp task that can just run through all the templates and add the pathname in automatically during the build, this is my preferred option I think and something to look into. If you do the gulp route then ensure it will run on gulp v4 as we are looking to upgrade to that (#4846).

[nul800sebastiaan]

Not sure I understand:

1. Why is it hard to find the template? In both v7 / v8 you can click open the template from the content item if you're an admin
2. What happens if you move around template files on disk, rename them, etc? The data in the template is going to out of sync
3. Gulp? So people will need to run both a VS build and a Gulp build while implementing their sites?

Mostly I'm struggling with the premise of the problem here, I'm probably missing something.

[PeteDuncanson]

Hi Seb, sorry I should have been clearer. This is for the AngularJS templates for directives etc. I've updated the issue title to reflect this. Enjoy Japan!

[nul800sebastiaan]

Ahaaaaa! 👍 Clear. :)

I've marked this as "Up for grabs" so that you or someone else coming along could create a pull request for it.

[umbrabot]

Hiya @PeteDuncanson,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant
This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[nul800sebastiaan]

@umbrabot still relevant

[Zeegaan]

Not sure if relevant still, maybe @nul800sebastiaan has the answer!
Either way this is a feature request, so I'm moving it to the discussions board 😁

[nathanwoulfe]

I don't see much (if any) value in pursuing this given the new backoffice is not that far away and would render this obsolete. Would have been useful a couple of years ago, but we're all about looking forward, not back.

[nul800sebastiaan]

Agreed! 👍

[Zeegaan]

Alright, with that I will lock the discussion then 👍