Reported by @sepehr500 in #25

Currently, if want to fake a string, I do the following

type CourtCase {
  jurisdiction: String @examples(values: ["DFT", "FUR"])
}

This makes the think that values expects it's value to be an array of whatever the property type is. So it would follow, that if the type was the following,

type CourtCase {
  jurisdiction:

Although there is nirum-python-wsgi library, it's difficult to find how to adapt a service implementation to WSGI containers (e.g., Green Unicorn, uWSGI) and finally expose it to HTTP(S).

If the instructions would made, it should be gone to docs/target/python.md file.

I'm submitting a ...

• bug report
• feature request
• support request

General infomration

Prerequisites

• Are you running the latest version?

Description

We have some build warnings.

C:\projects\bacardi\core/js_type_traits.h(54): warning C4244: 'argument': conversion from 'int64_t' to 'double', possible loss of data (compiling source file ..\buil

• Write reproto comments out into the generated code.
• Customize the name of the package for which the generated code should be put in, or if each module should have its own package.
• Follow coding conventions, this will require extending genco.
  • Indentation.
  • Spacing between statements.
  • Best-practices for handling interfaces.
• [ ]

The current documentation for the rule format is wrong https://qface.readthedocs.io/en/latest/extending.html#rule-base-generation, the correct documentation lives in the develop branch but isn't released yet.

To keep the PR #269 focused on "how to contribute to RST as a new user," I have moved @egthomas discussion to here on the discussion/todo to make a release guideline and formalized way of determining authorship. Thus we are following our communication guidelines.

It may not need to go in the readme or be decided with this pull request, but the procedure for generating the Zenodo/DOI citation

There should be a nice table of these somewhere.

The logic of what goes in the primary header vs. extension header is not clear to many people - why are sat spots and star position in the extension header? This was confusing Li Wei and I agree it's confusing so we should better document it.

There is support for primitive type constants/literals (e.g. integers, floats, strings, etc.) as introduced by @jb090979.

This can be used as a base for introducing complex type constants (e.g. arrays, structures, maps, etc.).

As currently implemented, service faults are specifying along with the definition of a failable type, rather than with the operations that raises them.

The pros and cons of these approaches, and the resulting design decision, should be explicitly documented. If necessary, the IDL definition and generators should be adapted.