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

Allowing null for links.next #162

Merged
merged 1 commit into from
Nov 5, 2018
Merged

Allowing null for links.next #162

merged 1 commit into from
Nov 5, 2018

Conversation

thekaveman
Copy link
Collaborator

Follow-on to #160

@thekaveman thekaveman added the Schema Implications for JSON Schema or OpenAPI label Nov 3, 2018
@thekaveman thekaveman added this to the 0.2.1 milestone Nov 3, 2018
@hunterowens hunterowens merged commit 9498bbd into 0.2.x Nov 5, 2018
@thekaveman thekaveman deleted the links-next branch November 5, 2018 21:32
hunterowens added a commit that referenced this pull request Dec 4, 2018
* 0.2.1: (61 commits)
  updating release notes for 0.2.x
  fix for required properties in generated schema
  add WIND as a dockless mobility provider (#185)
  add Spin as a dockless mobility provider (#184)
  Reverts PR #146, moving Timestamp change into future release (#180)
  wheels (#177)
  adding info about mailing list. (#175)
  Adding Release guidelines (#147)
  Update providers.csv (#174)
  Add `next` link requirement (#166)
  Add OAauth client_credentials auth guidelines section
  update JUMP provider URL (#164)
  allowing null for links.next (#162)
  Agency vs Provider Clarification. [#148] (#150)
  Add LADOT Guidelines for the Handling of MSP Data (#154)
  allowing for null links properties
  Suggestion: Add Clarification to Propulsion Types
  fix versions
  remove oneOf when required is being added
  regenerate the schemas
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Schema Implications for JSON Schema or OpenAPI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants