Update the JWT Service based on the changes in the related issue: SenseNet/sensenet#145

• JwtService.Logout() should fire a logout request to the backend
• Remove the X-Access-Data from requests - breaking change
• Re-validate JwtService based on the finialized implementation

We shoud wait until an API changes will be finialized, documented and a new version of sensenet Services will be released.

Version 8.5.3 of @types/node was just published.

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 🌴

OData Options

• Default fields to select (currently hardcoded to 'Id', 'Type')
• Required fields to select (they should be added explicitly, e.g.: Id, Path, Type, Name)
• Default metadata (currently hardcoded to metadata=no)
• Default inlinecount
• Default reference fields to select - TBD - can be related to SenseNet/sensenet#137
• Default top (to eliminate queries with extreme large result)
• Testing
• Docs

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 11.6.0 of nyc was just published.

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

nyc 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 🌴

Implement token based authentication in client-js so that developers can use these actions in their apps.

• Create a tutorial for sensenet.github.io
• The original JWT documentation should link to this new tutorial

note: removed the todo app implementations so we can close this story in spite of a blocker. The todo app implementations can be found here: #21

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 5.0.2 of mocha was just published.

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

mocha 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 🌴

We need a layout mockup for the new admin page GUI

Notes:

• Content repository funcions
• Content representations
• UI testing the layout
• Interviews with current users about the admin area
• How to manage SN7 components
• How to manage content types

When Typescript 2.4 comes out, refactor the generated API with the use of string-based enums.

Version 1.10.0 of tslint-consistent-codestyle was just published.

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

tslint-consistent-codestyle 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 🌴

Version 0.7.2 of typedoc just got published.

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

As typedoc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Tasks:

• My nice silky Loading
  • The main control needs to know what to load
• Mapping extension for the reference field
• Search in references in client-js
• Weave it through the redux layer

As a developer, I'd like to be able to specify whether my query should return with the result set in an ascending or a descending order.

Tasks

• Extend the query builder API
• Test and deploy (seek and destroy)

Acceptance crit

• I can specify the ordering by asc or desc

Mapping setup

• ContentType to Component
• FieldSetting to FieldComponent
• ConentType/Field to FieldComponent
• FieldSetting to ClientContentSetting
• Inherited FieldSetting to ClientContentSetting

Get adapted Schema from ContentTypes to ClientControls

• ContentTypeControl from Mapper
• Original Schema (with FieldSettings)
• FieldMappings (FieldSettings -> FieldControl -> adapted ClientSetting)

We should change our naming conventions with our NPM packages and introduce package scoping for @sensenet specific packages (see e.g. @Material, @angular, @aurelia, @types, @ReactiveX)
As sn-client-js started to grow too fast it will be a good idea to divide it into multiple packages.

The new structure:

• @sensenet/client-utils - Utility package (like sn-tools) for JavaScript / Typescript tools without any sensenet ECM dependency (Retrier, Disposable, etc...)
• @sensenet/query - Type safe Content Query builder and related stuff
• @sensenet/default-content-types - Default generated content types and schemas
• @sensenet/client-core - Interfaces and abstracts (e.g. IAuthenticationService), related Model classes (e.g. ODataResponse), Repository configuration, Also should contain Mocks for Repository, AuthenticationService and HttpProvider
• @sensenet/authentication-jwt - JWT authentication related stuff. Later we should create additional packages for another auth. providers, e.g. @sensenet/authentication-oauth-google
• @sensenet/authentication-google - Google OAuth client-side implementation
• @sensenet/repository-events - Observable client side events for sensenet ECM Repositories
• @sensenet/control-mapper - Control mapping utility for dynamic form generation from schemas
• @sensenet/controls-aurelia - Aurelia control package
• @sensenet/cli - =sn-client-cli - Command line utility for fetching Content Types - We should talk about #70 before refactor
• @sensenet/redux - =sn-redux - In progress, see SenseNet/sn-redux#70
• @sensenet/controls-react - We should finish @sensenet/redux first

If I call Remove on a SenseNet Collection, does it delete the content from the server or it only removes the content locally from the collection?

Version 8.0.17 of @types/node just got published.

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

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

@gallayl commented on Mon Apr 10 2017

Problems:

• Some config variables and methods (e.g. serviceToken, siteUrl) are stored globally, or statically on per-module-level
• The current ODataApi depends on the Ajax implementation from RxJS
• The current architecture doesn't allow a client to interact with multiple Sense/Net sites

Expected behavior:

• Create a more generic, non-static Sense/Net Client Service architecture
• Rewamp initialization / configuration logic.
  • Services should be configured on institation
• Make the Http layer 'providable'
  • Allow to define global headers on service level ( #7 JWT authentication prerequisit)
  • Allow to use Promise beside RxJs's Observable
  • Allow to use a 'mock' HttpProvider (for testing purposes)

Linked issue: #7

On client side, we have the fields and the means of querying. So instead of building query strings, we should have an Query API.

ToDo:

• Example
• Tasks

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.12.0 of tslint-consistent-codestyle was just published.

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

tslint-consistent-codestyle 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.

extends:
  - tslint-consistent-codestyle # makes rules from the package available with the 'tcc/' prefix
rules: # now configure the rules you want to use, remember to use the 'tcc/' prefix
  tcc/no-collapsible-if: error
  tcc/no-unused:
    options: 'ignore-parameters'

Your Greenkeeper Bot 🌴

The problem:

At the moment the generated classes (ContentTypes, Schemas, etc...) are bundled together with sn-client-js and tightly coupled with the Repository object. In that way we can not extend or add content types from different packages (e.g. if we want install the types from the Services, Webpages and our custom solution), the only way is to overwrite the whole ContentTypes library inside sn-client-js

Suggestion

In the future we should distribute ContentTypes in a different NPM package (see #67, e.g. @sensenet/content-services), maybe alongside with backend dependency releases and we should allow to add Content Types and Schemas

import { servicesContentTypes, servicesSchemas } from '@sensenet/content-services';
import { customerContentTypes, customerSchemas } from '../customer-related-stuff';
import { MyCustomizedRepository } from '../'

const myCustomizedRepository = new MyCustomizedRepository({
             // options
             ContentTypes: [servicesContentTypes, customerContentTypes],
             Schemas: [servicesSchemas, customerSchemas]
});

TBD

• Conflict between different packages and their content - Is it possible?

Tasks

• Use the extended response

At the moment we don't have enough information from bulk operations and therefore repository events
(e.g. Repository.Event.OnContentMoved vs Repository.Event.OnContentMoveFailed) can be unrealible.

Once the backend API will be extended with meaningful result, we should update the client API to improve realibility.
Related discussion issue: SenseNet/sensenet#147

Related methods:

• DeleteBatch
• MoveBatch
• CopyBatch

Hi,

I'm trying to create a simple login code, but I have some trouble when I try to instantiate the JwtService. It gives me this error:
__WEBPACK_IMPORTED_MODULE_0_sn_client_js__.JwtService is not a constructor

I'm using webpack 3.8.1 and sn-client-js 2.5.0.
I've created a repo where I can reproduce the issue: link

Am I doing something wrong or is this a bug?

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 9.4.7 of @types/node was just published.

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 🌴

🚨 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.