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

Allow per-field overrides of field values with placeholders #273

Closed
wants to merge 1 commit into from

Conversation

patcon
Copy link

@patcon patcon commented Dec 21, 2020

Hi! Looking for feedback of whether you'd ever accept something like this. If so, I'd be happy to spiff this up with proper docs within this PR.

Use-case is that I want to add guardrails to ensure that some PII (personally identifiable information) from airtable will not get written to a static government website.

Alternative approaches considered:

  • somehow hook into schema generation of gatsby. doesn't seem possible (no hooks to modify third party source plugin schemas)
  • extracting PII into a separate table. hurts UX of managing airtable, and hard to ask of nontechnical users, who are confused why information is now spread across a bunch of new tables.

Thanks for considering!

@patcon patcon changed the title Allow per-field overrides of values Allow per-field overrides of field values with placeholder values Dec 21, 2020
@patcon patcon changed the title Allow per-field overrides of field values with placeholder values Allow per-field overrides of field values with placeholders Dec 21, 2020
@jbolda
Copy link
Owner

jbolda commented Jun 18, 2021

Per #272, it seems that the best fit is proceeding with something as in the vein of #326. Thanks again for looking into this @patcon!

@jbolda jbolda closed this Jun 18, 2021
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.

2 participants