You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
since the last evolutions, editing profile.json files has become more complex, with the management of deployment rules. This requires a mastery of syntax and would benefit from a small graphical editing interface.
manual and laborious plugin listing (id and version in particular)
QGIS' behavior with ini files (write at launch AND close, total write, not incremental) makes it painful to keep track of parameters and changes between different versions of the plugin.
Description
The feature request takes the form of 2 functional tracks:
add an extract command to QDT with a profile name as parameter, so that it generates a profile file ready for committing: profile.json with list of plugins (versions, id, repository...), name, incremented version if the profile has already been edited with the command beforehand, INI files (only lines different from the default version).
We can therefore imagine that QDT has a dedicated folder in its working directory where it stores profiles for editing.
Related links
No response
Use Cases
No response
Visuals
No response
Before submitting
I have verified that my idea is a change request and not a bug report.
The text was updated successfully, but these errors were encountered:
Guts
linked a pull request
Jun 18, 2024
that will
close
this issue
Guts
changed the title
Feature: generate profile.json from existing QGIS profile
Feature: generate profile.json and QDT profile structure from existing QGIS profile
Jun 18, 2024
Context
Findings:
profile.json
files has become more complex, with the management of deployment rules. This requires a mastery of syntax and would benefit from a small graphical editing interface.Description
The feature request takes the form of 2 functional tracks:
extract
command to QDT with a profile name as parameter, so that it generates a profile file ready for committing: profile.json with list of plugins (versions, id, repository...), name, incremented version if the profile has already been edited with the command beforehand, INI files (only lines different from the default version).We can therefore imagine that QDT has a dedicated folder in its working directory where it stores profiles for editing.
Related links
No response
Use Cases
No response
Visuals
No response
Before submitting
The text was updated successfully, but these errors were encountered: