Add support for Data Type

[econchick]

Related roadmap page

• Support for four family types:
  • [ ] object [DOING]
  • [x] property declarations
  • [ ] additional properties
  • [ ] object type specialization
  • [ ] discriminators
  • [ ] scalar
  • [ ] built-in, e.g. string, number, etc [DOING]
  • [x] enums
  • [ ] custom scalars
  • [ ] arrays
  • [ ] external a.k.a JSON & XML (ideally, be forward-thinking to easily add support for additional file types)
• Supported functionality:
  • [ ] User-defined facets
  • [ ] Inheritance
  • [ ] Type Expression
  • [ ] Union types
  • [ ] Examples
  • [ ] Inline declaration
  • [ ] Determine default types
• Data Types support for (aka be able to assign data types to the following):
  • [x] URI Parameters
  • [x] Query parameters
  • [x] Request & Response Headers
  • [x] Request & Response Body
• [ ] Data type validation
• [ ] Documentation
• [ ] Test coverage [DOING]

[tardyp]

I take this bug, can you assign it to me?

[econchick]

@tardyp done! but I think I shouldn't have needed to add you to the spotify org - I just added you as a collaborator, but let me double check sine github org permissions are not that easy to immediately understand.

[sichvoge]

Hi @econchick & @tardyp, not sure what the progress is but the links to the different sections inside the spec are out of date. I also like to offer you as much help as possible from our experts as needed. Let me know.

[tardyp]

Hi Christian, Both myself and @econchick had a very busy second quarter, so this is why this is not progressing as we would like. For my side, I am still very interrested in raml potencial for python webapps, and willing not make it move forward as time allows.

[econchick]

@sichvoge hey Christian!

You're right that the links are outdated - but (FYI @tardyp 😄 ) I have been working on it! and current progress can be seen in the v.0.2.0-dev branch (although I have yet to push latest commits from the past couple of days which really work on this particular ticket).

I've updated this issue with appropriate links (and I will do that for the other issues at some point) and current status of progress.

[dethbird]

I just forked, are the issues you have listed for this repo the only issues to tackle in order to accomplish the upgrade to 1.0?

[sichvoge]

I think @econchick and maybe you should review the todos in this issue, and maybe others with the current spec version.