<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Proper Typing for API Calls in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397896#M100</link>
    <description>&lt;P&gt;Thank you! Thats pretty nice, but would you guys be interested in doing something like stubs or anything similar. I could probably contribute to that repo quite frequently. People without strict type checking would not even see any changes, while people that actually check types, be able to get nice linting for the output of their functions.&lt;/P&gt;</description>
    <pubDate>Wed, 13 Dec 2023 19:25:52 GMT</pubDate>
    <dc:creator>Eddysanoli</dc:creator>
    <dc:date>2023-12-13T19:25:52Z</dc:date>
    <item>
      <title>Proper Typing for API Calls</title>
      <link>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397892#M96</link>
      <description>&lt;P&gt;Hello! I've been using the API for almost a year now, and one of the things that I really don't like about it, is the fact that it doesn't provide any sort of typing for complex outputs. This makes it hard to guess the shape of the output, although I do know the documentation sort of provides a guide for them. What I have resorted to doing was simply to start creating a bunch of typed dictionaries that specify the structure of different endpoints. &lt;/P&gt;&lt;P&gt;Is there a chance that I could contribute with a stubs package for this? Or something similar? I feel like even though this is not absolutely needed, a bit of typing could go a long way to making the DX better.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 12 Dec 2023 18:06:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397892#M96</guid>
      <dc:creator>Eddysanoli</dc:creator>
      <dc:date>2023-12-12T18:06:47Z</dc:date>
    </item>
    <item>
      <title>Re: Proper Typing for API Calls</title>
      <link>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397893#M97</link>
      <description>&lt;P&gt;Please don't.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Dec 2023 18:54:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397893#M97</guid>
      <dc:creator>matt_uc</dc:creator>
      <dc:date>2023-12-12T18:54:11Z</dc:date>
    </item>
    <item>
      <title>Re: Proper Typing for API Calls</title>
      <link>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397894#M98</link>
      <description>&lt;P&gt;Check out the Open API specification.&lt;BR /&gt;&lt;A href="https://github.com/meraki/openapi" target="_self" rel="nofollow noopener noreferrer"&gt;https://github.com/meraki/openapi&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 07:09:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397894#M98</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2023-12-13T07:09:37Z</dc:date>
    </item>
    <item>
      <title>Re: Proper Typing for API Calls</title>
      <link>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397895#M99</link>
      <description>&lt;P&gt;Why not? lol&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 19:14:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397895#M99</guid>
      <dc:creator>Eddysanoli</dc:creator>
      <dc:date>2023-12-13T19:14:41Z</dc:date>
    </item>
    <item>
      <title>Re: Proper Typing for API Calls</title>
      <link>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397896#M100</link>
      <description>&lt;P&gt;Thank you! Thats pretty nice, but would you guys be interested in doing something like stubs or anything similar. I could probably contribute to that repo quite frequently. People without strict type checking would not even see any changes, while people that actually check types, be able to get nice linting for the output of their functions.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 19:25:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/proper-typing-for-api-calls/m-p/5397896#M100</guid>
      <dc:creator>Eddysanoli</dc:creator>
      <dc:date>2023-12-13T19:25:52Z</dc:date>
    </item>
  </channel>
</rss>

