Comments (15)
I had a patch for this lying on my disk and created a pull request (#13) from it. You might want to check it out if it works for you!
from paw-swaggerimporter.
@nosyjoe Just a short question: Your implementation just groups the first path-segment, right?
I'm struggling with this since hours… The problem is the tree-building.
I found some working solutions, but these require previous sorting and filtering. For PHP I found something actually working (except root-nodes must be omitted before): http://thehighcastle.com/blog/38/php-dynamic-access-array-elements-arbitrary-nesting-depth
Maybe you have some ideas?
from paw-swaggerimporter.
oh you want sub-groups? it's only grouping top-level path segments, yes
from paw-swaggerimporter.
Ah okay, I'm looking into it right now. Yeah, I thought it would be very useful to have a recursive attempt on this or so. But it seems a bit complicated to build up the tree.
It would be super easy with such array-access:
var string = "[1][2][3][4]";
array{string} = "42";
But I think, grouping the first segment is a huge improvement for now. We've got > 200 endpoints and it's kind of messy with Paw.
from paw-swaggerimporter.
recursion to the rescue, I agree. the API makes it a bit complicated since subgroups are handled differently from root-level groups, though. I'm playing around with it a little
from paw-swaggerimporter.
Thanks, I didn't really look into the Paw-Grouping before. My problem was more the grouping-algorithm. Maybe CoffeeScript handles this better than vanilla JavaScript, I'm not pro with CS/JS at all.
This is my current JavaScript attempt:
build_path_tree = function (paths, path_separator) {
path_separator = typeof path_separator !== 'undefined' ? path_separator : "/";
var separated_paths = split_paths(paths, path_separator);
return group_by_paths(separated_paths, path_separator);
}
group_by_paths = function (paths, path_separator) {
var result_array = [];
for (var current_path in paths) {
if (paths.hasOwnProperty(current_path)) {
array_set_path(result_array, paths[current_path], current_path);
}
}
return result_array;
}
split_paths = function (paths, path_separator) {
var result_array = [];
for (index = 0; index < paths.length; ++index) {
result_array[paths[index]] = split_path(paths[index], path_separator);
}
return result_array;
}
split_path = function (path, path_separator) {
var path_components = path.split(path_separator);
return path_components.filter(function(n){ return n != undefined && n != "" });
}
array_set_path = function (object, path, value) {
var o = object;
for (var i = 0; i < path.length - 1; i++) {
var n = path[i];
if (n in o) {
o = o[n];
} else {
o[n] = {};
o = o[n];
}
}
o[path[path.length - 1]] = value;
}
console.log(build_path_tree(["/test/12/", "/test/13/", "/test/13/14/", "/app/users/", "/app/users/test", "/app/files/"]));
This is my PHP attempt (I'm just more used to prototype with PHP):
<?php
$paths = ["/app/test", "/app/files/123", "/app/users/123", "/app/users/", "/web/"];
var_dump(build_path_tree($paths));
function build_path_tree($paths, $path_separator = "/")
{
$separated_paths = split_paths($paths, $path_separator);
return group_by_paths($separated_paths, $path_separator);
}
function group_by_paths($paths, $path_separator = "/")
{
$result_array = [];
foreach($paths as $current_path => $current_path_components)
{
array_set_path($current_path, $result_array, $current_path_components);
}
return $result_array;
}
function split_paths($paths, $path_separator = "/")
{
$result_array = [];
foreach ($paths as $current_path)
{
$result_array[$current_path] = split_path($current_path, $path_separator);
}
return $result_array;
}
function split_path($path, $path_separator = "/")
{
return array_filter(explode($path_separator, $path));
}
function &array_get_path( &$array, $path, $delim = NULL, $value = NULL, $unset = false ) {
$num_args = func_num_args();
$element = &$array;
if ( ! is_array( $path ) && strlen( $delim = (string) $delim ) ) {
$path = explode( $delim, $path );
}
// if
if ( ! is_array( $path ) ) {
// Exception?
}
// if
while ( $path && ( $key = array_shift( $path ) ) ) {
if ( ! $path && $num_args >= 5 && $unset ) {
unset( $element[ $key ] );
unset( $element );
$element = NULL;
}
// if
else {
//echo "Element: " . $element . " Key: " . $key . "\n\n";
$element =& $element[ $key ];
}
// else
}
// while
if ( $num_args >= 4 && ! $unset ) {
$element = $value;
}
// if
return $element;
}
// array_get_path
function array_set_path( $value, &$array, $path, $delimiter = NULL ) {
array_get_path( $array, $path, $delimiter, $value );
return;
}
// array_set_path
function array_unset_path( &$array, $path, $delimiter = NULL ) {
array_get_path( $array, $path, $delimiter, NULL, true );
return;
}
// array_unset_path
function array_has_path( $array, $path, $delimiter = NULL ) {
$has = false;
if ( ! is_array( $path ) ) {
$path = explode( $delimiter, $path );
}
// if
foreach ( $path as $key ) {
if ( $has = array_key_exists( $key, $array ) ) {
$array = $array[ $key ];
}
// if
}
// foreach
return $has;
}
// array_has_path;
?>
Part of the PHP code was taken from this URL: http://thehighcastle.com/blog/38/php-dynamic-access-array-elements-arbitrary-nesting-depth
from paw-swaggerimporter.
you can write it way easier. e.g. split the path segments and omit empty parts:
pathSegments = swaggerRequestPathName.split('/').filter (s) -> s && s != ""
console.log(pathSegments)
from paw-swaggerimporter.
ok, after diving into it a little bit more, I managed to come up with a solution, it is not perfect but it does do the creating of the recursive groups:
https://github.com/nosyjoe/Paw-SwaggerImporter/tree/recursive-request-groups
hope that helps!
from paw-swaggerimporter.
@nosyjoe Wow, thank you! That's definitely a huge improvement! I'm forking the Swagger-Importer for a specific Swagger-using framework, to make things more easy with the framework. For me, I think, I will add a breakpoint for path-segments containing placeholders like /{user_id}/.
I'm currently unsure whether the placeholder syntax is specified by Swagger. But if so, it should also be considered for the Default-Swagger-Importer to stop there.
Or would you recommend (a more complex way, I think) to just group these placeholder-segments just, if there are other such segments?
I mean:
https://api.my-product.com/my/path/{user_id}/{my_value_1}/
https://api.my-product.com/my/path/{user_id}/{my_value_2}/
https://api.my-product.com/my/path/{file_id}/
=>
- my (group)
- path (group)
- {user_id} (group)
- {my_value_1} (NO group)
- {my_value_2} (NO group)
- {file_id} (NO group)
This is an example with many empty parsed paths
So, for us it's currently as good as it could get. But for the future, someone might think about better breakpoint-handling for the sub-groups.
Thanks for your help!
UPDATE:
It looks like the sub-grouping creates sub-groups in wrong main-groups. I'm going to provide an example tomorrow, I think. Maybe something like a substring-match before adding to a sub-group would be needed. So, take the current parent's complete path and check whether the current child's path is a complete substring or so. Looking into it tomorrow…
from paw-swaggerimporter.
Nice work on this! Thank you for that. I'll have a look at this code quickly. Thought, I don't know if we should merge this to master yet: some users may not like the per-path-component grouping, and an update to Paw is coming soon that will bring options to importers. We will be able to set a checkbox and ask if the user wants to group per path component.
If you guys still have some questions on how this can be implemented, and about the use of the API, I'm happy to have a Skype call tomorrow (we're in Western Europe).
from paw-swaggerimporter.
@letsbyteit glad I could help. I think the placeholders in curly braces are swagger-standard. I was thinking about excluding them like in /pet/{petId}
but then there were cases with nested placeholders (like /pet/{petId}/uploadImage
) and things were starting to get too complicated :)
also, as a next step I would like to map these placeholders to environment variables through dynamic values...
from paw-swaggerimporter.
@mittsh yeah, offering the user an option to choose sounds great. although I don't think groups with 1 child each, like it is currently implemented, makes sense as a default. but choosing how many level or if there should be recursive groups would be a good configuration option, I agree!
from paw-swaggerimporter.
@nosyjoe yeah :) when we have options for importers it will all be much nicer!
from paw-swaggerimporter.
@mittsh any ETA on the 2.3.3 release? do you guys have a alpha/beta program?
from paw-swaggerimporter.
@letsbyteit This behavior is now supported in Paw.
from paw-swaggerimporter.
Related Issues (20)
- Show example in body HOT 8
- TypeError: undefined is not a function HOT 4
- definition references not correctly parsed HOT 5
- Does not correctly handle multiple "schemes" values HOT 6
- Support importing host and schemes attributes as environment variables HOT 4
- cannot export when using environment variables HOT 6
- Body parameters? HOT 10
- Import not working HOT 19
- Import not working HOT 2
- Import failing HOT 3
- Import failed - undefined is not an object HOT 9
- Failed to correctly import swagger yml file due to Content-Type error HOT 1
- apiKey securityDefinition is not respecting header key HOT 3
- schema reference not expanded for request body HOT 5
- Makefile missing
- Feature request: Import from swagger-ui spec HOT 3
- TypeError: Parameter 'url' must be a string, not object HOT 22
- Support Open API 3.0 HOT 31
- Import Failed: because of "- {}" in yaml file
- No tags when importing from Swagger
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from paw-swaggerimporter.