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: Frame now uses FrameMetadata instead of string record #232

Merged
merged 6 commits into from
Mar 7, 2024

Conversation

cnasc
Copy link
Contributor

@cnasc cnasc commented Mar 7, 2024

What changed? Why?
Following on #205, using the generated results within the Frame component. For the time being ValidationResults continues to use the legacy Record<string, string> tag object because it needs to be able to point to the actual tag name rather than the names from FrameMetadata.

Additionally started handling the frame state when posting back to api (part of #146).

Notes to reviewers

How has it been tested?
End-to-end against a-frame-in-100-lines to ensure results were same as before.

@@ -14,40 +15,14 @@ export function Frame() {

const latestFrame = results[results.length - 1];

if (!latestFrame.isValid) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed this because right now it's more useful to fully render the frame even if it is not 100% correct

@Zizzamia Zizzamia merged commit 1b17de1 into main Mar 7, 2024
9 checks passed
@Zizzamia Zizzamia deleted the cjn/frame-refactor branch March 7, 2024 05:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants