- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3
IBX-10527: Content type search API #196
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
Conversation
f6250bd    to
    76bfa81      
    Compare
  
    2a89508    to
    5a0c955      
    Compare
  
    | _instanceof: | ||
| Ibexa\Rest\Server\Input\Parser\ContentType\Criterion\ContentTypeCriterionInterface: | ||
| tags: | ||
| - 'ibexa.rest.content_type.criterion' | 
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.
This should be placed on top of the file, directly under services key - as this affects all services in this file.
Also note that this does not mean ContentTypeCriterionInterface parsers will be automatically tagged. It only means that services declared in this file that are instances of that will be tagged. You need Container::registerForAutoconfiguration() in extension instead for this to happen.
        
          
                src/lib/Server/Input/Parser/QueryBuilder/FromGetQueryContentTypeQueryBuilder.php
              
                Outdated
          
            Show resolved
            Hide resolved
        
              
          
                tests/lib/Server/Input/Parser/ContentType/Criterion/ContainsFieldDefinitionIdTest.php
              
                Outdated
          
            Show resolved
            Hide resolved
        
              
          
                tests/lib/Server/Input/Parser/ContentType/Criterion/ContentTypeGroupIdTest.php
              
                Outdated
          
            Show resolved
            Hide resolved
        
              
          
                tests/lib/Server/Input/Parser/ContentType/Criterion/ContentTypeIdentifierTest.php
              
                Outdated
          
            Show resolved
            Hide resolved
        
              
          
                tests/lib/Server/Input/Parser/ContentType/Criterion/ContentTypeIdTest.php
              
                Outdated
          
            Show resolved
            Hide resolved
        
              
          
                tests/lib/Server/Input/Parser/ContentType/Criterion/IsSystemTest.php
              
                Outdated
          
            Show resolved
            Hide resolved
        
      | 
 | 



Related PRs:
ibexa/core#633
Description:
The new route is exposed at
/api/ibexa/v2/content/types/view [POST]and accepts the following payload:{ "ViewInput": { "identifier": "ContentTypeView", "ContentTypeQuery": { "limit": "1", "offset": "0", "Query": { "ContentTypeIdCriterion": [1,2], "ContentTypeIdentifierCriterion": "folder", "IsSystemCriterion": true, "ContentTypeGroupIdCriterion": 1, "ContainsFieldDefinitionIdCriterion": 2 }, "SortClauses": { "Identifier": "descending", "Id": "ascending" } } } }with the following headers:
ContentType->application/vnd.ibexa.api.ContentTypeViewInput+jsonAccept=>application/vnd.ibexa.api.ContentTypeView+jsonFor QA:
Documentation: