Data

Tools

Indexes

Applications

Experiments

Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / grasshopper-cms/grasshopper-core-nodejs issues and pull requests

#100 - Refactoring install commands into install phase

Pull Request - State: open - Opened by keheliya over 8 years ago

#99 - Create contenttype.sync method

Issue - State: open - Opened by pajtai over 8 years ago
Labels: enhancement

#98 - Memory leak in content.queryFull

Issue - State: open - Opened by lukechinworth over 8 years ago
Labels: bug

#97 - Patch/use mongoose create connection

Pull Request - State: closed - Opened by travism over 8 years ago

#96 - Allow the use of multiple collections for content

Issue - State: open - Opened by pajtai over 8 years ago - 2 comments
Labels: enhancement

#94 - error deleting nodes forces app to restart

Issue - State: open - Opened by willphdavies over 8 years ago

#93 - ContentTypes does not have a query method

Issue - State: open - Opened by pajtai over 8 years ago
Labels: enhancement

#92 - the same tests sometimes pass or fail on travis ci

Issue - State: closed - Opened by pajtai over 8 years ago - 3 comments
Labels: bug

#91 - Generic Assets URL function required

Issue - State: open - Opened by willphdavies over 8 years ago

#90 - Add paging to assets

Issue - State: open - Opened by pajtai over 8 years ago

#88 - Ability to create $or queries

Issue - State: open - Opened by pajtai almost 9 years ago - 2 comments
Labels: enhancement

#87 - queryFull should take a depth parameter

Issue - State: open - Opened by pajtai almost 9 years ago
Labels: enhancement

#86 - Changing Content Type property name does not update cooresponding content

Issue - State: open - Opened by coleHafner almost 9 years ago - 1 comment
Labels: bug

#85 - Cannot View Files Added as Part of Content

Issue - State: closed - Opened by erwintj almost 9 years ago - 6 comments

#84 - Adding a node sometimes adds two

Issue - State: open - Opened by pajtai almost 9 years ago - 2 comments
Labels: bug

#83 - Deleting a node causes errors

Issue - State: open - Opened by pajtai almost 9 years ago - 1 comment
Labels: bug

#82 - Update to latest Mongoose and use bluebird

Issue - State: open - Opened by pajtai almost 9 years ago

#81 - Like and not like queries function differently

Issue - State: closed - Opened by pajtai almost 9 years ago - 1 comment
Labels: bug

#80 - Confirm that you can do an "or" with an array of values

Issue - State: closed - Opened by pajtai about 9 years ago - 1 comment
Labels: enhancement

#79 - Patch/assets find will return all assets

Pull Request - State: closed - Opened by Duder-onomy over 9 years ago - 1 comment

#77 - Content types should allow data to be segmented into different collections

Issue - State: open - Opened by travism over 9 years ago - 3 comments
Labels: enhancement

#76 - Should somehow add an easy way to do full text searches

Issue - State: open - Opened by pajtai over 9 years ago
Labels: enhancement

#75 - _id should be editable on initial insert and it should be allowed to be any valid Mongo _id

Issue - State: open - Opened by pajtai over 9 years ago - 5 comments
Labels: enhancement

#73 - Tests have been failing on Travis CI - feature/test-updates branch being used to fix

Issue - State: closed - Opened by pajtai almost 10 years ago - 1 comment
Labels: bug, ready

#72 - getFullById does not actually populate nested content references anymore.

Issue - State: closed - Opened by Duder-onomy almost 10 years ago - 1 comment

#71 - Fix Nested Embedded Content Refs

Pull Request - State: closed - Opened by altmind almost 10 years ago - 3 comments

#70 - Next publishing window

Pull Request - State: closed - Opened by lukechinworth about 10 years ago

#69 - Date and Date hour fields store result as string and not as Date object

Issue - State: open - Opened by pajtai about 10 years ago
Labels: bug

#67 - Boolean values returned from Grasshopper are boxed in to an object with a "value" key

Issue - State: closed - Opened by Browncoat about 10 years ago - 1 comment
Labels: bug

#65 - Error runing demo instances

Issue - State: closed - Opened by eikebartels about 10 years ago - 6 comments

#64 - the default mongoose connection should not be used by core

Issue - State: closed - Opened by pajtai over 10 years ago - 1 comment
Labels: bug

#63 - Grasshopper Without Jade?

Issue - State: closed - Opened by spencerthayer over 10 years ago - 2 comments

#62 - handling of null values in date conversion

Pull Request - State: closed - Opened by jjidt almost 11 years ago - 6 comments

#61 - contains / in throws error when used in a query filter

Issue - State: closed - Opened by dobbobolina almost 11 years ago - 2 comments

#60 - Make sure we are using path.join in only proper places.

Issue - State: closed - Opened by dobbobolina about 11 years ago - 1 comment

#59 - Content query test fail

Issue - State: closed - Opened by dobbobolina about 11 years ago

#58 - 2 tests failing

Issue - State: closed - Opened by pajtai about 11 years ago
Labels: bug

#57 - Tests fail using node 11

Issue - State: closed - Opened by dobbobolina about 11 years ago - 1 comment
Labels: bug

#56 - aws error causes app crash

Issue - State: closed - Opened by pajtai about 11 years ago - 1 comment
Labels: bug

#55 - Updated README.md

Pull Request - State: closed - Opened by serialworm about 11 years ago

#54 - Trying to find a user by id times out if the id is badly formatted

Issue - State: closed - Opened by pajtai about 11 years ago - 1 comment

#53 - Updated comments

Pull Request - State: closed - Opened by serialworm about 11 years ago

#51 - Allow posting with included ids

Issue - State: open - Opened by pajtai about 11 years ago

#50 - Documentation

Issue - State: closed - Opened by dobbobolina about 11 years ago - 13 comments

#49 - roles should be configurable

Issue - State: open - Opened by dobbobolina about 11 years ago - 4 comments

#48 - allow user creation without admin token

Issue - State: open - Opened by dobbobolina about 11 years ago - 6 comments

#47 - More than patches being introduced within mere patch changes?

Issue - State: closed - Opened by pajtai over 11 years ago - 1 comment

#46 - Which version of core should I use?

Issue - State: closed - Opened by pajtai over 11 years ago - 1 comment

#45 - Deleting a node should also delete assets in the node.

Issue - State: closed - Opened by travism over 11 years ago

#44 - nodes.getChildren should return back the nodes in alphabetical order.

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#43 - node.getChildren flat need to be implemented

Issue - State: closed - Opened by travism over 11 years ago

#42 - nodes.getChildren should support deep loading nodes

Issue - State: closed - Opened by travism over 11 years ago

#40 - getChildNodesDeep needs to support permissions

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#39 - getByIdDeep needs to respect permissions.

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#38 - getAssetsDeep needs to integrate with getChildnodes that respects permissions.

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#36 - getChildNodes needs to support node level permissions.

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#35 - getChildNodesAndContent end point needs to be ported over.

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#34 - Assets modules need to get ported over into new project

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#33 - deleteById Should delete a generated node.:

Issue - State: closed - Opened by travism over 11 years ago

#32 - deleteById Should delete an node.

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#29 - Get all the assets in a node. an editor should return a DEEP list of files in a node and it's children:

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#28 - Get all the assets in a node. a reader should return a list of files in a node:

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#26 - Get all the assets in a node. an editor with rights restricted to a specific node should return a 403 error:

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#23 - Delete assets should succeed when a user that is a reader but had editor rights on a specific node.

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#22 - Delete assets should fail because the user does not have permissions.:

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#21 - Delete assets should delete all files in a node.

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#18 - Copy asset should copy an asset from one node to another.:

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#17 - Rename asset should fail because the user does not have permissions.:

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#16 - Rename asset should fail because asset does not exist.

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#15 - Rename asset should rename an asset to a new name in the same node.:

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#14 - Create a new asset in a node post test fixtures

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#12 - Nodes get node children should return list of root level child nodes

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#10 - Nodes get node children should return a 403 because user does not have permissions to access this node

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#3 - Content that a user does not have access to should be filtered out of the query api

Issue - State: open - Opened by travism over 11 years ago
Labels: enhancement, permissions

#2 - Only admin users can use query api for content

Issue - State: closed - Opened by travism over 11 years ago - 1 comment

#1 - Unnecessary options argument in query object

Issue - State: closed - Opened by travism over 11 years ago - 1 comment