Skip to content

Roaster encourages 'unused' namespaces in api.xql #143

Description

@DrRataplan

See api.xql in the roasted app. Because of the xs:QName call, all namespaces need to be declared, but are not statically used.

This gives issues with linters: unused namespaces all over the place, and punishes when you want to clean them up with errors when you access any of the roaster stuff. This encourages keeping in unused namespace declarations.

Can we change (the examples) to use dynamic module imports? This would speed up most routes because we'd only load the needed modules, instead of all of them. I've seen dramatic slowdowns with modules running expensive variable declarations that were not even used, just because they were declared and imported.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions