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

fix: remove normalized spec from schema #6965

Merged
merged 2 commits into from
Nov 15, 2020
Merged

Conversation

domoritz
Copy link
Member

@domoritz domoritz requested review from kanitw and a team October 19, 2020 02:55
@domoritz
Copy link
Member Author

Also addresses 5c0b299#r41899248

@@ -53,20 +53,18 @@ export function remove(mark: string) {
delete compositeMarkRegistry[mark];
}

export type CompositeEncoding<F extends Field = Field> = Encoding<F> & ErrorExtraEncoding<F>;
export type CompositeEncoding<F extends Field> = Encoding<F> & ErrorExtraEncoding<F>;
Copy link
Member

Choose a reason for hiding this comment

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

Can you explain why do we remove the default = Field here?

Copy link
Member Author

Choose a reason for hiding this comment

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

I found it less confusing to explicitly say the type. It makes me more confident that we didn't miss using string somewhere.

Copy link
Member Author

Choose a reason for hiding this comment

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

Are you okay with this?

@kanitw kanitw merged commit df77ca1 into master Nov 15, 2020
@kanitw kanitw deleted the dom/remove-normalized branch November 15, 2020 09:36
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.

Schema shouldn't include normalized spec / FieldName
2 participants