[pgAdmin4][RM2136] Include "?<intver>" on all routes that are loaded

From: Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: [pgAdmin4][RM2136] Include "?<intver>" on all routes that are loaded
Date: 2018-07-26 12:24:27
Message-ID: CAM9w-_kU0p=sTSr4KTj7QYSfOjNjo6VOmMJqzsAsCExasjbr9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Hackers,

Attached is the patch for RM2136 which will add "?<ver_param>=<ver>" to all
the static files requested and will help in cache busting on upgrading
pgAdmin4.
<ver_param> name is configurable and is present in
config.py-INTERNAL_VERSION_PARAM.
The value <ver> is taken as APP_VERSION_INT (which is updated with every
release).
Setting INTERNAL_VERSION_PARAM value to blank or None will disable the
version param add.
New parameter INTERNAL_VERSION_EXTN (tuple) is also added to specify the
file extensions for which the version param to be added. I have added a few
for now.
Test cases included.

Kindly review.

--
Thanks and Regards,
Aditya Toshniwal
Software Engineer | EnterpriseDB Software Solutions | Pune
"Don't Complain about Heat, Plant a tree"

Attachment Content-Type Size
RM2136.patch application/octet-stream 6.0 KB

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Ashesh Vashi 2018-07-26 16:08:11 pgAdmin 4 commit: 'anyFamilyMember' runs the condition function for all
Previous Message Akshay Joshi 2018-07-25 12:31:24 Re: [pgAdmin4][Patch]: #3412 - Add support for PRIMARY KEY, FOREIGN KEY, indexes, and triggers on partitioned tables for PG 11