This issue provides visibility into Renovate updates and their statuses. Learn more

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

• Update dependency @types/jest to v23.3.14

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• Update dependency https-proxy-agent to 2.2.3 [SECURITY]

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency acorn to 5.7.4 [SECURITY]
• Update dependency dot-prop to 4.2.1 [SECURITY]
• Update dependency handlebars to 4.7.7 [SECURITY]
• Update dependency highlight.js to 10.4.1 [SECURITY]
• Update dependency hosted-git-info to 2.8.9 [SECURITY]
• Update dependency ini to 1.3.6 [SECURITY]
• Update dependency lodash to 4.17.21 [SECURITY]
• Update dependency marked to 4.0.10 [SECURITY]
• Update dependency minimist to 1.2.3 [SECURITY]
• Update dependency node-notifier to 8.0.1 [SECURITY]
• Update dependency shelljs to 0.8.5 [SECURITY]
• Update dependency tmpl to 1.0.5 [SECURITY]
• Update dependency trim-newlines to 3.0.1 [SECURITY]
• Update dependency y18n to 3.2.2 [SECURITY]
• Update all (@types/express, @types/lodash, @types/node, @types/request-promise, commitizen, conventional-changelog-cli, coveralls, express, jest-extended, rimraf, rollup, rollup-plugin-babel, rollup-plugin-commonjs, rollup-plugin-node-resolve, rollup-plugin-sourcemaps, rollup-plugin-terser, rollup-plugin-typescript2, tslint, typedoc, typescript)
• Update babel monorepo (@babel/core, @babel/preset-env)
• Update all (major) (@types/node, commitizen, cz-conventional-changelog, jest-extended, logform, rimraf, rollup, rollup-plugin-commonjs, rollup-plugin-jscc, rollup-plugin-json, rollup-plugin-node-resolve, rollup-plugin-terser, tslint-config-standard, typescript)
• Update dependency semantic-release to v19
• Update jest monorepo (major) (@types/jest, jest, ts-jest)
• Click on this checkbox to rebase all open PRs at once

• Check this box to trigger a request for Renovate to run again on this repository

The devDependency ts-jest was updated from 23.1.4 to 23.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

When running grunt build, following error is thrown:

Warning: Uglification failed.
Unexpected token: string (core-js/modules/es6.promise).
Line 13 in build/isolated/dist/diaspora.js
Use --force to continue.

Babelified file contains an import statement line 13:

import "core-js/modules/es6.promise";

Related to babel/babel#6601

Just like the Array field type, for which we can provide several definitions of the contained data, the Object field type should allow several definitions, so that the contained object can have multiple forms.

Watchers are entities synced with their data source, and we need a way to generate them.

Proposal

Entity.watch(sourceName: string | string[] | True | undefined): WatchableEntity

Params

• sourceName: string | string[] | True | undefined

  Represents sources to watch. If string or array of string are given, search sources with that name. True stands for all sources. undefined binds only default data source.

Returns

Returned value is the corresponding WatchableEntity

Typescript decorator seems to be a good alternative to the Proxy (on entities to replace .attributes) or the Wrapper of adapters, that casts function returns to entities

The devDependency @types/node was updated from 10.9.4 to 10.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency ts-jest was updated from 23.10.3 to 23.10.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

In order to watch entities, Diaspora may match queries itself or use source pubsub (eg: redis).
Diaspora need to have a way to check if the adapter can provide watch feature

Probably depending on #4

In order to help the user, the next adapter structure should allow developer to indicate which features are available, such as query operator, schemas, or pubsub (see #5). It may require each query operator to be casted using its own function.

Maybe a QL translator class may help, to translate from Diaspora QL & DB specific language.

But there are still some exceptions: Some adapters (such as In Memory, LocalStorage or WebAPI) should not translate query language from objects to string or objects. WebAPI should transfert the query "as is" and InMemory or LocalStorage may generate a matcher function to perform the query. The next adapters structure should support that

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Queries should allow to search with insensitive option, to match both lower & uppercase. Should it be an operator?

For now, sets are only snapshots of the data source matching a precise query, but this approach lacks of possibilities to actually manipulate data persisted in store through a set or operate on the set content

Read

Some methods, such as find, findMany, or upcoming has, count or every methods (see #25) would be useful on Sets too, to perform checks or filters on already retrieved sets.

Create

It would be useful to allow the user to manually add arbitrary entities to a set without persisting the insertion. To persist at the same time that we add items, maybe we should also offer the possibility to insert items in the set and in the data source, but it may be redundant with an add followed by a persist of the set.

Update

Update is OK IMO:

• To update some entities of the set, we can directly edit them then persist:

  mySet.entities[0].attributes.foo = 'bar';
  await mySet.persist();

• To update all entities of the set, we can use the update method, optionaly followed by a persist call.

Delete

For now, we can only change the collection of entities in the set by modifying the entities property, which should be readonly by design. Filtering entities from an existing set is pretty important to keep the code clear and concise, as well as optimizing by doing several different operations on different sets extracted using a single data source search.

Seeing that, the set may evolve in a class implementing both interfaces defined by adapters (like insert, insertMany, has, all, count, etc etc) and entities (such as persist, destroy and fetch). So, maybe we can re-manipulate the set to be a special kind of temporary in-memory data source. Of course, most of the new features described above can be done using the lodash wrapper returned by the toChainable method, but it requires extra method calls and lose the ability to use the Diaspora's query language

Comments welcome, @IkarosWilo

The dependency logform was updated from 1.9.1 to 1.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

logform is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency prettier was updated from 1.14.2 to 1.14.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

• Add has method on adapter & model to check if at least entity matches the query. It could be polyfilled with a find method, returning true if an item is matched
• Add count method on adapter & model to get the number of entities matching the query. It could be polyfilled with a findMany method, returning the count of matched items.
• Add every method on adapter & model to check if every entities matches the query. It can be polyfilled by running a findMany with the query, and check if the number of matched entities is equal to the count of entities matched by a findMany without any criterion

In its final form, the query language should allow a wide variety of combinations, to makes queries as easy to write as they are to think. Diaspora should perform following query-to-assertion translations:

• { "foo": { "==" { "bar": 2 }}} => entity.foo == {bar: 2}
• { "foo": { "bar": 2, "baz": 3 }} => entity.foo.bar == 2 && entity.foo.baz == 3
• { "foo" { "$contains": { "bar": 2, "baz": 3 }}} => entity.foo.bar == 2 && entity.foo.baz == 3
• { "==": { "foo": 1 }} => entity.foo == 1
• { "foo": { "||" [ 1, 2 ]}} => entity.foo == 1 || entity.foo == 2
• { "foo": { "||": [ 1, 2, 3 ] }, "bar": { ">": 1 }} => (entity.foo == 1 || entity.foo == 2 || entity.foo == 3) && entity.bar > 1
• { "||": [{ "foo": { "==": 1 }}, { "bar"; { "==" 2 }}]} => entity.foo == 1 || entity.bar == 2

Rules are that several operator properties are implicitly resolved as &&, and implicit { [field]: value} without operator will have different results depending on the type of the value.

• If its a primitive, it will be resolved as { "==": { [field]: value }}
• If its an object, it will be resolved as { "$contains": { [field]: value}}

We've seen with @IkarosWilo that operators at root set a "prefix" mode.
If it's a field name, the "infix" mode is enabled: it projects its left operand in a new operator child object.

About escaping

We have to support the case where a field is named the same way as an operator, like $equal or ||. Escaping query keys may be done with ., this way: { ".$equal": { ">": 1}}. The leading dot forces the key to be treated as a field name instead of an operator, and is removed in the resulting query.

To output a leading dot in the output query, 2 dots should be used: { "..$equal": { ">": 1}}

About fields relation

It may be relevant to support in-entity fields comparisons, like this assert: entity.a == entity.b. But how to mark the value as a field instead of a string ?

Entities should be able to have one-to-one, one-to-many, many-to-one or many-to-many relations.

When running a query on a model or entity, the returned Promise should be replaced by a QueryPromise. This promise should expose methods to populate relations at resolution time.

The devDependency rollup-plugin-commonjs was updated from 9.1.6 to 9.1.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup-plugin-commonjs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

In order to implement relations, entity relation fields should be an observable field, that runs the correct query if required when trying to access a property.

Example use case:

const entity: Entity = await myModel.find({id: 1});
const subEntity = await entity.attributes.relationalT1Field;// subEntity is an Entity
const subSet = await entity.attributes.relationalTxField;// subSet is a Set

Compatibility may be outdated, as Diaspora does not use proxies anymore

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

I can help if you want !

I should deprecate the old Diaspora package

npm deprecate diaspora "\"diaspora\" was moved to \"@diaspora/diaspora\". Please consider running \"npm un diaspora && npm i @diaspora/diaspora\" to install new versions."

The devDependency conventional-changelog-cli was updated from 2.0.5 to 2.0.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

conventional-changelog-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency semantic-release was updated from 15.9.15 to 15.9.16.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Update Diaspora logos

Some methods are obsolete and should be deleted. To avoid too many refactors, mark them as deprecated.

• Diaspora.createNamedDataSource => replaced with Diaspora.createDataSource