-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] "tiddlywiki invalid-path --listen" does start a server - IMO it should not #8542
Comments
@linonetwo @saqimtiaz -- Can you imagine a configuration, where it would make sense to run a server with an invalid path name? |
The canonical example of using an invalid pathname is when initialising a new wiki:
|
Yes, but that does not touch the code of the |
Hi @pmario so you are suggesting that the That's not right. TiddlyWiki can be run without a wiki folder. For example:
It is not necessary for there to be a wiki folder in order for TiddlyWiki to function correctly. |
Hi @pmario the "problem" here is just that there is no theme plugin loaded. If we think that that is confusing then perhaps a better approach would be to make the core display a warning banner if there is no theme plugin loaded. I think that could be done in wikitext as a page template segment. |
I don't use cli, I only call its JS api, so I have no opinion here. |
If I run
tiddlywiki invalid-path --listen
, it does still start a server - IMO it should notThis issue is related to: Add some new scripts to package.json, to make npm run command easier #8294
Proposal
It should produce "Error" instead of "Warning" -- and stop
Command to replicate the problem
It prints this info:
So it knows, that it will not work. But it still runs a server that will create this:
The text was updated successfully, but these errors were encountered: