-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add flag to ceylon doc
to open the docs in the browser.
#2057
Comments
@thradec any thoughts about this? It's currently marked as 1.2 so if we're serious about that we should probably start working on it now, otherwise defer it till 1.3. |
This should be quick to implement, that's why I marked it 1.2, but it can wait for 1.3 if it would take too long. |
The implementation is no problem, at least for local modules. I just wonder, that there are people who prefer to use cli for opening browser on specific url :-). |
Well, the use-case was as follows: using the CLI to get info on module with The other use-case is after building the docs you want to check them: |
I think it's definitely a good idea. And the docs are not really something you can easily show in the console, otherwise I'd suggest a |
ok, ok, it seems that I'm not so cli addicted as others :-) |
support for browsing local modules is done via 1285dbc |
OK that was indeed fast, thanks a lot :) |
I'm not sure how to integrate this with modules that are not available locally, because now the |
OK you're right, perhaps it makes sense to make this another command, but perhaps |
Done (for |
ceylon doc --browse com.foo
should open a browser for thecom.foo
documentation. Probably it should also generate the docs, although it would be nice if it would also work for modules that are not even available locally. For exampleceylon doc --browse ceylon.language
would just open a browser either to Herd where the docs are, or fetch the docs locally and point the browser there. So details to be discussed but the general idea is to make it easier to browse docs from the CLI.The text was updated successfully, but these errors were encountered: