Skip to content

Conversation

@wolf99
Copy link
Contributor

@wolf99 wolf99 commented Apr 17, 2022

Testing what schemata can do for #1972

@wolf99 wolf99 changed the title Start JSON schema for track config.json JSON schema for track config.json Apr 17, 2022
@wolf99 wolf99 force-pushed the json-schema branch 3 times, most recently from df742ad to ab6b105 Compare April 18, 2022 21:09
@IsaacG
Copy link
Member

IsaacG commented Jan 1, 2023

@wolf99 Are you still working on this?

@wolf99
Copy link
Contributor Author

wolf99 commented Jan 1, 2023

Hi @IsaacG ,
I haven't had time to look at this in quite some time. I don't think I will have time to prioritize it in the near future.

@IsaacG
Copy link
Member

IsaacG commented Jan 1, 2023

@wolf99 Would it make sense to close out this PR until you have time to return to it?

@wolf99
Copy link
Contributor Author

wolf99 commented Jan 1, 2023

Hmm, is there any issue for it to remain open?

Usually closed PRs indicate either the work is agreed to not be needed or that is completed.
With the PR open anyone else can easily find it and continue the work if they'd like to.

@IsaacG
Copy link
Member

IsaacG commented Jan 2, 2023

Nope. I don't think there's any issue. If there's some expectation that something will happen with it. If it's unlikely to be picked up, then I don't think there's value in keeping it around, though. PRs could always be reopened if someone wants to work on them. Issues are usually how work-to-be-done is tracked.

Disclaimer: I'm no more a repo owner/maintainer/decider than anyone else here, including you :) Just my thoughts and my desires to tidy things up.

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