Hi all, first of all thanks for putting together such an awesome library!

I believe that some of the Typescript definitions in the library are wrong or incomplete. In the following snippet, TypeScript will yell at you because the definition for PanelSection doesn't include a children prop.

This is from [email protected]:

export interface PanelSectionProps {
    title?: string;
    spinner?: boolean;
}
export declare const PanelSection: FC<PanelSectionProps>;
export declare const PanelSectionRow: FC<>;

I have the following setup for my src/index.tsx file.

import { FC } from 'react'
import { definePlugin, ServerAPI, PanelSection, PanelSectionRow } from 'decky-frontend-lib'

// Create Content component Interface
interface ContentProps {
    api: ServerAPI
}

// Create the Content component
const Content: FC<ContentProps> = ({ api }: ContentProps) => {
    return (
        <PanelSection>
            <PanelSectionRow>
                <div>Some content</div>
            </PanelSectionRow>
        </PanelSection>
    )
}

The typescript error is

Type '{ children: Element; }' has no properties in common with type 'IntrinsicAttributes & PanelSectionProps'.

Are you accepting PRs for these issues?

Hi ya'll,

A question about 'supported' exports from the DFL:

Is there a way to get the steam ID # for the current user? Or a way to get the AppOverview for a given appId? Currently I had to add the following defs to my project:

// FIXME - find a better source for these defs?, I'm hand specifying here
// based on looking at ProtonDB plugin
declare let App: any // used for m_currentUser

declare namespace appStore {
  function GetAppOverviewByGameID(appId: number): AppOverview
}

But I'd like to remove these. Do you want me to send in a PR to export these? I haven't written JS/TS code in a long time so I might just be doing something dumb and you are already exporting them?

🚨 The automated release from the v4-dev branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the v4-dev branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 3.26.0 on branch v4-dev cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=4.0.3 can be published from branch v4-dev.

The following commits are responsible for the invalid release:

• chore(ci): empty commit so semantic-release shuts up (c440fa7)
• chore(ci): empty commit so semantic-release shuts up (4e4859d)
• chore(ci): empty commit so semantic-release shuts up (9579c41)
• chore(ci): add v4-dev to release branches (4dd6afd)
• chore(ci): return of the CI (b092d49)
• fix(*): fixes for jun 26 beta (7e0cb15)
• fix(package): unbreak react (b1e5038)
• chore(package): v4.0.3 (832ad69)
• fix(package): pin react properly (62b454f)
• fix(package): fix ts memes (ea19d62)
• fix(Menu): work around ConfigContext error (9f26209)
• fix(components): forgot one (e6e8c91)
• fix(components): fix missing children prop also remove unnessecary use of tsx (688c747)
• chore(ci): disable on v4 for now (6c1b12b)
• chore(release): 3.26.1 [CI SKIP] (0dfb2ce)
• fix(Field): add children prop (2a78cc0)
• chore(package): ver bump [skip ci] (1716782)
• fix(plugin): shim definePlugin for now [ci skip] (0cd498b)
• chore(plugin): delete (b728d90)
• chore(*): fix version lol (3384d29)
• chore(release): 3.26.0 [CI SKIP] (78c4cdb)
• chore(releaserc): add v4-dev branch (d20659e)
• fix(utils/react): shut it ts (d91f49e)
• chore(*): init v4 package.json and release.yaml (735080f)
• chore(static-classes): add/fix/update css classes (#102) (86e6e4c)
• Dropdown contextMenuPositionOptions prop definition (#104) (46b1d6e)
• chore(*): run prettier (a7635b6)
• feat(*): add v4 webpack api and port everything to it also restructures a bunch (bffd530)
• chore(package): init v4 (9c79187)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch v4-dev with git revert or git reset.

A valid branch could be main or v4-dev.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The repo's currently lacking some documentation in form of a Readme.

having two plugins call wrapReactType on the same element causes the ui to crash

Should also solve Frog's MobX issues.

I discovered this while working on CSSLoader, the only ones I've found that affected my app is that FieldChildren has been replaced with FieldChildrenInner and SliderControlWithIcon was replaced by something unknown.

I'm writing this an issue instead of directly committing mostly because i want to establish some guidelines on how we update these.

The classes are currently changed on Beta, but not Stable.
Should we maintain two sets of classes, one for each update channel? Should we create an abstraction class similar to Navigation?

I'm not exactly sure how to proceed here. Requesting additional advice.

I need on page change event so I can pause the Audio. For some reason, it doesn't destroy if I change the page

This could be useful for e.g. editing the login page.

Is it possible to add colors onto text? I'm talking about headers, names, descriptions, etc.
Usage of such a feature could vary from defining the colors in-text or just by using a sort of setColor method.

Thank you!

Description
Got my steamdeck today and installed deck os 3.4(preview) when I installed decky loader and tried for example the guide plugin it failed to load a page and the overlay was stuck. I restarted the deck and tried the boot animation plugin but after sellecting a video the same thing happened. all I get is a blurred error(as its behind some kind of effect the decky produces for lower graphical layers and its even impossible to press the password to go to desktop mode and restart.

• SteamOS Version: 3.4 or 20221202.101
• Selected Update Channel:Preview

I was trying to access some window variable to use in a plugin when I encountered a never ending warning/error spam in the SharedJSContext due to failed initialization of internal navigators.

Video showing issue while trying to access CEF from remote debugging.

I am on the preview channel of SteamOS and currently have 3.5.13 installed. I rebuilt the latest pre-release version of decky-loader with DFL 3.24.4 (which includes a timeout increase from 100ms to 2000ms). This significantly reduced the amount of warning/error I received, but the internal navigators initialization problem still exists.