menu
Channels
Team
Posts
Chat
Members
Info

April 4, 2019 at 3:18am
Hi Felipe, Just wanted to provide some feedback. Everything works well and the latest updates are really nice. One item I noticed is when creating enumerators there is no validation on setting enumerator field names. However after scaffolding and trying to deploy back end you get an error stating graphql expected a name and got "o" or other variants of this message. I removed all spaces and special characters from my enumerator field names and this resolved the issue.
  • reply
  • like
I might have missed it, however is there a way to generate multi-select enumerators? Similar to the IAM role selection. Thanks.
  • reply
  • like

April 7, 2019 at 1:22pm
Hello Felipe, first of all, congrats for the amazing product...look, i'm facing an issue with graphql connection. I followed all the steps to deploy however, then trying to access my application I get connection refused error:
  • reply
  • like
  • reply
  • like
  • reply
  • like
Hi Felipe, Just wanted to provide some feedback. Everything works well and the latest updates are really nice. One item I noticed is when creating enumerators there is no validation on setting enumerator field names. However after scaffolding and trying to deploy back end you get an error stating graphql expected a name and got "o" or other variants of this message. I removed all spaces and special characters from my enumerator field names and this resolved the issue.
Hi Toufic, thanks for the feedback! I've added the validation to the enumerators.
  • reply
  • like
I might have missed it, however is there a way to generate multi-select enumerators? Similar to the IAM role selection. Thanks.
There is no multi-select enumerators yet.. But I'm planning to add it in the future..
  • reply
  • like
Hello Felipe, first of all, congrats for the amazing product...look, i'm facing an issue with graphql connection. I followed all the steps to deploy however, then trying to access my application I get connection refused error:
Hi Bruno, Thanks! Is your Firebase project set as "Blaze: Pay as you go"? Also, is the database at the same project as the Firebase? If not you'll have to grant access from one project to the other.. If none of those is your case, try to use the Public IP instead to see if it works, please..
  • reply
  • like
hi felipe, yet..the firebase plan is pay as you go....about the project be the same....don't know to be honest..i followed the step by step ... how do I ensure this?
  • reply
  • like
Now that I've paid attention to the error log I saw that they seems to be the same..
  • reply
  • like
Can you send me a print screen of the file 'backend/config/development.js'? Please, don't forget to remove the password from the file.. hehe
  • reply
  • like
Felipe, problem solved...the projects were different. Maybe it worth to mention this in your step by step. Make sure the projects are the same between FireBase and Google Cloud. Thanks for the quick support!!!
  • reply
  • like

April 8, 2019 at 2:13am
I can't seem to login or purchase the https://angular-firebase.com/buy product./ Can anyone help and email me at [email protected] :)
  • reply
  • like
Hi Gary, sorry about that.. Please access from https://scaffoldhub.io, it will work
  • reply
  • like
I'll have to fix it so the https://angular-firebase redirects to https://scaffoldhub.io instead of using it as the domain..
  • reply
  • like

April 16, 2019 at 12:49am
Hi there, , i'm having problems with i18n: ```C:\node\source\frontend\node_modules\eslint\lib\rules\no-useless-catch.js:1 (function (exports, require, module, filename, dirname) {
SyntaxError: Invalid or unexpected token at Array.forEach (<anonymous>) ```. I'm missing something that i'm not seeing ? could you help on that please? thanks.
  • reply
  • like
Hi Rafael, can you send me the entire error? (Can be a screenshot)
  • reply
  • like
Which scaffold is it?
  • reply
  • like

July 7, 2019 at 12:53am
Felipehelp me sir....i followed you from youtube to github now here
  • reply
  • like
its impossible to signup in your webapp soo i havent donloaded the repo
  • reply
  • like
kindly send me angular and that pets repo...i want to learn
  • reply
  • like

November 19, 2019 at 9:18pm
Hey Felipe, I cant seem to get the app to run on localhost. Something perhaps is wrong with the router? no matter what I try the server responds with "cannot get /" when I try to access localhost:8080, any ideas?
  • reply
  • like
its worth mentioning, everything works fine on the development server.
  • reply
  • like

November 20, 2019 at 4:22pm
Hey Felipe, I cant seem to get the app to run on localhost. Something perhaps is wrong with the router? no matter what I try the server responds with "cannot get /" when I try to access localhost:8080, any ideas?
Hi Colin, that's the port for the server. If you are using Angular, the port is 4200, React 3000 and Vue 8081 :) Sorry for the late reply
  • reply
  • like

January 17, 2020 at 5:16pm
When I try "npm run start" on the frontend, I occasionally get the message "Failed to compile Module not found: Can't resolve 'App'". I checked the jsconfig.json file and it does indeed have "baseUrl": "./src". It looks like its set up to resolve the path, but isn't. Has anyone else encountered this issue and found the cause/resolution?
  • reply
  • like