mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #384] npm modules of postwoman's vue components #138
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#138
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yubathom on GitHub (Nov 30, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/384
Is your feature request related to a problem? Please describe.
Yes. After deploying and testing an API it is a common task to create documentation websites. Postwoman is great for testing but it can't be used to create theese sites yet.
Describe the solution you'd like
Publish in NPM postwoman modules as vue components. So, in a documentation website you could use it like this:
I wrote an example for rest apis and name it
pw-rest(just GETs are working):use cases:
Many api documentation websites are using vuepress. In which theese modules could be easily imported and used in markdowns
With theese modules available some api documentation themes could be provided :)
Describe alternatives you've considered
Rely completly in a self based solution, like postman's docs.
Additional context
This enhancement is related to #326
@liyasthomas commented on GitHub (Nov 30, 2019):
This is awesome.
@liyasthomas commented on GitHub (Nov 30, 2019):
I gonna invest more time to this. Because this seems like a top priority. @yubathom can't we make the current implementation wrapped into a wrapper for npm module? With scoped styling and all.
@yubathom commented on GitHub (Dec 1, 2019):
I am not sure.. I will give a try and investigate a solution 🔍 If you find a nuxt project sharing components at npm please share it to me :octocat:
@liyasthomas commented on GitHub (Dec 1, 2019):
I'm on it 🤝
@yubathom commented on GitHub (Jan 26, 2020):
Hey @liyasthomas, I made a setup with rollup to publish standalone components:
https://github.com/yubathom/postwoman/tree/feature/library
Take a look at
lib/folderAs a prove of concept it's exporting
components/logo.vue.Everything that is exported at library/lib/lib-components/index.js could be published and available at npm.
there is some new scripts:
lib-build-> build components atlib/distlib-dev-> starts localhost:8080 to develop and test the components before publishingTo publish it you should type
npm publishafternpm run lib-buildAnd then, in another project we could install theese
and in a vue component you could import and use it
Downsides
So, before submitting the PR, I would like to discuss if this approach is ok..
@liyasthomas commented on GitHub (Jan 26, 2020):
I think this approach is okay. But want to experiment with webpack for the same usecase.
@AndrewBastin @NBTX @jamesgeorge007
What you guys think?
@liyasthomas commented on GitHub (Apr 13, 2020):
Closing due to inactivity