Git Product home page Git Product logo

sn-redux's Introduction

Welcome to sensenet

sensenet is a content repository with API first approach packed with a full featured permission system, preview and collaboration tools.

Join the chat at https://gitter.im/SenseNet/sensenet

A basic setup of sensenet has three top-level parts:

  • A content repository that is the storage and service layer
  • An application that uses the content of the connected content repository through API calls
  • A sensenet admin surface (only in SNaaS) that helps you carry out common content management tasks

SNaaS architecture

Everything is content

Content is the basic block for storing information in sensenet. A content can be any kind of data, user, document, workspace, memo, task, and more. Using content items everywhere unlocks a great deal of exceptional features, making your experience as a user more seamless, and your job as a developer a lot easier.

Licensing

SNaaS (sensenet as a service)

In this model, sensenet content repositories live in our cloud infrastructure.

Advantages

  • no installation required (easy onboarding)
  • patches and upgrades are taken care of by us
  • no hosting related tasks
  • central admin surface
  • flexible pricing plans (based on # of contents, requests, and users)

on-prem

For the terms of on-prem licensing please contact our sales team.

Resources

Check out the links below to get further information:

Contributing

All kinds of contributions are welcome! We are happy if you have an idea, bugfix or feature request to share with others. Please check out our Contribution guide for details.

sn-redux's People

Contributors

borsi avatar gallayl avatar greenkeeper[bot] avatar herflis avatar zoltanbedi avatar

Stargazers

avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

borsi tore0x

sn-redux's Issues

An in-range update of @types/chai is breaking the build 🚨

Version 4.1.0 of @types/chai was just published.

Branch Build failing 🚨
Dependency @types/chai
Current Version 4.0.10
Type devDependency

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

@types/chai 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

@types to dev dependencies

Hi, thanks for all the good work! One problem though, can you please bring all @types definitions into devDependencies from dependencies? It breaks compilation of all my projects since it introduces your typings into my project.

Thanks!

An in-range update of sn-client-js is breaking the build 🚨

Version 2.3.0 of sn-client-js just got published.

Branch Build failing 🚨
Dependency sn-client-js
Current Version 2.2.0
Type dependency

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

sn-client-js is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 2.3.0

New features

  • Extended Repository configuration with default OData parameters for default select, required select, default metadata, default inlinecount, expand and top
  • Added repository.GetCurrentUser() observable for tracking user identity changes
  • Created SavedContent< T > type where the content Id and Path is required
  • Added batch operations to Repository: CopyBatch, MoveBatch and DeleteBatch

Changes

  • Type checking for OData select, expand and orderby options
  • repository.handleLoadContent() will accept a SavedContent for parameter (Id and Path will be required)
Commits

The new version differs by 10 commits.

  • 4ebfa37 Merge branch 'master' into development
  • ee46ddc chore(package): update @types/chai to version 4.0.4 (#50)
  • 15a8f80 chore(package): update @types/mocha to version 2.2.42 (#51)
  • 3f83e2b Repository batches (#49)
  • d982b60 Feature/extend repository config (#48)
  • 0f80c32 GetCurrentUser observable for user identity changes, restore RxJs Ajax functionality (#47)
  • c75f319 chore(package): update @types/chai to version 4.0.3 (#46)
  • b637564 Merge branch 'release/2.2.0' into development
  • 8ffdb88 Merge branch 'release/2.2.0'
  • 89e7e67 chore(package): bumped version

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @sensenet/client-core is breaking the build 🚨

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

Version 1.0.1 of @sensenet/client-core was just published.

Branch Build failing 🚨
Dependency @sensenet/client-core
Current Version 1.0.0
Type dependency

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

@sensenet/client-core 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Refactor the store

The present store and reducers are designed and implemented for a basic purpose to build a simple todo app. Since we want to create a more complex app demonstrating document management features of sensenet ECM we need to restructure data and make it more readable and useable.
Following will be the skeleton of the new store

  • sensenet
    • session
      • country
      • device
      • language
      • loginState
      • user
        • id
        • fullName
        • userName
        • language
        • avatarUrl
    • entities
      • ids
      • contents
      • fetchStatus
      • error
      • actions
      • top
      • skip
      • query
      • order
    • currentcontent
      • contentState
      • error
      • actions
      • fields
        • Id
        • DisplayName

myDoclib
myUsers
Tree
Followers

The built-in reducers will only affect the current content, its children items and session information so they are for basic purposes. Component related stuff (e.g. tree data) have to be implemented and stored separately in the store beside sensenet built-in reducers.

  • Refactor reducers
  • Update related Actions and the Schema
  • Fix the tests and add new ones for the newly created stuff
  • Update the docs
  • Upgrade sn-client-js to the latest version
  • Create a new release

Action required: Greenkeeper could not be activated 🚨

🚨 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.

@sensenet/redux type safety improvements

Problem:

The current store implementation doesn't have exlicit Redux types, we should define explicit types for all actions and reducers.

Example for Action:

export const userLogout = () => ({
    type: 'USER_LOGOUT',
    // tslint:disable:completed-docs
    async payload(repository) {
        const response = await repository.authentication.logout()
        return response
    },
})

should be:

export const userLogout: 
    Action & { payload: (repository: Repository) => Promise<boolean> } = () => ({
    type: 'USER_LOGOUT',
    async payload(repository: Repository) {
        const response = await repository.authentication.logout()
        return response
    },
})

Example for reducer:

export const country = (state = '', action) => {
    return state
}

should be

export const country: Reducer<string, Action> = (state = '', action: Action) => {
    return state
}

Reducer helper methods should be also extended with type info.

Tasks

  • Enable strict mode & strict null checks in tsconfig
  • Fix the missing type declarations
  • Review 3rd party components (e.g. normalizr) typescript compatibility
  • Review the sensenet state structure. There should'nt be 'any' leafs left in the store

An in-range update of redux-mock-store is breaking the build 🚨

Version 1.5.0 of redux-mock-store was just published.

Branch Build failing 🚨
Dependency redux-mock-store
Current Version 1.4.0
Type devDependency

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

redux-mock-store 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 13 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of tslint is breaking the build 🚨

Version 5.8.0 of tslint was just published.

Branch Build failing 🚨
Dependency tslint
Current Version 5.7.0
Type devDependency

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

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

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Release Notes v5.8.0

⚠️ Deprecations

  • [deprecation] typeof-compare is deprecated because typescript already does that check (#3286)
  • [deprecation] CLI argument --type-check is no longer necessary and will be removed in the next major version (#3322)

⚠️ Updates to tslint:latest configuration

+    "ban-comma-operator": true,
+    "jsdoc-format": {
+        options: "check-multiline-start",
+    },
+    "no-duplicate-switch-case": true,
+    "no-implicit-dependencies": true,
+    "no-return-await": true,

🎉 Features

🛠 Bugfixes & enhancements

Thanks to our contributors!

  • Klaus Meinhardt
  • Charles Samborski
  • Donald Pipowitch
  • Josh Goldberg
  • mmkal
  • Erik
  • Csaba Miklos
  • Dominik Moritz
  • Khalid Saifullah
  • Lukas Spieß
  • Merott Movahedi
  • Bowen Ni
  • ksvitkovsky
  • Hutson Betts
  • Caleb Eggensperger
  • Brent Erickson
  • Trivikram
  • Brandon Furtwangler
  • Pavel Zet
  • aervin_
  • Holger Jeromin
  • Danny Guo
  • Jeremy Morton
  • Cyril Gandon
  • Andy Hanson
  • yadan
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @sensenet/client-core is breaking the build 🚨

The dependency @sensenet/client-core was updated from 1.3.0 to 1.3.1.

🚨 View failing branch.

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

@sensenet/client-core 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.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Strongly typed actions

We should add strict types to our actions from the Promise middleware

Promise middleware

  • Turn on "strict" mode in the middleware library
  • Add missing types
  • Add new property for "result" and "error", the new actions should use them instead of the "payload" property
  • Update tests
  • Update docs & examples

@sensenet/redux

  • Update middleware package
  • Update reducers, add action types

sn-dms-demo

  • Update Redux
  • Fix connects

Reducers ids create content success payload doesn't have result property

In reducers line 210 the action.payload doesn't have a result property.

export const createContent = <T extends IContent = IContent>(parentPath: string, content: T, contentType: string) => ({
    type: 'CREATE_CONTENT',
    // tslint:disable:completed-docs
    async payload(repository: Repository): Promise<IODataResponse<T>> {
        const data = await repository.post<T>({ parentPath, content, contentType })
        return data
    },
})

Create content returns an IODataResponse.

@sensenet/redux Actions and Reducers refactor

The problem

Actions (550 lines) and Reducers (850 lines) and their tests are too large modules for real time type checking (). We should refactor them into separate TS modules (=files)

Tasks

  • Move reducer helpers into a separate module
  • Split reducers into separate modules (tbd: by the affected state level?)

Can be affect #98

An in-range update of @types/node is breaking the build 🚨

Version 10.3.2 of @types/node was just published.

Branch Build failing 🚨
Dependency @types/node
Current Version 10.3.1
Type devDependency

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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of sn-client-js is breaking the build 🚨

Version 2.0.0 of sn-client-js just got published.

Branch Build failing 🚨
Dependency sn-client-js
Current Version 2.0.0-RC.4-development3
Type dependency

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

sn-client-js is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @sensenet/authentication-jwt is breaking the build 🚨

The dependency @sensenet/authentication-jwt was updated from 1.0.4 to 1.0.5.

🚨 View failing branch.

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

@sensenet/authentication-jwt 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.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits

The new version differs by 2 commits ahead by 2, behind by 1.

  • 4325137 [KFI]build(replaced codecov package with a bash script):
  • 3752f33 [KFI]chore(updated dependencies, bumped version):

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Loginstate doesn't go to Pending state

After 'USER_CHANGED' the state set to Unauthenticated. After dispatching login from actions 'USER_LOGIN_LOADING' doesn't change the state to pending. I expect the loginstate to be pending once it is in a loading state.

An in-range update of @types/mocha is breaking the build 🚨

Version 5.2.2 of @types/mocha was just published.

Branch Build failing 🚨
Dependency @types/mocha
Current Version 5.2.1
Type devDependency

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

@types/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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

[scoped packages] Refactor + async operations

  • make it a scoped package (@sensenet/redux)
  • change dependencies by the new scoped packages
  • remove gulp (create a typedoc script, modify travis config)
  • remove properties.json (wtf is this?)
  • update the code where it is necessary
  • try redux-promise, redux-thunk, redux-saga and native es6 promise to replace rxjs+redux-observables+epics and choose the one that fit our needs the best (complexity, typesafety, number of dependencies, maintability)
  • remove epics, redux-observable and rxjs completely from the project
  • update todo apps and the dms if it is necessarry
    • update todo app
    • update dms
  • improve code coverage
  • setup higher linting standards
  • update documentation
    • code comments
    • api doc on github.io
    • update README.md
  • update tutorials
  • release version 4.0.0
  • create a blog post about the process and the decisions we've made
compexity typesafety dependencies maintainability
redux-promise
redux-thunk
redux-saga
native es6 promise

An in-range update of sn-client-js is breaking the build 🚨

Version 2.1.0 of sn-client-js just got published.

Branch Build failing 🚨
Dependency sn-client-js
Current Version 2.0.1
Type dependency

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

sn-client-js is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 10 commits.

  • 6f5126e chore(package): bumped version
  • 84124af Feature/reference loading (#35)
  • 020b100 Merge branch 'master' into development
  • 0f04123 feat(Enums): Updated Enums to Typescript 2.4.1 string based enums (#34)
  • 342437e chore(package): update typescript to version 2.4.2 (#36)
  • d07bdfd Merge branch 'hotfix/2.0.1' into development
  • 9ce5b77 Merge branch 'hotfix/2.0.1'
  • 56483d7 Merge branch 'master' into hotfix/2.0.1
  • e71d2e2 chore(package): update chai to version 4.1.0 (#33)
  • ed59e6c Merge branch 'release/2.0.0' into development

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Add types to CreateStoreOptions

CreateStoreOptions doesn't have types added to the properties. Please add types to them so intelisense can work better.

export interface CreateStoreOptions {
    rootReducer,
    repository,
    middlewares?,
    persistedState?
}

An in-range update of @types/mocha is breaking the build 🚨

Version 2.2.46 of @types/mocha was just published.

Branch Build failing 🚨
Dependency @types/mocha
Current Version 2.2.45
Type dependency

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

@types/mocha 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Package.json notices

  • License file extension should be .md or without an extension
  • files: test, documentation folders are they needed to be there once I install this package?

An in-range update of sn-client-js is breaking the build 🚨

Version 2.4.0 of sn-client-js just got published.

Branch Build failing 🚨
Dependency sn-client-js
Current Version 2.3.0
Type devDependency

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

As sn-client-js 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 💪

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 2.4.0

New features

  • Improved OData 'orderby' options, now ordering direction can be specified for fields
Commits

The new version differs by 11 commits.

  • 53f09b5 [KFI]chore(bumped version):
  • 1f683c2 Feature/query ordering (#60)
  • 505eea3 Merge branch 'master' into development
  • a94889b [KFI]feat(package): added sensenet-kfi-cz-conventional-changelog
  • 380923b chore(package): update mocha to version 3.5.3 (#58)
  • 5ba92a5 chore(package): update @types/mocha to version 2.2.43 (#56)
  • c5b4056 chore(package): update typescript to version 2.5.2 (#54)
  • 9cb6fe3 chore(package): update chai to version 4.1.2 (#55)
  • 392eb20 Merge branch 'release/2.3.0' into development
  • 41d490d Merge branch 'release/2.3.0'
  • cf0d3e6 chore(package): bumped version

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of typescript is breaking the build 🚨

Version 2.4.1 of typescript just got published.

Branch Build failing 🚨
Dependency typescript
Current Version 2.4.0
Type devDependency

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

As typescript 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 💪

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes TypeScript 2.4

For release notes, check out the release announcement

For new features, check out the What's new in TypeScript 2.4.

For breaking changes, check out the Breaking changes in TypeScript 2.4 page.

For the complete list of fixed issues, check out the fixed issues query for Typescript 2.4.

Download:

Commits

The new version differs by 141 commits.

  • 8b2fe13 Update LKG.
  • 14d95ed Test:Block-scoped definition of Promise works
  • a8846bf Skip block scope check with no error location
  • 44f2336 Merge pull request #16633 from Microsoft/release-2.4_fixIncrementalParsing
  • 4875a27 Add tests
  • 15ef20d Set the structureReused to be safemoudles when dynamic import change
  • 6d33083 Add tests
  • 11b9f6e Wip-fix incremental parsing
  • 2721fd4 In TypeScript code, never bind JSDoc normally, just set parent pointers (#16555) (#16561)
  • 0968ed9 Revert string enum changes (#16569)
  • 096f8cc Update LKG
  • 9241175 Allow running in strict mode (#16557)
  • f49b007 Update LKG
  • f1b0f59 Update version to 2.4.1
  • ed9cde9 Update LKG

There are 141 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of sn-client-js is breaking the build 🚨

Version 2.5.0 of sn-client-js was just published.

Branch Build failing 🚨
Dependency sn-client-js
Current Version 2.4.1
Type devDependency

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

sn-client-js 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 2.5.0

New features

Upload functionality has been improved, now chunked upload is supported from the library. The new upload endpoints on Content level:

  • content.UploadTextAsFile(options) - Create a text file from a string variable
  • content.UploadFile(options) - Upload a file from a File instance (e.g. from form data)
  • content.UploadFromDropEvent(options) - Upload a file structure from a single Drop event

Binary field support has been added, now you can overwrite binaries on content field level. The new endpoints per binary fields (e.g. file.Binary) are:

  • fileContent.SaveBinaryFile(file: File)
  • fileContent.SaveBinaryText(text: string)
  • fileContent.GetDownloadUrl(): string

New Repository setting - If you've modified the default BinaryChunkSize, you can adjust it with the Repository's ChunkSize setting

Changes

MockHttpProvider has been refactored in order to handle a request/response queue instead of defining single results. The provider will
The following methods has been removed / replaced

  • setResponse(response) -> AddResponse(response)
  • setError(error) -> AddError(error)
  • lastOptions -> RequestLog

RxAjaxHttpProvider - The unused ForceCheckCrossDomain property has been removed.

Commits

The new version differs by 3 commits.

  • b810743 Feature/Upload (#69)
  • 57d9d64 Merge branch 'release/2.4.1' into development
  • bdde0b0 [KFI]chore(package): bumped version

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.