Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 17 20:12

    matthewp on master

    Update dist for release (compare)

  • Oct 17 20:12

    matthewp on v6.1.2

    Update dist for release 6.1.2 (compare)

  • Oct 17 20:04

    matthewp on master

    Update dist for release (compare)

  • Oct 17 20:04

    matthewp on v6.1.2-0

    Update dist for release 6.1.2-0 (compare)

  • Oct 17 19:17
    akbaruddin starred canjs/canjs
  • Oct 17 17:25
    matthewp edited #5384
  • Oct 17 17:00

    matthewp on can-dom-mutate-2.0.7

    (compare)

  • Oct 17 17:00

    matthewp on master

    fix(package): update can-dom-mu… Merge pull request #5386 from c… (compare)

  • Oct 17 17:00
    matthewp closed #5386
  • Oct 17 16:27
    greenkeeper[bot] labeled #5386
  • Oct 17 16:27
    greenkeeper[bot] opened #5386
  • Oct 17 16:27

    greenkeeper[bot] on can-dom-mutate-2.0.7

    fix(package): update can-dom-mu… (compare)

  • Oct 17 16:25

    matthewp on can-dom-mutate-2.0.6

    (compare)

  • Oct 17 16:24
    matthewp closed #5379
  • Oct 17 16:24
    matthewp commented #5379
  • Oct 17 15:26

    greenkeeper[bot] on can-type-1.1.2

    (compare)

  • Oct 17 15:26

    matthewp on master

    fix(package): update can-type t… Merge pull request #5385 from c… (compare)

  • Oct 17 15:26
    matthewp closed #5385
  • Oct 17 14:11
    matthewp closed #5377
  • Oct 17 14:11
    matthewp closed #5376
Frank Lemanschik
@frank-dspeed
because can-route would not work as good in a can-element only scenario
as you will not have the ability to pass down vars so easy
Conclusion can-element will replace can-component done-component 100% no question there
but it needs a lot of coding to use its nativ methods
Chasen Le Hara
@chasenlehara
@jeroencornelissen Yes, you do need to use a polyfill if you want to target anything other than Chrome or Safari.
@Lighttree We have some work to do before I would really recommend using can-element over can-component, although I think that is the eventual goal.
Looking through the issues, you can see that there’s a good chunk of work to be done: https://github.com/canjs/can-element/issues
Brad Momberger
@bmomberger-bitovi
I need help with can-connect/real-time and a set algebra
Our algebra looks like this:
export default new set.Algebra(
  set.props.id('_id'),
  set.props.offsetLimit('$skip', '$limit'),
  set.props.sort('$sort', mongoSort),
  {
    address: function () {
      return true
    }
  }
}
mongoSort is a sorting function
When I try to query like this:
      const params = {
        $limit: this.limit,
        $skip: 0,
        type: this.type,
        $sort: 'price ' + (this.type === 'BUY' ? 'asc' : 'desc'),
        issuanceAddress: this.issuanceAddress
      }
I get the "One or more items were retrieved which do not match the 'Set' parameters used to load them." warning.
So can-connect/real-time gotListData() uses algebra.has() on the set (i.e. params) and each returned list item, and the list items don't have a $sort property.
And that seems to be failing this test here. Additionally, mongoSort() never fires. it seems to be using a default sort instead.
Anyone have any ideas why this would be warning and not working as intended? The net effect of this is when I add in the $sort parameter to the query, real-time stops working and newly created items don't get added to lists.
Brad Momberger
@bmomberger-bitovi
(removing $sort makes it work again, but I need the sorting)
Eben
@eben-roux
any help would be appreciated :)
Brad Momberger
@bmomberger-bitovi
can-set 1.4.0 is now released and should resolve my problem above and any others like it.
Frank Lemanschik
@frank-dspeed
@bmomberger-bitovi does that mean your existing syntac works with 1.4.0?
Brad Momberger
@bmomberger-bitovi
Yes, the set including $limit/$skip/$sort now passes Algebra.has() with matching instances.
Viktor Busko
@Lighttree

Guys, I have a question regarding canjs dependencies. My app has following dependencies:

  "dependencies": {
    "entity-details-component": "^0.2.1",
    "can-component": "^3.3.4",
    ...
    "can-define": "^1.4.4",
    ...
    "can-stache": "^3.6.2",
    ...
  }

There is entity-details-component - custom canjs component developed separately from main app (like donejs plugin). And the idea is that It can be reused in different apps. Its dependencies:

 "dependencies": {
        "can-component": "^3.3.7",
        "can-define": "^1.5.4",
        "can-stache": "^3.14.5"
 }

As you can see there are different versions of can-{something} in dependencies.
Is this something that can lead to issues or should be ok ? I'm asking because I got some errors like You have 2 versions ofcan-cidcheck your dependencies, but after some cleaning re-install etc. this issues disappeared.

I was thinking that this will be resolved and all required versions of dependencies will be downloaded, but these console errors made me worry about this.
Kevin Phillips
@phillipskevin
we throw those errors for the can-* dependencies that can cause problems if you load multiple versions
for example... can-view-callbacks is where we keep the list of tags you register with can-component
Frank Lemanschik
@frank-dspeed
oh god bless kevin is there
Kevin Phillips
@phillipskevin
so if you register with one version... and stache uses a different version when trying to find your components, your app won't work
this is one of the obvious ones, but there are much more subtle issues that you might not notice right away
Frank Lemanschik
@frank-dspeed
@phillipskevin i get a lot of warnings about the fact that i should use ~/ to load my modules
Kevin Phillips
@phillipskevin
so... to answer your question, if you're not seeing those errors, you should be safe
Frank Lemanschik
@frank-dspeed
because they are loaded twice but i think thats false
Viktor Busko
@Lighttree
hmm... so I need to freeze versions of dependencies across all apps and components ? or there is some another way ?
Frank Lemanschik
@frank-dspeed
it lists can-* modules
that are only loaded via steal normal donejs pattern
is that expected?
Kevin Phillips
@phillipskevin
@Lighttree you shouldn't need to freeze your dependencies
(although it might not hurt)
but you'll want to use the same range as much as you can
Justin Meyer
@justinbmeyer
starting in a moment
Kevin Phillips
@phillipskevin
@frank-dspeed no I don't think that's expected
also, @Lighttree you may want to :+1: this issue: canjs/canjs#3767
or vote for it in our next donejs survey
Frank Lemanschik
@frank-dspeed
@phillipskevin did you ever run into the fact that modules that you import via its npm name get logged as loaded twice?
i have simply no idea how that can happen when they all have the same name i get that also for moment and that kind of stuff
jquery
it works it loads but the warning are not logical