text stringlengths 0 1.82k |
|---|
[2059.90 --> 2060.24] you want |
[2060.24 --> 2060.68] to use |
[2060.68 --> 2061.20] a query |
[2061.20 --> 2061.50] string |
[2061.50 --> 2062.02] parameter |
[2062.02 --> 2062.92] called |
[2062.92 --> 2063.34] view, |
[2063.66 --> 2064.18] and the |
[2064.18 --> 2064.56] name can |
[2064.56 --> 2065.24] be either |
[2065.24 --> 2066.12] indexed |
[2066.12 --> 2067.64] or expanded, |
[2068.44 --> 2069.54] then great, |
[2069.72 --> 2070.18] do that. |
[2070.56 --> 2071.88] And in |
[2071.88 --> 2072.50] your controller, |
[2072.62 --> 2072.84] in your |
[2072.84 --> 2073.16] code, |
[2073.54 --> 2074.48] you basically |
[2074.48 --> 2075.00] build a |
[2075.00 --> 2075.78] response using |
[2075.78 --> 2076.30] the view |
[2076.30 --> 2076.94] that you |
[2076.94 --> 2078.04] wanted for |
[2078.04 --> 2079.46] that value |
[2079.46 --> 2079.74] of the |
[2079.74 --> 2080.18] query string. |
[2081.62 --> 2081.92] So, |
[2082.26 --> 2082.76] and that |
[2082.76 --> 2083.62] all gets |
[2083.62 --> 2084.86] also translated |
[2084.86 --> 2085.46] into the |
[2085.46 --> 2085.92] swagger |
[2085.92 --> 2086.86] that gets |
[2086.86 --> 2087.44] generated |
[2087.44 --> 2088.18] as |
[2088.18 --> 2088.86] basically |
[2088.86 --> 2090.32] different |
[2090.32 --> 2094.78] responses |
[2094.78 --> 2095.84] for the |
[2095.84 --> 2096.18] action. |
[2096.74 --> 2096.84] So, |
[2097.20 --> 2097.84] it's all |
[2097.84 --> 2098.38] documented |
[2098.38 --> 2100.52] and you |
[2100.52 --> 2100.90] get also |
[2100.90 --> 2102.14] the benefit |
[2102.14 --> 2103.10] of not |
[2103.10 --> 2103.66] having to |
[2103.66 --> 2104.34] redefine all |
[2104.34 --> 2104.86] those different |
[2104.86 --> 2105.36] media types |
[2105.36 --> 2105.76] every time. |
[2106.06 --> 2106.18] Yeah, |
[2106.20 --> 2106.54] that sounds |
[2106.54 --> 2106.90] brilliant. |
[2107.18 --> 2107.76] And I bet |
[2107.76 --> 2108.12] it's a lot |
[2108.12 --> 2108.56] easier to |
[2108.56 --> 2109.30] document as |
[2109.30 --> 2109.52] well. |
[2109.86 --> 2110.06] Yeah, |
[2110.18 --> 2110.40] yeah, |
[2110.44 --> 2110.68] I mean, |
[2110.72 --> 2111.20] it is. |
[2111.28 --> 2111.52] And I |
[2111.52 --> 2112.04] think people |
[2112.04 --> 2112.82] have a |
[2112.82 --> 2113.24] sort of |
[2113.24 --> 2114.28] instinctive |
[2114.28 --> 2114.86] understanding |
[2114.86 --> 2115.24] of it, |
[2115.30 --> 2115.50] right? |
[2115.58 --> 2116.68] It makes |
[2116.68 --> 2117.12] sense. |
[2117.40 --> 2118.20] If I want |
[2118.20 --> 2118.56] to index |
[2118.56 --> 2118.74] you, |
[2118.86 --> 2119.40] then great. |
[2119.78 --> 2120.32] It's the |
[2120.32 --> 2121.02] same backing |
[2121.02 --> 2121.44] resource, |
[2121.56 --> 2121.76] it's just |
[2121.76 --> 2122.18] different ways |
[2122.18 --> 2122.70] of representing |
[2122.70 --> 2122.92] it. |
[2122.94 --> 2123.02] So, |
[2123.06 --> 2123.24] I don't |
[2123.24 --> 2123.60] think it's |
[2123.60 --> 2124.20] a very |
[2124.20 --> 2124.80] complicated |
[2124.80 --> 2125.98] abstraction |
[2125.98 --> 2127.08] and it |
[2127.08 --> 2127.58] does add |
[2127.58 --> 2127.96] a lot |
[2127.96 --> 2129.48] to the |
[2129.48 --> 2130.54] DSL. |
[2131.02 --> 2131.24] So, |
[2131.38 --> 2131.78] I'd like to |
[2131.78 --> 2132.16] make... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.