Skip to content

unable to serve CSS - same as #51, path confusion #55

@mooseyboots

Description

@mooseyboots

hi,

i'm trying out radiance, as per the readme getting started instructions, and it's unclear how the local /static/ CSS should work.

if i spin up a new module from scratch, it only renders CSS if the path for the uri-to-url function is given as /static/example/example.css, but the relative file path actually on disk is just /static/example.css.

it doesn't work if both paths are the same, i.e both /static/example.css or both /static/example/example.css, it only works if they don't match.

which is very confusing, to this total noob at least. is this deliberate somehow? shouldn't all css files under /static/ just be read so the subdir doesn't matter in this way, and its left up to the user? and if we are already in our module directory, do we need a subdir below static to specify that we are also in our module directory? (maybe later on, but then it'd be helpful to explain the necessity in the getting started guide! :) )

while i'm here, is this always a strictly relative path? asking as i want to change *modules-directory*.

thanks.

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