Skip to content
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

feat: add gamesource layer and node #87

Merged
merged 13 commits into from
Feb 20, 2024
Merged

Conversation

maddygoround
Copy link
Contributor

@maddygoround maddygoround commented Feb 13, 2024

This PR introduces a game source layer to the studio-kit. Additionally, we've performed a cleanup within the studio-kit by removing unused transformers and sources.

[sc-21377]

@maddygoround maddygoround marked this pull request as draft February 13, 2024 06:48
@maddygoround maddygoround changed the title chore: add gamesource layer and node WIP: add gamesource layer and node Feb 13, 2024
Copy link

This pull request has been linked to Shortcut Story #21377: Implement “game source” into studio-kit.

@maddygoround maddygoround marked this pull request as ready for review February 16, 2024 16:35
@maddygoround maddygoround changed the title WIP: add gamesource layer and node feat: add gamesource layer and node Feb 16, 2024
chore: element transformer is needed

fix: add element to index file

chore: add more logging

chore: add more logging

chore: cleanup dublicate code in rtmp source

chore: cleanup code
…diokit source

fix: remove package-lock file from repo
@@ -325,19 +327,4 @@ export interface InternalEventMap {
projectId: LiveApiModel.Project['projectId']
nodeId: SDK.SceneNode['id']
}
// TODO: remove this code after a while when this version of sdk (1.1.58) is adopted by all users
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch!

@@ -96,17 +96,15 @@ export const updateUserProps = async (payload: {
export const createSource = async (payload: {
projectId: string
displayName?: string
address?: Partial<LiveApiModel.SourceAddress>
metadata?: any
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we were moving around allowing users to interface with the metadata property directly, in favor of "props". That way metadata.props is always reserved for renderer properties and we leave the metadata property open for other internal state as needed.

You can see this implementation in addDestination()

Not a big deal, just might be nice to update for consistency

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the clarity; I was missing this information. Luckily, I am creating the property in metadata.props, just trying to follow how it's managed everywhere 😄 : https://github.com/golightstream/api.stream-studio-kit/blob/mahendra/game-source/examples/studio-kit-demo/src/host/host.tsx#L516

@@ -267,105 +258,6 @@ export const prepareInternalEvents = () => {

return
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:)

Copy link
Contributor

@hudbuddy hudbuddy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great

@maddygoround maddygoround merged commit 9b0a846 into main Feb 20, 2024
1 check passed
@maddygoround maddygoround deleted the mahendra/game-source branch February 20, 2024 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants