perf(dashboard): dashboard list endpoint returning large and unnecessary data

[Always-prog]

SUMMARY

The endpoint of the response list returns unnecessary data - css, position_json, and json_metadata. This fields data is large, and loads the network, but it is not used at the frontend, because they are not needed to display the dashboards list.

In my company, there was a problem with this, because our dashboards are large, and getting list of dashboards was taking 2-3 seconds. As soon as we deleted the return of these fields, it began to load instantly.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before

After

Look at the Content Length

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.67%. Comparing base (76d897e) to head (3602f11).
Report is 298 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #29121       +/-   ##
===========================================
+ Coverage   60.48%   83.67%   +23.18%     
===========================================
  Files        1931      518     -1413     
  Lines       76236    37492    -38744     
  Branches     8568        0     -8568     
===========================================
- Hits        46114    31371    -14743     
+ Misses      28017     6121    -21896     
+ Partials     2105        0     -2105     

Flag	Coverage Δ
hive	48.92% <ø> (-0.24%)	⬇️
javascript	?
mysql	77.21% <ø> (?)
postgres	77.32% <ø> (?)
presto	53.53% <ø> (-0.27%)	⬇️
python	83.67% <ø> (+20.18%)	⬆️
sqlite	76.77% <ø> (?)
unit	59.04% <ø> (+1.42%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Always-prog]

@supersetbot org-label

[Always-prog]

@supersetbot orglabel

[mistercrunch]

This looks similar to #28609 (?) @dpgaspar

[john-bodley]

The challenge with this is it's unclear where and how both Superset* and third party applications are using the payload. At the very least this is a breaking change.

* Ideally the Superset frontend would explicitly define which fields it requires so it is evident which fields are actually used by the application. So the non-breaking fix here would be to leave list_columns as is and update the frontend code.