Releases: meedan/check
v0.113.0
This note describes the latest changes on API and changes on database.
- Configure Slack notifications per list:
- ➕
updateProject
mutation now accepts aslack_events
string field. It allows projects to send notifications related to item creation to different channels (example of value to send on mutation:'[{ "event": "item_added", "slack_channel": "#channel-name" }]'
) - ➕
Project
type have a new fieldget_slack_events
that returns the setting above, as a JSON object
- ➕
- ➕
Version
type: added a new fieldsmooch_user_external_identifier
. For versions related tosmooch
annotations, the field returns the external identifier (phone number or Twitter handle) of the Smooch user related to thesmooch
annotation - Add message to assignment (list and item) e-mail
- ➕ Added a new migration to add column
message
toassignments
table. The migration should run very fast duringdocker-compose up
- ➕
updateProject
andupdateDynamic
mutations: added the fieldassignment_message
to set the message attribute for the project assignment or annotation assignment
- ➕ Added a new migration to add column
- ➖ Archive.is was removed from Keep Bot options. A task was added to remove the option from existing Keep Bot intallations and to delete the fields and versions related to its responses. To run the task:
rake check:migrate:remove_archive_is_archiver
v0.112.0
This release include changes on GraphQL types and queries, on database and on a task.
Tasks now can be configured to appear or not in the Check browser extension:
- ➕ Added a new migration to add column
show_in_browser_extension
toteam_tasks
table. The migration should run very fast duringdocker-compose up
- ➕
TeamTask
GraphQL mutations accept ashow_in_browser_extension
boolean field - ➕
TeamTask
andTask
GraphQL types have a new boolean fieldshow_in_browser_extension
There was also improvements on task to fix projects ids
on elasticsearch
. To run the task: rake check:migrate:fix_elastic_search_project_ids
v0.111.0
This note describes the latest changes on API and changes on database
- New media type:
- ➕ Added a
Blank
media: this media type doesn't haveurl
,quote
orfile
- ➕ Added the mutation
replaceProjectMedia
: it allows aProjectMedia
that is related to aBlank
media to be replaced by anotherProjectMedia
. Thereport_design
andverification_status
annotations related to the former are moved and overwrite the ones from the latter
- ➕ Added a
- Explicitly set "analysis" information for an item. This structure will be responsible for storing the fact-checking information
- ➕ New analysis fields were added to
verification_status
annotation. The fields should store the analysis informationtitle
: customized title for the item. If present, it is displayed on searches, list view, Slack notifications and reports instead of the originaltitle
content
: customized description for the item. If present, it is displayed on searches, list view, Slack notifications and reports instead of the originaldescription
published_article_url
: the published article URL of the item being analyzeddate_published
: the date the content was publishedexternal_id
: for analysis imported from other source with Fetch, it stores its original IDraw
: for analysis imported from other source with Fetch, it stores the raw information
- ➕ Changes on database to support the changes. The migrations should run very fast during
docker-compose up
- Migration to add the new fields to
verification_status
annotation - Migration to remove the
DynamicAnnotation::AnnotationType
withannotation_type: fetch
- Migration to add the new fields to
- ➕ New task to convert analysis structure. To run the task:
rake check:migrate:convert_analysis
- Delete
metadata
annotations andmetadata_value
fields. The information is migrated to the new fields onverification_status
annotation - Delete
analysis
annotations andanalysis_text
fields. The information is migrated to the new fields onverification_status
annotation
- Delete
- ➖ GraphQL fields removed from
ProjectMedia
:metadata
andoverridden
. The fields were replaced by the new fields onverification_status
annotation
- ➕ New analysis fields were added to
v0.110.0
This release includes improvements on development and test environments.
Changes ♻️
- The MinIO buckets created by Pender to save the URLs information and images are now public. This change makes possible to see the item picture on list page when running Check locally.
- Removed the gems
sauce_whisk
andrubyzip
from CheckWeb. They were no longer being used when running integration tests. - Test files refactoration on CheckWeb. Some helper methods were created to avoid repetition and simplify the creation of tests. Please check the file
test/spec/app_spec_helpers.rb
to see the the helper methods.
v0.109.0
This release includes a change on database.
Changes ♻️
A new migration was included to add new fields title
and date
to report_design
annotation type schema.
The migration should run very fast during docker-compose up
.
v0.108.0
This note describes the latest changes on API.
Changes ♻️
Existing queries were changed or removed and some arguments and fields were included to support the new concept of field sets, where a set is a container for an ordered list of fields (a.k.a. tasks):
- ➕
createTeamTask
,updateTeamTask
,createTask
andupdateTask
mutations: addedfieldset
attribute ofstring
type - ➕
TeamTask
andTask
types: addedfieldset
attribute which is a text name to group fields - ➕
ProjectMedia
type: thetasks
connection now accepts an optionalfieldset
argument to return only the tasks with the definedfieldset
- ➕
Team
type: theteam_tasks
connection now accepts an optionalfieldset
argument to return only the team tasks with the definedfieldset
- ➕
Team
type: addedget_fieldsets
JSON field that returns the fieldsets configured for that team - ♻️ Replacing tasks ordering mutations
- ➕
moveTaskUp
,moveTaskDown
,moveTeamTaskUp
andmoveTeamTaskDown
mutations: change the order of tasks and team tasks - ➖
taskOrder
mutation was removed. Please use the mutations above to order the fields.
- ➕
v0.107.0
This release includes a change on local test environment.
Changes ♻️
Automated integration tests run with the latest Google Chrome version
v0.106.0
This note describes the latest changes on API and local development environment.
New ⭐
New type and mutations related to the new feature read/unread items:
ProjectMediaUser
: a mapping between users and project medias. This type has the boolean fieldread
to identify when a project media is read by a usercreateProjectMediaUser
,updateProjectMediaUser
anddestroyProjectMediaUser
: create, update and destroy the mapping between users and project medias
Changes ♻️
- ➕
About
type: audio files are now supported and two new fields were added to show details of it:audio_max_size
: returns the maximum audio upload size. Currently audios larger than 20.97 MB are not supportedaudio_extensions
returns the allowed audio types. Currently the supported types aremp3
,wav
andogg
- Annotations can return the version created as a result of any action (create, update, delete):
- ♻️
createComment
,updateComment
anddestroyComment
mutations: renamed the payload fieldscomment_version
andcomment_versionEdge
toversion
andversionEdge
, respectively - ♻️
createTask
,updateTask
anddestroyTask
mutations: renamed the payload fieldsfirst_response_version
andfirst_response_versionEdge
toversion
andversionEdge
, respectively - ➕
createDynamic
,updateDynamic
anddestroyDynamic
mutations: added the payload fieldversion
- ♻️
- ➕
ProjectMedia
type: included the fieldis_read
. This field istrue
when the item has already been opened- If the argument
by_me
is sent to the fieldis_read
, it shows if the item was read by the user that made the request
- If the argument
- ➕ Set the team slug to allow requests in the context of the team
- for GraphiQL page: added a new field "Team Slug" in the top of the page
- for API endpoint: using command line or external app, use:
https://check-api.checkmedia.org/api/graphql?team=your_team_slug
v0.105.0
This note describes the latest changes on API and local development environment.
New ⭐
New mutations were added to this release. Most of them related to bulk operations:
deleteTeamStatus
: delete a team status and change existing items to another statusupdateProjectMediaProject
: update the relation between a project media and a project- Bulk operations:
updateProjectMedias
: send or restore trashed project mediascreateProjectMediaProjects
: add project medias to listsupdateProjectMediaProjects
: move project medias from one list to anotherdestroyProjectMediaProjects
: remove project medias from a list
Changes ♻️
Existing queries were changed, some arguments and fields were included or removed:
- ➕
Team
type: included two new arguments on fieldverification_statuses
items_count
: whentrue
, get the number of items that are marked with each team statuspublished_reports_count
: whentrue
is sent, get the number of reports published with each team status
- ➕
User
type: included the argumentstatus
on fieldteam_users
to filter only the team associations that have the specific status - ➖
ProjectMedia
type: removed fieldverification_statuses
. Please get it fromTeam
type - ➖
PublicTeam
type: removed fieldverification_statuses
. Please get it fromTeam
type - ➖
updateProjectMedia
anddestroyProjectMedia
: these mutations now are exclusive for single operations with project medias- removed argument
ids
and payload fieldaffectedIds
- removed argument
- ➖
createTags
mutation: removed payload fieldenqueued
. The mutation now is executed in foreground - ⬆️ Upgraded PostgreSQL database to version 11: users that are running Check locally should follow these instructions to upgrade the database: https://github.com/meedan/check#upgrading-databases-in-development-environment