Age | Commit message (Collapse) | Author |
|
All that is returned as the error type is a string so there's no point
in using a custom error type when we can just have the error type be a
string.
Co-authored-by: Remy Raes <contact@remyraes.com>
|
|
This way none of them are run on main thread and as such if a function
panics, it will only crash that specific thread allowing the rest of the
application to survive.
The only exception is `force_panic()` as its purpose is hard crashing
the application.
From the frontend side of things, `invoke()` is already async, so no
frontend changes are needed.
|
|
Instead of re-implementing existing logic just re-use what we already
have.
|
|
* feat: Enable toggling enabled mods
Co-authored-by: pg9182 <96569817+pg9182@users.noreply.github.com>
* chore: Update leftover comment
Co-authored-by: pg9182 <96569817+pg9182@users.noreply.github.com>
|
|
Simply parses `enabledmods.json`.
In the future we should also opt to check individual mods and compare
with the JSON file.
|
|
|
|
* feat: Backend code to get list of installed mods
For now simply parses `enabledmods.json`.
Note that this file will not be up-to-date if the user just installed a
mod but hasn't launched Northstar yet.
* feat: Empty skeleton page for ModsView
Will be populated later with list of installed mods
* chore: Remove leftover print statement
|
|
* refactor: Add error return type
* style: Auto-format
Only minor changes, did not take over all changes from auto-format.
* refactor: Rename function to get FC version number
To make it more clear which version number we're getting
(FlightCore vs Northstar)
|
|
refactor: Router view
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is more of a hotfix, we should really just use propery regex or
something better instead.
|
|
|
|
|
|
|
|
* refactor: Use result return type for Linux checks
* refactor: Store min required ldd version in const
This way we only need to update a single variable in case min required
version changes.
|
|
* refactor: move updateGamePath method in store mutations
* feat: play button allows game path update
If game path was not found automatically and the user clicks the
play button, FlightCore will ask him to point out his Titanfall2
installation folder.
* refactor: change button text
* feat: display a notification on successful game folder selection
* feat: close permanent notification on successful game folder selection
* fix: allow game launch with UNKNOWN install type on Windows
* feat: set install type to UNKNOWN on manual folder pick
* refactor: update omni-button text when game folder wasn't found
|
|
* refactor: Rename object field
So that is specifically references Northstar
* chore: Add plugin-store as npm dependency
* feat: Persistent storing selected NS release canal
* docs: Add explanation about persistent store
|
|
|
|
Files no longer exist since the UI rewrite
|
|
|
|
* Move release notes to own variable
* Show link in update notification
|
|
* feat: dragging app bar drags the whole app
The data-tauri-drag-region attribute cannot be put on menu bar directly because
it contains elements, so we emulate its behavior with a mousedown listener.
* fix: app cannot be dragged by background container
* fix: type issues
|
|
* feat: Show own version number in settings view
Adds a new field to state that stores FlightCore version number.
Version number is pulled from backend on application launch.
* style: Reorder so that FC version is shown first
* chore: Remove leftover TODO comment
|
|
Remedies the issue that anyone pushing without access to private key
will see their CI fail.
|
|
feat: Enable dev mode directly if in debug mode
|
|
Allows skipping clicking version number 5 times when working on
FlightCore.
Release builds are not in debug mode, so dev mode is still disabled by
default for end-users.
|
|
feat: Initial logic to disable all but core mods
|
|
chore: Remove unused code and dependencies
|
|
instead of encapsulating in template literal
|
|
As requested in review
|
|
In the future, this button should be moved to a "Repair" view. For now
I'm putting it into Dev view for testing.
|
|
|
|
|
|
|
|
Less jarring then receiving an `alert()` as the first thing when opening
FlightCore
|
|
Useful for having different UI between dev and release
|
|
|