{"action":"created","issue":{"url":"https://api.github.com/repos/swagger-api/swagger-editor/issues/1704","repository_url":"https://api.github.com/repos/swagger-api/swagger-editor","labels_url":"https://api.github.com/repos/swagger-api/swagger-editor/issues/1704/labels{/name}","comments_url":"https://api.github.com/repos/swagger-api/swagger-editor/issues/1704/comments","events_url":"https://api.github.com/repos/swagger-api/swagger-editor/issues/1704/events","html_url":"https://github.com/swagger-api/swagger-editor/issues/1704","id":307089129,"number":1704,"title":"Improve Validation Rendering","user":{"login":"webron","id":241629,"avatar_url":"https://avatars0.githubusercontent.com/u/241629?v=4","gravatar_id":"","url":"https://api.github.com/users/webron","html_url":"https://github.com/webron","followers_url":"https://api.github.com/users/webron/followers","following_url":"https://api.github.com/users/webron/following{/other_user}","gists_url":"https://api.github.com/users/webron/gists{/gist_id}","starred_url":"https://api.github.com/users/webron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/webron/subscriptions","organizations_url":"https://api.github.com/users/webron/orgs","repos_url":"https://api.github.com/users/webron/repos","events_url":"https://api.github.com/users/webron/events{/privacy}","received_events_url":"https://api.github.com/users/webron/received_events","type":"User","site_admin":false},"labels":[{"id":96783396,"url":"https://api.github.com/repos/swagger-api/swagger-editor/labels/type:%20enhancement","name":"type: enhancement","color":"f9d0c4","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-03-21T00:52:10Z","updated_at":"2018-04-30T22:32:44Z","closed_at":null,"author_association":"OWNER","body":"<!---\r\nThanks for filing an issue 😄 ! Before you submit, please read the following:\r\n\r\nSearch open/closed issues before submitting since someone might have asked the same thing before!\r\n\r\nIssues on GitHub are only related to problems of Swagger-Editor itself. We'll try to offer support\r\nhere for your use case, but we can't offer help with projects that use Swagger-UI indirectly,\r\nlike Springfox or swagger-node.\r\n\r\nIf your issue has to do with the right-hand side of the Editor, you're likely talking about\r\nSwagger-UI. Please file your issue there instead: https://github.com/swagger-api/swagger-ui/issues/new\r\n\r\nLikewise, we can't accept features or bugs within the Swagger/OpenAPI specifications themselves,\r\nor anything that violates the specifications.\r\n\r\n-->\r\n\r\n<!--- Provide a general summary of the issue in the title above -->\r\n\r\n\r\n| Q                                   | A\r\n| ----------------------------------- | -------\r\n| Bug or feature request?             | Enhancement \r\n| Which Swagger/OpenAPI version?      | Any\r\n| Which Swagger-Editor version?       | Any\r\n| How did you install Swagger-Editor? | N/A\r\n| Which browser & version?            | N/A\r\n| Which operating system?             |  N/A\r\n\r\n\r\nCurrently, the validation errors are displayed directly on the right panel (swagger-ui). This is very distracting and blocks the view of the documentation.\r\n\r\nThe goal is to move the validation information to a collapsible panel at the bottom of the editor pane.\r\n\r\n#### UX/UI Design Changes & Updated Design Rule Request\r\n1. Double-clicking an Error or Warning in the Validation Panel navigates the editor to that line.\r\n2. When the definition is navigated to the line, the line should be highlighted.\r\n3. The cursor goes to the exact point of where the error begins in the API definition.\r\n4. We should have classifications of 'errors' (Errors & Warnings).\r\n5. The validations panel should be able to resize bigger/smaller & fully collapse.\r\n6. When user collapses the validation panel and then reopens, panel should reopen at the last size that the user expanded or contracted the panel to be.\r\n7. The user can Open/Close the validation panel by clicking on the ( x INVALID) icon or anywhere on the collapsed panel row.\r\n8. When an error is 'fixed' and no longer exists, Error should be automatically removed from the list as well as the code indications that there is no longer an error/warning existing. User should be able to compare the error/warning list with the code as they are making changes and watch the error disappear from the list. Important for the validation panel to be static as I edit so that I can see the error go away.\r\n9. Line numbers should be a different color in case of an Error/Warning.\r\n10. When user mouses over error/warning line number, show a tooltip of error/warning.\r\n11. Line error/warning number color should move WHEN CODE lines move.\r\n13. Line number tooltips should not cover the line but rather show above or below so the user can compare the error to the line of code.\r\n15. Errors are triggered for a line *once the user cursor is onto a different line after a slight delay of 1-2 secs.\r\n16. When the script is Valid (No Errors or Warnings) the Validations panel does not open, it should stay collapsed when clicked on or user attempts to expand.\r\n17. Improve spacing in the gutter so that error/warning icons ALL align no matter how many digits the line number is. Possibly build numbers to the right opposed to the left where the line number cuts into the gutter space.\r\n\r\n#### UI Mock\r\n![image](https://user-images.githubusercontent.com/241629/37690304-a4f8bfc2-2c6f-11e8-921d-e730413886e7.png)\r\n"},"comment":{"url":"https://api.github.com/repos/swagger-api/swagger-editor/issues/comments/385548669","html_url":"https://github.com/swagger-api/swagger-editor/issues/1704#issuecomment-385548669","issue_url":"https://api.github.com/repos/swagger-api/swagger-editor/issues/1704","id":385548669,"user":{"login":"webron","id":241629,"avatar_url":"https://avatars0.githubusercontent.com/u/241629?v=4","gravatar_id":"","url":"https://api.github.com/users/webron","html_url":"https://github.com/webron","followers_url":"https://api.github.com/users/webron/followers","following_url":"https://api.github.com/users/webron/following{/other_user}","gists_url":"https://api.github.com/users/webron/gists{/gist_id}","starred_url":"https://api.github.com/users/webron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/webron/subscriptions","organizations_url":"https://api.github.com/users/webron/orgs","repos_url":"https://api.github.com/users/webron/repos","events_url":"https://api.github.com/users/webron/events{/privacy}","received_events_url":"https://api.github.com/users/webron/received_events","type":"User","site_admin":false},"created_at":"2018-04-30T22:32:44Z","updated_at":"2018-04-30T22:32:44Z","author_association":"OWNER","body":"1. Great question. Will have to get back to you on that.\r\n2. Should be available, yes.\r\n3. I believe the main concern is first to get to the correct line. This is the current behavior, expect when the errors point to the wrong line.\r\n4. It's asking for both.\r\n5. Do you mean 13? Doesn't make sense with 15.\r\n\r\nItem 17 doesn't exist! Is that means to be 15?"}}
{"actor":{"display_login":"webron"}}