Fails when package name has a slash (/)

[defunkydrummer]

The documentation generation fails if the package name has a "/" on it, because this "/" goes straight into the pathname name and thus it's interpreted like a directory separator.

(defun document-package (package-index &key keep-rst (base-path #P"docs/"))
 "Generates documentation in html form for :param:`package-index`.

The documentation file will have the pathanme ``{{base-path}}{{package-name}}.html``, so a package named ``cool-package`` with :param:`base-dir` ``docs/`` will have the generated pathame ``docs/cool-package.html``.

If :param:`keep-rst` is truthy, don't delete the intermediate restructured text file."

 (let* ((pathname (make-pathname :defaults base-path
                                 :name (-> package-index docparser:package-index-name string-downcase)
                                 :type "rst"
                                 :version nil))
        (coo.roles:*context-package* (find-package (docparser:package-index-name package-index)))
        (args (list :variables nil
                    :functions nil
                    :macros nil
                    :generic-functions nil
                    :structures nil
                    :classes nil)))

The problem is at name (-> package-index docparser:package-index-name string-downcase) : pathname is not filtering the package-index's name.

If this package name has a slash (/) (for example "mypackage/utils", then it becomes part of the pathname. It shouldn't.

The system needs to filter the package names accordingly.

[fisxoj]

Thanks for reporting that...

I'll have to think about how to handle it. urlencoding things comes to mind, but I'll try to think about it more, soon.