allensmith81
Boss
Joined 14 years ago
User Profile
User Widgets
Contributions
Re: Using user_context.read as a constraint on messages collection
So this user_context.read, which is returned when you make a call to the API, it doesn't have a value stored some where but is calculated on the fly? is that the problem? I am beginning to think a) wait for aurora and b) if I was going to do this I would be better to do it in and endpoint so the performance hit was on the server side.259Views0likes0CommentsRe: Requesting feedback on our Dev Lab!
I was actually wondering if any devs in the Khoros would would be interested in having a Khoros Development Office hours - maybe even community led. Essentially a monthly call for developers across Khoros customers to get together, discuss challenges they are facing - share hints, tips and maybe even do some 'public code' development to help better the community over all?448Views4likes1CommentRe: Requesting feedback on our Dev Lab!
BlakeH First of all thank you for hosting it, I would love to see more of them. I think for us, remembering we are already up to our ears in Aurora planning, I was hoping for something more level 400/500 in how to build for Aurora. I would love to have had a dev lab which had clear objectives i.e.: How to set up the SDK? Getting Postman Configured? Hints, tips, dos and don't for building effective custom components with Aurora Hackathon - Build your first Handlebars component Hackathon - Build your first react component React or Handlebars, that is the question Hackathon - Helpful utilities, code snippets Permissions Translation - Classic to Aurora - what's changed? Meet Big Pipe: The Firehose - What, why and how to handle big data Deep Dive - Breaking out of the community box (Integrations with pages and endpoints outside the community). Theming the Theme - Exploring how to setup multiple theme communities Aurora and AI These are just a quick brain dump of things I would love to see in future sessions. It wasn't that there was anything wrong with the devlab, I just felt it was to close to a roadmap / marketing call and not close enough to an engineering call, which is what I was hoping it would be. Loved meeting everyone though and the breakout sessions were especially productive.451Views6likes3CommentsRe: Aurora SDK install via NPM
MattV Thanks Matt - that makes allot of sense to me! I think I am just trying to make sure I give feedback here to help make watertight documentation. So maybe we should put a line in the 'Installing the SDK' documentation that says "You must make sure you are using an SDK version that is at least the same or lower than your community version" unless you plan to release a new SDK with each version? I also think we need to check the 'Node 16 and 17' are supported statement because 24.4 won't install on 17. Also since node is up to like what 22, will the Khoros SDK keep up with newer versions of node?415Views0likes0CommentsRe: Aurora SDK install via NPM
saikumarn Your right I am, because the installing the SDK documentation doesn't tell you thats where the file is 🙂 Indeed I would go so far to say it actually tells you to clone the git repo and then in this directory find the env.local file ! Clone your community's plugin repository from GitHub into a local directory (for example, ~/development/plugin/exampleco) Locate the file named .env.local in this directory. If you don't see it, note that the file may be hidden by default by your OS (Mac, Windows). I actually have no idea where the sdk files are, any ideas? If you can provide guidance that would be helpful but I think this should be in the documentation 🙂416Views0likes0CommentsAurora SDK install via NPM
LarryI Was excited to see the new SDK via NPM but I hit some problems I wanted to share with you. The documentation says you support NodeJS 16 and 17. With Node 17.9.1 installed you get errors when you try to install the sdk, specifically: sudo npm install khoros-aurora-sdk --no-fund npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/eslint-plugin@6.8.0', npm WARN EBADENGINE required: { node: '^16.0.0 || >=18.0.0' }, npm WARN EBADENGINE current: { node: 'v17.9.1', npm: '8.11.0' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/parser@6.8.0', npm WARN EBADENGINE required: { node: '^16.0.0 || >=18.0.0' }, npm WARN EBADENGINE current: { node: 'v17.9.1', npm: '8.11.0' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/scope-manager@6.8.0', npm WARN EBADENGINE required: { node: '^16.0.0 || >=18.0.0' }, npm WARN EBADENGINE current: { node: 'v17.9.1', npm: '8.11.0' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/type-utils@6.8.0', npm WARN EBADENGINE required: { node: '^16.0.0 || >=18.0.0' }, npm WARN EBADENGINE current: { node: 'v17.9.1', npm: '8.11.0' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/types@6.8.0', npm WARN EBADENGINE required: { node: '^16.0.0 || >=18.0.0' }, npm WARN EBADENGINE current: { node: 'v17.9.1', npm: '8.11.0' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/typescript-estree@6.8.0', npm WARN EBADENGINE required: { node: '^16.0.0 || >=18.0.0' }, npm WARN EBADENGINE current: { node: 'v17.9.1', npm: '8.11.0' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/utils@6.8.0', npm WARN EBADENGINE required: { node: '^16.0.0 || >=18.0.0' }, npm WARN EBADENGINE current: { node: 'v17.9.1', npm: '8.11.0' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/visitor-keys@6.8.0', npm WARN EBADENGINE required: { node: '^16.0.0 || >=18.0.0' }, npm WARN EBADENGINE current: { node: 'v17.9.1', npm: '8.11.0' } npm WARN EBADENGINE } I had to drop back down to 16.20.2 to be able to successfully install the aurora SDK. When I run npm list I now get: `-- khoros-aurora-sdk@24.5.0-rc.0 Ok so fixed but looks like node 17 isn't supported. Next problem, it tells me to clone the repo from git, which I do. It then tells me to find .env.local file and edit it in a text editor. I have checked that hidden files are visible in file explorer but there is no file called .env.local.. What am I missing? The only files in the cloned repo are: 1. a directory called res which contains sub-directories [components,props,quilts,texts,themes] 2. a file called README.md459Views1like10Comments