meteor
Here are 1,509 public repositories matching this topic...
We wanted to include the email address into our user search and found the option in the UI Fields to Consider in Search, but it took a while to find the correct entry. The only hint on how to reference the email was in a comment on another issue. Since the right way to refer to the email address is entering `emails.a
Wiki platforms page
I was looking into creating a better install section for Cloudron at https://github.com/wekan/wekan/wiki/Platforms . However, that page is a bit of a mess. Ideally, I would like to make a big list of all providers and each provider page can provide more information. Is this something that you would like to see as well? If so, I can help in editing the page but I am not sure how I should edit a git
Pluralize has unexpected results, it can't be used safely in code. It is only relevant for UI features.
Example: latin words, "schema" => "schemata", "datum => data", plural word are kept plural etc.
Adding an "s" blindly is more efficient though semantically incorrect sometimes. Better, allowing user to provide it's own names for resolver.
Version: `0.10.0`
OS & Version: linux
Node version: `geth 1.8.2-stable-b8b9f7f4`
It seems that in "Latest transactions" in Ethereum Wallet there are listed pending transactions from all networks (the real network and several test networks) without displaying which network this transaction is of.
So either show it noticeably or l
AMP
Hi,
I started a new AMP project, and as we do not need to reinvent the wheel, I had reduced the original mui.css version to which I had added some lines that I had injected in the "amp-custom" with a size of 35kb (the limit imposed by google is 50kb)
As proposed here : ampproject/amphtml#2851, I think we should build a mui.css lightweight package for the AMP community a
-
Updated
Jul 15, 2020 - JavaScript
-
Updated
May 8, 2020 - Dockerfile
-
Updated
Jun 21, 2020
Since I discovered stopAppDuringPrepareBundle: false I've been trying to remember to create a swap file whenever I spin up a new server. I've just realised I could use a hook for this.
Here's what I've come up with:
hooks: {
'post.setup': {
// create swap file so can safely use stopAppDuringPrepareBundle: false
remoteComman
If you just want to replace one field (e.g. replace the ListField with a custom one for all schemas), you need to reimplement the whole AutoField.
It would probably easier, if you could pass a getFieldComponent to a AutoForm, which would hook into here: https://github.com/vazco/uniforms/blob/master/packages/uniforms-material/src/AutoField.tsx#L24 and would take props and could return a Comp
Update docs
Update docs and wikis.
- Minimize amount of data presented at front page (README.md);
- Simplify examples presented at front page (README.md);
- Split wikis (docs) by functionality (a.k.a. API), not tasks (Howtos);
- Differentiate feature, functionality (API), and tasks (Howtos) docs;
Articles:
- Security
- Publish / Subscribe
- Using files without references and pub
-
Updated
Jun 13, 2020 - JavaScript
-
Updated
Jan 16, 2018 - JavaScript
-
Updated
Jul 10, 2019 - JavaScript
-
Updated
Jun 18, 2020 - Python
I'm fairly new to React and npm imports so not sure, but I was reading the react-bootstrap documentation, and saw this:
If you install React-Bootstrap using npm, you can import individual components from react-bootstrap/lib rather than the entire library. Doing so pulls in only the specific components that you use, which can significan
-
Updated
Jul 14, 2018 - JavaScript
I have noticed that when calling Collection.update with { multi: true } set as an option, the collection.before.update hook is called once per document, however, the modifier parameter is the same object that was used in the previous iteration.
This is dangerous if we are setting modifier values based solely on the individual properties of the document we are currently iterating over.
I had assumed that observeSource would make the GroundDB collection match the collection it was observing. But that doesn't appear to be the case. I think I need to call keep first to make the collections match and then observeSource to keep it up to date, otherwise old records might be lying around in the GroundDB collection.
I can understand the need for both cases. Should there be a dif
Developing on the default config with localhost:3000 is fine.
However when I tried to test the local dev version from a device in the local network, say 192.169.110.1:3000, one of the client requests is still pointing to localhost:3000. Specifically, it's http://localhost:3000/__meteor__/dynamic-import/fetch, which makes the app unresponsive/unable to login from devices other than localhost.
That would be pretty useful to be able to access the parent cursor from a document returned to the helpers method, and in particuler its previous / next docs in the cursor.
That would make things like grouping elements by an attribute very clean. Examples: for a chat app where you would need to insert a separator for each day, a contacts list where you need to group people by the first letter of
https://circleci.com/gh/meteor/blaze/274
FATAL Something's wrong. Maybe you can find the solution here: http://hexo.io/docs/troubleshooting.html
Template render error: (unknown path) [Line 100, Column 2]
unknown block tag: enddtdd
at Object.exports.prettifyError (/home/ubuntu/blaze/site/node_modules/hexo/node_modules/nunjucks/src/lib.js:34:15)
at Obj.extend.render (/home/ubun
DTube Avalon uses leaders which are the equivalent to Steem witnesses. They are listed on their own section. Those leaders should add their own IP -or hostname- so other nodes are able to connect to them. When hover the mouse over a leader which has provided an URL, the UI shows it as a tooltip.
It is currently not checking for the IP address to be a valid one. Web page will show that leader as
I think there's a typo in one of the examples on this page:
http://matteodem.github.io/meteor-easy-search/docs/recipes/
The first example for a custom selector is this:
import { Index, MongoDBEngine } from 'meteor/easy:search'
// Client and Server
const index = new Index({
...
engine: new MongoDBEngine({
selector(searchDefinition, options, aggregation) {
// retr
Hey,
My team and I decided to create a documentation for the components created inside our app. I'm searching for some way to easily do BlazeComponent.listComponents(), and it would be awesome to have access to variables inside the component and list them.
Any ideas on how to do this?
-
Updated
Dec 28, 2019 - JavaScript
Improve this page
Add a description, image, and links to the meteor topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the meteor topic, visit your repo's landing page and select "manage topics."
Some of the issues below are already mentioned in other tickets, but I have the feeling that a proper generic issue is due to give it visibility, as for now the current package is unusable for many users.
I understand that meteor needs to control some compilation option