<?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: Import path in Developer Q&amp;A Forum</title>
    <link>https://community.dynatrace.com/t5/Developer-Q-A-Forum/Import-path/m-p/201370#M121</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/32376"&gt;@lucas_hocker&lt;/a&gt;&amp;nbsp;, technically speaking, there is no difference between the two imports. Because imports from &lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;@dynatrace/strato-components-preview&lt;/CODE&gt; are re-exports of all other packages like the &lt;STRONG&gt;layout &lt;/STRONG&gt;and so on.&lt;/P&gt;
&lt;P&gt;My personal preference is to use&amp;nbsp;&lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;@dynatrace/strato-components-preview&lt;/CODE&gt;&amp;nbsp;because then you don't have to know the underlined folder names, potentially saving you from headaches if the internal path changes.&lt;/P&gt;</description>
    <pubDate>Tue, 18 Apr 2023 10:29:05 GMT</pubDate>
    <dc:creator>imsingh</dc:creator>
    <dc:date>2023-04-18T10:29:05Z</dc:date>
    <item>
      <title>Import path</title>
      <link>https://community.dynatrace.com/t5/Developer-Q-A-Forum/Import-path/m-p/201365#M120</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Is there a reason to prefer more specific imports&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;@dynatrace/strato-compontents-preview/layouts&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;instead of just&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;@dynatrace/strato-components-preview&lt;/CODE&gt;&lt;SPAN&gt;? It seems either works, but examples tend to use more specific paths. Just wondering if there’s a reason…&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Apr 2023 08:01:11 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Developer-Q-A-Forum/Import-path/m-p/201365#M120</guid>
      <dc:creator>lucas_hocker</dc:creator>
      <dc:date>2023-04-20T08:01:11Z</dc:date>
    </item>
    <item>
      <title>Re: Import path</title>
      <link>https://community.dynatrace.com/t5/Developer-Q-A-Forum/Import-path/m-p/201370#M121</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/32376"&gt;@lucas_hocker&lt;/a&gt;&amp;nbsp;, technically speaking, there is no difference between the two imports. Because imports from &lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;@dynatrace/strato-components-preview&lt;/CODE&gt; are re-exports of all other packages like the &lt;STRONG&gt;layout &lt;/STRONG&gt;and so on.&lt;/P&gt;
&lt;P&gt;My personal preference is to use&amp;nbsp;&lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;@dynatrace/strato-components-preview&lt;/CODE&gt;&amp;nbsp;because then you don't have to know the underlined folder names, potentially saving you from headaches if the internal path changes.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Apr 2023 10:29:05 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Developer-Q-A-Forum/Import-path/m-p/201370#M121</guid>
      <dc:creator>imsingh</dc:creator>
      <dc:date>2023-04-18T10:29:05Z</dc:date>
    </item>
  </channel>
</rss>

