Release/14.1.0 - Extension Data #470
Open
Conversation
This file contains hidden or 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
refactor: Huge changes to right sidebar to allow flexibility
refactor: Various lint cleanup. Will need to do more later.
… useEffect lint warns
colin969
force-pushed
the
release/14.1.0
branch
from
d2f726d to
9f33bcc
Compare
fix: Various state fixes for Logs page fix: Fixed logs page source dropdown
refactor: Migrate Footer to functional component
refactor: More memo cleanup
feat: Logos and screenshots paths now stored in Game table
feat: Ruffle embed for NG runs
feat: Add Launcher Embed Ruffle option
refactor: Cleaner ruffle embed
fix: Make watch() work for exts fix: Make sure Ruffle embed uses NGA sizing when available
…ering feat: Added DropdownFrame component for custom dropdown content like previous Dropdown had feat: Exposed Dropdown and DropdownFrame to exts
…pdowns being in a stacking context feat: Expose DropdownCheckboxRow (like logs page) and DropdownStringRow components to ext feat: Add closeDropdown() to Dropdown row props fix: Properly center the arrow in Dropdown buttons
refactor: Remove outdated devScripts contribs
fix: System ext path being wrong in browser mode refactor: Remove outdated extension curationTemplate system fix: Shift selection in Curate
test: Add backend server mock support for testing
test: Prevent socket connection retries
feat: ThemeProvider for updating theme based on application state instead of purely in callbacks fix: Issues with rendered themes sometimes becoming out of sync, hopefully fix: Selecting no theme not working
…ion state feat: core.css and fancy.css changes during dev are applied without a window reload refactor: Improve ThemeProvider readability refactor: Replace fs.watch with chokidar in FolderWatcher for more consistent behaviour across different operating systems fix: Wait for new theme css to load before unloading old to prevent flickering fix: Prevent file reads flagging FolderWatcher change events
refactor: Stripped out unused 'installed' flag
…d --browser-mode-url startup arguments refactor: Replaced bespoke argument parsing with node:util's parseArgs fix: Properly set isDev value in renderer refactor: Minify renderer in production refactor: Only use perf plugin in development
…ost available fix: Remaining linting issues fix: Reimplement FPFSS auth requests from backend ext
…ard and save refactor: Use prop provided view for RightBrowseSidebar and remove explicit game and playlist passes eslint: Added rule to mark as error /src files importing runtime modules meant for extensions refactor: Allow browser frontend to start before app is ready, it'll wait on connection screen anyway
ext: Expose various Config page components ext: Expose setExtConfigValue
refactor: Minimized frequency of preference updates sent refactor: Let clients apply partial preference updates instead of sending the entire state from back each time refactor: Little bits of maintenance on older backend code
…runners fix: Hide all ! prefix views from browse header buttons fix: Explicit check in create and rename for ! prefix fix: Highlight non-Browse header buttons regardless of additional pathnames
…aDownloaded makes a changes
refactor: Replace theme numbers with theme uuids for better cache avoidance
feat: Add showRightSidebar to CustomRoute, default false refactor: Sort custom route header items alphabetically by title
refactor: Forcefully resolve game path to absolute path during execution
refactor: Remove all references to GameData 'Path' as we shift to building it from scratch each time
refactor: Add an easy use error dialog to most user-initiated API errors
fix: Pathing issue when resolving data pack in makeCurationFromGame fix: Make context menu use same code as right sidebar for initiating fpfss edits fix: Remove outdated http proxying rules getting in the way of local fpfss dev
…g info sent to frontend fix: Dumb screenshot path issue mapping fpfss games
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A fairly large update to allow extensions to work with their own data for games.
May be in this state for a while as it matures and docs get written.
Extensions can now: