Call to undeclared geometry function/attribute in wasm crate
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rust, wasm
- Domain
- build-system
Research direction
Start at crates/processing_wasm/src/lib.rs around line 2285 and compare the geometry_attribute_dead binding with the declarations in crates/processing_render/src/geometry/attribute.rs around lines 220-231 and 293-308. Run the wasm crate build to reproduce the undeclared-call error; done means the binding matches an available geometry function or is otherwise corrected and the crate builds successfully.
Written by the indexing model from the issue text.
Description
Hey!
I was playing around with libprocessing today and couldn't build because of a undeclared call to geometry_attribute_dead in the wasm crate. From what i understand, there's no dead attribute in the geometry crate, but i'm no Rust or Bevy expert (yet! :D)
I got it to work by commenting the whole binding like so :
/*
#[wasm_bindgen(js_name = "geometryAttributeDead")]
pub fn js_geometry_attribute_dead() -> u64 {
geometry_attribute_dead().to_bits()
}
*/
- Dominant language
- Rust
- Stars
- 69
- Forks
- 14
- Avg merge
- 15d 22h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from processing/libprocessing
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
processing/libprocessing#229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
processing/libprocessing#201 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
processing/libprocessing#194 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
processing/libprocessing#146 · 1 comment ·
-
github-actions task
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
processing/libprocessing#103 ·
All issues in processing/libprocessing
Similar issues
-
todo:perf
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
ACP agents get no MCP servers when the thread is created before the project's first worktree loads Openstate:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zed-industries/zed#64611 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
objectionary/phie#154 ·