-
Notifications
You must be signed in to change notification settings - Fork 27
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.
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
Add button to quickly include all form variables in JSON dump plugin #5070
Merged
robinmolen
merged 3 commits into
master
from
5066-add-possiblity-to-quickly-include-all-form-fields-in-the-data-to-be-sent-for-the-json-dump-registration-backend
Feb 13, 2025
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
.. _developers_frontend_admin_styling: | ||
|
||
Admin styling | ||
============= | ||
Custom styling of admin components can be realized by adding/updating .scss files, | ||
which are located in ``src/openforms/scss``. | ||
|
||
Adding a custom style | ||
--------------------- | ||
The steps below describe how to add custom styling for a component in the admin, with the | ||
help of an example ``div`` component: | ||
|
||
.. code-block:: html | ||
|
||
<div className="json-dump-variables json-dump-variables--horizontal"> | ||
... | ||
</div> | ||
|
||
1. Create a new file called ``_component-file-name.scss`` in ``src/openforms/scss/components/admin``, | ||
where ``component-file-name`` reflects the class name of the component. For example: ``_json-dump-variables.scss`` | ||
|
||
2. Add the custom styling. For example: | ||
|
||
.. code-block:: scss | ||
|
||
.json-dump-variables { | ||
display: flex; | ||
|
||
@include bem.modifier('horizontal') { | ||
align-items: center; | ||
gap: 0.5em; | ||
} | ||
} | ||
|
||
3. To ensure it gets picked up, add an import of the file name (without underscore) to the ``_index.scss`` | ||
file of the parent directory. For example, in ``src/openforms/scss/components/admin/_index.scss``): | ||
|
||
.. code-block:: scss | ||
|
||
... | ||
@import './json-dump-variables'; | ||
... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
10 changes: 10 additions & 0 deletions
10
src/openforms/scss/components/admin/_json-dump-variables.scss
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
@use 'microscope-sass/lib/bem'; | ||
|
||
.json-dump-variables { | ||
display: flex; | ||
|
||
@include bem.modifier('horizontal') { | ||
align-items: center; | ||
gap: 0.5em; | ||
} | ||
} |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking now this might be better placed in Backend -> Admin styling?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No this would be the correct place. (S)CSS is frontend stuff :)
I would suggest moving this to a separate file, instead of added it to the index.rst, just to give some structure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was a bit confused by the definition of frontend here. If you look at the frontend documentation, it only mentions the repos related to the form frontend, not the admin styling. I guess it depends on what is meant exactly by Backend and Frontend here:

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mhh, yeah.. it's a bit confusing.. I assume 'Frontend' contains all things related to frontend code (including the frontend of the open-forms project). I think this is fine, otherwise you can blame me 😉