is there a bug in 6.1.3 around module resources not getting registered?

[markdav-is]

I'm pulling my hair out trying to figure out why my module index action razor component is not registering it's resources. I can set a breakpoint on the Resources definition and it get's called, but never gets added to the page. Not in Debug or when deployed. Seems like his was working, but maybe something changed in 6.1.3? Before I upgrade to 6.1.4 looking for a fix, is this a known issue? I tried adding resource locations and exact URLs, but they are not getting rendered.

    public override List<Resource> Resources => new List<Resource>()
    {
        new Resource { ResourceType = ResourceType.Script, Url = "~/Module.js" },
    };

[markdav-is]

maybe this #5323

[sbwalker]

@markdav-is you have not provided any of the details necessary to troubleshoot ie. if the site is using interactive or static render mode, if the module is using interactive or static render mode, etc... JavaScript resources are handled completely differently based on render mode.

[sbwalker]

@markdav-is I am not aware of any issues with Resources in recent versions. If the Resources are declared in index.razor I would suggest specifying Url = ModulePath() + "Module.js" rather than using tilde (as tilde was introduced for Resources declared in ModuleInfo.cs where ModulePath is not available). I would also validate that the folder name under wwwroot/Modules EXACTLY matches the namespace of your module ie. the exact value specified by @namespace in your index.razor file.

[markdav-is]

Thanks for the quick answer. I was able to create a new test module and the JS file shows up properly so It's something I'm doing that's out -of-pattern. you can ignore me, I'll post the final answer when i figure it out.

[markdav-is]

I was never able to get the module.js loading and eventually added the missing script to the theme as a work-around. I'll be on the lookout for other projects with similar issues. Super obscure.

[sbwalker]

@markdav-is are you able to share some details so that it is possible to investigate:

1. Is the site experiencing the issue using Interactive or Static (default) render mode?
2. Is the module's razor component using Interactive (default) or Static render mode?
3. Is the module defining the Resources in the ModuleInfo.cs or within a razor component?
4. Does your module's razor component implement OnAfterRenderAsync (and if so, what logic does it contain)?

These 4 items define the behavior for how JavaScript resources are injected.

[sbwalker]

I did find an anomoly with JavaScript resources - but I am not sure if its the same problem you encountered. When using the following configuration:

1. Site render mode = Static (default)
2. Module razor component render mode = Interactive (default)
3. Module defining its Script Resources in a razor component (not via ModuleInfo.cs)
4. Module implements OnAfterRenderAsync in its razor component - which calls "await base.OnAfterRenderAsync"

The framework is injecting 2 script tags into the DOM for the same resource.

Since the general goal in Oqtane is to hide complexity from developers and allow them to write logic which works consistently across different render modes, I believe the correct behavior in this case is that the framework should NOT automatically inject a module's script resources within App.razor if the module component is using Interactive render mode - as when Interactive render mode is specified (for either a Site or a Module) the component should rely solely on JS Interop and OnAfterRenderAsync.

[markdav-is]

thanks for these details. My simplistic worldview is that script (or others) resources defined in ModuleInfo.cs should show up for any action in the module. Specific actions can add more specific resources. When I try adding resources in various places and they don't show up, my escape hatch is to add them to the theme. The theme seems to always get the resources added, although it's a heavy handed approach and breaks the concept of module encapsulation.

[JoeAucoin]

I've found . . . .

public override string RenderMode => RenderModes.Interactive;
// THIS DOES NOT WORK
// public override List<Resource> Resources => new List<Resource>()
// {
//     new Stylesheet("_content/GIBS.Module.QuickPoll/Module.css"),
//     new Script("_content/GIBS.Module.QuickPoll/Module.js")
// };

// THIS WORKS

public override List<Resource> Resources => new List<Resource>()
{
    new Resource { ResourceType = ResourceType.Stylesheet, Url = "_content/GIBS.Module.QuickPoll/Module.css?v=1.0.5" },
    new Resource { ResourceType = ResourceType.Script, Level = ResourceLevel.Site, Url = "_content/GIBS.Module.QuickPoll/Module.js?v=1.7" }

};