Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 05:21

    greenkeeper[bot] on steal-2.2.4

    chore(package): update steal to… (compare)

  • Oct 21 18:27
    greenkeeper[bot] labeled #5392
  • Oct 21 18:27
    greenkeeper[bot] opened #5392
  • Oct 21 18:27

    greenkeeper[bot] on core-js-3.3.3

    chore(package): update core-js … (compare)

  • Oct 18 22:20
    greenkeeper[bot] labeled #5391
  • Oct 18 22:20
    greenkeeper[bot] opened #5391
  • Oct 18 22:20

    greenkeeper[bot] on can-observable-mixin-1.0.3

    fix(package): update can-observ… (compare)

  • Oct 18 19:08
    cherifGsoul labeled #5390
  • Oct 18 19:07
    cherifGsoul opened #5390
  • Oct 18 18:45
    greenkeeper[bot] labeled #5389
  • Oct 18 18:45
    greenkeeper[bot] opened #5389
  • Oct 18 18:45

    greenkeeper[bot] on can-observable-bindings-1.3.0

    fix(package): update can-observ… (compare)

  • Oct 18 18:29

    matthewp on master

    Update dist for release (compare)

  • Oct 18 18:29

    matthewp on v6.1.3

    Update dist for release 6.1.3 (compare)

  • Oct 18 17:59

    matthewp on can-observable-array-1.0.2

    (compare)

  • Oct 18 17:59

    matthewp on master

    fix(package): update can-observ… Merge pull request #5388 from c… (compare)

  • Oct 18 17:59
    matthewp closed #5388
  • Oct 18 16:46
    greenkeeper[bot] labeled #5388
  • Oct 18 16:46
    greenkeeper[bot] opened #5388
  • Oct 18 16:46

    greenkeeper[bot] on can-observable-array-1.0.2

    fix(package): update can-observ… (compare)

Viktor Busko
@Lighttree
This is interesting topic. Am I right that its better to use can-element if you can ? Based on one of the latest videos (don't remember which exactly) there is idea that can-elementpreferred option.
Frank Lemanschik
@frank-dspeed
@Lighttree @jeroencornelissen browser support is well yes it exists the google polyfill
can-element is the most best option for individual elements but its missing stuff like composing of components
while it would support composing of can-elements
you can also use a can-element to act as a can-component entry point
and from there on stache and can-view-callbacks
take over
so can-element is in terms of donejs only usefull to do the inital rendering
else it has not out of the box advantage
can-component registers a can-view-callback that renders the tag
can-element registers a element that renders it self
can-element at current offical state is not useable as real replacement for can-component
i created Elements with can-element that render can-components for example
or that are using can-define
but all that is custom work
can-element bare at present is only use able as base for a element its more a skeletton then anything else at current state because its missing the real Element replacements for the functionality that can-stache and that offers
Frank Lemanschik
@frank-dspeed
for a example i created a can-route-element with a own router version
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