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/towards writer extension point #258

Merged

Conversation

blaggacao
Copy link
Contributor

@blaggacao blaggacao commented Mar 8, 2024


  • feat: return full results from result processing

Context

#253 prototypes a "writer" implementation.

It takes a version result and not only updates references but then also mutates the code base on the basis of the newly obtained references.

A Nix writer is certainly no good in-tree use case.

Hence, this PR tries to conceptualize a potential extension point for downstream packages which could implement writer implementations similarly as, today, nvfetcher_source provides source implementations.

@blaggacao blaggacao force-pushed the feat/towards-writer-extension-point branch 5 times, most recently from 6074cf5 to 87ed641 Compare March 13, 2024 21:53
@blaggacao blaggacao marked this pull request as ready for review March 13, 2024 21:53
Comment on lines 415 to 416
ret[r1.name] = r1.version
results.append(r1)
Copy link
Owner

Choose a reason for hiding this comment

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

What about returning data like this:

Suggested change
ret[r1.name] = r1.version
results.append(r1)
ret[r1.name] = r1

In this way we can avoid returning duplicate information in two ways.

@blaggacao blaggacao force-pushed the feat/towards-writer-extension-point branch 4 times, most recently from 1e42ca7 to 883cef6 Compare March 14, 2024 09:32
@blaggacao blaggacao force-pushed the feat/towards-writer-extension-point branch from 883cef6 to f29bdee Compare March 14, 2024 09:40
@lilydjwg lilydjwg merged commit f29bdee into lilydjwg:master Mar 14, 2024
21 of 22 checks passed
@lilydjwg
Copy link
Owner

I've also got rid of the Result & VersData types. Now rich results are recorded in verfiles.

@blaggacao blaggacao deleted the feat/towards-writer-extension-point branch March 14, 2024 10:42
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.

Issue on newver files when run with --entry
2 participants