Skip to content

Duplication of javascript files (with packages) #6999

@valadas

Description

@valadas

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

We currently have packages for many javascript libraries. Those js files get put in Javascript Libraries/DnnPlugins/ with their package name and version.

When this was done, the original files in Website/Resources/Shared/scripts were left in place. To prevent confusion and duplication, we should try our best to warn developers to not directly reference those old files and instead use their named package for registration.

This can also cause fixes that are not applied in both copies as what happened before #6927

The proposed solution is to show a browser console warning when the old files are used with instructions to not reference them directly and use DNN APIs to request those libraries instead.

Steps to reproduce?

Here is a list of our current javascript packages.

Current Behavior

Developers may do fixes or consume those older duplicated files.

Expected Behavior

Developers should be warned to not do so.

Relevant log output

Anything else?

No response

Affected Versions

10.2.2 (latest v10 release)

What browsers are you seeing the problem on?

Chrome

Code of Conduct

  • I agree to follow this project's Code of Conduct

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions