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

[Feature] Alias Custom Fields #20

Open
2 of 4 tasks
rrivera-kh opened this issue May 24, 2023 · 1 comment
Open
2 of 4 tasks

[Feature] Alias Custom Fields #20

rrivera-kh opened this issue May 24, 2023 · 1 comment
Labels
good first issue Good for newcomers type:enhancement New functionality or enhancement update_type:feature Primary focus is to add new functionality

Comments

@rrivera-kh
Copy link

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

For custom fields coming from the Application, Candidate, or Job tables, would like the ability to alias those columns. For example, some of the columns coming through are not inteligible.

Examples:

  • CUSTOM_NON_COMPETE_CANDIDATE_1663102674_4122803 => candidate_has_non_compete

Describe alternatives you've considered

No response

Are you interested in contributing this feature?

  • Yes.
  • Yes, but I will need assistance and will schedule time during your office hours for guidance.
  • No.

Anything else?

No response

@fivetran-joemarkiewicz
Copy link
Contributor

Hi @rrivera-kh thanks for opening this feature request!

I agree with you that including the ability to alias these custom fields would be a benefit to the package output. We actually have applied a similar update to a few of our other packages. See the below PRs for a similar enhancement made to the Salesforce dbt package.

In these PRs we take advantage of a series of macros within our fivetran_utils package that allow for more functionality and flexibility of the passthrough columns. Similar updates can be made to the Greenhouse package to address your feature request. I understand you are not interested in opening a PR, but I will mark this as a good first issue in case others want to contribute. Similarly, I will add this to our backlog and will let you know once we are able to address this in an upcoming sprint.

Thanks!

@fivetran-joemarkiewicz fivetran-joemarkiewicz added good first issue Good for newcomers type:enhancement New functionality or enhancement update_type:feature Primary focus is to add new functionality labels May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers type:enhancement New functionality or enhancement update_type:feature Primary focus is to add new functionality
Projects
None yet
Development

No branches or pull requests

2 participants