References to assets folder not working with build?

[jkarlsen]

I'm having an issue where if I create a custom component and include a reference to an image in the html template, when I build the package for upload, the asset isn't found.

For instance in the html file I have an element
<img src="../../assets/images/onesearch-logo.png" alt="OneSearch">
In the development environment, the image is found and appears correctly.

When I build and upload the customization package, I can see the src attribute/value are unchanged. But that's not the path to the assets file at the production site, so the file isn't found.

Maybe I don't understand about how to include references to asset files? Or is there a bug?

[wadeguid]

jkarlsen, here's an example of the path I use, which seems to work, both when I upload to Alma and also when I use the proxy for local development... src="../nde/custom/01ALLIANCE_UW-DEV_NDE/assets/images/worldcat_logo.png"

UPDATE: You can also do it like so: src="../../../../assets/images/worldcat_logo.png"

So that you aren't locked to a particular view name.

[jkarlsen]

I will definitely give this a try, thank you so much for replying, Wade.

[jkarlsen]

The first version you included, with the view code, works for me both in the development proxy and when uploaded. The second, with ../../../../, works locally but not when uploaded.

I will be working with 4 views and sharing components among them, so ideally I wouldn't have the view code in there, but there's probably a way to set up some constants in a different file and import them to the components. Anyway it's great to have something working, thank you!

I would still like to hear from the developers about what the intended strategy is.

[wadeguid]

That makes sense. With multiple views at that level of the directory tree, you would need to specify the view directory explicitly. There's probably a way to set a global variable for view name in angular somewhere. We do something similar with the Primo VE package.