bevyengine / bevyengine/bevy

expose parse & parse_some from bevy_remote crate

Open
#17,732 1 comment 1 reaction 0 assignees View on GitHub
A-Dev-Tools C-Usability D-Straightforward S-Ready-For-Implementation X-Uncontroversial
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 16h
Merged PRs (30d)
171

Description

## What problem does this solve or what need does it fill?

When writing custom methods with bevy_remote you need to parse the params. The builtin_methods for bevy_remote have the helpers "parse" and "parse_some" which solve this issue. I believe they should be exposed in some way.

## What solution would you like?

make parse & parse_some pub. Though they are in mod builtin_methods within bevy_remote so maybe they should be moved for a better public api.

## What alternative(s) have you considered?

don't make them public

## Additional context

When implementing my custom methods i copy pasted parse and parse_some into my code as they did exactly what I wanted.

Contributor guide

Open the contributing guide

Research direction

Start by locating the `parse` and `parse_some` helpers in the `bevy_remote` crate's `builtin_methods` module. Read how the built-in methods use them and inspect nearby public API conventions before deciding how they should be exposed. Done means custom methods can use these helpers without copying their implementations, with relevant tests passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.