We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is it currently correct to store custom link options of a need flat, e.g.
"ACTIVITY_ThisAndThat": { "description": "", "id": "ACTIVITY_ThisAndThat", "implements": [], "has_in_port": ["...", ...], "has_out_port": ["...", ...], "instantiates": ["...", ...] },
or nested below "links", like this:
"ACTIVITY_ThisAndThat": { "description": "", "id": "ACTIVITY_ThisAndThat", "implements": [], "links": { "has_in_port": "...,...", "has_out_port": "...", "instantiates": "...", }, }
I could not find anything in the docs. I'm writing a needs.json generator right now, so I needs to know 😆
The text was updated successfully, but these errors were encountered:
The first one is correct, so it's just a "flat" dictionary.
Sorry, something went wrong.
No branches or pull requests
Is it currently correct to store custom link options of a need flat, e.g.
or nested below "links", like this:
I could not find anything in the docs. I'm writing a needs.json generator right now, so I needs to know 😆
The text was updated successfully, but these errors were encountered: