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

refactor: remove local fork of yamlicious #345

Merged
merged 1 commit into from
Jul 5, 2022

Conversation

blaugold
Copy link
Collaborator

@blaugold blaugold commented Jul 5, 2022

YAML is a superset of JSON and what we need to write as YAML it is never visible to users.
We can just write JSON instead and get rid of this dependency.

Description

Type of Change

  • feat -- New feature (non-breaking change which adds functionality)
  • 🛠️ fix -- Bug fix (non-breaking change which fixes an issue)
  • ! -- Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 refactor -- Code refactor
  • ci -- Build configuration change
  • 📝 docs -- Documentation
  • 🗑️ chore -- Chore

YAML is a superset of JSON and what we need to write as YAML it is never visible to users.
We can just write JSON instead and get rid of this dependency.
Copy link
Member

@Salakar Salakar left a comment

Choose a reason for hiding this comment

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

LGTM as long as Pub Get can handle it as JSON in the temp workspace we make then I see no issue

@blaugold
Copy link
Collaborator Author

blaugold commented Jul 5, 2022

We have tests covering bootstrapping with the temp workspace, and those all pass.

@blaugold blaugold merged commit 64a15b8 into main Jul 5, 2022
@blaugold blaugold deleted the refactor/remove-yamlicious-fork branch July 5, 2022 11:09
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