Coder Social home page Coder Social logo

angular-xml's People

Contributors

barroudjo avatar greenkeeper[bot] avatar johngeorgewright avatar lukasdrgon avatar orthographic-pedant avatar smromain avatar stanjav avatar trueqbit avatar

Stargazers

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

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

angular-xml's Issues

x2js should come bundled?

But... it doesn't if i use the exact bower install like mentioned on the readme.
x2js seems to be installable by bower so i went with that, and that works.
Just thought i'd let you know.

An in-range update of jasmine-core is breaking the build 🚨

The devDependency jasmine-core was updated from 3.4.0 to 3.5.0.

🚨 View failing branch.

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

jasmine-core 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).

Commits

The new version differs by 117 commits.

  • 99799f7 Still need some ruby stuff around to release the jasmine-core gem
  • e8263e3 bump version to 3.5.0
  • 53561ae Show details of syntax (etc) errors when loading Jasmine's own specs
  • 68f25a7 Don't create env instances in beforeEach
  • 96ba66a Built distribution
  • ba4a8d1 Fixed jsdocs
  • 65d9e93 Removed broken & long-disabled JsApiReporter integration specs
  • 2d3ac38 toBeRejectedWithError can expect the error to be Error, not just a subtype
  • 5a219da Added basic integration tests for all built-in matchers
  • f056f3b Fixed indentation
  • aeb0b73 Merge branch 'dtychshenko-1740-fail-on-no-expectations'
  • 7263a38 Adds new configuration option to failSpecWithNoExpectations that will report specs without expectations as failures if enabled
  • e8870db Merge branch 'fix-missing-asynchronous-stacktrace' of https://github.com/prantlf/jasmine into prantlf-fix-missing-asynchronous-stacktrace
  • 35d1508 Show argument diffs in toHaveBeenCalledWith failure messages
  • 19292e4 Stop testing against PhantomJS

There are 117 commits in total.

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 🌴

Interceptor should only work on String response

When using:
$httpProvider.interceptors.push('xmlHttpInterceptor');
it tries to convert the response even when it not a xml string anymore (and fails)

Example scenario, in the application an XML is received and transformed like:
transformResponse : function(data) {
return $.parseXML(data);
}
to a dom tree, to be used for xpath expressions.
In this scenario its not required for x2js to kick in and try to convert to json, since its not an xml string anymore

Content-Type missing breaks Angular

Hi! We've noticed a bug in the library that breaks the whole application when it occurs:

function responseIsXml(response) {
var contentType = response.headers('content-type'),
XML = '/xml',
minIndex = 'text/xml'.indexOf(XML);
return contentType.indexOf(XML) >= minIndex;
}

If for some reason content-type is not set, this fails with a "undefined exception".

XMLParser

Move the logic behind the XML parsing in to a separate service called XMLParser.

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

The devDependency nodemon was updated from 1.18.7 to 1.18.8.

🚨 View failing branch.

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

nodemon 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
  • ci/circleci: Build Error: Your tests failed on CircleCI (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for v1.18.8

1.18.8 (2018-12-10)

Bug Fixes

Commits

The new version differs by 5 commits.

  • 3dfd5cc chore: Merge branch 'master'
  • 735afd5 fix: docker leaving running pids (via pstree)
  • eb457be chore: update issue template
  • 8132db6 docs: Example of how to allow a graceful reload (#1481)
  • 2dcdd0e docs: how to watch .env files

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 🌴

Bower

Get this on bower

angular-xml.js function argument "win"

I am sure it isn't a common issue since I'm managing all of my 3rd party packages by using Grunt.

It was unable to detect the window object through the function argument "win", so I changed it to "window".

I am still fairly new to Angular so I am not sure if I am doing anything wrong, please let me know if I am missing something.

npm install fails

npm --version
1.4.16

sh: node_modules/grunt-protractor-runner/node_modules/.bin/webdriver-manager: No such file or directory
npm ERR! [email protected] postinstall: node_modules/grunt-protractor-runner/node_modules/.bin/webdriver-manager update
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is most likely a problem with the angular-xml package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node_modules/grunt-protractor-runner/node_modules/.bin/webdriver-manager update
npm ERR! You can get their info via:
npm ERR! npm owner ls angular-xml
npm ERR! There is likely additional logging output above.

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

The devDependency karma was updated from 3.1.0 to 3.1.1.

🚨 View failing branch.

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

karma 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 for v3.1.1

Bug Fixes

  • config: move puppeteer from dependency to dev-dependency (#3193) (f0d52ad), closes #3191
Commits

The new version differs by 2 commits.

  • 361aa3f chore: release v3.1.1
  • f0d52ad fix(config): move puppeteer from dependency to dev-dependency (#3193)

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 karma is breaking the build 🚨

The devDependency karma was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

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

karma 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 for v3.1.2

Bug Fixes

Features

Commits

The new version differs by 11 commits.

  • 7d4d347 chore: release v3.1.2
  • 5077c18 chore: update contributors
  • fb05fb1 fix(server): use flatted for json.stringify (#3220)
  • 2682bff feat(docs): callout the key debug strategies. (#3219)
  • 4e87902 fix(changelog): remove release which does not exist (#3214)
  • 30ff73b fix(browser): report errors to console during singleRun=false (#3209)
  • 5334d1a fix(file-list): do not preprocess up-to-date files (#3196)
  • dc5f5de fix(deps): upgrade sinon-chai 2.x -> 3.x (#3207)
  • d38f344 fix(package): bump lodash version (#3203)
  • ffb41f9 refactor(browser): log state transitions in debug (#3202)
  • 240209f fix(dep): Bump useragent to fix HeadlessChrome version (#3201)

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 🌴

How to send XML?

Is it currently possible to specify an option or flag in $http.get() that sends JSON array requests as XML, or should I manually convert using x2js and then send?

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

The devDependency codecov was updated from 3.3.0 to 3.4.0.

🚨 View failing branch.

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

codecov 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).

Commits

The new version differs by 4 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 🌴

Routing not working with xmlHttpInterceptor

while I am working with angular routing, once I used $httpProvider.interceptors.push('xmlHttpInterceptor'); inside the config block, my routing is just left working. When I comment that line, it started to work again.

Using the X2JS library

I've been putting it off for a while, but thinking maybe it would be a nicer option to use the x2js library. It adds dependencies, but it could make code a lot cleaner:

angular
  .module('myMode', ['xml'])
  .controller('Blogs', function ($scope, $http) {
    $scope.blogs = $http.get('/blogs.xml');
  });

Here's the branch

How do i parse wordpress RSS+XML?

I get the XML similar to this from a wordpress 4 site.
I can parse all the items, but I cant get to the title and link and desc.

  <title>W3Schools Home Page</title>
  <link>http://www.w3schools.com</link>
  <description>Free web building tutorials</description>
  <item>
    <title>RSS Tutorial</title>
    <link>http://www.w3schools.com/rss</link>
    <description>New RSS tutorial on W3Schools</description>
  </item>
  <item>
    <title>XML Tutorial</title>
    <link>http://www.w3schools.com/xml</link>
    <description>New XML tutorial on W3Schools</description>
  </item>
</channel>


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

The devDependency nodemon was updated from 1.18.5 to 1.18.6.

🚨 View failing branch.

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

nodemon 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 for v1.18.6

1.18.6 (2018-11-05)

Bug Fixes

Commits

The new version differs by 1 commits.

  • 521eb1e fix: restart on change for non-default signals (#1409) (#1430)

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 🌴

Multiple elements in xml

I have tried to use your example and add elements to the xml like so:

For some reason I can only get to the first element doing this:

$http.get('view1/blogs.xml').success(function (data) {
$scope.blogs = data.blogs;
console.log($scope.blogs);
});

Is there a way to get it as an array of objects?

Example

Would you mind uploading a quick XML example?

Thanks

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

The devDependency karma was updated from 4.1.0 to 4.2.0.

🚨 View failing branch.

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

karma 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 for v4.2.0

Bug Fixes

  • logging: Util inspect for logging the config. (#3332) (70b72a9)
  • reporter: format stack with 1-based column (#3325) (182c04d), closes #3324
  • server: Add error handler for webserver socket. (#3300) (fe9a1dd)
Commits

The new version differs by 13 commits.

  • 42933c9 chore: release v4.2.0
  • db1ea57 chore: update contributors
  • a1049c6 chore: update eslint packages to latest and fix complaints (#3312)
  • 70b72a9 fix(logging): Util inspect for logging the config. (#3332)
  • 1087926 fix typo: (#3334)
  • 182c04d fix(reporter): format stack with 1-based column (#3325)
  • f0c4677 docs(travis): Correct the docs to also show how to do it on Xenial (#3316)
  • 3aea7ec chore(deps): update core-js -> ^3.1.3 (#3321)
  • 5e11340 chore: revert back to Mocha 4 (#3313)
  • 1205bce chore(test): fix flaky test cases (#3314)
  • 7f40349 Cleanup dependencies (#3309)
  • 7828bea chore: update braces and chokidar to latest versions (#3307)
  • fe9a1dd fix(server): Add error handler for webserver socket. (#3300)

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 karma-firefox-launcher is breaking the build 🚨

The devDependency karma-firefox-launcher was updated from 1.1.0 to 1.2.0.

🚨 View failing branch.

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

karma-firefox-launcher 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).

Commits

The new version differs by 13 commits.

  • a398dae chore(release): 1.2.0
  • c1a3939 fix: Detect and kill browser process when launcher process is being used (#103)
  • c3fea39 chore: Update dependencies
  • 2e94873 chore: Add missing is-wsl entry to yarn.lock
  • b4e260e feat: Add support for running Windows Firefox from WSL
  • 2443631 chore: Add self to contributors
  • 2dca609 chore: Update dev dependencies
  • 16e6673 chore: Sort contributors list [skip ci]
  • 9e86d04 chore: Drop support for Node 6 (#98)
  • 540c1dd fix: Add -wait-for-browser
  • 6377ee3 fix: Look for other paths for Firefox Nightly on Windows and Mac
  • b9455c8 chore: Fix travis (#97)
  • 0e37f76 feat(headless): add enable remote debugging by default

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 commitizen is breaking the build 🚨

The devDependency commitizen was updated from 3.0.4 to 3.0.5.

🚨 View failing branch.

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

commitizen 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 for v3.0.5

3.0.5 (2018-11-27)

Bug Fixes

  • package: avoid depending on flatmap-stream (#591) (0eded0a)
Commits

The new version differs by 1 commits.

  • 0eded0a fix(package): avoid depending on flatmap-stream (#591)

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 🌴

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:

  • Replaced the old Node.js version in your .nvmrc with the new one

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 🌴

Missing license

Nice project, works great reading my RSS feed.

However the project is missing an explicit license, perhaps you could add one?

Cheers,
Rob

Specify which files to convert in the request?

Is there a way to specify which files to convert and which files to let through as is? Maybe the ability to add some req expressions to integrate the path and filename in the request?

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

The devDependency express was updated from 4.17.0 to 4.17.1.

🚨 View failing branch.

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

express 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).

Commits

The new version differs by 3 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 commitizen is breaking the build 🚨

The devDependency commitizen was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

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

commitizen 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 for v3.1.2

3.1.2 (2019-07-17)

Bug Fixes

Commits

The new version differs by 5 commits.

  • 4417fcf fix: release fixed sem-release (#648)
  • b3dd4c4 fix: update dependencies for security (#645)
  • 1875a38 fix(deps): update dependency lodash to v4.17.14 [security] (#641)
  • 372c75e docs: highlight pre-requisties and bubble up related sections (#613)
  • b24eade chore(security): fixed 5 vulnerabilities (#599)

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 concurrently is breaking the build 🚨

The devDependency concurrently was updated from 4.1.0 to 4.1.1.

🚨 View failing branch.

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

concurrently 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 for v4.1.1
  • bin: pass --prefix-length argument through (#189)
Commits

The new version differs by 2 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 🌴

angular-xml not correctly recognizing all RSS feeds as XML

Just started using the new version of angular-xml in a podcast application, where response headers are usually returned as text/xml;charset=UTF-8, but occasionally returned as application/rss+xml by certain feeds, such as: http://wtfpod.libsyn.com/rss.

I noticed that in the angular-xml.js file, whether or not a response is XML is determined by the following function:

function responseIsXml(response) {
    var contentType = response.headers('content-type'),
        XML = '/xml',
        minIndex = 'text/xml'.indexOf(XML);
    if (contentType) {
      return contentType.indexOf(XML) >= minIndex;
    } else {
      return false;
    }
  }

I've thought about making certain modifications to the functionality such as:

  function responseIsXml(response) {
    var contentType = response.headers('content-type');
    if (contentType) {
      return contentType.indexOf('xml') > -1;
    } else {
      return false;
    }
  }

but I do worry that this may result in some gotchas. Any thoughts?

Should probably avoid $-prefixed properties

I'm trying a single example structure (which contains $$hashKey as added by AngularJS during edit) and x2js.json2xml_str is producing a <$$hashKey>030</$$hashKey> node, which then the parser chokes on.
The end effect is that x2js.json2xml(myVar) is always null.
I would expect an exception not a null, but in this case I guess $-prefixed properties should simply be skipped, as they are both reserved in AngularJS and invalid XML tag names anyways.

Right now I'm doing this:

function removeDollars(obj) {
    if (typeof obj != 'object')
        return;
    for (var k in obj) {
        if (k.charAt(0) == '$')
            delete obj[k];
        removeDollars(obj[k]);
    }
}
var data = angular.copy($scope.value);
removeDollars(data);
var xml = x2js.json2xml_str(data);

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

The devDependency nodemon was updated from 1.19.0 to 1.19.1.

🚨 View failing branch.

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

nodemon 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 for v1.19.1

1.19.1 (2019-05-25)

Bug Fixes

  • ensure signal is sent to exit event (13afac2)
Commits

The new version differs by 5 commits.

  • 5124ae9 Merge branch 'master' of github.com:remy/nodemon
  • 95fa05a chore: git card
  • d84f421 chore: adding funding file
  • 13afac2 fix: ensure signal is sent to exit event
  • d088cb6 chore: update stalebot

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.