-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
refactor: simplify reading dashboard config from a json file #1828
refactor: simplify reading dashboard config from a json file #1828
Conversation
Thanks for opening this pull request!
|
This is only internal, without any changes required for existing deployments? In other words, this does not lead to a breaking change? |
@mtrezza Fortunately it is limited only to this file, but just in case we can restore the nesting and tackle it in the future if needed. |
I think we can keep the reduced nesting of this PR, if we are sure it is only internal. But I see you already reverted it, so we can also go that way 🙂 |
* refactor: simplify reading dashboard config from a json file (#1828) * refactor: simplify reading config from a json file * refactor: restore `data` nesting of config object Co-authored-by: Manuel <5673677+mtrezza@users.noreply.github.com> * docs: fix changelog branch names (#1837) * docs: reword changelog quote * docs: fix release changelog filename Co-authored-by: Damian Stasik <visualfanatic@users.noreply.github.com>
* refactor: simplify reading dashboard config from a json file (#1828) * refactor: simplify reading config from a json file * refactor: restore `data` nesting of config object Co-authored-by: Manuel <5673677+mtrezza@users.noreply.github.com> * docs: fix changelog branch names (#1837) * docs: reword changelog quote * docs: fix release changelog filename Co-authored-by: Damian Stasik <visualfanatic@users.noreply.github.com> Co-authored-by: Damian Stasik <visualfanatic@users.noreply.github.com>
🎉 This pull request has been released in version 3.2.1-alpha.1 |
The label |
* alpha: chore(release): 3.2.1-alpha.1 [skip ci] fix: enabling context menu for read-only cells (parse-community#1844) docs: add info about --dev parameter (parse-community#1842) docs: fix release changelog filename docs: reword changelog quote docs: fix changelog branch names (parse-community#1837) refactor: simplify reading dashboard config from a json file (parse-community#1828)
🎉 This pull request has been released in version 3.2.1-beta.1 |
🎉 This pull request has been released in version 3.2.1 |
* source: (53 commits) chore(release): 3.2.1 [skip ci] chore(release): 3.2.1-beta.1 [skip ci] ci: fix prerelease labels chore(release): 3.2.1-alpha.1 [skip ci] fix: enabling context menu for read-only cells (parse-community#1844) docs: add info about --dev parameter (parse-community#1842) build: merge beta (parse-community#1841) build: merge alpha (parse-community#1840) docs: fix release changelog filename docs: reword changelog quote docs: fix changelog branch names (parse-community#1837) refactor: simplify reading dashboard config from a json file (parse-community#1828) ci: update release branch names chore(release): 3.2.0 [skip ci] feat: add ctrl + arrow key to jump to first/last cell; fix left/right key navigation with hidden columns (parse-community#1827) refactor: upgrade inquirer from 8.1.2 to 8.1.3 (parse-community#1829) refactor: upgrade otpauth from 7.0.5 to 7.0.6 (parse-community#1830) refactor: replace create-react-class with ES6 classes (parse-community#1818) refactor: replace query-string with URLSearchParams (parse-community#1819) docs: fix typo in refactor changelog entry ... # Conflicts: # package-lock.json
New Pull Request Checklist
Issue Description
I replaced
json-file-plus
with a simple file reading function andJSON.parse
.json-file-plus
is no longer maintained, the last update was 4 years ago. There is also no need for JSON manipulation, which made this refactor much easier.After the package was gone there was no longer a need for thedata
property nesting, so I flattened the structure by one level.To improve readability of the changes I suggest to hide whitespace changes.
Approach
TODOs before merging