-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Issues Saving Changes #123
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
Comments
screenshot with chrome dev tools: https://s3.amazonaws.com/uploads.hipchat.com/41195/902644/6NSwvihCTQIXOBG/Screen%20Shot%202014-09-02%20at%205.58.44%20PM%20%282%29.png |
What are steps to reproduce? Delete |
@mohsen1 yes that seems to be the step to reproduce |
@jwest-apigee 0e1c06f should've fixed it already. I just pushed a new build to npm. Please close this issue if it's not happening anymore. |
refactor(editor): rename scss index files to _all
…agger-api#98) * Tests for swagger-api#96. * Fix: swagger-api#96. Use @context to resolve @type. * See: swagger-api#63. About nested @context. * Fix: swagger-api#31. Resolve $ref'd contexts. * Don't show array/items in properties. * Remove unused variables. * Show semantic properties of . * Basic working solution, with regressions. * Use slice. Never use splice. * Fix: swagger-api#122. Resolve 'd contexts. (swagger-api#123) * Don't resolve jsonld keywords. * Fix jsonld type resolver. --------- Co-authored-by: Stefano Baruzzo <[email protected]>
Not sure how else to capture this effectively aside from screenshot. It seems the 'working...' --> 'all changes saved' hook is not always working?
The text was updated successfully, but these errors were encountered: