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

Stop suggesting adding p-name e-content #87

Open
aaronpk opened this issue Apr 13, 2020 · 2 comments
Open

Stop suggesting adding p-name e-content #87

aaronpk opened this issue Apr 13, 2020 · 2 comments

Comments

@aaronpk
Copy link
Member

aaronpk commented Apr 13, 2020

p-name — if your post has a name, use this classname. Otherwise, (if for example the post is a note), either leave it off or apply to the same element as e-.

This should be updated to suggest only adding the name property for articles

capjamesg added a commit to capjamesg/indiewebify-me that referenced this issue Jan 10, 2022
gRegorLove added a commit that referenced this issue Jan 15, 2022
address #87 suggestion to update p-name description
@gRegorLove
Copy link
Member

Closed by #98

@gRegorLove
Copy link
Member

Reopening because there's still a validation message here that directs to add p-name e-content.

We should double-check the logic here for what an "invalid" name is and what message to show (if any). The mf2 parsing spec has changed to reduce how often a name is parsed implicitly. For example, other p- properties will prevent an implicit name. If notes are published with p-content like the how-to, there will be no name and this validator will indicate an "invalid" name.

I ran into this testing my post that has no p-name.

@gRegorLove gRegorLove reopened this Jan 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants