Provide a globally accessible place for data events / code (within a single organization) | Voters

Provide a globally accessible place for data events / code (within a single organization)

under review

Century IS2 (Owner)

This would allow any apps that fall under that organization to import in things like:
* Copies of external libraries
* Datasets / Objects (JSON / GeoJSON)
* Helper functions

May 21, 2019

Chris Schroeder

This is actually a great idea. our current work around is copying the codes to MS Teams and then the users or superusers go into copy and paste the codes they need when they are duplicating apps or want to use features another superuser built.

Katie Briggs

marked this post as

under review

Shawn Pickett

Joe Larson Dale Wilson - Just doing my annual pilgrimage. Any updates on this one? This is a real pain point for our group having to manage the same 400+ lines of code across 100+ apps. I know it is easier said than done, just trying to be the squeaky wheel. :)

Joe Larson

Merged in a post:

Text editor/file for Sourcing custom functions within apps

Walter Leo

In alot of our apps we use the same custom functions and each time we make a new app we need to write them over again. It would be nice to be able to have a place we can write these and then when the apps would start source them in. This would allow consistency between apps and ensure they are all working the same and reduce redundancy by not having to re write the same functions over and over

January 10, 2023

Dale Wilson

marked this post as

open

Shawn Pickett

Dale Wilson: Hey Dale, are there any updates on this feature request?

Shawn Pickett

Another potential benefit is that you could house code in a git repo and (if there is an API endpoint for this new feature 😉 ), you could deploy updates across multiple organizations.

Jeremy Palmer

I would find this very useful. It's hard to manage code when it's copied into multiple apps. Far better if I could build libraries that could be shared (e.g. to managed our QA/Review process).

Bryan McBride

marked this post as

under review

Thanks for the feedback! One way to handle this currently is to utilize Fulcrum's local storage to store your JS libs. You can fetch the script with a REQUEST call and save to storage for future use. See here for an example: https://gist.github.com/bmcbride/568bb31c073af412f35db3a558cc246a.

Making this easier is definitely something we are reviewing so thanks again for the great feedback!

Coleman McCormick

This is interesting! It’s something we’ve discussed the best approach for. We’re thinking now on how best to implement for maximum utility. Would definitely reduce the amount of repetition with embedding things inside of code per app (like turf.js, moment.js, and other libraries).

Joseph McCann

With this functionality, we could, for example, place turf.js into our org's repo, and the library would sync down to mobile devices once, rather than once-per-app, as is the case with ramming the library into a data event. I like it!

→