-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Rename grist-electron to grist-desktop #38
Conversation
Add CLI argument parsing Rename grist-electron to grist-desktop
237136c
to
f4ac13e
Compare
f4ac13e
to
fb23dff
Compare
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.
Thanks @SleepyLeslie ! Looks broadly reasonable. One case of code duplication I'd like to avoid if possible, I suggest something.
ext/app/electron/config.ts
Outdated
|
||
|
||
/** | ||
* Copied from grist-core, since it is unsafe to import core code at this point. |
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.
Oh wow, bluebird, this code must be old. What is the unsafety issue leading to this need for code duplication? Is it the TYPEORM_DATABASE issue? If so, how do you feel about factoring the method you need in grist-core out to a separate file that doesn't import anything awkward? It will be awkward in future to make sure bugfixes/improvements to this method end up going to the two copies.
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.
Thanks for bringing this again to my attention! A closer look suggests that the TYPEORM_DATABASE
issue is an urban myth. I remember testing importing dbUtils before setting up TYPEORM_DATABASE
and it didn't work, but it likely failed for some other reasons as I couldn't reproduce the failure now (and on the base commit as well). I just did more tests and as a conclusion it could be safely dismissed.
Will remove related hacks and comments. My bad for not catching it early on.
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.
Also, I read the dbUtils code, and logically believe that importing it is not supposed to have side effects.
676500d
to
5d9991a
Compare
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.
Thanks for the clean-up! What role does test.db play?
5d9991a
to
7421a49
Compare
Nothing. It slipped into my commit. Removed. |
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.
Thanks @SleepyLeslie !
Successor of #36 with changes related to the config file reverted to keep backwards compatibility.
This includes some miscellaneous changes:
--version