		@@ -125,5 +125,5 @@ 'use strict';
		value: function getListQuery(options) {
		var typeName = options.typeName;
		var keyForId = options.keyForId;
		var keyForDisplayFieldName = options.keyForDisplayFieldName;
		var typeName = options.typeName,
		keyForId = options.keyForId,
		keyForDisplayFieldName = options.keyForDisplayFieldName;

		@@ -130,0 +130,0 @@ var fieldName = this.getItemDisplayField(typeName);

package.json

		{
		"name": "@sanity/data-aspects",
		"version": "0.0.4",
		"version": "0.0.5",
		"description": "Sanity plugin which controls how your data is presented",
		@@ -23,5 +23,5 @@ "main": "lib/DataAspectsResolver.js",
		"devDependencies": {
		"@sanity/check": "0.0.2",
		"@sanity/check": "^0.0.3",
		"babel-cli": "^6.9.0",
		"babel-eslint": "^6.0.4",
		"babel-eslint": "^7.0.0",
		"babel-plugin-syntax-class-properties": "^6.8.0",
		@@ -28,0 +28,0 @@ "babel-plugin-transform-class-properties": "^6.9.1",

README.md

		@@ -5,10 +5,7 @@ # @sanity/data-aspects

		## HOWEVER

		## BIG FAT DISCLAIMER
		We'll re-design how control of data presentation is handed over to a sanity studio maintainer. Hang on for snake tornado.

		This is alpha software. Nothing should be expected to work.

		## TODO
		[ ] When gql/gradient supports limit, offset and order, make sure DataAspectsResolver rolls the query cigar correctly.

		## Usage
		@@ -23,3 +20,3 @@
		"hiddenTypes": [
		"secretTypeName"
		"nameOfTypeToExcludeFromView"
		],
		@@ -29,5 +26,3 @@ "typeOptions": {
		"displayName": "Article",
		"itemDisplayField": "name",
		"limit": 100,
		"offset": 0
		"itemDisplayField": "name"
		},
		@@ -34,0 +29,0 @@ "siteConfig": {

@sanity/data-aspects - npm Package Compare versions

New alerts