Skip to content
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

Integrating Swashbuckle with DapperDox #1105

Open
lockewritesdocs opened this issue Jun 7, 2017 · 15 comments
Open

Integrating Swashbuckle with DapperDox #1105

lockewritesdocs opened this issue Jun 7, 2017 · 15 comments

Comments

@lockewritesdocs
Copy link

@heldersepu, I am writing an article for a technical communications blog documenting how I integrated Swashbuckle with DapperDox. I will submit a PR with the article, which I think could be helpful to Swashbuckle users that want to generate a swagger.json file that they can serve to a static site generator other than the Swagger UI. Let me know what you think.

@lockewritesdocs
Copy link
Author

@heldersepu, I created a branch and tried to merge it into master, but permission was denied. Can you give me access to merge the branch and create a PR?

@heldersepu
Copy link
Contributor

heldersepu commented Jun 7, 2017

I'm not sure what exactly are you trying to do /?!?!
You don't need any permissions to submit a PR
And I do not have any more access than you do, I can NOT give or take permission to this project

@heldersepu
Copy link
Contributor

I do not see a Swashbuckle fork on your profile:
https://github.com/lockewritesdocs

@lockewritesdocs
Copy link
Author

Apologies! I goofed on my end. PR #1107 submitted.

@heldersepu
Copy link
Contributor

no problem, we all do at some point!
Do you have a public URL for your project working with DapperDox ?

A lot of steps...
I'm wondering if we can detach a fork and start a project that uses DapperDox instead of Swagger-Ui ?!?
Which one do you like better?

@lockewritesdocs
Copy link
Author

Unfortunately, the implementation is being used to create documentation for our support team, and the information is proprietary.

DapperDox is a new technology, but it provides the capability to include documentation beyond just the API reference. I think that capability is really important. Also, the creator is very responsive!

@heldersepu
Copy link
Contributor

is there a live demo somewhere of DapperDox ?

@lockewritesdocs
Copy link
Author

If you download the latest release, you can run the integrated demo.

@heldersepu
Copy link
Contributor

Ok, I download it and I'm running it ...
I like what I see! the Swagger Petstore (in my eyes) it looks better than:
http://petstore.swagger.io/

But I'm not quite sure how we can integrate this into a Nuget package, it seems that download is its own server not just a UI for a swagger definition

@lockewritesdocs
Copy link
Author

After I use Swashbuckle to create a swagger.json file, I run .\dapperdox --spec-dir=dir_with_swagger.json_file, and then point my browser at http://localhost:3123. That's it! What would we need beyond the executable?

@heldersepu
Copy link
Contributor

heldersepu commented Jun 7, 2017

O yeah I did get it running ...
My idea was to detach a fork from Swashbuckle and replace the SwaggerUi with DapperDox
But DapperDox is not just a UI that we can "easily" integrate

@heldersepu
Copy link
Contributor

I think it will be nice if you would not need to create a file.
instead DapperDox should read directly from something like:
http://swashbuckletest.azurewebsites.net/swagger/docs/v1

@lockewritesdocs
Copy link
Author

DapperDox is not creating the file. Swashbuckle (with some tweaking) creates a swagger.json file from the code source (like the one you linked to), which DapperDox consumes and displays in its UI.

Please let me know if I am misunderstanding your statement.

@heldersepu
Copy link
Contributor

heldersepu commented Jun 12, 2017

@lockewritesdocs
My idea is to not create any file!
Instead DapperDox should read, consumes and display directly from url (that will probably be a new feature)
Right now you run .\dapperdox --spec-dir=dir_with_swagger.json_file
It will be nice something like:
.\dapperdox --spec-url=http://swashbuckletest.azurewebsites.net/swagger/docs/v1

@lockewritesdocs
Copy link
Author

@heldersepu, thank you for the explanation! I'm going to reach out to the DapperDox folks to see if a feature like that one is something that they are considering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants