Skip to content

Require <getetag> eTag values #10

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

Merged
merged 1 commit into from
Jan 9, 2023

Conversation

rfc2822
Copy link
Member

@rfc2822 rfc2822 commented Jan 9, 2023

  • introduce XmlUtils.requireReadText()
  • GetETag: require input text so that the value fields don't have to be nullable

@rfc2822 rfc2822 linked an issue Jan 9, 2023 that may be closed by this pull request
3 tasks
@rfc2822 rfc2822 force-pushed the 9-check-how-to-deal-with-invalid-values branch 2 times, most recently from 4efeb00 to c11ebb6 Compare January 9, 2023 15:19
- introduce XmlUtils.requireReadText()
- Property.parse(): ignore invalid properties
- GetETag: require input text so that the value fields don't have to be nullable
@rfc2822 rfc2822 force-pushed the 9-check-how-to-deal-with-invalid-values branch from c11ebb6 to 0d02784 Compare January 9, 2023 15:23
@rfc2822 rfc2822 marked this pull request as ready for review January 9, 2023 15:23
@rfc2822
Copy link
Member Author

rfc2822 commented Jan 9, 2023

@tobiasKaminsky: Does that make sense to you?

@rfc2822 rfc2822 self-assigned this Jan 9, 2023
@rfc2822 rfc2822 merged commit aac98bd into main Jan 9, 2023
@rfc2822 rfc2822 deleted the 9-check-how-to-deal-with-invalid-values branch January 9, 2023 16:43
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.

Check how to deal with invalid values
1 participant