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
Fields API #406
Fields API #406
Conversation
06df38a
to
1b81fac
Compare
1b81fac
to
67d7371
Compare
@@ -66,7 +66,7 @@ | |||
"behat/mink-extension": "^2.3", | |||
"behat/mink-goutte-driver": "^1.2", | |||
"behatch/contexts": "^3.2", | |||
"coduo/php-matcher": "^3.1.2", | |||
"coduo/php-matcher": "dev-patch-2@dev", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocking issue, but is this coduo/php-matcher
robust? I think this is the second or third time we've had to use it as non-stable, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because I've made another PR to them ;)
@bobdenotter wdyt? would it be useful for headless frontend? |
Yes, very much! it'll be great for context. If something has a value of |
@bobdenotter field type added in API response. Also I've made Dynamic DiscriminatorMap :D |
f02cefc
to
bbc6e47
Compare
As an addition to #150 I've added API endpoints for fields, so now you can make a request like
GET /api/contents/1/fields.json
and it will return all names and values fields of this content. Values are always arrays here, like:
TBD: I can also add type of field to it in case someone will find it is useful information in frontend for proper rendering.