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: move object functions using JSON paths to a new /object/path/ folder #66

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

aleclarson
Copy link
Member

Tip

The owner of this PR can publish a preview release by commenting /publish in this PR. Afterwards, anyone can try it out by running pnpm add radashi@pr<PR_NUMBER>.

Summary

The idea is to separate the object functions that work with JSON paths, since they're kind of in a category of their own. By separating them, it'll be easier to see the holes in this area of the API.

For any code change,

  • Related documentation has been updated, if needed
  • Related tests have been added or updated, if needed
  • Related benchmarks have been added or updated, if needed

Does this PR introduce a breaking change?

No

@aleclarson aleclarson force-pushed the refactor/move-path-related-functions branch from da50efc to b9abd7e Compare July 3, 2024 17:40
@aleclarson
Copy link
Member Author

aleclarson commented Jul 3, 2024

Hmm, on 2nd thought, maybe "deep" is a better name for this group 🤔

edit: Going with ./object/path/

@aleclarson aleclarson added the stage 0: proposed A proposal for a change that is offered for community and team evaluation. label Jul 7, 2024
@aleclarson aleclarson force-pushed the refactor/move-path-related-functions branch from b9abd7e to 44f2e72 Compare July 8, 2024 00:52
@aleclarson aleclarson changed the title refactor: move object functions using JSON paths to a new "path" folder refactor: move object functions using JSON paths to a new /object/path/ folder Jul 8, 2024
@aleclarson aleclarson removed the stage 0: proposed A proposal for a change that is offered for community and team evaluation. label Jul 9, 2024
@aleclarson aleclarson force-pushed the main branch 2 times, most recently from 2154f96 to 6a4b4f6 Compare July 12, 2024 00:23
export * from './object/shake.ts'
export * from './object/upperize.ts'

export * from './path/construct.ts'
export * from './path/crush.ts'
export * from './path/get.ts'
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
export * from './path/get.ts'
export * from './object/path/construct.ts'
export * from './object/path/crush.ts'
export * from './object/path/get.ts'
export * from './object/path/keys.ts'
export * from './object/path/set.ts

@aleclarson aleclarson added the priority: low Delayed action on this is acceptable. label Sep 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low Delayed action on this is acceptable.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants