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

Discussion of Transcript Component Architecture #503

Open
2 tasks
joncameron opened this issue May 21, 2024 · 1 comment
Open
2 tasks

Discussion of Transcript Component Architecture #503

joncameron opened this issue May 21, 2024 · 1 comment

Comments

@joncameron
Copy link
Contributor

Description

Changing the Transcript Component Architecture:
Does the Transcript component need to retain independence? If so, we may need to change code; Patrick has pulled the component under the overall state which will complicate standalone usage. We should have a discussion on this: what are our needs? Do we need to keep it any particular way? Ideally it would be possible to use the Transcript component independently.

Done Looks Like

  • Discussion of how to approach Transcript component architecture
  • Develop proposal for changing the architecture to make sure the Transcript component can be used independently of other Ramp components
@joncameron
Copy link
Contributor Author

Could be discussed in the future after the Ramp refactor.

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

No branches or pull requests

1 participant