text stringlengths 0 1.82k |
|---|
[1822.52 --> 1822.92] express in |
[1822.92 --> 1823.46] Swagger in |
[1823.46 --> 1824.08] a DSL. |
[1825.26 --> 1825.62] Actually, |
[1825.80 --> 1826.04] the first |
[1826.04 --> 1829.00] inspiration was |
[1829.00 --> 1829.78] JSON schema. |
[1830.28 --> 1830.78] I don't know |
[1830.78 --> 1831.08] if you're |
[1831.08 --> 1831.64] familiar with |
[1831.64 --> 1832.58] how Heroku |
[1832.58 --> 1834.66] document their |
[1834.66 --> 1835.28] APIs, but |
[1835.28 --> 1835.62] they use |
[1835.62 --> 1836.46] JSON schema |
[1836.46 --> 1837.02] this kind |
[1837.02 --> 1837.96] of recursive |
[1837.96 --> 1839.06] JSON schema |
[1839.06 --> 1839.62] to describe |
[1839.62 --> 1840.62] all of their |
[1840.62 --> 1841.18] APIs. |
[1842.48 --> 1842.82] And so that |
[1842.82 --> 1843.20] was kind of |
[1843.20 --> 1843.72] the initial |
[1843.72 --> 1844.88] inspiration for |
[1844.88 --> 1845.94] the abstractions |
[1845.94 --> 1846.44] in the design |
[1846.44 --> 1846.86] language. |
[1847.60 --> 1848.44] But then it |
[1848.44 --> 1848.86] so happened |
[1848.86 --> 1849.68] that Swagger |
[1849.68 --> 1850.64] is also using |
[1850.64 --> 1851.26] JSON schema |
[1851.26 --> 1851.96] for a lot |
[1851.96 --> 1852.50] of their |
[1852.50 --> 1854.48] representation |
[1854.48 --> 1855.78] of what |
[1855.78 --> 1856.14] they call |
[1856.14 --> 1857.22] the path |
[1857.22 --> 1857.64] object. |
[1858.40 --> 1858.82] And so |
[1858.82 --> 1859.96] that mapping |
[1859.96 --> 1860.92] was very |
[1860.92 --> 1861.70] easy to do |
[1861.70 --> 1862.66] and it |
[1862.66 --> 1863.36] just was |
[1863.36 --> 1863.72] sort of |
[1863.72 --> 1864.16] natural. |
[1865.04 --> 1865.60] So, yeah, |
[1865.60 --> 1865.94] I think |
[1865.94 --> 1866.34] it's great |
[1866.34 --> 1867.02] too because |
[1867.02 --> 1867.86] that means |
[1867.86 --> 1868.28] that people |
[1868.28 --> 1868.86] that already |
[1868.86 --> 1869.44] know Swagger |
[1869.44 --> 1870.26] are already |
[1870.26 --> 1870.92] used to |
[1870.92 --> 1871.86] thinking about |
[1871.86 --> 1872.54] design of |
[1872.54 --> 1873.84] APIs will |
[1873.84 --> 1874.62] feel right at |
[1874.62 --> 1874.86] home. |
[1875.10 --> 1876.12] They will have |
[1876.12 --> 1876.60] to deal with |
[1876.60 --> 1876.94] the same |
[1876.94 --> 1877.74] abstractions that |
[1877.74 --> 1878.10] they already |
[1878.10 --> 1878.42] know. |
[1879.42 --> 1880.06] And actually, |
[1880.20 --> 1880.94] I think an |
[1880.94 --> 1881.42] interesting |
[1881.42 --> 1883.82] project or |
[1883.82 --> 1884.36] add-on that |
[1884.36 --> 1885.00] could be done |
[1885.00 --> 1886.30] with Goa |
[1886.30 --> 1887.16] is a tool |
[1887.16 --> 1887.46] that would |
[1887.46 --> 1888.12] take the |
[1888.12 --> 1888.50] Swagger |
[1888.50 --> 1889.14] definition |
[1889.14 --> 1889.76] specification |
[1889.76 --> 1890.60] and generate |
[1890.60 --> 1892.02] so that the |
[1892.02 --> 1892.90] Goa DSL |
[1892.90 --> 1893.30] kind of go |
[1893.30 --> 1893.54] the other |
[1893.54 --> 1894.02] way around. |
[1894.30 --> 1895.68] So, if you |
[1895.68 --> 1896.06] write the Goa |
[1896.06 --> 1896.44] DSL, you |
[1896.44 --> 1896.90] get Swagger. |
[1897.10 --> 1897.40] It would be |
[1897.40 --> 1897.96] also interesting |
[1897.96 --> 1898.58] if you had |
[1898.58 --> 1899.04] Swagger to |
[1899.04 --> 1899.58] be able to |
[1899.58 --> 1900.00] go to a |
[1900.00 --> 1900.66] Goa DSL |
[1900.66 --> 1901.36] because then |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.