Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add schemas for registry customization #84

Merged
merged 3 commits into from
Apr 1, 2024

Conversation

WillieRuemmele
Copy link
Member

What does this PR do?

adds custom registry schema information

What issues does this PR fix or reference?

@W-14609009@

Functionality Before

red lines when using registryCustomizations or registryPresets

Functionality After

full type support

transformer?:
| "decomposed"
| "staticResource"
| "nonDecomposed"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'd like to NOT expose the stuff that CustomLabels was using. I don't want more people creating dependencies on those behaviors since they've been so bad.

| "nonDecomposed"
| "standard";
decomposition?: "topLevel" | "folderPerType";
recomposition?: "startEmpty";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
recomposition?: "startEmpty";

transformer?:
| "decomposed"
| "staticResource"
| "nonDecomposed"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| "nonDecomposed"

| "mixedContent"
| "matchingContentFile"
| "decomposed"
| "digitalExperience"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| "digitalExperience"

and maybe not let people use DEB's weird stuff either.

Comment on lines 30 to 37
/**
* Whether or not components are stored in folders.
*
* __Examples:__ Reports, Dashboards, Documents, EmailTemplates
*
* @deprecated use `folderType` to get the related folder type, if one exists
*/
inFolder?: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/**
* Whether or not components are stored in folders.
*
* __Examples:__ Reports, Dashboards, Documents, EmailTemplates
*
* @deprecated use `folderType` to get the related folder type, if one exists
*/
inFolder?: boolean;

because it's deprecated

Comment on lines 46 to 53
/**
* MetaFile suffix
*
* An override to the default "-meta.xml" suffix.
*
* __Examples:__ "_meta.json" for DigitalExperience.
*/
metaFileSuffix?: string;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/**
* MetaFile suffix
*
* An override to the default "-meta.xml" suffix.
*
* __Examples:__ "_meta.json" for DigitalExperience.
*/
metaFileSuffix?: string;

another thing I'd like to avoid exposing

Comment on lines 71 to 74
/**
* If the parent name should be ignored when constructing the type's fullName
*/
ignoreParentName?: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/**
* If the parent name should be ignored when constructing the type's fullName
*/
ignoreParentName?: boolean;

hide, also only currently for customLabels/nonDecomposed

Comment on lines 79 to 83
/**
* When converting deploying source, this will update the suffix in the output or temporary directory (metadata format)
* Use this, along with additional suffix keys in the registry, to support incorrect suffixes from existing code
*/
legacySuffix?: string;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's keep that hidden unless someone needs it. This was really just for things toolbelt had wrong.

Suggested change
/**
* When converting deploying source, this will update the suffix in the output or temporary directory (metadata format)
* Use this, along with additional suffix keys in the registry, to support incorrect suffixes from existing code
*/
legacySuffix?: string;

},
"registryPresets": {
"title": "Custom predefined presets for decomposing metadata types",
"description": "filenames from https://github.com/forcedotcom/source-deploy-retrieve/tree/main/src/registry/presets ",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

@gbockus-sf gbockus-sf merged commit 542b61d into main Apr 1, 2024
11 checks passed
@gbockus-sf gbockus-sf deleted the wr/addRegistryCustomization branch April 1, 2024 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants