Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 06 18:40
    cherifGsoul review_requested #5441
  • Dec 06 18:39
    cherifGsoul opened #5441
  • Dec 06 18:22

    cherifGsoul on update-infrastructure-page

    Update infrastructure page with… (compare)

  • Dec 06 18:14
    greenkeeper[bot] commented #5422
  • Dec 06 18:14

    greenkeeper[bot] on @feathersjs

    chore(package): update @feather… (compare)

  • Dec 06 18:11
    greenkeeper[bot] commented #5401
  • Dec 06 18:11

    greenkeeper[bot] on @feathersjs

    chore(package): update @feather… (compare)

  • Dec 04 22:03
    chasenlehara opened #5440
  • Dec 04 22:03
    chasenlehara labeled #5440
  • Dec 04 19:18
    cherifGsoul review_requested #5432
  • Dec 04 14:09
    m-ahmadi starred canjs/canjs
  • Dec 04 10:52
    ansyeow starred canjs/canjs
  • Dec 03 14:53
    matthewp commented #5439
  • Dec 03 14:30
    frank-dspeed opened #5439
  • Dec 02 18:13
    greenkeeper[bot] commented #5392
  • Dec 02 18:13

    greenkeeper[bot] on core-js-3.4.7

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

  • Dec 02 17:48
    greenkeeper[bot] commented #5392
  • Dec 02 17:48

    greenkeeper[bot] on core-js-3.4.6

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

  • Dec 02 15:38
    phillipskevin commented #5438
  • Dec 02 15:38
    phillipskevin closed #5438
Frank Lemanschik
@frank-dspeed
@nmingneau if you can do a minimal example maybe in a codepen i can tell you whats wrong
Gregg Roemhildt
@roemhildtg
@nmingneau I've been seeing a lot of those also. Not sure what they mean but so far haven't caused an issue. Seems like a child property is setting a parent and vice versa at near the same time so they're trying to update each other.
Like I said though, hasn't appeared to cause an issue yet, so I'd say its safe to ignore, but something to consider in the future for future enhancements might be to log where the property is getting set and what the property name is..etc.
Frank Lemanschik
@frank-dspeed
i am so happy that i never saw this leads me to the conclusion that my new code style keeps me away from doing such stuff
:D
i stoped using stache bindings and all this stache stuff and refactored all to js syntax
Kevin Phillips
@phillipskevin
it probably means that a parent sets a child and the child then tries to set the parent in a cycle
there is actually some ongoing discussion around this warning
Kevin Phillips
@phillipskevin
as discussed on that issue, there might be a bug here
so if you have cases that cause this warning that you think are not real issues, please let us know @roemhildtg @nmingneau
Justin Meyer
@justinbmeyer
yeah, I'm about to publish some better logging on it
nmingneau
@nmingneau
Hi, using assigndeep solved it in my case because the reference is preserved. Not exactly sure why the DefineMap became not settable. The update happened in a route listener in a separately loaded bundle.
Gregg Roemhildt
@roemhildtg
Awesome job on the new vm debug tools guys!
Figured I'd share this with the community
It looks and works amazingly well
drag-resize.gif
Gregg Roemhildt
@roemhildtg
I guess my only suggestion would be a smaller font size perhaps
Kevin Phillips
@phillipskevin
Awesome @roemhildtg. Glad it's working well for you.
Gregg Roemhildt
@roemhildtg
:clap:
Kevin Phillips
@phillipskevin
I'll be tweaking the UX over the next couple days, so I'll bump down the font a bit
there are a couple open issues here: https://github.com/canjs/can-devtools-components/issues that I'm working on
if you find anything else, please feel free to open issues
Gregg Roemhildt
@roemhildtg
Kevin Phillips
@phillipskevin
yeah, that's annoying
if you right click in the devtools panel and click "reload frame" it fixes it
obviously, not a great workaround :smile:
Gregg Roemhildt
@roemhildtg
That's what I'm doing for now. It works fine, but yeah eventually a nice polished devtools will be good, which I'm sure you'll get to. I mean its already so much easier to debug than a year ago, and having the viewmodel editor makes it a lot easier to get others up to speed on the stuff I'm working on
Good documentation is one thing...but being able to play with the viewmodel in dev tools makes it super simple
Kevin Phillips
@phillipskevin
:thumbsup: we'll keep improving it
Gregg Roemhildt
@roemhildtg
I'm thinking I might even build the viewmodel editor into demo projects.
Kevin Phillips
@phillipskevin
yeah, I'm going to post on the forums how to add it to demo pages
Gregg Roemhildt
@roemhildtg
Not sure how feasible that is at the moment but having a sort of editor like some libs have would be a really nice tool
Kevin Phillips
@phillipskevin
it's not too bad to add to demo pages
Gregg Roemhildt
@roemhildtg
Okay :)
I wonder, like down the road could the view model editor get passed a tag, like componentSelector:raw="my-component"
And then the viewmodel editor would just pick that component's viewmodel?
That would make it super easy to embed in a demo
Kevin Phillips
@phillipskevin
yeah, that would be tough
well, we could create a component that wraps the current one and does that
but for it to work in devtools it can only take in serialized data
Kevin Phillips
@phillipskevin
same-comp-fix.gif
@roemhildtg here's the fix for that issue... I'm going to put the index of that element in the tagName
and reset the data when the tagName changes
Viktor Busko
@Lighttree
Guys is there big difference between such getters in VM ?
get someProp() {
        return 'something';
},

// VS

someProp: {
    get() {
         return 'something';
    }
}
Maybe some preferences when to use
kostya.aderiho
@kaderiho

Hi guys, is there any way to save DefineList data on the server using PUT request?

For instance:

const Todo = DefineMap.extend({ ... some properties ... });

Todo.List = DefineList.extend({ "#": Todo });

let TodosList = new Todo.List([ ...several items there... ]);

// send PUT request here with TodoList inside of the body

Thank you in advance

Matthew Phillips
@matthewp
are you using can-rest-model?