Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Splitting CSS/HTML files into generic and custom one #388

Open
ralfsmolarek3 opened this issue Feb 21, 2025 · 2 comments · May be fixed by #398
Open

Splitting CSS/HTML files into generic and custom one #388

ralfsmolarek3 opened this issue Feb 21, 2025 · 2 comments · May be fixed by #398
Assignees
@yurtsevich-sbb
Labels
enhancement New feature or request

Comments

@ralfsmolarek3
Copy link

Description

Split all existing input files in two parts:

  • one containing the default from the extension (default file)
  • one containing the additions from the user (user file)

The default one should be automatically updated with a new version of the extension (if there are any changes)
Add a checkbox to disable the default one (default: false). If selected, the default is deactivated and only the user file is being used.
If both are active, the user-file is at (logically) added after the default-file

Motivation

At this moment the update of the CSS is rather painful. We hope to simplify this for future updates with that feature

Proposed Solution (optional)

see above
@ralfsmolarek3 ralfsmolarek3 added the enhancement New feature or request label Feb 21, 2025
@yurtsevich-sbb yurtsevich-sbb self-assigned this Feb 27, 2025
@yurtsevich-sbb
Copy link
Contributor

@ralfsmolarek3 I suppose this requirement is related only to main CSS, don't see use cases for other configurations

@ralfsmolarek3
Copy link
Author

No, it should apply to all files which can be overridden by the user. Motivation is to simplify updates

yurtsevich-sbb added a commit that referenced this issue Mar 7, 2025
@yurtsevich-sbb
feat: Splitting settings into generic and custom one (where relevant)
0938e1b 
Fixes #388
yurtsevich-sbb added a commit that referenced this issue Mar 7, 2025
@yurtsevich-sbb
feat: Splitting settings into generic and custom one (where relevant)
db3c8c7 
Fixes #388
yurtsevich-sbb added a commit that referenced this issue Mar 8, 2025
@yurtsevich-sbb
feat: Splitting settings into generic and custom one (where relevant)
5720ac0 
Fixes #388
@yurtsevich-sbb yurtsevich-sbb linked a pull request Mar 8, 2025 that will close this issue
feat: Splitting csshtml files into generic and custom one #398
Draft
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yurtsevich-sbb yurtsevich-sbb

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
2 participants
@ralfsmolarek3 @yurtsevich-sbb