Skip to content
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

Swagger ui redesign/standardize default inputs #5379

Conversation

Rody-Kirwan
Copy link
Contributor

Description

Standardize all native inputs to use custom Input component in layout-utils. Minor updates to input styling to reflect UX design spec. Also updated any relevant px values to em or rem where necessary

Motivation and Context

Swagger-UI Redesign

How Has This Been Tested?

  • Tested manually against UX spec,
  • Tested against existing cypress test-suite

Screenshots (if appropriate):

Checklist

My PR contains...

  • No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
  • Dependency changes (any modification to dependencies in package.json)
  • Bug fixes (non-breaking change which fixes an issue)
  • Improvements (misc. changes to existing features)
  • Features (non-breaking change which adds functionality)

My changes...

  • are breaking changes to a public API (config options, System API, major UI change, etc).
  • are breaking changes to a private API (Redux, component props, utility functions, etc.).
  • are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
  • are not breaking changes.

Documentation

  • My changes do not require a change to the project documentation.
  • My changes require a change to the project documentation.
  • If yes to above: I have updated the documentation accordingly.

Automated tests

  • My changes can not or do not need to be tested.
  • My changes can and should be tested by unit and/or integration tests.
  • If yes to above: I have added tests to cover my changes.
  • If yes to above: I have taken care to cover edge cases in my tests.
  • All new and existing tests passed.

Rody Kirwan and others added 30 commits April 25, 2019 15:13
…ult-margins-padding

Reset default text margins, Add updated spacing to information-container, scheme-container
@Rody-Kirwan Rody-Kirwan changed the base branch from master to facelift May 29, 2019 11:04
@Rody-Kirwan
Copy link
Contributor Author

@shockey Seems to be a problem with our branching process...
97 commits (most of which are already merged) being tracked as changes?

@shockey
Copy link
Contributor

shockey commented May 30, 2019

@Rody-Kirwan indeed -- likely because I've been merging PRs by squashing. Try git merge --rebase origin facelift in your feature branch to replay those squash commits on top of it.

@Rody-Kirwan
Copy link
Contributor Author

@shockey Aha! Got ya. Didn't think of that.
Yeah, rebasing was an absolute mess when three of us changing the same files but shouldn't be an issue anymore

@shockey shockey merged commit 214c3dc into swagger-api:facelift May 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants