<p dir="auto">I have few filters in dashboards and until i click on the <strong>Filter button</strong> in sidebar the dashboard data does not load. I have option <strong>Select the first value</strong> checked in one of the filter and unchecking the same loads the data easily.<br>
But i need this selecting the first vale.</p>
<p dir="auto">Any fix for this</p>
<h2 dir="auto">[SIP] Proposal for moving frontend assets to the base of the repo</h2>
<h3 dir="auto">Motivation</h3>
<p dir="auto">Currently frontend assets are embedded in the superset package under <code class="notranslate">superset/assets/</code>, which is symlinked in<code class="notranslate">superset/assets/static</code>. This is really confusing for newcomers to the project as it's unclear why code appears to be duplicated. Additionally this is a UNIX symlink so the link isn't created on Windows machines.</p>
<p dir="auto">Moreover is seems there's code (eg, <code class="notranslate">MANIFEST.in</code>, <code class="notranslate">Dockerfile</code> ) that tries to work around the fact that the entire frontend exists in the superset module and most of these files are not needed during runtime. Things like whitelisting files and removing files after builds are workarounds to the actual issue and only add complexity to the problem.</p>
<h3 dir="auto">Proposed Change</h3>
<ul dir="auto">
<li>Move the frontend code into a top level directory, something like <code class="notranslate">frontend</code> or <code class="notranslate">client</code></li>
<li>Configure webpack to output the built/dist files to <code class="notranslate">superset/assets/dist</code>. This can include the package.json (needed for version info) and any other necessary runtime files.</li>
<li>remove the symlinks.</li>
<li>update build scripts</li>
<li>make sure everything works (local builds, docker builds, python package, CI, etc.)</li>
<li>update documentation.</li>
</ul>
<h3 dir="auto">New or Changed Public Interfaces</h3>
<p dir="auto">[no changes]</p>
<h3 dir="auto">New dependencies</h3>
<p dir="auto">[no changes]</p>
<h3 dir="auto">Migration Plan and Compatibility</h3>
<p dir="auto">No major/breaking changes should be necessary. The bulk of the work would be around making sure no existing builds/scripts break and documentation is updated. Since most of the changes will only be moving files, rebases should be automatic, though this will probably require a lot of existing branches to be rebased.</p>
<h3 dir="auto">Rejected Alternatives</h3>
<ol dir="auto">
<li>Remove the symlink and move everything to <code class="notranslate">superset/static/assets</code> and continue to support the whitelisting in <code class="notranslate">MANIFEST.in</code> and the cleanup in <code class="notranslate">Dockerfile</code> and possibly other places.</li>
<li>Continue to support the current file organization and continue to field questions such as: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="535986551" data-permission-text="Title is private" data-url="https://github.com/apache/superset/issues/8804" data-hovercard-type="issue" data-hovercard-url="/apache/superset/issues/8804/hovercard" href="https://github.com/apache/superset/issues/8804">#8804</a></li>
</ol>