"Creating a definition file" links to moved content

[brabster]

The link to the article on codeplex.com on http://definitelytyped.org/guides/creating.html points to a page that says the content is moved. I couldn't find the article at all.

[Maxim-Mazurok]

After downloading full archive from CodePlex, I was able to find original Wiki article.
If it's still valid - I can convert it to *.html.md.eco and contribute to this website.
@vvakame what do you think about this?

Here's the original article source:

! Introduction
When using an external JavaScript library, or new host API, you'll need to use a declaration file (.d.ts) to describe the shape of that library. This guide covers a few high-level concepts specific to writing definition files, then proceeds with a number of examples that show how to transcribe various concepts to their matching definition file descriptions.

! Guidelines and Specifics

!! Workflow

The best way to write a .d.ts file is to start from the documentation of the library, not the code. Working from the documentation ensures the surface you present isn't muddied with implementation details, and is typically much easier to read than JS code. The examples below will be written as if you were reading documentation that presented example calling code.

!! Namespacing

When defining interfaces (for example, "options" objects), you have a choice about whether to put these types inside a module or not. This is largely a judgement call -- if the consumer is likely to often declare variables or parameters of that type, and the type can be named without risk of colliding with other types, prefer placing it in the global namespace. If the type is not likely to be referenced directly, or can't be named with a reasonably unique name, do use a module to prevent it from colliding with other types.

!! Callbacks

Many JavaScript libraries take a function as a parameter, then invoke that function later with a known set of arguments. When writing the function signatures for these types, *do not* mark those parameters as optional. The right way to think of this is _"What parameters will be provided?"_, not _"What parameters will be consumed?"_. While TypeScript 0.9.7 and above does not enforce that the optionality, bivariance on argument optionality might be enforced by an external linter.

!! Extensibility and Declaration Merging

When writing definition files, it's important to remember TypeScript's rules for extending existing objects. You might have a choice of declaring a variable using an anonymous type or an interface type:

*Anonymously-typed var*

{code:javascript}
declare var MyPoint: { x: number; y: number; };
{code:javascript}

*Interfaced-typed var*

{code:javascript}
interface SomePoint { x: number; y: number; }
declare var MyPoint: SomePoint;
{code:javascript}

From a consumption side these declarations are identical, but the type {{SomePoint}} can be extended through interface merging:

{code:javascript}
interface SomePoint { z: number; }
MyPoint.z = 4; // OK
{code:javascript}

Whether or not you want your declarations to be extensible in this way is a bit of a judgement call. As always, try to represent the intent of the library here.

!! Class Decomposition

Classes in TypeScript create two separate types: the instance type, which defines what members an instance of a class has, and the constructor function type, which defines what members the class constructor function has. The constructor function type is also known as the "static side" type because it includes static members of the class.

While you can reference the static side of a class using the {{typeof}} keyword, it is sometimes useful or necessary when writing definition files to use the _decomposed class_ pattern which explicitly separates the instance and static types of class.

As an example, the following two declarations are nearly equivalent from a consumption perspective:

*Standard*

{code:javascript}
class A {
    static st: string;
    inst: number;
    constructor(m: any) {}
}
{code:javascript}

*Decomposed*

{code:javascript}
interface A_Static {
    new(m: any): A_Instance;
    st: string;
}
interface A_Instance {
    inst: number;
}
declare var A: A_Static;
{code:javascript}

The trade-offs here are as follows:
* Standard classes can be inherited from using {{extends}}; decomposed classes cannot. This might change in later version of TypeScript if arbitrary {{extends}} expressions are allowed.
* It is possible to add members later (through declaration merging) to the static side of both standard and decomposed classes
* It is possible to add instance members to decomposed classes, but not standard classes
* You'll need to come up with sensible names for more types when writing a decomposed class

!! Naming Conventions

In general, do not prefix interfaces with {{I}} (e.g. {{IColor}}). Because the concept of an interface in TypeScript is much more broad than in C# or Java, the {{IFoo}} naming convention is not broadly useful.

! Examples

Let's jump in to the examples section. For each example, sample _usage_ of the library is provided, followed by the definition code that accurately types the usage. When there are multiple good representations, more than one definition sample might be listed.

!! Options Objects

*Usage*
{code:javascript}
animalFactory.create("dog");
animalFactory.create("giraffe", { name: "ronald" });
animalFactory.create("panda", { name: "bob", height: 400 });
// Invalid: name must be provided if options is given
animalFactory.create("cat", { height: 32 });
{code:javascript}

*Typing*
{code:javascript}
module animalFactory {
    interface AnimalOptions {
        name: string;
        height?: number;
        weight?: number;
    }
    function create(name: string, animalOptions?: AnimalOptions): Animal;
}
{code:javascript}

!! Functions with Properties
*Usage*
{code:javascript}
zooKeeper.workSchedule = "morning";
zooKeeper(giraffeCage);
{code:javascript}

*Typing*
{code:javascript}
// Note: Function must precede module
function zooKeeper(cage: AnimalCage);
module zooKeeper {
    var workSchedule: string;
}
{code:javascript}

!! New + callable methods
*Usage*
{code:javascript}
var w = widget(32, 16);
var y = new widget("sprocket");
// w and y are both widgets
w.sprock();
y.sprock();
{code:javascript}

*Typing*
{code:javascript}
interface Widget {
    sprock(): void;
}

interface WidgetFactory {
    new(name: string): Widget;
    (width: number, height: number): Widget;
}

declare var widget: WidgetFactory;
{code:javascript}

!! Global / External-agnostic Libraries
*Usage*
{code:javascript}
// Either
import x = require('zoo');
x.open();
// or
zoo.open();
{code:javascript}

*Typing*
{code:javascript}
module zoo {
  function open(): void;
}

declare module "zoo" {
    export = zoo;
}
{code:javascript}

!! Single Complex Object in External Modules
*Usage*
{code:javascript}
// Super-chainable library for eagles
import eagle = require('./eagle');
// Call directly
eagle('bald').fly();
// Invoke with new
var eddie = new eagle(1000);
// Set properties
eagle.favorite = 'golden';
{code:javascript}

*Typing*
{code:javascript}
// Note: can use any name here, but has to be the same throughout this file
declare function eagle(name: string): eagle;
declare module eagle {
    var favorite: string;
    function fly(): void;
}
interface eagle {
    new(awesomeness: number): eagle;
}

export = eagle;
{code:javascript}

!! Callbacks
*Usage*
{code:javascript}
addLater(3, 4, (x) => console.log('x = ' + x));
{code:javascript}

*Typing*
{code:javascript}
// Note: 'void' return type is preferred here
function addLater(x: number, y: number, (sum: number) => void): void;
{code:javascript}

Please post a comment [here|https://github.com/Microsoft/TypeScript/issues] if there's a pattern you'd like to see documented! We'll add to this as we can.