| Age | Commit message (Collapse) | Author |
|---|
|
Instead of deserializing into a generic serde struct and then extracting
specific value from it, deserialize directly into the struct we want.
|
|
|
|
Simply run cmd with `start "" "PATH/TO/NORTHSTAR_EXE"`
Co-authored-by: ASpoonPlaysGames <66967891+ASpoonPlaysGames@users.noreply.github.com>
Co-authored-by: ASpoonPlaysGames <66967891+ASpoonPlaysGames@users.noreply.github.com>
|
|
* feat: Expose installed NS mod directory
This allows other functions to get a mod directory directly which is
useful for e.g. deleting a mod.
* refactor: Return vector of NorthstarMod
instead of unnamed Tuples
|
|
For this we first rebuild the `enabledmods.json` file. This ensures that
all installed mods are actually listed there.
The function was originally created before we could rebuild
`enabledmods.json` by checking installed mods.
|
|
Makes it easier to update/re-use in the future
Co-authored-by: Remy Raes <contact@remyraes.com>
|
|
|
|
Now using a library instead of calling a PowerShell command should
prevent the PowerShell window from opening.
|
|
* feat: Threshold before showing update notification
This way we don't spam the end-user with an update notification before
an update is fully build and released
* fix: Push missing dependencies
* fix: Adjust delay to 2 hours
|
|
* refactor: Remove Origin running check in frontend
We already perform the check in the backend. Frontend does not check for
OS and as such on Linux will just always tell you that Origin is not
running.
* feat: Show notification toast, not alert pop-up
* refactor: Perform OS check before Origin check
|
|
|
|
* feat: Rebuild enabledmods.json if value not found
When toggling a mod on enabled mods that is not present in
`enabledmods.json` we would previously just error out. Now we rebuild
the `enabledmods.json` file in a Northstar compatible format and then
toggle the mod in question.
* feat: Handle missing or corrupted enabledmods.json
* chore: Remove leftover print statement
|
|
* feat: Option to launch NS bypassing update check
Hidden behind dev view
* refactor: Use existing function to launch NS
Instead of duplicating code
* feat: Adjust button to allow bypassing all checks
|
|
This way we only define them in one place
|
|
and change them to R2NorthstarTools org
|
|
Getting log files is part of repair and troubleshooting
|
|
|
|
* refactor: Rename function
to better differentiate what it does
* refactor: Add TS mod string field to NS mod struct
This allows us to expose to frontend which Thunderstore mod a Northstar
mod may belong to. Field is optional as not all mods may contain a
Thunderstore mod string for example when they were installed manually.
* feat: Add TS mod string field to NS mod interace
* feat: Parse TS mod string and expose to frontend
* fix: Mark unused variable as such
|
|
* feat: Initial support for installing mods from TS
This is the basic code needed to install a mod from Thunderstore
* refactor: Remove console log, show msg in notif
Instead of console logging result message, show it in notification
instead.
* refactor: Rename function to indicate behaviour
Function not only installs but also downloads mod first.
Although it does remove downloaded zip post installation.
* refactor: Move install logic to dedicated module
`mod_management` module didn't exist when this PR was created
* chore: Trim single leftover newline
* fix: Update code for newer `libthermite` version
* feat: Allow installing older versions of mods
Installs the given version number instead of only allowing latest.
* fix: Explicit error msg for installing NS as mod
While it would fail during install anyway, having explicit error message
is nicer
* feat: Write TS mod string to mod.json
Write Thunderstore mod string of installed mod to its `mod.json`
This way we can later check whether a mod is outdated based on the
Thunderstore mod string
* fix: Early return on empty string
Prevent trying to install the first mod that matches an early string. We
should never pass an empty string in the first place but better safe
then sorry.
* build: Add dependency for recursive async
Needed for recursive mod dependency install
* feat: Recursively install mod dependencies
* fix: Early catch installing R2modman as mod
Just in case to prevent someone trying to install R2modman as a mod.
* refactor: Remove debug prints
* fix: Allow installing mods having NS as dependency
They would previously error out as Northstar cannot be installed as
dependency. We now catch that specific error and return Ok(())
* fix: Delete download folder after mod install
Deletes download folder after mod install if non-empty.
* fix: Do not early leave when dependency is NS
Logic error, instead of skipping installing Northstar as dependency it
would previously just return early with success.
* chore: Remove leftover commented out code
|
|
* refactor: Import all functions from lib
So that I don't need to update the header each time I add/remove a
function.
* refactor: Move function to submodule
Move it to module for GitHub API related tasks.
* refactor: Re-use existing func for fetching GH API
|
|
|
|
Some mods have comments in their JSON. Northstar handles it fine, so we
should too.
|
|
So that it can be re-used by other functions later such as for checking
newest FlightCore version by checking against GitHub releases.
|
|
as opposed to using an empty string to indicate an error.
|
|
* feat: Parse actually installed mods
Instead of using solely `enabledmods.json` parse the `mod.json` of found
mods in `mods` folder.
* refactor: Remove leftover print statements
* refactor: Move logic into dedicated module
* fix: Load mods despite `enabledmods.json` missing
Previously we would error out early if `enabledmods.json` was missing
despite not actually needing it for mod list.
* style: Autoformat
|
|
* feat: add Rust method to fetch Northstar release notes
* feat: fetch release notes on changelog view mount
* feat: only transmit some info to frontend
GitHub API gives much information about releases, we only need some: name,
publication date and content of such release; so other information is not
transmitted to UI.
* feat: add ReleaseInfo Typescript interface matching Rust struct
* feat: display release notes on a timeline
* refactor: remove old releases external link
* build: add marked dependency
* build: add marked types dev dependency
* feat: format release notes' markdown
* fix: member typo in ReleaseInfo interface
* fix: type releases array
* fix: open github links in external browser
* fix: adjust marked import
* refactor: store release notes in store
Release notes are now stored in the app store, so we don't have to
fetch them multiple times.
* fix: notes fetching method is now async
* feat: display a loading bar while release notes are being fetched
* feat: display dates in white
* feat: release notes' dates are human-readable
* fix: make menu bar appear on top of release notes view when scrolled
* feat: add custom scrollbar
* refactor: format releases creation to please reviewer
* Update src-tauri/src/github/mod.rs
* Update src-tauri/src/github/release_notes.rs
* Update src-vue/src/utils/ReleaseInfo.d.ts
* fix: augment scrollbar opacity
* fix: only display releases' release date (no more time of the day)
* fix: adjust Github request user agent
* style: add missing end line in src-vue/src/style.css
* fix: link formatting only targets GitHub PR links (whose name begins with a #)
* fix: timeline element children cannot be bigger than container card
|
|
Only a single function for now as a sort of proof-of-concept.
|
|
|
|
Set the function to async but it was still using blocking version of
reqwest.
|
|
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: 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)
|
|
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
|
|
|
|
Useful for having different UI between dev and release
|
|
Should help with fixing a Northstar install in the case of conflicting
mods.
|
|
|
|
|
|
|
|
|
|
Once done, should help with some tickets.
|
|
|
|
when building
|
|
|
|
|
|
|
