-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
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
Redmine update #10
Redmine update #10
Conversation
Update examples values in JSON and YAML files
- test outputType options - verify deleted issue
0afde15
to
02a2e4b
Compare
"path": "issue.custom_fields", | ||
"originalType": "array", | ||
"items": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jirihofman Since you changed the type from an array to a string, do we still need to keep these items?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need items
anymore but that would need to be handled in the generator. As of now it keeps many other properties there if they are in openAPI specs even though Appmixer doesn't use them.
Definitely a good idea to start removing them in the generator so that our component.json
files are smaller.
What
receive()
outputType
option toIssuesFind
by addingx-connector-pagination
extensionMonday
Some unrelated Monday changes needed here in order to make the CI pass. These changes were merged before CI checks were introduced.
outputType
checks