npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

folder-profile

v0.1.5

Published

A simple sfdx script to streamline the process of profile creation making use of folder structure, CSV and JSON files.

Downloads

44

Readme

folder-profile

Version CircleCI Appveyor CI Codecov Greenkeeper Known Vulnerabilities Downloads/week License

Providing an easier way to manage profile changes through source control

A simple sfdx script to streamline the process of profile creation making use of folder structure, CSV and JSON files.

  • The script takes a source folder with named subfolders.
  • These subfolders will be the the names of the created Profiles.
  • CSV names provide the attribute type name + CSV data provides values.
  • JSON is used for single attribute tags. i.e 'custom'
Profiles [SOURCE]
|---Admin
|   |   fieldPermission.csv
|   |   objectPermission.csv
|---Sales User
|   |   fieldPermission.csv
|   |   objectPermission.csv
|   |   layoutAssignment.csv
|---Marketing User
|   |   fieldPermission.csv
|   |   objectPermission.csv
|   |   otherAttributes.json

Transforms to

ProfilesOutput [TARGET]
|   Admin.profile-meta.xml
|   Sales User.profile-meta.xml
|   Marketing User.profile-meta.xml

Warning

  • Currently SOURCE and TARGET should both be absolute paths due to the early nature of this project.
$ sfdx plugins:install folder-profile
$ sfdx folder:profile -s [SOURCE] -t [TARGET]
running command...
$ sfdx (-v|--version|version)
folder-profile/0.1.3 win32-x64 node-v14.17.4
$ sfdx --help [COMMAND]
USAGE
  $ sfdx COMMAND
...

sfdx folder:profile -s <string> -t <string> [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

Convert Folder Structure to XML

Convert Folder Structure to XML

USAGE
  $ sfdx folder:profile -s <string> -t <string> [--json] [--loglevel 
  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

OPTIONS
  -s, --source=source                                                               (required) Source of Profile
                                                                                    Attributes

  -t, --target=target                                                               (required) Target Folder for
                                                                                    Generated Profiles

  --json                                                                            format output as json

  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
                                                                                    this command invocation

See code: lib/commands/folder/profile.js