Rendering "attributes" section using attributes-kit #337
Conversation
feat: rename jade to pug, fix compatibility
fix: queryString typo
|
feat #103 |
fix: remove redundant variable
|
Awesome, please merge this! cc @kylef |
.gitignore
Outdated
| @@ -3,3 +3,5 @@ node_modules | |||
| npm-debug.log | |||
| coverage | |||
| cache | |||
| .idea/ | |||
| yarn.lock | |||
There was a problem hiding this comment.
.idea is WebStorm config directory, I use yarn to install node.js dependencies instead of npm, Yarn uses a yarn.lock file to get consistent installs across machines
There was a problem hiding this comment.
Yet it's a common practice to include lock files in your source control. Ignoring this file doesn't seem right
|
any update? @Morozzzko @jk2K |
|
@dmnlk you should probably ask @danielgtaylor instead. He hasn't been active for a long while, though. |
|
@Morozzzko thanks, and sorry my mistake. |
|
do you think it will be nearly ready? |
|
Is there a working fork that we can use? |
1 similar comment
|
Is there a working fork that we can use? |
|
This project has been seeking maintainers since October 2018 and is no longer under active development. 0cef09a I strongly recommend people switch to OpenAPI v3.0 in general. There are loads of tools for documentation that look amazing and work really well. ReDoc for example takes care of data structure display very nicely.
I was a big fan of API Blueprint for a long time, but it's not being worked on and its ecosystem has been stagnant for years. Make the switch and use nice things instead of hacking old things. 🤷♂️ |
Show schema when user presses show button
Screenshot