github-starred/meteor-api

Fork 0

mirror of https://github.com/awatson1978/meteor-api.git synced 2026-05-15 22:02:11 -06:00

[GH-ISSUE #74] onRendered helper #60

New issue

Open

opened 2026-05-05 15:00:37 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 15:00:37 -06:00

Owner

Originally created by @0o-de-lally on GitHub (Sep 27, 2015).
Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/74

Thanks for this Abigail !

Perhaps the Meteor syntax has changed since this package was originally written. Currently the autocomplete writes:

Template.name.onRendered = function(){}

When the up-to-date (Sept 2015) syntax should be:

Template.name.onRendered( function() { } )

http://docs.meteor.com/#/full/template_onRendered

Originally created by @0o-de-lally on GitHub (Sep 27, 2015). Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/74 Thanks for this Abigail ! Perhaps the Meteor syntax has changed since this package was originally written. Currently the autocomplete writes: ``` Template.name.onRendered = function(){} ``` When the up-to-date (Sept 2015) syntax should be: ``` Template.name.onRendered( function() { } ) ``` http://docs.meteor.com/#/full/template_onRendered

gitea-mirror commented

2026-05-05 15:00:41 -06:00

Author

Owner

@madhan5000 commented on GitHub (Sep 28, 2015):

I believe the master branch has the new syntax and current tag V2.20.0 that atom editor pulls in is out dated. @awatson1978 Thanks for packaging this ! Could you also create a tag for the latest code in master branch?

@madhan5000 commented on GitHub (Sep 28, 2015): I believe the master branch has the new syntax and current tag V2.20.0 that atom editor pulls in is out dated. @awatson1978 Thanks for packaging this ! Could you also create a tag for the latest code in master branch?

gitea-mirror commented

2026-05-05 15:00:44 -06:00

Author

Owner

@derwaldgeist commented on GitHub (Nov 11, 2015):

I would also like to see this package updated to the latest syntax.

I'm also heaving problems with the implementations of the highlights for special words. For instance, I am using FlowRouter instead of IronRouter, and the package will always only highlight the "Router" part in FlowRouter, which looks quite ugly. Same goes for things like SupportSession.get(), where the Session.get is highlighted. Obviously, the highlighter grammar does not take care of selecting whole words only.

This package needs some love :-)

@derwaldgeist commented on GitHub (Nov 11, 2015): +1 I would also like to see this package updated to the latest syntax. I'm also heaving problems with the implementations of the highlights for special words. For instance, I am using FlowRouter instead of IronRouter, and the package will always only highlight the "Router" part in FlowRouter, which looks quite ugly. Same goes for things like SupportSession.get(), where the Session.get is highlighted. Obviously, the highlighter grammar does not take care of selecting whole words only. This package needs some love :-)

gitea-mirror commented

2026-05-05 15:00:46 -06:00

Author

Owner

@awatson1978 commented on GitHub (Nov 12, 2015):

Yeah.... so, the folks who develop GitHub and Atom are very clever in general; but whoever implemented the Atom package management kinda screwed things up. The publication command tries to increment and publish; and gets out of sync with the github tags. It's super annoying. Long story short...I've actually had a fix for this for a couple of months, and have tried publishing it a couple of times now, with no success. Super frustrating.

I'll give it another look today. In general, I'm open to accepting pull-requests on any regexes or snippets in this package (provided they don't blatantly deprecate existing functionality; I'd support Router regex updates that include FlowRouter functionality; but not ones that remove IronRouter functionality).

Given the mechanics of Atom's package manager, however; this package is unlikely to get updated more frequently than a seasonal basis.

That being said, it would be nice to get the publication functionality working again.

@awatson1978 commented on GitHub (Nov 12, 2015): Yeah.... so, the folks who develop GitHub and Atom are very clever in general; but whoever implemented the Atom package management kinda screwed things up. The publication command tries to increment and publish; and gets out of sync with the github tags. It's super annoying. Long story short...I've actually had a fix for this for a couple of months, and have tried publishing it a couple of times now, with no success. Super frustrating. I'll give it another look today. In general, I'm open to accepting pull-requests on any regexes or snippets in this package (provided they don't blatantly deprecate existing functionality; I'd support Router regex updates that include FlowRouter functionality; but not ones that remove IronRouter functionality). Given the mechanics of Atom's package manager, however; this package is unlikely to get updated more frequently than a seasonal basis. That being said, it would be nice to get the publication functionality working again.

gitea-mirror commented

2026-05-05 15:00:47 -06:00

Author

Owner

@mapl commented on GitHub (Jan 3, 2016):

any new activities on this?

@mapl commented on GitHub (Jan 3, 2016): any new activities on this?

gitea-mirror commented

2026-05-05 15:00:49 -06:00

Author

Owner

@artiescie commented on GitHub (Jan 25, 2016):

One quick and dirty favor - to the incoming stream of meteor users - in case of time shortage -

maybe the atom.io package readme page could add something. Like an NB: get the latest fixes directly from github repo, after you install the atom package.

@artiescie commented on GitHub (Jan 25, 2016): One quick and dirty favor - to the incoming stream of meteor users - in case of time shortage - maybe the atom.io package readme page could add something. Like an NB: get the latest fixes directly from github repo, after you install the atom package.

gitea-mirror commented

2026-05-05 15:00:50 -06:00

Author

Owner

@onedr0p commented on GitHub (Feb 14, 2016):

+1 please update

@onedr0p commented on GitHub (Feb 14, 2016): +1 please update

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/meteor-api#60

No description provided.

Rows
Columns