UNPKG

@tsed/common

Version:

A TypeScript Framework on top of Express

github.com/TypedProject/tsed/tree/production/packages/common

TypedProject/tsed

129 lines (128 loc) • 6.28 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
/** * This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs). * * This method is extremely useful for mapping “global” logic for specific path prefixes or arbitrary matches. * For example, if you placed the following route at the top of all other route definitions, it would require that * all routes from that point on would require authentication, and automatically load a user. * Keep in mind that these callbacks do not have to act as end points; loadUser can perform a task, then call next() * to continue matching subsequent routes. * @param path * @param args * @returns {Function} * @decorator * @operation * @httpMethod */ export declare function All(path?: string | RegExp | any, ...args: any[]): Function; /** * This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs). * * This method is extremely useful for mapping “global” logic for specific path prefixes or arbitrary matches. * For example, if you placed the following route at the top of all other route definitions, it would require that * all routes from that point on would require authentication, and automatically load a user. * Keep in mind that these callbacks do not have to act as end points; loadUser can perform a task, then call next() * to continue matching subsequent routes. * @param path * @param args * @returns {Function} * @decorator * @operation * @httpMethod */ export declare function Get(path?: string | RegExp | any, ...args: any[]): Function; /** * This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs). * * This method is extremely useful for mapping “global” logic for specific path prefixes or arbitrary matches. * For example, if you placed the following route at the top of all other route definitions, it would require that * all routes from that point on would require authentication, and automatically load a user. * Keep in mind that these callbacks do not have to act as end points; loadUser can perform a task, then call next() * to continue matching subsequent routes. * @param path * @param args * @returns {Function} * @decorator * @operation * @httpMethod */ export declare function Post(path?: string | RegExp | any, ...args: any[]): Function; /** * This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs). * * This method is extremely useful for mapping “global” logic for specific path prefixes or arbitrary matches. * For example, if you placed the following route at the top of all other route definitions, it would require that * all routes from that point on would require authentication, and automatically load a user. * Keep in mind that these callbacks do not have to act as end points; loadUser can perform a task, then call next() * to continue matching subsequent routes. * @param path * @param args * @returns {Function} * @decorator * @operation * @httpMethod */ export declare function Put(path?: string | RegExp | any, ...args: any[]): Function; /** * This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs). * * This method is extremely useful for mapping “global” logic for specific path prefixes or arbitrary matches. * For example, if you placed the following route at the top of all other route definitions, it would require that * all routes from that point on would require authentication, and automatically load a user. * Keep in mind that these callbacks do not have to act as end points; loadUser can perform a task, then call next() * to continue matching subsequent routes. * @param path * @param args * @returns {Function} * @decorator * @operation * @httpMethod */ export declare function Delete(path?: string | RegExp | any, ...args: any[]): Function; /** * This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs). * * This method is extremely useful for mapping “global” logic for specific path prefixes or arbitrary matches. * For example, if you placed the following route at the top of all other route definitions, it would require that * all routes from that point on would require authentication, and automatically load a user. * Keep in mind that these callbacks do not have to act as end points; loadUser can perform a task, then call next() * to continue matching subsequent routes. * @param path * @param args * @returns {Function} * @decorator * @operation * @httpMethod */ export declare function Head(path?: string | RegExp | any, ...args: any[]): Function; /** * This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs). * * This method is extremely useful for mapping “global” logic for specific path prefixes or arbitrary matches. * For example, if you placed the following route at the top of all other route definitions, it would require that * all routes from that point on would require authentication, and automatically load a user. * Keep in mind that these callbacks do not have to act as end points; loadUser can perform a task, then call next() * to continue matching subsequent routes. * @param path * @param args * @returns {Function} * @decorator * @operation * @httpMethod */ export declare function Patch(path?: string | RegExp | any, ...args: any[]): Function; /** * This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs). * * This method is extremely useful for mapping “global” logic for specific path prefixes or arbitrary matches. * For example, if you placed the following route at the top of all other route definitions, it would require that * all routes from that point on would require authentication, and automatically load a user. * Keep in mind that these callbacks do not have to act as end points; loadUser can perform a task, then call next() * to continue matching subsequent routes. * @param path * @param args * @returns {Function} * @decorator * @operation * @httpMethod */ export declare function Options(path?: string | RegExp | any, ...args: any[]): Function;