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.

Sign up for GitHub

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

Jump to bottom

@href on a c:manifest/c:entry must become mandatory #150

Closed
xatapult opened this issue Jun 27, 2019 · 2 comments
Closed

@href on a c:manifest/c:entry must become mandatory #150

xatapult opened this issue Jun 27, 2019 · 2 comments

Comments

@xatapult
Copy link
Contributor

xatapult commented Jun 27, 2019 •
edited
Loading

Given the decisions we made on #116, the c:entry/@href attribute must become mandatory. At least, I don't see the meaning or possible usage of a c:entry without an @href.

However, where the master schema resides and therefore how this must be done is beyond my current understanding.
@xatapult xatapult mentioned this issue Jun 27, 2019
Merged
@ndw
Copy link
Collaborator

ndw commented Jun 27, 2019

I've pushed a PR to make the href attribute required.

@xatapult
Copy link
Contributor Author

This was already done (long ago)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ndw @xatapult