Sophie Dankel

## Description Closes https://github.com/FuelLabs/sway/issues/6018 Makes trait & inherent implementations show up for enums now:  And makes the sidebar include links to the impls:  ## Checklist - [ ]...

Example: ```sway pub enum TestEnum { TestVariant: (), } impl TestEnum { pub fn test_fn() {} } impl Eq for TestEnum { fn eq(self, other: Self) -> bool { true...

## Description This warning is mostly unnecessary. For fuelup users, it's expected that they might install some forc plugins outside of fuelup (with rust, nix, npm, etc.). For pure nix...

Add a CI step to check significant package output changes resulting from changes to `patches.nix`

1

@mitchmindtree mentioned that `nix flake show` can tell us which packages would be changed by `refresh-manifest.sh`. We could add this to PRs to show this output to help us catch...

The fuel-indexer is deprecated and we should remove it from the documentation. Should we also remove old manifest files for it?

Create a github action that uses `fuel.nix` to install forc

2

This would give us an idea of whether `fuel.nix` could be a viable replacement for `fuelup` in CI, in terms of latency to install forc.

package-lock.json version not updated correctly

6

Newer versions of npm require updating package-lock.json in two places, like this: ```diff --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "my-pkg", - "version": "0.3.1", + "version": "0.3.2",...

This PR disables it: https://github.com/FuelLabs/sway/pull/6181 The issue is that we don't have a custom LSP client for nvim, so we don't have a way to support features that aren't built...

Here is an example of what it looks like for a rust file:  Here is an example of what it looks like for a sway file currently:  This...

Related: https://github.com/FuelLabs/sway/pull/6032