-
Bug
-
Resolution: Obsolete
-
Major
-
None
(Migrated from https://github.com/syndesisio/syndesis/issues/3459)
Author: @mcada
Assignees: Daniel Florian, @mmajerni,
This is a...
[!-- Check ONLY one of the following options with "x" --]
[pre][code]
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report [!-- Please search GitHub for a similar issue or PR before submitting --]
[ ] Documentation issue or request
[/code][/pre]
[!-- If possible, please choose the appropriate labels for your issue. You find a description of all
labels used at https://doc.syndesis.io/#dev-labels --]
The problem
[!--
Briefly describe the issue you are experiencing (or the feature you want to see implemented on Syndesis).
+ For BUGS, tell us what you were trying to do and what happened instead.
+ For NEW FEATURES, describe the User Persona demanding it and its use case.
--]
When adding custom API connector and editing it in apicurio, operation numbers are refreshed, but warnings are not.
Expected behavior
[!-- Describe what the desired behavior would be, enlistin gthe acceptance criteria. --]
Warnings from apicur gui should be propagated out when saved
Screenshot
[!--
For features/bugs tackling with UI functionality, drag and drop a screenshot depicting the desired presentation layer or supporting the UX narrative for the new functionality.
--]
!screenshot_20180827_125204
Tasks involved / Steps to Reproduce
[!--
Enlist all the acceptance criteria for new features or the steps required to reproduce the bug/regression reported.
--]
1. From customization page update an OpenAPI file with warnings
2. Go next and click review/edit button to open apicurio gui
3. Solve at least one warning and save, you will be returned to overview page
4. Note that warnings number was not updated