Include multiple portman config json #274
Replies: 7 comments 12 replies
-
I think you are referring to splitting up the Portman configuration (or the OpenAPI file)? For the Portman conversion configuration, currently we expect it all grouped in 1 file. You can include a file reference for the prerequestscripts using a "file:" syntax, to make the configuration a bit more compact. Possible workaroundYou can define the Portman configuration in JSON or YAML, what you could do is add an additional step before you run the portman conversion by leveraging a dereference package (ex: json-schema-ref-parser).
|
Beta Was this translation helpful? Give feedback.
-
Curious how large you Portman config would be? |
Beta Was this translation helpful? Give feedback.
-
Tagging @savage-alex & @AliKhalili & @nicklloyd to capture their experience here. |
Beta Was this translation helpful? Give feedback.
-
@AliKhalili @jdevosMagento If you have some time, have a look and see if the proposal would work? |
Beta Was this translation helpful? Give feedback.
-
hi @AliKhalili, @savage-alex & @jdevosMagento We just released version 1.15.0 of Portman, where this feature is included. |
Beta Was this translation helpful? Give feedback.
-
If in the coming weeks, anybody will give the '$ref' usage an attempt, if possible leave some feedback (good or bad). |
Beta Was this translation helpful? Give feedback.
-
@AliKhalili @jdevosMagento Are you still using the Since Portman config can become quite big, especially when using Variations & Fuzzing, we are wondering how we could document this capability better so that users would discover the Any tips or suggestion are welcome. |
Beta Was this translation helpful? Give feedback.
-
Hello,
First of all, thank you for this tool which is really interesting!
I wanted to know if it was possible to make file inclusions in a root configuration file.
I have a big project in terms of api and I'm afraid that having everything in a single file will become unreadable.
With openapi yaml, I was able to cut out the different paths via $refs which allows you to cut out the interfaces well and find your way around easily.
Is there a similar solution with portman?
If not, what advice can you give to get organized on a project with multiple APIs?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions