Search results

Drop the requirement of the API review?

Status: Open.

#45 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Sep 7, 2017

Clarifying use of schema for documentation, not code generation

Status: Open.

#44 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Aug 25, 2017

add section on the need for api evangelism

Status: Open.

#41 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Jul 21, 2017

Clarify use of GraphQL for mobile app interfaces only when using React/Redux

Status: Open.

#40 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Jun 21, 2017

Add batch API (design) guidance

Status: Open.

#39 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on May 22, 2017

Re-evaluate (in 11/2017) error response formats

Status: Open.

#37 In Haufe-Lexware/api-style-guide;

· chludwig-haufe opened on May 2, 2017

Define API Discovery Format

Status: Open.

#35 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Apr 22, 2017

Explicitly ban snake-syntax

Status: Open.

#34 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Apr 21, 2017

Add hiding of internal codes

Status: Open.

#33 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Apr 20, 2017

Add best practices from QT API guide

Status: Open.

#31 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Mar 25, 2017

Add discussion of idempotency

Status: Open.

#30 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Feb 27, 2017

Add Fielding Property Maps

Status: Open.

#29 In Haufe-Lexware/api-style-guide;

· hlgr360 opened on Feb 27, 2017