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

chore!: remove refs property from schemas #196

Merged
merged 1 commit into from
Jul 23, 2024
Merged

chore!: remove refs property from schemas #196

merged 1 commit into from
Jul 23, 2024

Conversation

EvanHahn
Copy link
Contributor

This isn't necessary for now, so we can remove it.

refs is still present for Tracks.

Tested this with automated tests and by integrating it into @mapeo/core with a temporary build of this module.

Closes #193.

This isn't necessary for now, so we can remove it.

`refs` is still present for `Track`s.

Tested this with automated tests and by integrating it into
`@mapeo/core` with a temporary build of this module.
@tomasciccola
Copy link
Contributor

Aproved, but wondering, why are we keeping refs on tracks?

@EvanHahn
Copy link
Contributor Author

I don't know much about tracks so I don't know if they're needed. I'll ask.

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.

Remove refs property from observation proto and JSONSchema
2 participants