-
-
Notifications
You must be signed in to change notification settings - Fork 428
ignore html files with missing base element #1237
Conversation
This seems like a duplicate of #984 |
I don't think so. This just fixes a bug with export, it doesn't change normal handling of the base element. |
It does seem like an alternative solution of #1208 though. That one uses a fake base value to continue crawling. My solution just skips the file if no base is present, which I thought was safer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, I see. thanks for clarifying. I didn't look too closely at first. wouldn't you want the file exported though? otherwise, why have it present in your static directory in the first place?
It is exported, it just skips the link crawling. |
It sounds to me like |
In this case it would make most sense to use normal base handling like a browser. So on page /abc/def, base defaults to /abc. Sound good? |
Yeah, that makes sense to me |
Anyway I think it's correct that I close this in favor of 1208 since that one has a test case too. |
I have some html files in my static folder. This caused
sapper export
to die because it expects all html files to have a<base>
element and they do not. This is a simple fix.